On 16 April 2014 12:49, Francois Bissey <[email protected]> wrote: > Hum, yes the parent process is listening for the child but the child seem to > be > mute. Very difficult to do that kind of stuff over email, we'd need to find > what
I know -- and your help in debugging this is appreciated! > look that process and I cannot think of anything simple to do that... > > Instead of using make, go into a sage shell (./sage -sh) and start the build > process > manually from python. i.e. > python /home/jec/sage/src/doc/common/builder.py --no-pdf-links all html > > And let's see what happens. > Doing that.... much the same. 4 subprocesses are running, it got to exactly the same point, one of the four is using 99% CPU but doing nothing that strace notices. And if I kill that process I get more activity logged until it stops again. John > François > On 16/04/2014, at 23:43, John Cremona <[email protected]> wrote: > >> On 16 April 2014 12:36, Francois Bissey >> <[email protected]> wrote: >>> Find the PID of the process and then do "strace -p PID" to see what exactly >>> it is >>> doing. >>> Warning you'll probably get a ton of output that means nothing to you. >>> >> >> OK, I did that after restarting the make (since I had killed the 99% >> process). >> >> Had to use sudo or it didn't work: >> >> $ sudo strace -p 63131 >> Process 63131 attached - interrupt to quit >> >> (no more output at all though that process is still using 99-100% of a CPU). >> >> For the parent process (also python with same command line, presumably >> before it forks) I get >> >> >> $ sudo strace -p 62320 >> Process 62320 attached - interrupt to quit >> select(0, NULL, NULL, NULL, {0, 12082}) = 0 (Timeout) >> select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout) >> >> (repeating for ever) >> >> >> >>> François >>> On 16/04/2014, at 23:27, John Cremona <[email protected]> wrote: >>> >>>> On 16 April 2014 12:18, Francois Bissey >>>> <[email protected]> wrote: >>>>> Is it even from this attempt to build the doc or an earlier attempt? >>>> >>>> It's this attempt -- I verified that by Ctrl-C-ing the make, when >>>> these processes disappeared, then running make again. The four >>>> processes started up and now the situation is as before (3 idle, one >>>> using 99% CPU and the output stuck at the same place. >>>> >>>> The machine has plenty of processors and RAM. >>>> >>>> John >>>> >>>>> >>>>> On 16/04/2014, at 23:13, John Cremona <[email protected]> wrote: >>>>> >>>>>> Thanks for the suggestions: at the bottom of the tree, it is running 4 >>>>>> copies of >>>>>> >>>>>> python /home/jec/sage/src/doc/common/builder.py --no-pdf-links all html >>>>>> >>>>>> One of the four is using 99% of a CPU, the others none. >>>>>> >>>>>> John >>>>>> >>>>>> On 16 April 2014 12:01, P Purkayastha <[email protected]> wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Apr 16, 2014 at 6:56 PM, John Cremona <[email protected]> >>>>>>> wrote: >>>>>>>> >>>>>>>> Still no success with make doc. I have no idea what it is doing when >>>>>>>> it stops outputting (to either the screen of log file). There are no >>>>>>>> error messages, it just stops. >>>>>>>> >>>>>>>> John >>>>>>> >>>>>>> >>>>>>> Try running htop and look at the tree view to see what command it is >>>>>>> stuck >>>>>>> at. >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups >>>>>>> "sage-release" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>>>> an >>>>>>> email to [email protected]. >>>>>>> To post to this group, send email to [email protected]. >>>>>>> Visit this group at http://groups.google.com/group/sage-release. >>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "sage-release" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>>> an email to [email protected]. >>>>>> To post to this group, send email to [email protected]. >>>>>> Visit this group at http://groups.google.com/group/sage-release. >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>>> >>>>> This email may be confidential and subject to legal privilege, it may >>>>> not reflect the views of the University of Canterbury, and it is not >>>>> guaranteed to be virus free. If you are not an intended recipient, >>>>> please notify the sender immediately and erase all copies of the message >>>>> and any attachments. >>>>> >>>>> Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more >>>>> information. >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google Groups >>>>> "sage-release" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send an >>>>> email to [email protected]. >>>>> To post to this group, send email to [email protected]. >>>>> Visit this group at http://groups.google.com/group/sage-release. >>>>> For more options, visit https://groups.google.com/d/optout. >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "sage-release" group. >>>> To unsubscribe from this group and stop receiving emails from it, send an >>>> email to [email protected]. >>>> To post to this group, send email to [email protected]. >>>> Visit this group at http://groups.google.com/group/sage-release. >>>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> This email may be confidential and subject to legal privilege, it may >>> not reflect the views of the University of Canterbury, and it is not >>> guaranteed to be virus free. If you are not an intended recipient, >>> please notify the sender immediately and erase all copies of the message >>> and any attachments. >>> >>> Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more >>> information. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "sage-release" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/sage-release. >>> For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sage-release" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/sage-release. >> For more options, visit https://groups.google.com/d/optout. > > > This email may be confidential and subject to legal privilege, it may > not reflect the views of the University of Canterbury, and it is not > guaranteed to be virus free. If you are not an intended recipient, > please notify the sender immediately and erase all copies of the message > and any attachments. > > Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more > information. > > -- > You received this message because you are subscribed to the Google Groups > "sage-release" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sage-release. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
