Re: [sage-support] Re: Sage server failed to start

[Jan Groenewald]

Hi


On 8 January 2015 at 14:32, Jeroen Demeyer  wrote:

> On 2015-01-08 06:36, Jan Groenewald wrote:
>
>> I get about one zero sized users.pickle 2-3 times per week.
>>
> Really, how does that happen? I am also running a sagenb server on my
> university and this never happened.
>

It is not a server, it is standalone sage installs, and ~/.sage is on NFS.
It seems to be NOT related to disk space quotas.

However, I also see it on laptops (non-NFS, standalone installs) at times.

Regards,
Jan


-- 
  .~.
  /V\ Jan Groenewald
 /( )\www.aims.ac.za
 ^^-^^

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage server failed to start

[Ivan Andrus]

I posted trac #17610 which is ready for review.  It now tries starting it in a 
Terminal if it fails for any reason.  This should be more robust to any sort of 
corruption, and also help show the problem in the cases where it does fail.

-Ivan

> On Jan 8, 2015, at 5:17 PM, Ivan Andrus  wrote:
> 
> Do you mean that if you open Sage.app and click on the Terminal Session > 
> Sage menu, that Terminal.app doesn’t open?  Or do you mean that Terminal.app 
> doesn’t open automatically when you try to start the notebook server?
> 
> For now, doing it manually once (and typing in a password) should fix the 
> problem.  If it doesn’t, then there is some other problem.
> 
> -Ivan
> 
>> On Jan 8, 2015, at 4:39 PM, Ruizhi Deng > > wrote:
>> 
>> Thank you! But the problem for me is that the terminal don't start.
>> 
>> On Wednesday, January 7, 2015 at 11:04:20 PM UTC-5, kcrisman wrote:
>> 
>> 
>> On Wednesday, January 7, 2015 7:57:36 PM UTC-5, Ruizhi Deng wrote:
>> I'm a new comer to Sage and I'm running sage on my mac with OS X 10.10. I 
>> started sage successfully for the first time but I have trouble running sage 
>> after that. It constantly shows that Sage server failed to start.
>> And here's the log information I find. It might be useful.
>> 
>> Looks like the issues at 
>> https://groups.google.com/forum/#!topic/sage-support/_Ly5eQ2E-10 
>>  and 
>> originally reported in a different form at 
>> http://trac.sagemath.org/ticket/9873#comment:33 
>> 
>> 
>> Ivan, any ideas for a long-term fix on this?  This really should work 
>> without having to do 
>> 
>> Terminal Session > Sage > then type notebook(). 
>> 
>> as suggested in that thread.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage server failed to start

[Ivan Andrus]

Do you mean that if you open Sage.app and click on the Terminal Session >
Sage menu, that Terminal.app doesn’t open?  Or do you mean that
Terminal.app doesn’t open automatically when you try to start the notebook
server?

For now, doing it manually once (and typing in a password) should fix the
problem.  If it doesn’t, then there is some other problem.

-Ivan

On Jan 8, 2015, at 4:39 PM, Ruizhi Deng  wrote:

Thank you! But the problem for me is that the terminal don't start.

On Wednesday, January 7, 2015 at 11:04:20 PM UTC-5, kcrisman wrote:
>
>
>
> On Wednesday, January 7, 2015 7:57:36 PM UTC-5, Ruizhi Deng wrote:
>>
>> I'm a new comer to Sage and I'm running sage on my mac with OS X 10.10. I
>> started sage successfully for the first time but I have trouble running
>> sage after that. It constantly shows that Sage server failed to start.
>> And here's the log information I find. It might be useful.
>>
>
> Looks like the issues at https://groups.google.com/
> forum/#!topic/sage-support/_Ly5eQ2E-10 and originally reported in a
> different form at http://trac.sagemath.org/ticket/9873#comment:33
>
> Ivan, any ideas for a long-term fix on this?  This really should work
> without having to do
>
> Terminal Session > Sage > then type notebook().
>
> as suggested in that thread.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage server failed to start

