cove Posted May 20, 2003 Report Share Posted May 20, 2003 For some reasons the retrospect client just decides to gobble up CPU time. Today is May 20th, this client was started on May 5th, 21411 mins. of CPU time = ca. 14 days out of < 15 days! USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 8409 99.8 0.1 281144 900 ? T May05 21411:00 /usr/local/dantz/client/retroclient -daemon This is verison 6.0 of the client, running under RedHat 7.2 Linux. Any thoughts? Cove Link to comment Share on other sites More sharing options...
merrisr Posted June 9, 2003 Report Share Posted June 9, 2003 I've seen the same thing with 6.0 and 6.5. One thing you can try is setting the nice level for the retrospect client to something high - I set one of mine to 19 and that dropped utilization from 99% to 0. The client system had 2 CPUs, and one of them was pegged at 99% even when it wasn't being backed up. Of course, you'll want to test and make sure your backups are running properly after niceing them. Rhian Merris merrisr@saic.com Link to comment Share on other sites More sharing options...
cove Posted September 11, 2003 Author Report Share Posted September 11, 2003 Yeah, that sounds a bit iffy to me actually. I've just had to go an restart the clients every now and then when they go crazy. Though I don't think I've seen this with the 6.5 client... I'll keep my finger crossed. Cove Link to comment Share on other sites More sharing options...
cove Posted October 9, 2003 Author Report Share Posted October 9, 2003 Well, here is what it's doing when it uses up too much CPU time. It reads in 0 bytes and then to writes out 0 bytes... PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 1903 root 25 0 1164 1084 628 R 99.4 0.2 11:01 0 retropds.23 rst:~# strace -p 1903 0 13:40:21 write(7, "", 0) = 0 read(6, "", 65536) = 0 write(7, "", 0) = 0 read(6, "", 65536) = 0 write(7, "", 0) = 0 read(6, "", 65536) = 0 write(7, "", 0) = 0 read(6, "", 65536) = 0 write(7, "", 0) = 0 read(6, "", 65536) = 0 write(7, "", 0) = 0 read(6, "", 65536) = 0 write(7, "", 0) = 0 read(6, "", 65536) = 0 write(7, "", 0) = 0 read(6, "", 65536) = 0 write(7, "", 0) = 0 read(6, "", 65536) = 0 write(7, "", 0) = 0 read(6, "", 65536) = 0 write(7, "", 0) = 0 read(6, "", 65536) = 0 write(7, "", 0) = 0 read(6, "", 65536) = 0 write(7, "", 0) = 0 read(6, "", 65536) = 0 write(7, "", 0) = 0 read(6, "", 65536) = 0 write(7, "", 0) = 0 read(6, "", 65536) = 0 write(7, "", 0) = 0 read(6, "", 65536) = 0 write(7, "", 0) = 0 read(6, "", 65536) = 0 Link to comment Share on other sites More sharing options...
Guest psykoyiko Posted October 10, 2003 Report Share Posted October 10, 2003 Was this strace performed on the 6.0 or the 6.5 client? Is this still Redhat 7.2? Link to comment Share on other sites More sharing options...
cove Posted November 24, 2003 Author Report Share Posted November 24, 2003 That strace was on RedHat 9, and the latest client, 6.5 I believe. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.