#14358: Permission denied error with jmol and "remote" user
----------------------------+-----------------------------------------------
       Reporter:  ppurka    |         Owner:  jason, mpatel, was
           Type:  defect    |        Status:  new               
       Priority:  major     |     Milestone:  sage-5.9          
      Component:  notebook  |    Resolution:                    
       Keywords:            |   Work issues:                    
Report Upstream:  N/A       |     Reviewers:                    
        Authors:            |     Merged in:                    
   Dependencies:            |      Stopgaps:                    
----------------------------+-----------------------------------------------
Changes (by ppurka):

 * cc: dima (added)


Old description:

> We have been running the sage worksheets as an unprivileged user. The
> setup is as follows.
>
> 1. A user, say user1, starts the sage server remotely using
> {{{
> sage -n port=8888 accounts=True interface=''
> server_pool=['sagenb@localhost'] openid=True automatic_login=False
> port_tries=0 directory=/home/user1/a.sagenb
> }}}
> 2. Because of the server_pool command, any worksheet is opened as an
> unprivileged user called sagenb.
> 3. With default sage-5.2 there is no problem with this and everything
> works.
> 4. With sage-5.2 + "#13121 without new jmol", jmol works but one needs to
> close the worksheet and then reopen the worksheet and then the jmol pops
> up.
> 5. With sage-5.2 + #13121, jmol works partially:
>  1. First, the static image can not be created and there is a permission
> denied error. See [attachment:permission_error.jpg].
>  2. However, once the 3D output is toggled, jmol loads fine. The
> permission denied error is still there.
>  3. The error obtained is of the form
> {{{
> script ERROR: script ERROR: io error reading
> /home/user1/a.sagenb/home/__store__/0/09/098/098f/te\
> st/0/cells/7/sage0-size500-499889951.jmol.zip|SCRIPT:
> java.io.FileNotFoundException:
> /home/user1/a.sagenb/home/__store__/0/09/098/098f/te\
> st/0/cells/7/sage0-size500-499889951.jmol.zip (Permission denied)
> Sleeping...Make Interactive
> }}}
> 6. When run locally, i.e., without server_pool, the jmol loads and runs
> fine. For instance, this is fine:
> {{{
> sage -n directory=a.sagenb
> }}}
>
> This problem has made it difficult for me to upgrade a server from 5.2
> and I think the error is introduced by some change in jmol. The error
> itself stems from some java component. A diff of the changes between the
> directory `$SAGE_ROOT/devel/sagenb/sagenb/data/sage3d` for sage-5.2 and
> sage-5.7.rc0 has not yielded any difference. So, I believe the difference
> is really in the jmol spkg introduced in #12299.

New description:

 We have been running the sage worksheets as an unprivileged user. The
 setup is as follows.

 1. A user, say user1, starts the sage server using
 {{{
 sage -n port=8888 accounts=True interface=''
 server_pool=['sagenb@localhost'] openid=True automatic_login=False
 port_tries=0 directory=/home/user1/a.sagenb
 }}}
 2. Because of the server_pool command, any worksheet is opened as an
 unprivileged user called sagenb.
 3. With default sage-5.2 there is no problem with this and everything
 works.
 4. With sage-5.2 + "#13121 without new jmol", jmol works but one needs to
 close the worksheet and then reopen the worksheet and then the jmol pops
 up.
 5. With sage-5.2 + #13121, jmol works partially:
  1. First, the static image can not be created and there is a permission
 denied error. See [attachment:permission_error.jpg].
  2. However, once the 3D output is toggled, jmol loads fine. The
 permission denied error is still there.
  3. The error obtained is of the form
 {{{
 script ERROR: script ERROR: io error reading
 /home/user1/a.sagenb/home/__store__/0/09/098/098f/te\
 st/0/cells/7/sage0-size500-499889951.jmol.zip|SCRIPT:
 java.io.FileNotFoundException:
 /home/user1/a.sagenb/home/__store__/0/09/098/098f/te\
 st/0/cells/7/sage0-size500-499889951.jmol.zip (Permission denied)
 Sleeping...Make Interactive
 }}}
 6. When run locally, i.e., without server_pool, the jmol loads and runs
 fine. For instance, this is fine:
 {{{
 sage -n directory=a.sagenb
 }}}

 This problem has made it difficult for me to upgrade a server from 5.2 and
 I think the error is introduced by some change in jmol. The error itself
 stems from some java component. A diff of the changes between the
 directory `$SAGE_ROOT/devel/sagenb/sagenb/data/sage3d` for sage-5.2 and
 sage-5.7.rc0 has not yielded any difference. So, I believe the difference
 is really in the jmol spkg introduced in #12299.

 I have traced it back and reproduced it in sage-5.2 + new notebook + new
 jmol. Although I wrote sage-5.2 above, the error is present in all the
 sage versions I have tried - sage-5.4 till sage-5.9.beta0.

--

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14358#comment:1>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" 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-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to