running process?

crshep · Jan 3, 2015

I now see all these when I look at "process manager" in WHM anyone know what all this is? I have a few vps's running cpanel and this one vps is the only one showing all of this.

Code:

1 (Trace) (Kill) 	root 	0 	0.0 	0.0 	/sbin/init
2 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[kthreadd]
3 (Trace) (Kill) 	root 	- 	0.0 	0.0 	[migration/0]
4 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[ksoftirqd/0]
5 (Trace) (Kill) 	root 	- 	0.0 	0.0 	[migration/0]
6 (Trace) (Kill) 	root 	- 	0.0 	0.0 	[watchdog/0]
7 (Trace) (Kill) 	root 	- 	0.0 	0.0 	[migration/1]
8 (Trace) (Kill) 	root 	- 	0.0 	0.0 	[migration/1]
9 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[ksoftirqd/1]
10 (Trace) (Kill) 	root 	- 	0.0 	0.0 	[watchdog/1]
11 (Trace) (Kill) 	root 	- 	0.0 	0.0 	[migration/2]
12 (Trace) (Kill) 	root 	- 	0.0 	0.0 	[migration/2]
13 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[ksoftirqd/2]
14 (Trace) (Kill) 	root 	- 	0.0 	0.0 	[watchdog/2]
15 (Trace) (Kill) 	root 	- 	0.0 	0.0 	[migration/3]
16 (Trace) (Kill) 	root 	- 	0.0 	0.0 	[migration/3]
17 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[ksoftirqd/3]
18 (Trace) (Kill) 	root 	- 	0.0 	0.0 	[watchdog/3]
19 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[events/0]
20 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[events/1]
21 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[events/2]
22 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[events/3]
23 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[cgroup]
24 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[khelper]
25 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[netns]
26 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[async/mgr]
27 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[pm]
28 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[xenwatch]
29 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[xenbus]
30 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[sync_supers]
31 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[bdi-default]
32 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[kintegrityd/0]
33 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[kintegrityd/1]
34 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[kintegrityd/2]
35 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[kintegrityd/3]
36 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[kblockd/0]
37 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[kblockd/1]
38 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[kblockd/2]
39 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[kblockd/3]
40 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[kacpid]
41 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[kacpi_notify]
42 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[kacpi_hotplug]
43 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[ata_aux]
44 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[ata_sff/0]
45 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[ata_sff/1]
46 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[ata_sff/2]
47 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[ata_sff/3]
48 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[ksuspend_usbd]
49 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[khubd]
50 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[kseriod]
51 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[md/0]
52 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[md/1]
53 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[md/2]
54 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[md/3]
55 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[md_misc/0]
56 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[md_misc/1]
57 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[md_misc/2]
58 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[md_misc/3]
59 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[linkwatch]
60 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[khungtaskd]
61 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[kswapd0]
62 (Trace) (Kill) 	root 	5 	0.0 	0.0 	[ksmd]
63 (Trace) (Kill) 	root 	19 	0.0 	0.0 	[khugepaged]
64 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[aio/0]
65 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[aio/1]
66 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[aio/2]
67 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[aio/3]
68 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[crypto/0]
69 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[crypto/1]
70 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[crypto/2]
71 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[crypto/3]
76 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[kthrotld/0]
77 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[kthrotld/1]
78 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[kthrotld/2]
79 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[kthrotld/3]
81 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[kpsmoused]
82 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[usbhid_resumer]
112 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[kstriped]
198 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[scsi_eh_0]
199 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[scsi_eh_1]
299 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[jbd2/xvda2-8]
300 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[ext4-dio-unwrit]
386 (Trace) (Kill) 	root 	-4 	0.0 	0.0 	/sbin/udevd -d
650 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[flush-202:0]
680 (Trace) (Kill) 	root 	-2 	0.0 	0.0 	/sbin/udevd -d
703 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[jbd2/xvda1-8]
704 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[ext4-dio-unwrit]
866 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[kauditd]
898 (Trace) (Kill) 	root 	-20 	0.0 	0.0 	[loop0]
901 (Trace) (Kill) 	root 	0 	0.0 	0.0 	[kjournald]
1108 (Trace) (Kill) 	root 	-4 	0.0 	0.0 	auditd

Thanks

cPanelMichael · Jan 6, 2015

Re: running process ??

Hello

I don't see anything abnormal about the process list you provided. You will see a similar output if you run a command such as "ps aux" from the command line. What do you see on your other VPS machines?

Thank you.

crshep · Jan 6, 2015

Re: running process ??

I do not see any of those precess running on my other vps and on this one they just started a few days ago so I thought something maybe wrong since I am now getting emails like this

Notification Message: nameserver failed @ Sun Jan 4 11:55:20 2015. A restart was attempted automagically.

then the restarted one follows I get about 200+ emails every morning when I get up.

I look in my logs files and I see a ton of these

