iworx-web ¿ what is? eating cpu all time !!

iworx-db and iworx-web use a lot of cpu, specially iworx-db

Ths create super loads, all days in few of my boxes?
Some fix? some way to make run better?
Some way to optimize server for make load go down?
60% of the server load or more its created by this 2 process all time !!
And all and unique overloads i have are created by this !!

I apreciate any info. please !!

[quote=Dj-Grobe;9642]iworx-db and iworx-web use a lot of cpu, specially iworx-db

Ths create super loads, all days in few of my boxes?
Some fix? some way to make run better?
Some way to optimize server for make load go down?
60% of the server load or more its created by this 2 process all time !!
And all and unique overloads i have are created by this !!

I apreciate any info. please !![/quote]

Those two processes run InterWorx and you do NOT want to kill them obviously :wink:

That being said what are the system specs of your server?

  • 128 MB of memory
  • Pentium III 866 CPU
  • 512 MB of disk space (for InterWorx-CP alone)
Those are our MINIMUM system requirements -- thout it will run slowly on that.

Can you give us an example of the output of top when your server load is high?

I never had a problem with InterWorx even on my old server which only had 512 Ram and was 1.7 cele. And actually in one of the updates from a while back cut the CPU load in half on my cele, from like average of 10 to 5%.

top - 13:08:38 up 1 day, 21:59, 1 user, load average: 10.73, 11.33, 6.61
Tasks: 171 total, 4 running, 167 sleeping, 0 stopped, 0 zombie
Cpu(s): 56.0% us, 7.9% sy, 0.0% ni, 0.0% id, 35.4% wa, 0.7% hi, 0.0% si
Mem: 507816k total, 493724k used, 14092k free, 18624k buffers
Swap: 2096472k total, 231132k used, 1865340k free, 124824k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
11184 iworx 16 0 17040 3268 1392 S 21.6 0.6 0:10.72 iworx-db
11174 root 15 0 45500 36m 3000 D 10.6 7.4 0:05.38 php

PHP its bandwidth process form iworx.
So how optimize this?

This not happen all time, but lot of time per dy server go with laod to 20 and moreand then back.
What create this? webmail?

my cpu is 2402.06Mhz Intel® Celeron® CPU 2.40GHz (256 KB Cache) 512mb ram
I have another servers with same specs, and only tghis box have this trouble.

I have had this problem from time to time too…

Although not so much lately - now it’s Apache and/or MySQL that eats all my CPU. Restarting httpd, mysql and iworx (i made a script to do it at the same time) seems to help it.

[quote=Dj-Grobe;9657]top - 13:08:38 up 1 day, 21:59, 1 user, load average: 10.73, 11.33, 6.61
Tasks: 171 total, 4 running, 167 sleeping, 0 stopped, 0 zombie
Cpu(s): 56.0% us, 7.9% sy, 0.0% ni, 0.0% id, 35.4% wa, 0.7% hi, 0.0% si
Mem: 507816k total, 493724k used, 14092k free, 18624k buffers
Swap: 2096472k total, 231132k used, 1865340k free, 124824k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
11184 iworx 16 0 17040 3268 1392 S 21.6 0.6 0:10.72 iworx-db
11174 root 15 0 45500 36m 3000 D 10.6 7.4 0:05.38 php

PHP its bandwidth process form iworx.
So how optimize this?

This not happen all time, but lot of time per dy server go with laod to 20 and moreand then back.
What create this? webmail?

my cpu is 2402.06Mhz Intel® Celeron® CPU 2.40GHz (256 KB Cache) 512mb ram
I have another servers with same specs, and only tghis box have this trouble.[/quote]

Can you run ps -aux and see if there are any odd processis running as iworx? If so kill them. Also verify that you are running Iworx 2.1.3 this sounds a lot like the Horde compromose that 2.1.3 was supposed to fix.

You should NOT have to restart iworx and httpd regularly. Either you have an awefull lot of people logged into Iworx at the same time or something is deffinitely up.

If that doesn’t work, to be on the safe side why don’t you open a ticket refferencing this forum post and someone will take a look.

[QUOTE=IWorx-Tim;9665]You should NOT have to restart iworx and httpd regularly. Either you have an awefull lot of people logged into Iworx at the same time or something is deffinitely up.[/QUOTE]Indeed, but sometimes httpd and/or mysql just receive so many requests that they slow down and need to be restarted. I did open a ticket about a similar problem but the problem wasn’t found.
For me, just logging in as the “root” user of Nodeworx is enough to significantly increase the load.