jmr wrote: > Danek - I'm on mountaineer.sfbay box and checked the > updatemanagernotifier and schema, both are identical to my own machine. > I can see the cpu being pegged with prstat. Can you ask Brock to: > $ cat ~/.updatemanager/notify/opensolaris-lastcheck > cat ~/.updatemanager/notify/mountaineer-lastcheck 1226709067.29 > $ pstack `pgrep update` > [EMAIL PROTECTED]:~$ pstack `pgrep update` 713: /usr/bin/python2.4 /usr/lib/updatemanagernotifier fe37ce0a g_source_list_add (34220ed0, 83b6f08) + 36 fe37cf33 g_source_attach (34220ed0, 83b6f08) + ab fe381cf7 g_idle_add_full (c8, fe32290c, 341dd78c, fe322868) + 4f fe435dc0 pyglib_idle_add (0, 8349d6c, 0) + 1cc feee4274 PyCFunction_Call (81110cc, 8349d6c, 0) + 124 fef1464a call_function (8046d84, 1) + 406 fef1000f PyEval_EvalFrame (80c0894) + bdf fef13352 PyEval_EvalCodeEx (815b6e0, 8079824, 0, 8349d38, 1, 0) + 732 feed5f26 function_call (85eee9c, 8349d2c, 0) + 15e feec5595 PyObject_Call (85eee9c, 8349d2c, 0) + 1d feecb462 instancemethod_call (810cd74, 8349d2c, 0) + b2 feec5595 PyObject_Call (810cd74, 806102c, 0) + 1d fef140ec PyEval_CallObjectWithKeywords (810cd74, 806102c, 0) + b8 feec5573 PyObject_CallObject (810cd74, 806102c) + 13 fe32299b _pyglib_handler_marshal (c4922cc) + 8f fe381430 g_timeout_dispatch (858d128, fe32290c, c4922cc) + 24 fe37e9dc g_main_dispatch (83b6f08) + 1e0 fe37fadd g_main_context_dispatch (83b6f08) + 85 fe37fefa g_main_context_iterate (83b6f08, 1, 1, 81c40c8) + 3ce fe3804fc g_main_loop_run (85b0520) + 1b8 fd95b05e gtk_main (8125144, 80472f0, 8548b20, 8060cc0, 8148dfc, 8082640) + b2 fde13e06 _wrap_gtk_main (0, 0) + 7e fef1456e call_function (80473a4, 0) + 32a fef1000f PyEval_EvalFrame (8124ff4) + bdf fef14750 fast_function (8347a74, 80474b4, 0, 0, 0) + a8 fef1431e call_function (80474b4, 0) + da fef1000f PyEval_EvalFrame (81181cc) + bdf fef13352 PyEval_EvalCodeEx (815b860, 8079824, 8079824, 0, 0, 0) + 732 fef0f392 PyEval_EvalCode (815b860, 8079824, 8079824) + 22 fef2ee89 run_node (80612c0, 80478a7, 8079824, 8079824, 804770c) + 35 fef2ee4b run_err_node (80612c0, 80478a7, 8079824, 8079824, 804770c) + 1f fef2ee22 PyRun_FileExFlags (fecf27d0, 80478a7, 101, 8079824, 8079824, 1) + 5e fef2e1b3 PyRun_SimpleFileExFlags (fecf27d0, 80478a7, 1, 804770c) + 12f fef2dcbe PyRun_AnyFileExFlags (fecf27d0, 80478a7, 1, 804770c) + 56 fef34216 Py_Main (2, 8047754) + 75a 08050a19 main (2, 8047754, 8047760) + 11 0805097a _start (2, 8047894, 80478a7, 0, 80478c6, 80478fa) + 7a
> Then do the: > > $ pkill updatemanagernotifier > $ rm ~/.updatemanager/notify/opensolaris-lastcheck > $ /usr/bin/python2.4 /usr/lib/updatemanagernotifier -d > > If this does not chew CPU then come out of it and run it again: > $ /usr/bin/python2.4 /usr/lib/updatemanagernotifier -d > > > Danek Duvall wrote: > >> On Mon, Nov 17, 2008 at 10:38:49PM +0000, jmr wrote: >> >> >> >>> I'm not at a build machine, we'll look into it tomorrow. Could you give >>> Padraig or myself remote access to the box? >>> >>> >> Brock's in Dan's office debugging the problem, but his machine is >> mountaineer.sfbay, and is currently exhibiting the problem, if you want to >> go poking. >> >> Danek >> >> > > _______________________________________________ > pkg-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/pkg-discuss > _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