[Ruizhi Deng]

I reinstalled sage on my computer, but it still doesn't work.

On Wednesday, January 7, 2015 at 7:57:36 PM UTC-5, Ruizhi Deng wrote:
>
> I'm a new comer to Sage and I'm running sage on my mac with OS X 10.10. I 
> started sage successfully for the first time but I have trouble running 
> sage after that. It constantly shows that Sage server failed to start.
> And here's the log information I find. It might be useful.
>
> Setting environment variables
> /Applications/Sage-6.4.1.app/Contents/Resources/start-sage.sh: line 43: 
> spkg/bin/sage-env: No such file or directory
> Warning: overwriting SAGE_ROOT environment variable:
> Old SAGE_ROOT=/Applications/Sage-6.4.1.app/Contents/Resources/sage/
> New SAGE_ROOT=/Applications/Sage-6.4.1.app/Contents/Resources/sage
> Checking install location
> Checking existence of notebook directory
> Starting Notebook
> ┌┐
> │ Sage Version 6.4.1, Release Date: 2014-11-23   │
> │ Type "notebook()" for the browser-based notebook interface.│
> │ Type "help()" for help.│
> └┘
> Please wait while the Sage Notebook server starts...
> /Applications/Sage-6.4.1.app/Contents/Resources/sage/local/lib/python/getpass.py:83:
>  
> GetPassWarning: Can not control echo on the terminal.
>   passwd = fallback_getpass(prompt, stream)
> Warning: Password input may be echoed.
> Enter new password: The notebook files are stored in: sage_notebook.sagenb
>
>
>
> Please choose a new password for the Sage Notebook 'admin' user.
> Do _not_ choose a stupid password, since anybody who could guess your 
> password
> and connect to your machine could access or delete your files.
> NOTE: Only the hash of the password you type is stored by Sage.
> You can change your password by typing notebook(reset=True).
>
>
>
> Traceback (most recent call last):
>   File 
> "/Applications/Sage-6.4.1.app/Contents/Resources/sage/src/bin/sage-notebook", 
> line 180, in 
> launcher(unknown)
>   File 
> "/Applications/Sage-6.4.1.app/Contents/Resources/sage/src/bin/sage-notebook", 
> line 63, in __init__
> notebook(*self.args, **self.kwds)
>   File 
> "/Applications/Sage-6.4.1.app/Contents/Resources/sage/local/lib/python2.7/site-packages/sagenb-0.11.1-py2.7.egg/sagenb/notebook/notebook_object.py",
>  
> line 234, in __call__
> return self.notebook(*args, **kwds)
>   File 
> "/Applications/Sage-6.4.1.app/Contents/Resources/sage/local/lib/python2.7/site-packages/sagenb-0.11.1-py2.7.egg/sagenb/notebook/run_notebook.py",
>  
> line 563, in notebook_run
> passwd = get_admin_passwd()
>   File 
> "/Applications/Sage-6.4.1.app/Contents/Resources/sage/local/lib/python2.7/site-packages/sagenb-0.11.1-py2.7.egg/sagenb/notebook/run_notebook.py",
>  
> line 652, in get_admin_passwd
> passwd = getpass.getpass("Enter new password: ")
>   File 
> "/Applications/Sage-6.4.1.app/Contents/Resources/sage/local/lib/python/getpass.py",
>  
> line 83, in unix_getpass
> passwd = fallback_getpass(prompt, stream)
>   File 
> "/Applications/Sage-6.4.1.app/Contents/Resources/sage/local/lib/python/getpass.py",
>  
> line 118, in fallback_getpass
> return _raw_input(prompt, stream)
>   File 
> "/Applications/Sage-6.4.1.app/Contents/Resources/sage/local/lib/python/getpass.py",
>  
> line 135, in _raw_input
> raise EOFError
> EOFError
>  
> Can anyone help me solve this problem?
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage server failed to start