Jan 6 07:07:02 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:02 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:07 server1 kernel: __ratelimit: 3657 callbacks suppressed
Jan 6 07:07:07 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:07 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:07 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:07 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:07 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:07 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:07 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:07 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:07 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:07 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:12 server1 kernel: __ratelimit: 3440 callbacks suppressed
Jan 6 07:07:12 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:12 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:12 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:12 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:12 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:12 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:12 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:12 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:12 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:12 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:17 server1 kernel: __ratelimit: 3333 callbacks suppressed
Jan 6 07:07:17 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:17 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:17 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:17 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:17 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:17 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:17 server1 kernel: nf_conntrack: table full, dropping packet.
Jan 6 07:07:17 server1 kernel: nf_conntrack: table full, dropping packet.

so lost here

cPanelMichael · Jan 7, 2015

The issue with your service failing is unrelated. Feel free to open a support ticket using the link in my signature if you want us to take a closer look. You can post the ticket number here and we can update this thread with the outcome.

Thank you.

crshep · Jan 12, 2015

This has been taken care of now. But the original post has not all the process running on this one VPS what are they. They are not running on my other 2 VPS's

1 (Trace) (Kill) root 0 0.0 0.0 /sbin/init
2 (Trace) (Kill) root 0 0.0 0.0 [kthreadd]
3 (Trace) (Kill) root - 0.0 0.0 [migration/0]
4 (Trace) (Kill) root 0 0.0 0.0 [ksoftirqd/0]
5 (Trace) (Kill) root - 0.0 0.0 [migration/0]
6 (Trace) (Kill) root - 0.0 0.0 [watchdog/0]
7 (Trace) (Kill) root - 0.0 0.0 [migration/1]
8 (Trace) (Kill) root - 0.0 0.0 [migration/1]
9 (Trace) (Kill) root 0 0.0 0.0 [ksoftirqd/1]
10 (Trace) (Kill) root - 0.0 0.0 [watchdog/1]
11 (Trace) (Kill) root - 0.0 0.0 [migration/2]
12 (Trace) (Kill) root - 0.0 0.0 [migration/2]
13 (Trace) (Kill) root 0 0.0 0.0 [ksoftirqd/2]
14 (Trace) (Kill) root - 0.0 0.0 [watchdog/2]
15 (Trace) (Kill) root - 0.0 0.0 [migration/3]
16 (Trace) (Kill) root - 0.0 0.0 [migration/3]
17 (Trace) (Kill) root 0 0.0 0.0 [ksoftirqd/3]
18 (Trace) (Kill) root - 0.0 0.0 [watchdog/3]
19 (Trace) (Kill) root 0 0.0 0.0 [events/0]
20 (Trace) (Kill) root 0 0.0 0.0 [events/1]
21 (Trace) (Kill) root 0 0.0 0.0 [events/2]
22 (Trace) (Kill) root 0 0.0 0.0 [events/3]
23 (Trace) (Kill) root 0 0.0 0.0 [cgroup]
24 (Trace) (Kill) root 0 0.0 0.0 [khelper]
25 (Trace) (Kill) root 0 0.0 0.0 [netns]
26 (Trace) (Kill) root 0 0.0 0.0 [async/mgr]
27 (Trace) (Kill) root 0 0.0 0.0 [pm]
28 (Trace) (Kill) root 0 0.0 0.0 [xenwatch]
29 (Trace) (Kill) root 0 0.0 0.0 [xenbus]
30 (Trace) (Kill) root 0 0.0 0.0 [sync_supers]
31 (Trace) (Kill) root 0 0.0 0.0 [bdi-default]
32 (Trace) (Kill) root 0 0.0 0.0 [kintegrityd/0]
33 (Trace) (Kill) root 0 0.0 0.0 [kintegrityd/1]
34 (Trace) (Kill) root 0 0.0 0.0 [kintegrityd/2]
35 (Trace) (Kill) root 0 0.0 0.0 [kintegrityd/3]
36 (Trace) (Kill) root 0 0.0 0.0 [kblockd/0]
37 (Trace) (Kill) root 0 0.0 0.0 [kblockd/1]
38 (Trace) (Kill) root 0 0.0 0.0 [kblockd/2]
39 (Trace) (Kill) root 0 0.0 0.0 [kblockd/3]
40 (Trace) (Kill) root 0 0.0 0.0 [kacpid]
41 (Trace) (Kill) root 0 0.0 0.0 [kacpi_notify]
42 (Trace) (Kill) root 0 0.0 0.0 [kacpi_hotplug]
43 (Trace) (Kill) root 0 0.0 0.0 [ata_aux]
44 (Trace) (Kill) root 0 0.0 0.0 [ata_sff/0]
45 (Trace) (Kill) root 0 0.0 0.0 [ata_sff/1]
46 (Trace) (Kill) root 0 0.0 0.0 [ata_sff/2]
47 (Trace) (Kill) root 0 0.0 0.0 [ata_sff/3]
48 (Trace) (Kill) root 0 0.0 0.0 [ksuspend_usbd]
49 (Trace) (Kill) root 0 0.0 0.0 [khubd]
50 (Trace) (Kill) root 0 0.0 0.0 [kseriod]
51 (Trace) (Kill) root 0 0.0 0.0 [md/0]
52 (Trace) (Kill) root 0 0.0 0.0 [md/1]
53 (Trace) (Kill) root 0 0.0 0.0 [md/2]
54 (Trace) (Kill) root 0 0.0 0.0 [md/3]
55 (Trace) (Kill) root 0 0.0 0.0 [md_misc/0]
56 (Trace) (Kill) root 0 0.0 0.0 [md_misc/1]
57 (Trace) (Kill) root 0 0.0 0.0 [md_misc/2]
58 (Trace) (Kill) root 0 0.0 0.0 [md_misc/3]
59 (Trace) (Kill) root 0 0.0 0.0 [linkwatch]
60 (Trace) (Kill) root 0 0.0 0.0 [khungtaskd]
61 (Trace) (Kill) root 0 0.0 0.0 [kswapd0]
62 (Trace) (Kill) root 5 0.0 0.0 [ksmd]
63 (Trace) (Kill) root 19 0.0 0.0 [khugepaged]
64 (Trace) (Kill) root 0 0.0 0.0 [aio/0]
65 (Trace) (Kill) root 0 0.0 0.0 [aio/1]
66 (Trace) (Kill) root 0 0.0 0.0 [aio/2]
67 (Trace) (Kill) root 0 0.0 0.0 [aio/3]
68 (Trace) (Kill) root 0 0.0 0.0 [crypto/0]
69 (Trace) (Kill) root 0 0.0 0.0 [crypto/1]
70 (Trace) (Kill) root 0 0.0 0.0 [crypto/2]
71 (Trace) (Kill) root 0 0.0 0.0 [crypto/3]
76 (Trace) (Kill) root 0 0.0 0.0 [kthrotld/0]
77 (Trace) (Kill) root 0 0.0 0.0 [kthrotld/1]
78 (Trace) (Kill) root 0 0.0 0.0 [kthrotld/2]
79 (Trace) (Kill) root 0 0.0 0.0 [kthrotld/3]
81 (Trace) (Kill) root 0 0.0 0.0 [kpsmoused]
82 (Trace) (Kill) root 0 0.0 0.0 [usbhid_resumer]
112 (Trace) (Kill) root 0 0.0 0.0 [kstriped]
198 (Trace) (Kill) root 0 0.0 0.0 [scsi_eh_0]
199 (Trace) (Kill) root 0 0.0 0.0 [scsi_eh_1]
299 (Trace) (Kill) root 0 0.0 0.0 [jbd2/xvda2-8]
300 (Trace) (Kill) root 0 0.0 0.0 [ext4-dio-unwrit]
386 (Trace) (Kill) root -4 0.0 0.0 /sbin/udevd -d
650 (Trace) (Kill) root 0 0.0 0.0 [flush-202:0]
680 (Trace) (Kill) root -2 0.0 0.0 /sbin/udevd -d
703 (Trace) (Kill) root 0 0.0 0.0 [jbd2/xvda1-8]
704 (Trace) (Kill) root 0 0.0 0.0 [ext4-dio-unwrit]
866 (Trace) (Kill) root 0 0.0 0.0 [kauditd]
898 (Trace) (Kill) root -20 0.0 0.0 [loop0]
901 (Trace) (Kill) root 0 0.0 0.0 [kjournald]
1108 (Trace) (Kill) root -4 0.0 0.0 auditd

