Opened 7 years ago

Closed 7 years ago

#992 closed defect (fixed)

chroot build method: sahana does not start

Reported by: kalxas Owned by: live-demo@…
Priority: major Milestone: OSGeoLive6.0RC1
Component: OSGeoLive Keywords: 6.0 beta9
Cc: live-demo@…, rediguana, flavour

Description

Sahana is faining to start in beta9 (live session) with an "Unable to connect" error

Change history (9)

comment:1 Changed 7 years ago by hamish

still broken.

Firefox can't establish a connection to the server at localhost:8007

running the start script from the command line shows a bunch of permissions related errors, see #994.

in particular web2py/cron.master and je lockfiles can't be written.

Hamish

comment:2 Changed 7 years ago by hamish

Cc: rediguana flavour added

We've done our best at fixing a lot of the permissions problems. What remains are just under 1000 files in the web2py file tree which seem to be created by these two commands in the install_sahana.sh script:

sudo -H -u "$USER_NAME" python web2py.py -S eden -M \
   -R applications/eden/static/scripts/tools/noop.py

[...]

sudo -H -u "$USER_NAME" python web2py.py -S eden -M \
   -R applications/eden/static/scripts/tools/compile.py

which I assume is byte compiling the .pyc files, but it seems that it is doing more as well?

the trouble is that the user at build time (UID 1000) is not the same as the user at run time (UID 999), so all of the files which # 999 wants to write to are owned by another (non-existent) user. In any event, the user shouldn't be owning files outside of the home dir*.

[*] if they need to be writable, we can make them belong to a group which the user has write permissions for, but we need to know which files need that.

Also a long-term goal is to allow additional users to be added later (in a VM or install-from-disc), so locking it to the single user account isn't desirable.

So, how to go about running the above web2py.py commands if "$USER_NAME" won't exist later?

thanks, Hamish

comment:3 Changed 7 years ago by kalxas

Resolution: fixed
Status: newclosed

fixed in beta10

comment:4 Changed 7 years ago by hamish

Priority: criticalmajor
Resolution: fixed
Status: closedreopened

fixing the file ownership of ~680 .pyc and ~180 .table files is still todo. The .pyc files can probably be safely set to be owned by root and read-only, the .table files I'm not sure about.

Hamish

comment:5 Changed 7 years ago by hamish

should be all fixed. the ticket can be closed after the quickstart is tested from end to end.

Hamish

comment:6 Changed 7 years ago by darkblueb

it appears to be broken in build 9057

comment:7 Changed 7 years ago by darkblueb

retraction - I meant to mark ticket #969; thanks to Hamish for pointing that out

comment:8 Changed 7 years ago by kalxas

can we close this now?

comment:9 Changed 7 years ago by hamish

Resolution: fixed
Status: reopenedclosed

tested, everything seems working.

Note: See TracTickets for help on using tickets.