[Ruizhi Deng]

Thank you! But the problem for me is that the terminal don't start.

On Wednesday, January 7, 2015 at 11:04:20 PM UTC-5, kcrisman wrote:
>
>
>
> On Wednesday, January 7, 2015 7:57:36 PM UTC-5, Ruizhi Deng wrote:
>>
>> I'm a new comer to Sage and I'm running sage on my mac with OS X 10.10. I 
>> started sage successfully for the first time but I have trouble running 
>> sage after that. It constantly shows that Sage server failed to start.
>> And here's the log information I find. It might be useful.
>>
>
> Looks like the issues at 
> https://groups.google.com/forum/#!topic/sage-support/_Ly5eQ2E-10 and 
> originally reported in a different form at 
> http://trac.sagemath.org/ticket/9873#comment:33
>
> Ivan, any ideas for a long-term fix on this?  This really should work 
> without having to do 
>
> Terminal Session > Sage > then type notebook(). 
>
> as suggested in that thread.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Re: Bug in solve?

[kcrisman]

>
> >> Only 2 years later, and I found a way around segmentation faults due to 
> >> memory problems. It seems that my looping functions fill up memory over 
> time 
> >> and lead to segmentation faults at random stages. I now define such 
> >> functions using the @fork decorator and then they don't seem to cause 
> >> crashes any more (memory gets freed after each run). Just in case 
> someone 
> >> with a similar problem stumbles over this. 
> > 
> > 
>

Stan, do you have a fairly small (in terms of code length, I mean, not 
timing or anything) example that could be used to demonstrate how @fork 
avoids this problem?
 

> > Huh.  Maybe this would be worth adding to the documentation... 
> somewhere, I 
> > have no idea where. 
>
> This would go well in the FAQ. 
>
>
Yeah, I guess.  See http://trac.sagemath.org/ticket/17604 and hopefully we 
can put a good example there.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Re: Sage server failed to start

[kcrisman]

>
> > I get about one zero sized users.pickle 2-3 times per week. 
> Really, how does that happen? I am also running a sagenb server on my 
> university and this never happened. 
>
> In any case, I hope that this issue will be fixed by 
> https://github.com/sagemath/sagenb/pull/287 
>

For completeness - which is in the merged Trac 10057, I believe, so should 
be in Sage 6.5.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Re: Sage server failed to start

[Jeroen Demeyer]

On 2015-01-08 06:36, Jan Groenewald wrote:

I get about one zero sized users.pickle 2-3 times per week.
Really, how does that happen? I am also running a sagenb server on my 
university and this never happened.


In any case, I hope that this issue will be fixed by
https://github.com/sagemath/sagenb/pull/287

--
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: sage hardcoded links problem

[Volker Braun]

I only changed the way the buildbot builds the binary release. The new 
binary is not on the web page yet, but should be soon.



On Thursday, January 8, 2015 6:10:33 AM UTC+1, Robert McBroom wrote:
>
> Fixes to the source files?
>
> On Tuesday, January 6, 2015 3:23:10 AM UTC-5, Volker Braun wrote:
>>
>> I built a new binary. Harald, can you replace the F21 binary with the new 
>> one on the mirrors?
>>
>> buildbot@build:~$ md5sum 
>> binaries/sage-6.4.1-x86_64-Linux-Fedora_21_x86_64.tar.gz
>> cbdf8a8a1e4ee99c10c5b00d2c976b9e 
>>  binaries/sage-6.4.1-x86_64-Linux-Fedora_21_x86_64.tar.gz
>>
>>
>>
>> On Tuesday, January 6, 2015 3:43:29 AM UTC+1, kcrisman wrote:
>>>
>>> Thanks, I updated the buildbot to ignore SAGE_ATLAS_LIB in binary builds.

>>> Is it possible to put new binaries out for this, at least for the Fedora 
>>> one? 
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.