cPanelMichael · Jan 12, 2015

Those are normal system processes. You can run the "ps aux" command on another VPS and you should see similar processes. It's also possible that a different visualization software is in-use on your other servers that limits the processes that are visible to you. Check with your VPS provider to determine if that's the case.

Thank you.

bizzgang · Jun 1, 2015

Is Crypt Process is Infected or something because lastime it says Crypto is one of the very wellknown viruses......

cPanelMichael · Jun 2, 2015

bizzgang said:
Is Crypt Process is Infected or something because lastime it says Crypto is one of the very wellknown viruses......

Hello,

No, it's used for cryptographic services in the kernel.

Thank you.

Thread starter	Similar threads	Forum	Replies	Date
N	xm process running with high cpu	Server Management	1	May 16, 2023
	Detected processes that are running outdated binary executables.	Server Management	4	Aug 28, 2015
M	selecting background running processes	Server Management	5	Aug 20, 2014
M	Large no of processes are running	Server Management	1	Feb 28, 2013
T	Too many processes running	Server Management	1	Feb 12, 2013

Search

Search

running process?

crshep

Well-Known Member

cPanelMichael

Administrator

crshep

Well-Known Member

cPanelMichael

Administrator

crshep

Well-Known Member

cPanelMichael

Administrator

bizzgang

Registered

cPanelMichael

Administrator