Server load avg 4.30+ from cpgsd.pl

[SNN]

#ps acx
...
26314 ?        R    1622:35 cpgsd.pl
...

I saw (After fixing my friends account, and checking the "Service Status" page) that load averages were over 4.30 (cap 4.31 so far) and killed the process.
I am running CentOS 5 on a VPSLink Xen server.
512 MB RAM (1024 SWAP)
1 CPU
2.50 GHz
20 GB Hard Drive

# cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Xeon(R) CPU           E5420  @ 2.50GHz
stepping        : 6
cpu MHz         : 2493.748
cache size      : 6144 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu tsc msr pae mce cx8 apic mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc up pni monitor ds_cpl vmx est tm2 cx16 xtpr lahf_lm
bogomips        : 6236.82

Edit: After killing the process, load averages are back to 0.05

[darren]

Were you able to strace the process to see what it was doing that was eating up all the CPU ?
I saw a report where a broken pipe during a package download could cause this but I've yet to be able to replicate it.

[SNN]

Hmm. Well the cpgsd.pl process is once again running up the load average (atm: 2.10) but I'll upgrade to 0.6.6 and then see what happens. It only happens every few hours.

Edit: I noticed a error...
Sending self-update command to 127.0.0.1 .. Something went wrong while unpacking the daemon: (exit code: 512)Bad file descriptor

[darren]

Would it be possible for you to put in a ticket ? That unpacking error is new to me; I'm wondering if it could be related to the CPU usage issue in some way. I'd like to take a look in any case to try and ensure that whatever is causing the CPU load problem gets fixed.

[SNN]

Okay, I've created a ticket.
If you need the ID:
"Support Request Id: 246743"

My server load is currently down (back to normal) but I expect after an hour or two that it will be back up.

Edit: I guess the upgrade fixed it..I don't know what the problem is..but will reply to the ticket should it go back up ^^)