At some point overnight the process which I thought had hung must have
revived itself and finished, since I left it running and when I came
in this morning I had a running sage server!  It's hard to tell how
long it took, but at least an hour as far as I can tell.

John

On 19 Nov, 17:35, John Cremona <john.crem...@gmail.com> wrote:
> I installed certtool on the system using apt-get install gnutls-bin.
> Then running certtool by itself worked fine, but running notebook(...)
> from within sage still hung.
>
> So I moved aside sage's certtool and copied the system /usr/bin/
> certtool into sage's local/bin directory.  The same happened again: it
> hangs after outputting " Generating a 2048 bit RSA private key..."
>
> I can try installing the openssl version instead (does that have
> another name?  or what ubuntu package it is in?)  But it is bizarre
> that running certtool from the command line now works fine while from
> sage it does not.
>
> John
>
> On Nov 19, 4:26 pm, William Stein <wst...@gmail.com> wrote:
>
> > On Thu, Nov 19, 2009 at 3:33 AM, John Cremona <john.crem...@gmail.com> 
> > wrote:
> > > I am having exactly the same problem as the original poster.  The
> > > machine runs 64-bit ubuntu (Linux version 2.6.28-13-generic
> > > (bui...@yellow) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #44-
> > > Ubuntu SMP Tue Jun 2 07:55:09 UTC 2009)
>
> > > I don't have certtool installed on the machine (except the Sage
> > > version).
>
> > Can you try installing the system-wide certtool and see what happens?
>
> > GNU provides one implementation of certtool and openssl provides another.
> > The openssl one is excellent and robust -- the GNU one is often insanely 
> > slow.
> > Sage has to include the GNU one...
>
> > > While it hangs at the point "Generating a 2048 bit RSA private
> > > key..."  I checked what was happening in another window:
>
> > > j...@selmer%ps aux | grep certtool
> > > sage     13068  0.0  0.0   4028   588 pts/7    S<+  11:05   0:00 /bin/
> > > sh -c certtool --generate-privkey --outfile /home/sage/.sage/dsage/
> > > cacert.pem
> > > sage     13069  0.0  0.0  15960  1480 pts/7    S<+  11:05   0:00
> > > certtool --generate-privkey --outfile /home/sage/.sage/dsage/
> > > cacert.pem
>
> > > Note that this is 25 minutes after starting to wait, and that certtool
> > > is doing nothing at all (S means Suspended, right?)
>
> > > I tried running the certtool command outside Sage (after doing "sage -
> > > sh"), namely
> > >  certtool --generate-privkey --outfile /home/sage/.sage/dsage/
> > > cacert.pem
> > > but the same happened, i.e. nothing and no return...
>
> > > Any ideas for how to sort this out would be welcome.  And it would be
> > > nice to be able to test the correct running of certtool when Sage is
> > > built.
>
> > > John Cremona
>
> > > On 16 Nov, 09:45, "marc.burw...@googlemail.com"
> > > <philipp.kl...@gmail.com> wrote:
> > >> In my case just waiting for about 10 minutes solved the problem as the
> > >> entropy on the computer where I started sage was too low.
>
> > >> greetings marc
>
> > >> On Nov 12, 3:22 am, Kwankyu <ekwan...@gmail.com> wrote:
>
> > >> > Hi,
>
> > >> > I have a problem starting a sage server after, I think, upgrading to
> > >> > Ubuntu 9.10 server edition. It just hangs at the point "Generating a
> > >> > 2048 bit RSA private key..." See the following transcript
> > >> > [...]
>
> > > --
> > > To post to this group, send email to sage-support@googlegroups.com
> > > To unsubscribe from this group, send email to 
> > > sage-support-unsubscr...@googlegroups.com
> > > For more options, visit this group 
> > > athttp://groups.google.com/group/sage-support
> > > URL:http://www.sagemath.org
>
> > --
> > William Stein
> > Associate Professor of Mathematics
> > University of Washingtonhttp://wstein.org

-- 
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to 
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/sage-support
URL: http://www.sagemath.org

Reply via email to