Guys,
We''re having a similar problem to that documented, but not resolved,
here:
http://lists.xensource.com/archives/html/xen-users/2005-08/msg00110.html
The python process that runs "/usr/sbin/xend start" has reached 99.9%
CPU
utilization.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
3569 root 25 0 12952 7876 2456 R 99.9 6.2 13444:26 python
/usr/sbin/xend start
xm commands don''t respond, because the daemon process has apparently
entered an endless loop. Stracing to the process yields:
gettimeofday({1132076987, 801316}, NULL) = 0
gettimeofday({1132076987, 801401}, NULL) = 0
gettimeofday({1132076987, 801486}, NULL) = 0
gettimeofday({1132076987, 801571}, NULL) = 0
gettimeofday({1132076987, 801657}, NULL) = 0
gettimeofday({1132076987, 801742}, NULL) = 0
gettimeofday({1132076987, 801828}, NULL) = 0
gettimeofday({1132076987, 801913}, NULL) = 0
gettimeofday({1132076987, 801999}, NULL) = 0
gettimeofday({1132076987, 802084}, NULL) = 0
...over, and over, and over again.
This is on a CentOS4 (RHEL4) box, on an i686.
Kernel: 2.6.11.12-xen0
Xen version: 2.0.7
Has anyone else experienced this? Any idea what might be causing it?
Thanks!
John
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Guys,
We''re having a similar problem to that documented, but not resolved,
here:
http://lists.xensource.com/archives/html/xen-users/2005-08/msg00110.html
The python process that runs "/usr/sbin/xend start" has reached 99.9%
CPU
utilization.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
3569 root 25 0 12952 7876 2456 R 99.9 6.2 13444:26 python
/usr/sbin/xend start
xm commands don''t respond, because the daemon process has apparently
entered an endless loop. Stracing to the process yields:
gettimeofday({1132076987, 801316}, NULL) = 0
gettimeofday({1132076987, 801401}, NULL) = 0
gettimeofday({1132076987, 801486}, NULL) = 0
gettimeofday({1132076987, 801571}, NULL) = 0
gettimeofday({1132076987, 801657}, NULL) = 0
gettimeofday({1132076987, 801742}, NULL) = 0
gettimeofday({1132076987, 801828}, NULL) = 0
gettimeofday({1132076987, 801913}, NULL) = 0
gettimeofday({1132076987, 801999}, NULL) = 0
gettimeofday({1132076987, 802084}, NULL) = 0
...over, and over, and over again.
This is on a CentOS4 (RHEL4) box, on an i686.
Kernel: 2.6.11.12-xen0
Xen version: 2.0.7
Has anyone else experienced this? Any idea what might be causing it?
Thanks!
John
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
John Wells said:> Guys, > > We''re having a similar problem to that documented, but not resolved, here: > http://lists.xensource.com/archives/html/xen-users/2005-08/msg00110.htmlHeh...ok, well, we rebooted the box, and of course the problem went away. However, now I notice my problem description is wrong. I connected via strace to the now working process and note that it also continuously spits out gettimeofday messages, but that intermixed are calls to poll: gettimeofday({1132084397, 346225}, NULL) = 0xen.xend.server import SrvDaemon gettimeofday({1132084397, 346536}, NULL) = 0= SrvDaemon.instance() poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=6, events=POLLIN}, {fd=10, events=POLLIN}, {fd=15, events=POLLIN}, {fd=18, events=POLLIN}], 6, 178) = 0 gettimeofday({1132084397, 534960}, NULL) = 0 gettimeofday({1132084397, 535283}, NULL) = 0 So apparently, whatever our problem was caused by led to this poll() call not being called. Anyone have any ideas what I might look at? I''m hunting down the SrvDaemon code currently to try get some insight, but if you have any ideas in the meantime it would be appreciated. Thanks, John _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users