<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hello,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Changing the project name in the configuration page (https://loris.url/configuration/) of LORIS, only change the title of the project. To see this change, you have to log out of LORIS and then go back to the login page (https://.loris.url/). This is the only
place you can find the project name (except from the configuration page). See ProjectName.png<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
As for files permission, I would suggest a few change to improve security of you server. Some extra permissions where granted to help you but are not needed.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<ul>
<li><font size="2"><span style="font-size:11pt"></span><span style="font-size: 12pt; font-family: calibri, arial, helvetica, sans-serif; line-height: normal; color: rgb(0, 0, 0); background-color: rgba(0, 0, 0, 0);">/srv/www/loris/smarty/templates_c</span></font><span style="font-family: calibri, arial, helvetica, sans-serif; font-size: 12pt; line-height: normal; color: rgb(0, 0, 0); background-color: rgba(0, 0, 0, 0);">/
should have ownership of lorisadmin:httpd and permission 770 (or 775)</span><br>
</li><li><span style="font-family: calibri, arial, helvetica, sans-serif; font-size: 12pt; line-height: normal; color: rgb(0, 0, 0); background-color: rgba(0, 0, 0, 0);">srv/www/loris/project/ should have owners</span>hip lorisadmin:httpd and permission 770 (775)<br>
</li><li>All other files under loris should have lorisadmin:lorisadmin 755<br>
</li></ul>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Reading through this change of mail, I understand that you let Apache store file in /srv/www/loris
<br>
<font size="2"><span style="font-size:11pt"> | 31 | DownloadPath | Downloads | /srv/www/loris/ | Where<br>
>> files are downloaded</span></font><br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Downloaded files should not be in the same tree as LORIS code. It should be in a separate structure where Apache will not try and do not have permission (in httpd.conf) to execute files.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Kind regards,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="Signature">
<div id="divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p style="margin-top: 0px; margin-bottom: 0px;margin-top:0; margin-bottom:0">M<span class="_Xbe">é</span>lanie Legault
<span style="color:rgb(255,0,0)">|</span> Software developer <span style="color:rgb(255,0,0)">|</span> Faculty of Medicine<span style="color:rgb(255,0,0)"> |</span>
<span style="color:rgb(255,0,0)">McGill University </span> <br>
</p>
<div>3801 University, Montr<span id="ms-rterangepaste-start"></span><span class="_Xbe">é</span><span id="ms-rterangepaste-end"></span>al, QC H3A 2B4 </div>
<br>
<p style="margin-top: 0px; margin-bottom: 0px;"></p>
</div>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> loris-dev-bounces@bic.mni.mcgill.ca <loris-dev-bounces@bic.mni.mcgill.ca> on behalf of Ioannis Pappas <ioannis@berkeley.edu><br>
<b>Sent:</b> November 7, 2019 0:18<br>
<b>To:</b> loris-dev@bic.mni.mcgill.ca <loris-dev@bic.mni.mcgill.ca><br>
<b>Cc:</b> Julie Ashworth, HWNI Computing Support <support-cirl@berkeley.edu>; Christine Rogers, Ms. <christine.rogers@mcgill.ca><br>
<b>Subject:</b> Re: [Loris-dev] loris server</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hi Christine and Julie.<br>
<br>
Yes it looks like that any attempt to configure something in the front-end results in the same page. I am sending this to the list (as you requested Christine) alongside the troubleshooting and discussion so far with Julie.<br>
<br>
Best wishes,<br>
Ioannis<br>
<br>
> On Nov 6, 2019, at 7:03 PM, Julie Ashworth, HWNI Computing Support <support-cirl@berkeley.edu> wrote:<br>
> <br>
> hi Christine and Ioannis,<br>
> Ioannis, can you follow-up with Christine about using the front-end?<br>
> <br>
> We're using CentOS7.7 and loris-21.0.1.<br>
> <br>
> I confirmed that I could login as the mysql user (lorismyqsl) and change the 'url' config setting from '<a href="http://loris.priv">http://loris.priv</a>' to '<a href="http://localhost">http://localhost</a>', and back again.<br>
> <br>
> MariaDB [loris_database]> SELECT c.ConfigID, cs.Name, cs.Label, c.Value, cs.Description FROM Config c LEFT JOIN ConfigSettings cs ON (c.ConfigID = cs.ID) JOIN ConfigSettings csp ON (cs.Parent = csp.ID) WHERE csp.Name = 'www';<br>
> +----------+-------------------+-------------------+-------------------+--------------------------------------+<br>
> | ConfigID | Name | Label | Value | Description |<br>
> +----------+-------------------+-------------------+-------------------+--------------------------------------+<br>
> | 44 | host | Host | loris.priv | Host |<br>
> | 45 | url | Main LORIS URL | <a href="http://loris.priv">
http://loris.priv</a> | Main URL where LORIS can be accessed |<br>
> | 46 | issue_tracker_url | Issue tracker URL | /issue_tracker | The *new* bug/issue tracker url |<br>
> +----------+-------------------+-------------------+-------------------+--------------------------------------+<br>
> <br>
> MariaDB [loris_database]> UPDATE Config SET Value='<a href="http://localhost">http://localhost</a>' WHERE ConfigID=(SELECT ID FROM ConfigSettings WHERE Name='url');
<br>
> Rows matched: 1 Changed: 1 Warnings: 0<br>
> <br>
> MariaDB [loris_database]> SELECT c.ConfigID, cs.Name, cs.Label, c.Value, cs.Description FROM Config c LEFT JOIN ConfigSettings cs ON (c.ConfigID = cs.ID) JOIN ConfigSettings csp ON (cs.Parent = csp.ID) WHERE csp.Name = 'www';<br>
> +----------+-------------------+-------------------+------------------+--------------------------------------+<br>
> | ConfigID | Name | Label | Value | Description |<br>
> +----------+-------------------+-------------------+------------------+--------------------------------------+<br>
> | 44 | host | Host | loris.priv | Host |<br>
> | 45 | url | Main LORIS URL | <a href="http://localhost">
http://localhost</a> | Main URL where LORIS can be accessed |<br>
> | 46 | issue_tracker_url | Issue tracker URL | /issue_tracker | The *new* bug/issue tracker url |<br>
> +----------+-------------------+-------------------+------------------+--------------------------------------+<br>
> 3 rows in set (0.00 sec)<br>
> <br>
> best,<br>
> Julie<br>
> <br>
> <br>
> On 06-11-2019 21.43 +0000, Christine Rogers, Ms. wrote:<br>
>> Hi Julie, <br>
>> Forgive my ambiguity - We run the community support listserv for<br>
>> developers, project administrators and sysadmins setting up LORIS, so that<br>
>> these users can contact our technical team for exactly such technical<br>
>> help. <br>
>> If it's ok with you, I'd encourage you subscribe to the listserv and<br>
>> contact our technical team that way for the same reason.<br>
>> (Note that front-end users of LORIS typically contact their project team<br>
>> for support, rather than us.)<br>
>> Given that your lorismysql user privileges seem appropriate ('UPDATE" is<br>
>> there, I mistyped 'INSERT" before) <br>
>> -- is there any other indication why the database record is not<br>
>> updating? <br>
>> In the front-end, can your 'admin' user effect any changes in (any) Config<br>
>> setting? <br>
>> In the back-end, when you tried updating a field using your<br>
>> lorismysql credential, what happened? <br>
>> Your front end is loading ok, and you can log in there, if I understood<br>
>> correctly. <br>
>> Thanks for letting us know these details at<br>
>> [1]loris-dev@bic.mni.mcgill.ca <br>
>> Please also include what version of LORIS you are installing, and on what<br>
>> OS version. <br>
>> Best, <br>
>> Christine<br>
>> On Wed, Nov 6, 2019 at 3:31 PM Julie Ashworth, HWNI Computing Support<br>
>> <[2]support-cirl@berkeley.edu> wrote:<br>
>> <br>
>> Thank you Christine,<br>
>> I'm the linux sysadmin who installed the loris database for Ioannis.<br>
>> I'm not a loris user, however, so that makes it a little awkward for<br>
>> troubleshooting via the mailing list. I'm happy to help in whatever way<br>
>> I can.<br>
>> <br>
>> Regarding the database permissions, I ran:<br>
>> <br>
>> MariaDB [(none)]> show grants for 'lorismysql'@'%';<br>
>> +--------------------------------------------------------------------------------+<br>
>> | Grants for lorismysql@%<br>
>> |<br>
>> +--------------------------------------------------------------------------------+<br>
>> | GRANT USAGE ON *.* TO 'lorismysql'@'%'<br>
>> |<br>
>> | GRANT SELECT, INSERT, UPDATE, DELETE ON `loris_database`.* TO<br>
>> 'lorismysql'@'%' |<br>
>> +--------------------------------------------------------------------------------+<br>
>> 2 rows in set (0.00 sec)<br>
>> <br>
>> looking at the 'tips' section in the page you referred to...<br>
>> <br>
>> | 29 | base | Base | /srv/www/loris/ | The base<br>
>> filesystem path where LORIS is installed |<br>
>> | 31 | DownloadPath | Downloads | /srv/www/loris/ | Where<br>
>> files are downloaded<br>
>> <br>
>> +----------+-------------------+-------------------+-------------------+--------------------------------------+<br>
>> | ConfigID | Name | Label | Value |<br>
>> Description |<br>
>> +----------+-------------------+-------------------+-------------------+--------------------------------------+<br>
>> | 44 | host | Host | loris.priv |<br>
>> Host |<br>
>> | 45 | url | Main LORIS URL |<br>
>> [3]http://loris.priv | Main URL where LORIS can be accessed |<br>
>> | 46 | issue_tracker_url | Issue tracker URL | /issue_tracker |<br>
>> The *new* bug/issue tracker url |<br>
>> +----------+-------------------+-------------------+-------------------+--------------------------------------+<br>
>> <br>
>> apache config:<br>
>> <br>
>> Listen 80<br>
>> User apache<br>
>> Group apache<br>
>> DocumentRoot "/srv/www/loris/htdocs"<br>
>> <br>
>> <Directory /><br>
>> AllowOverride none<br>
>> Require all denied<br>
>> </Directory><br>
>> <br>
>> <Directory "/srv/www"><br>
>> AllowOverride All<br>
>> Options Indexes FollowSymLinks<br>
>> Require all granted<br>
>> </Directory><br>
>> <br>
>> <Directory "/srv/www/loris/htdocs"><br>
>> Options Indexes FollowSymLinks<br>
>> AllowOverride All<br>
>> Require all granted<br>
>> </Directory><br>
>> <br>
>> file permissions:<br>
>> <br>
>> # ls -ld /srv/www/loris/smarty/templates_c<br>
>> drwxrwxrwx 2 lorisadmin lorisadmin 4096 Oct 31 09:46<br>
>> /srv/www/loris/smarty/templates_c/<br>
>> <br>
>> [root@loris loris]# ls -l /srv/www/loris/smarty/templates_c<br>
>> -rw-r--r-- 1 lorisadmin lorisadmin 2444 Oct 31 09:46<br>
>> 0e1b94643329544102d69ebd990c8b0165d1bd0d_0.file.form_passwordexpiry.tpl.php<br>
>> -rw-r--r-- 1 lorisadmin lorisadmin 10490 Sep 10 10:55<br>
>> 195463768851669204bf65105fe4e81a03455b48_0.file.form_data_team_helper.tpl.php<br>
>> -rw-r--r-- 1 lorisadmin lorisadmin 21126 Sep 7 18:39<br>
>> 1ebadd1dabd19543319b9015a275a25fb3ea1271_0.file.main.tpl.php<br>
>> -rw-r--r-- 1 lorisadmin lorisadmin 3296 Sep 7 18:35<br>
>> 32a6e0e3cc0aee3715361b33919eac95c0bb9cdc_0.file.form_login.tpl.php<br>
>> -rw-r--r-- 1 lorisadmin lorisadmin 5901 Sep 7 21:10<br>
>> 5cdeb715e5ad48d381bf4ea25405f9bfe5b81533_0.file.form_my_preferences.tpl.php<br>
>> -rw-r--r-- 1 lorisadmin lorisadmin 23339 Sep 7 18:39<br>
>> 71d07644a1309b40189d42145f7042af6743e856_0.file.form_dashboard.tpl.php<br>
>> -rw-r--r-- 1 lorisadmin lorisadmin 874 Sep 10 11:01<br>
>> 82495f3f78d11898c2eb816f93ec7338caa5ca28_0.file.500.tpl.php<br>
>> -rw-r--r-- 1 lorisadmin lorisadmin 1101 Sep 10 10:58<br>
>> 981927c886552e58e58f493e3153d095d2fe5d66_0.file.form_instrument_builder.tpl.php<br>
>> -rw-r--r-- 1 lorisadmin lorisadmin 18054 Sep 10 10:59<br>
>> 9dc62269f6e5525550f5928a805017c5e110a582_0.file.menu_data_release.tpl.php<br>
>> -rw-r--r-- 1 lorisadmin lorisadmin 3590 Sep 7 18:39<br>
>> a03bc16552e4c92f220889e46134f8fe96caf2ea_0.file.progress_bar.tpl.php<br>
>> -rw-r--r-- 1 lorisadmin lorisadmin 25141 Sep 7 21:08<br>
>> a07d2701a4cda44e7ef7f6025b78e76f7b6e65c4_0.file.form_configuration.tpl.php<br>
>> -rw-r--r-- 1 lorisadmin lorisadmin 897 Sep 7 18:35<br>
>> a0b6f32d181ed65d471eea20abc4abbc40bf3469_0.file.404.tpl.php<br>
>> -rw-r--r-- 1 lorisadmin lorisadmin 9210 Sep 10 11:01<br>
>> a1c292c69532174e9aa753a48e112d4b0eb33594_0.file.menu_mri_violations.tpl.php<br>
>> -rw-r--r-- 1 lorisadmin lorisadmin 8917 Sep 10 13:21<br>
>> ae14f13d831988de3500d7174b53a47390649eb5_0.file.form_project.tpl.php<br>
>> -rw-r--r-- 1 lorisadmin lorisadmin 4811 Sep 7 18:35<br>
>> d1ca754a8d9c5ab253e43310722bf6504c17d6e1_0.file.public_layout.tpl.php<br>
>> -rw-r--r-- 1 lorisadmin lorisadmin 3309 Sep 10 11:02<br>
>> d8ced7af9adee12c690eb2cc0d3ad5dc4ff54d10_0.file.form_statistics.tpl.php<br>
>> -rw-r--r-- 1 lorisadmin lorisadmin 10303 Sep 10 10:59<br>
>> e6424ba9933db2e98436eb3df00ea38ae63d7b18_0.file.menu_genomic_browser.tpl.php<br>
>> -rw-r--r-- 1 lorisadmin lorisadmin 12273 Sep 7 17:42<br>
>> fb872a21af70c86930fd51b0f25275c1e0912249_0.file.install.tpl.php<br>
>> <br>
>> thanks again!<br>
>> Julie<br>
>> <br>
>> On 06-11-2019 19.01 +0000, Christine Rogers, Ms. wrote:<br>
>>> Hi Ioannis, <br>
>>> Thanks for your question. <br>
>>> Given that the URL field is not updating, I suspect it's a database<br>
>>> back-end issue. <br>
>>> Can you verify -- Has your mysql user lorismysql been granted the<br>
>> "INSERT"<br>
>>> privilege for the right database? If not, that would result in an<br>
>> error<br>
>>> like the kind you are seeing. <br>
>>> Also, if you wish to check your LORIS Configuration settings in the<br>
>>> backend database such as the URL field -- to see what was actually<br>
>> stored<br>
>>> in a given database field and should display in the Config<br>
>> module:Â <br>
>>> You can run the queries listed in the "Troubleshooting<br>
>> Configuration<br>
>>> settings" section of our Github-wiki Setup Guide (under Project<br>
>>> Customization) :Â <br>
>>> <br>
>> [1][4]https://github.com/aces/Loris/wiki/Project-Customization#troubleshooting-configuration-settings<br>
>>> Lastly, this question is perfectly appropriate for the loris-dev<br>
>> community<br>
>>> support listserv -- please [2]subscribe here and then email our<br>
>> technical<br>
>>> team your next question at [3][5]loris-dev@bic.mni.mcgill.ca<br>
>> (after checking<br>
>>> any forwarded threads for sensitive info). <br>
>>> We prefer to answer technical questions there for the benefit of<br>
>> the<br>
>>> community and other first-time users in the same position as<br>
>> yourself.  <br>
>>> Thanks and cheers, <br>
>>> Christine <br>
>>> On Mon, Nov 4, 2019 at 5:49 PM Dr. Ioannis Pappas PhD<br>
>>> <[4][6]ioannis@berkeley.edu> wrote:<br>
>>> <br>
>>> Hi Loris support. <br>
>>> My name is ioannis Pappas, a post-doc at the D'Esposito lab<br>
>> stroke group<br>
>>> at UC Berkeley. With the kind of help of our sys admin Julie<br>
>> (cc'ed) we<br>
>>> have set up our loris database in our cluster (she is the sudo<br>
>> user and<br>
>>> I am the admin user).<br>
>>> If you allow me, I would like to ask you about the first<br>
>> configuration<br>
>>> steps in the front end as they are described in the tutorial. We<br>
>> can<br>
>>> login to [5][7]http://loris and the front end normally.<br>
>>> However any update that I am trying to perform in<br>
>> Admin->Configuration<br>
>>> doesn't work (e.g. updating the study name). It just refreshes<br>
>> the same<br>
>>> page. I am just wondering if there is an issue with writing in<br>
>> the<br>
>>> configuration file.<br>
>>> Here are the permissions setup for where Loris is installed.<br>
>>> chmod 777 /var/www/loris/smarty/templates_c<br>
>>> cd /srv/www/loris<br>
>>> chown -R lorisadmin:lorisadmin .<br>
>>> chmod -c -R a+r .<br>
>>> Â Â this command gives everyone read access, and outputs what<br>
>> changes<br>
>>> were made:<br>
>>>   mode of ¿./project¿ changed from 0770 (rwxrwx---) to 0774<br>
>>> (rwxrwxr--)<br>
>>>   mode of ¿./tools/logs¿ changed from 0770 (rwxrwx---) to<br>
>> 0774<br>
>>> (rwxrwxr--)<br>
>>> find . -type d -exec chmod a+x -c {} \;<br>
>>> Â Â this command gives everyone permission to open a directory,<br>
>> and<br>
>>> outputs what changes were made:<br>
>>>   mode of ¿./project¿ changed from 0774 (rwxrwxr--) to 0775<br>
>>> (rwxrwxr-x)<br>
>>>   mode of ¿./tools/logs¿ changed from 0774 (rwxrwxr--) to<br>
>> 0775<br>
>>> (rwxrwxr-x)<br>
>>> Hopefully you can help me with this. I also subscribed to the<br>
>> mailing<br>
>>> list but I am not sure if this too much of a basic question for<br>
>> the<br>
>>> list.<br>
>>> Best wishes,<br>
>>> Ioannis<br>
>>> On Mon, Nov 4, 2019 at 1:12 PM Julie Ashworth, HWNI Computing<br>
>> Support<br>
>>> <[6][8]support-cirl@berkeley.edu> wrote:<br>
>>> <br>
>>> Hi ioannis, maybe it's best to ask the developers? You can cc<br>
>> me if<br>
>>> you'd like.<br>
>>> On Mon, Nov 4, 2019, 12:37 PM Ioannis Pappas<br>
>> <[7][9]ioannis@berkeley.edu><br>
>>> wrote:<br>
>>> <br>
>>> That did the trick Julie. Thank you!<br>
>>> <br>
>>> I am still trying to understand how configuration works<br>
>> though. For<br>
>>> example if I just try to change the name of the<br>
>>> study from the front end, I get nowhere (it just refreshes<br>
>> the same<br>
>>> page).<br>
>>> <br>
>>> I am not sure if this requires write permissions somewhere in<br>
>> a<br>
>>> config file/folder and that’s why it doesn’t update it.<br>
>>> <br>
>>> Best wishes,<br>
>>> Ioannis<br>
>>> <br>
>>> > On Nov 4, 2019, at 12:08 PM, Julie Ashworth, HWNI Computing<br>
>>> Support <[8][10]support-cirl@berkeley.edu> wrote:<br>
>>> ><br>
>>> > just in case you're interested, these are the permission<br>
>> changes I<br>
>>> made:<br>
>>> ><br>
>>> > chmod 777 /var/www/loris/smarty/templates_c<br>
>>> > cd /srv/www/loris<br>
>>> > chown -R lorisadmin:lorisadmin .<br>
>>> > chmod -c -R a+r .<br>
>>> >Â Â this command gives everyone read access, and outputs<br>
>> what<br>
>>> changes were made:<br>
>>> >  mode of ¿./project¿ changed from 0770 (rwxrwx---) to<br>
>> 0774<br>
>>> (rwxrwxr--)<br>
>>> >  mode of ¿./tools/logs¿ changed from 0770 (rwxrwx---)<br>
>> to 0774<br>
>>> (rwxrwxr--)<br>
>>> > find . -type d -exec chmod a+x -c {} \;<br>
>>> >Â Â this command gives everyone permission to open a<br>
>> directory, and<br>
>>> outputs what changes were made:<br>
>>> >  mode of ¿./project¿ changed from 0774 (rwxrwxr--) to<br>
>> 0775<br>
>>> (rwxrwxr-x)<br>
>>> >  mode of ¿./tools/logs¿ changed from 0774 (rwxrwxr--)<br>
>> to 0775<br>
>>> (rwxrwxr-x)<br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> > On 04-11-2019 12.03 -0800, Ioannis Pappas wrote:<br>
>>> >> Hi Julie.<br>
>>> >> I just tried and I still don???t get anything. I also<br>
>> tried<br>
>>> private mode in Firefox in case the empty page was cached.<br>
>>> >> Sorry for this.<br>
>>> >><br>
>>> >> Best wishes,<br>
>>> >> Ioannis<br>
>>> >><br>
>>> >>> On Nov 4, 2019, at 11:58 AM, Julie Ashworth, HWNI<br>
>> Computing<br>
>>> Support <[9][11]support-cirl@berkeley.edu> wrote:<br>
>>> >>><br>
>>> >>> hi Ioannis,<br>
>>> >>> no worries, I changed the following directory to 777:<br>
>>> >>><br>
>>> >>> /var/www/loris/smarty/templates_c<br>
>>> >>><br>
>>> >>> will you please check if that works?<br>
>>> >>><br>
>>> >>> thanks!<br>
>>> >>><br>
>>> >>><br>
>>> >>><br>
>>> >>><br>
>>> >>><br>
>>> >>> On 04-11-2019 11.49 -0800, Dr. Ioannis Pappas PhD wrote:<br>
>>> >>>>Â Hi Julie.<br>
>>> >>>>Â Apologies for bugging you with this again. We tried<br>
>> now to<br>
>>> >>>> access [1][10][12]http://lorisÂ<br>
>>> >>>> and we are getting a blank page. I think the reason<br>
>> for this<br>
>>> is that we<br>
>>> >>>> don't have read permissions to read from the<br>
>> template located<br>
>>> in<br>
>>> >>>>Â /var/www/loris/smarty See here bottom of the<br>
>>> >>>> pageÂ<br>
>>> <br>
>> [2][11][13]https://github.com/aces/Loris/wiki/Installing-Loris-in-Brief<br>
>>> >>>>Â I think, in general, I am a little bit confused as to<br>
>> what the<br>
>>> permissions<br>
>>> >>>>Â should be for us that are not sudos. My understanding<br>
>> is that<br>
>>> if we don't<br>
>>> >>>>Â have read or write permissions then we can't access or<br>
>> write<br>
>>> to<br>
>>> >>>>Â /var/www/loris, meaning that we can't access or<br>
>> configure.<br>
>>> Should<br>
>>> >>>> everything be chmod 777 for example?Â<br>
>>> >>>>Â Thank you very much once again.<br>
>>> >>>>Â Best wishes,<br>
>>> >>>>Â Ioannis<br>
>>> >>>>Â On Thu, Oct 31, 2019 at 1:56 PM Dr. Ioannis Pappas PhD<br>
>>> >>>>Â <[3][12][14]ioannis@berkeley.edu> wrote:<br>
>>> >>>><br>
>>> >>>>Â Â Thank you very much Julie. I appreciate this and I<br>
>> will dig<br>
>>> into Loris<br>
>>> >>>>Â Â given your changes. Thank you so much for your<br>
>> help.<br>
>>> >>>>Â Â Best wishes,<br>
>>> >>>>Â Â Ioannis<br>
>>> >>>>Â Â On Thu, Oct 31, 2019 at 12:48 PM Julie Ashworth,<br>
>> HWNI<br>
>>> Computing Support<br>
>>> >>>>Â Â <[4][13][15]support-cirl@berkeley.edu> wrote:<br>
>>> >>>><br>
>>> >>>>Â Â Â hi Ioannis,<br>
>>> >>>><br>
>>> >>>>Â Â Â 1. I changed the permissions of /srv/www/loris<br>
>> to be owned<br>
>>> by<br>
>>> >>>>Â Â Â lorisadmin. I reivewed my installation notes,<br>
>> and I did<br>
>>> this already<br>
>>> >>>>Â Â Â when<br>
>>> >>>>Â Â Â I installed the server. I'm not sure why they<br>
>> changed, so<br>
>>> it's<br>
>>> >>>>Â Â Â probably a<br>
>>> >>>>Â Â Â good idea to keep an eye on that.<br>
>>> >>>><br>
>>> >>>>Â Â Â 2. When I installed the loris software, I also<br>
>> installed a<br>
>>> mysql<br>
>>> >>>>Â Â Â database as recommended in the instructions:<br>
>>> >>>><br>
>>> >>>>Â Â Â projectname: LORIS<br>
>>> >>>>Â Â Â databasename: loris_database<br>
>>> >>>>Â Â Â mysqluser: lorismysql<br>
>>> >>>>Â Â Â frontend: lorisweb<br>
>>> >>>><br>
>>> >>>>Â Â Â 3. A couple of weeks ago, I moved Henrik's home<br>
>> directory<br>
>>> to<br>
>>> >>>>Â Â Â /home/despoA,<br>
>>> >>>>Â Â Â but I forgot to update loris. This is done now.<br>
>>> >>>><br>
>>> >>>>Â Â Â best,<br>
>>> >>>>Â Â Â Julie<br>
>>> >>>><br>
>>> >>>>Â Â Â On 31-10-2019 11.15 -0700, Dr. Ioannis Pappas<br>
>> PhD wrote:<br>
>>> >>>>>   Hi Julie.<br>
>>> >>>>>   I hope you are well. We are trying to<br>
>> configure loris<br>
>>> that you<br>
>>> >>>>Â Â Â kindly set<br>
>>> >>>>>   up for us.<br>
>>> >>>>>   I have a couple of questions for you if you<br>
>> allow me<br>
>>> so.Â<br>
>>> >>>>>   1) First, although we are logging into the<br>
>> front end<br>
>>> with admin<br>
>>> >>>>Â Â Â username<br>
>>> >>>>>   (lorisweb) and password, it seems that any<br>
>> kind of<br>
>>> update of<br>
>>> >>>>Â Â Â configuration<br>
>>> >>>>>   we are trying to do fails (meaning that if<br>
>> we, say,<br>
>>> change the<br>
>>> >>>>Â Â Â name of the<br>
>>> >>>>>   study and press "submit", this doesn't do<br>
>> anything-it<br>
>>> doesn't<br>
>>> >>>>Â Â Â update).<br>
>>> >>>>>   It's almost like our lorisweb user doesn't<br>
>> have write<br>
>>> privileges<br>
>>> >>>>Â Â Â in the<br>
>>> >>>>>   /var/www/loris/project (where I think every<br>
>>> configuration should<br>
>>> >>>>Â Â Â be).<br>
>>> >>>>>   This generalizes for everything that we are<br>
>> trying to do<br>
>>> in the<br>
>>> >>>>Â Â Â front end.<br>
>>> >>>>>   Clicking any instrument/tab in the front end<br>
>> doesn't<br>
>>> really point<br>
>>> >>>>Â Â Â to<br>
>>> >>>>>   anything.Â<br>
>>> >>>>>   2) Loris suggest doing configurations via<br>
>> SQL. Is it<br>
>>> possible to<br>
>>> >>>>Â Â Â run SQL<br>
>>> >>>>>   scripts in the backend<br>
>>> >>>>>   3) For some reason typing ssh lors for Henrik<br>
>> doesn't<br>
>>> directly<br>
>>> >>>>Â Â Â take him to<br>
>>> >>>>>   loris (it requires a password that is not the<br>
>> password<br>
>>> setup for<br>
>>> >>>>Â Â Â the<br>
>>> >>>>>   lorisweb user). Will you be able to fix this<br>
>> via your<br>
>>> sudo<br>
>>> >>>>Â Â Â privileges?<br>
>>> >>>>>   Thank you very much in advance for all your<br>
>> help Julie.<br>
>>> Let us<br>
>>> >>>>Â Â Â know if<br>
>>> >>>>>   this is something that shouldn't be directed<br>
>> to you (but<br>
>>> instead<br>
>>> >>>>Â Â Â to the<br>
>>> >>>>>   loris people).Â<br>
>>> >>>>>   Best wishes,<br>
>>> >>>>>   Ioannis<br>
>>> >>>>>   On Mon, Sep 9, 2019 at 6:25 PM Julie<br>
>> Ashworth, HWNI<br>
>>> Computing<br>
>>> >>>>Â Â Â Support<br>
>>> >>>>>   <[1][5][14][16]support-cirl@berkeley.edu><br>
>> wrote:<br>
>>> >>>>><br>
>>> >>>>>    hi Henrik and Ioannis,<br>
>>> >>>>>    the loris server is available for you to<br>
>> use.<br>
>>> >>>>><br>
>>> >>>>>    The servername is 'loris'. I created a<br>
>> directory<br>
>>> called<br>
>>> >>>>Â Â Â /data/loris for<br>
>>> >>>>>    you to store data. You may create new<br>
>> folders in<br>
>>> /data/loris to<br>
>>> >>>>Â Â Â organize<br>
>>> >>>>>    your data.<br>
>>> >>>>><br>
>>> >>>>>    1) secure shell or secure copy:<br>
>>> >>>>>    You can log in with the 'ssh' or 'scp'<br>
>> command from<br>
>>> your remote<br>
>>> >>>>Â Â Â desktop<br>
>>> >>>>>    session. You don't need to authenticate<br>
>> to log in.<br>
>>> Maybe you'll<br>
>>> >>>>Â Â Â use scp<br>
>>> >>>>>    to transfer data between your cluster<br>
>> account and the<br>
>>> loris<br>
>>> >>>>Â Â Â server?<br>
>>> >>>>>    Please put the data in /data/loris, so I<br>
>> can make<br>
>>> backups more<br>
>>> >>>>Â Â Â easily.<br>
>>> >>>>><br>
>>> >>>>>      secure shell:<br>
>>> >>>>>      $ ssh loris<br>
>>> >>>>><br>
>>> >>>>>      secure copy (change the names<br>
>> in brackets). Let<br>
>>> me know if<br>
>>> >>>>Â Â Â I can<br>
>>> >>>>>      help with syntax:<br>
>>> >>>>>      $ scp -r <data><br>
>> loris:/data/loris/<newfolder><br>
>>> >>>>><br>
>>> >>>>>    2) front-end web interface. Open a<br>
>> web browser in<br>
>>> your remote<br>
>>> >>>>Â Â Â desktop<br>
>>> >>>>>    session and enter the hostname:<br>
>>> >>>>>    [2][6][15][17]http://loris<br>
>>> >>>>>    I created an admin user called<br>
>> 'lorisweb'. I put the<br>
>>> password<br>
>>> >>>>Â Â Â in<br>
>>> >>>>>    $HOME/newuser on the cluster. To see it,<br>
>> open a<br>
>>> terminal, and<br>
>>> >>>>Â Â Â run:<br>
>>> >>>>><br>
>>> >>>>>      $ cat $HOME/newuser<br>
>>> >>>>><br>
>>> >>>>>    If other people need shell access to the<br>
>> webserver,<br>
>>> please let<br>
>>> >>>>Â Â Â me know<br>
>>> >>>>>    so I can create a home directory for<br>
>> them.<br>
>>> >>>>><br>
>>> >>>>>    We should eventually discuss backups.<br>
>>> >>>>><br>
>>> >>>>>    best,<br>
>>> >>>>>    Julie<br>
>>> >>>>><br>
>>> >>>>> References<br>
>>> >>>>><br>
>>> >>>>>   Visible links<br>
>>> >>>>>   1.<br>
>> mailto:[7][16][18]support-cirl@berkeley.edu<br>
>>> >>>>>   2. [8][17][19]http://loris/<br>
>>> >>>>Â Â Â ---end quoted text---<br>
>>> >>>><br>
>>> >>>> References<br>
>>> >>>><br>
>>> >>>>Â Visible links<br>
>>> >>>>Â 1. [18][20]http://loris/<br>
>>> >>>>Â 2.<br>
>>> <br>
>> [19][21]https://github.com/aces/Loris/wiki/Installing-Loris-in-Brief<br>
>>> >>>>Â 3. mailto:[20][22]ioannis@berkeley.edu<br>
>>> >>>>Â 4. mailto:[21][23]support-cirl@berkeley.edu<br>
>>> >>>>Â 5. mailto:[22][24]support-cirl@berkeley.edu<br>
>>> >>>>Â 6. [23][25]http://loris/<br>
>>> >>>>Â 7. mailto:[24][26]support-cirl@berkeley.edu<br>
>>> >>>>Â 8. [25][27]http://loris/<br>
>>> >>> ---end quoted text---<br>
>>> >><br>
>>> > ---end quoted text---<br>
>>> <br>
>>> --<br>
>>> [26][28]christine.rogers@mcgill.ca<br>
>>> McGill Centre for Integrative Neuroscience | MCIN.ca<br>
>>> Montreal Neurological Institute<br>
>>> McGill University | Montreal | Canada<br>
>>> <br>
>>> References<br>
>>> <br>
>>> Visible links<br>
>>> 1.<br>
>> [29]https://github.com/aces/Loris/wiki/Project-Customization#troubleshooting-configuration-settings<br>
>>> 2. [30]https://mailman.bic.mni.mcgill.ca/mailman/listinfo/loris-dev<br>
>>> 3. mailto:[31]loris-dev@bic.mni.mcgill.ca<br>
>>> 4. mailto:[32]ioannis@berkeley.edu<br>
>>> 5. [33]http://loris/<br>
>>> 6. mailto:[34]support-cirl@berkeley.edu<br>
>>> 7. mailto:[35]ioannis@berkeley.edu<br>
>>> 8. mailto:[36]support-cirl@berkeley.edu<br>
>>> 9. mailto:[37]support-cirl@berkeley.edu<br>
>>> 10. [38]http://xn--loris-7qa/<br>
>>> 11. [39]https://github.com/aces/Loris/wiki/Installing-Loris-in-Brief<br>
>>> 12. mailto:[40]ioannis@berkeley.edu<br>
>>> 13. mailto:[41]support-cirl@berkeley.edu<br>
>>> 14. mailto:[42]support-cirl@berkeley.edu<br>
>>> 15. [43]http://loris/<br>
>>> 16. mailto:[44]support-cirl@berkeley.edu<br>
>>> 17. [45]http://loris/<br>
>>> 18. [46]http://loris/<br>
>>> 19. [47]https://github.com/aces/Loris/wiki/Installing-Loris-in-Brief<br>
>>> 20. mailto:[48]ioannis@berkeley.edu<br>
>>> 21. mailto:[49]support-cirl@berkeley.edu<br>
>>> 22. mailto:[50]support-cirl@berkeley.edu<br>
>>> 23. [51]http://loris/<br>
>>> 24. mailto:[52]support-cirl@berkeley.edu<br>
>>> 25. [53]http://loris/<br>
>>> 26. mailto:[54]christine.rogers@mcgill.ca<br>
>> ---end quoted text---<br>
>> <br>
>> --<br>
>> [55]christine.rogers@mcgill.ca<br>
>> McGill Centre for Integrative Neuroscience | MCIN.ca<br>
>> Montreal Neurological Institute<br>
>> McGill University | Montreal | Canada<br>
>> <br>
>> References<br>
>> <br>
>> Visible links<br>
>> 1. <a href="mailto:loris-dev@bic.mni.mcgill.ca">mailto:loris-dev@bic.mni.mcgill.ca</a><br>
>> 2. <a href="mailto:support-cirl@berkeley.edu">mailto:support-cirl@berkeley.edu</a><br>
>> 3. <a href="http://loris.priv/">http://loris.priv/</a><br>
>> 4. <a href="https://github.com/aces/Loris/wiki/Project-Customization#troubleshooting-configuration-settings">
https://github.com/aces/Loris/wiki/Project-Customization#troubleshooting-configuration-settings</a><br>
>> 5. <a href="mailto:loris-dev@bic.mni.mcgill.ca">mailto:loris-dev@bic.mni.mcgill.ca</a><br>
>> 6. <a href="mailto:ioannis@berkeley.edu">mailto:ioannis@berkeley.edu</a><br>
>> 7. <a href="http://loris/">http://loris/</a><br>
>> 8. <a href="mailto:support-cirl@berkeley.edu">mailto:support-cirl@berkeley.edu</a><br>
>> 9. <a href="mailto:ioannis@berkeley.edu">mailto:ioannis@berkeley.edu</a><br>
>> 10. <a href="mailto:support-cirl@berkeley.edu">mailto:support-cirl@berkeley.edu</a><br>
>> 11. <a href="mailto:support-cirl@berkeley.edu">mailto:support-cirl@berkeley.edu</a><br>
>> 12. <a href="http://xn--loris-era/">http://xn--loris-era/</a><br>
>> 13. <a href="https://github.com/aces/Loris/wiki/Installing-Loris-in-Brief">https://github.com/aces/Loris/wiki/Installing-Loris-in-Brief</a><br>
>> 14. <a href="mailto:ioannis@berkeley.edu">mailto:ioannis@berkeley.edu</a><br>
>> 15. <a href="mailto:support-cirl@berkeley.edu">mailto:support-cirl@berkeley.edu</a><br>
>> 16. <a href="mailto:support-cirl@berkeley.edu">mailto:support-cirl@berkeley.edu</a><br>
>> 17. <a href="http://loris/">http://loris/</a><br>
>> 18. <a href="mailto:support-cirl@berkeley.edu">mailto:support-cirl@berkeley.edu</a><br>
>> 19. <a href="http://loris/">http://loris/</a><br>
>> 20. <a href="http://loris/">http://loris/</a><br>
>> 21. <a href="https://github.com/aces/Loris/wiki/Installing-Loris-in-Brief">https://github.com/aces/Loris/wiki/Installing-Loris-in-Brief</a><br>
>> 22. <a href="mailto:ioannis@berkeley.edu">mailto:ioannis@berkeley.edu</a><br>
>> 23. <a href="mailto:support-cirl@berkeley.edu">mailto:support-cirl@berkeley.edu</a><br>
>> 24. <a href="mailto:support-cirl@berkeley.edu">mailto:support-cirl@berkeley.edu</a><br>
>> 25. <a href="http://loris/">http://loris/</a><br>
>> 26. <a href="mailto:support-cirl@berkeley.edu">mailto:support-cirl@berkeley.edu</a><br>
>> 27. <a href="http://loris/">http://loris/</a><br>
>> 28. <a href="mailto:christine.rogers@mcgill.ca">mailto:christine.rogers@mcgill.ca</a><br>
>> 29. <a href="https://github.com/aces/Loris/wiki/Project-Customization#troubleshooting-configuration-settings">
https://github.com/aces/Loris/wiki/Project-Customization#troubleshooting-configuration-settings</a><br>
>> 30. <a href="https://mailman.bic.mni.mcgill.ca/mailman/listinfo/loris-dev">https://mailman.bic.mni.mcgill.ca/mailman/listinfo/loris-dev</a><br>
>> 31. <a href="mailto:loris-dev@bic.mni.mcgill.ca">mailto:loris-dev@bic.mni.mcgill.ca</a><br>
>> 32. <a href="mailto:ioannis@berkeley.edu">mailto:ioannis@berkeley.edu</a><br>
>> 33. <a href="http://loris/">http://loris/</a><br>
>> 34. <a href="mailto:support-cirl@berkeley.edu">mailto:support-cirl@berkeley.edu</a><br>
>> 35. <a href="mailto:ioannis@berkeley.edu">mailto:ioannis@berkeley.edu</a><br>
>> 36. <a href="mailto:support-cirl@berkeley.edu">mailto:support-cirl@berkeley.edu</a><br>
>> 37. <a href="mailto:support-cirl@berkeley.edu">mailto:support-cirl@berkeley.edu</a><br>
>> 38. <a href="http://xn--loris-7qa/">http://xn--loris-7qa/</a><br>
>> 39. <a href="https://github.com/aces/Loris/wiki/Installing-Loris-in-Brief">https://github.com/aces/Loris/wiki/Installing-Loris-in-Brief</a><br>
>> 40. <a href="mailto:ioannis@berkeley.edu">mailto:ioannis@berkeley.edu</a><br>
>> 41. <a href="mailto:support-cirl@berkeley.edu">mailto:support-cirl@berkeley.edu</a><br>
>> 42. <a href="mailto:support-cirl@berkeley.edu">mailto:support-cirl@berkeley.edu</a><br>
>> 43. <a href="http://loris/">http://loris/</a><br>
>> 44. <a href="mailto:support-cirl@berkeley.edu">mailto:support-cirl@berkeley.edu</a><br>
>> 45. <a href="http://loris/">http://loris/</a><br>
>> 46. <a href="http://loris/">http://loris/</a><br>
>> 47. <a href="https://github.com/aces/Loris/wiki/Installing-Loris-in-Brief">https://github.com/aces/Loris/wiki/Installing-Loris-in-Brief</a><br>
>> 48. <a href="mailto:ioannis@berkeley.edu">mailto:ioannis@berkeley.edu</a><br>
>> 49. <a href="mailto:support-cirl@berkeley.edu">mailto:support-cirl@berkeley.edu</a><br>
>> 50. <a href="mailto:support-cirl@berkeley.edu">mailto:support-cirl@berkeley.edu</a><br>
>> 51. <a href="http://loris/">http://loris/</a><br>
>> 52. <a href="mailto:support-cirl@berkeley.edu">mailto:support-cirl@berkeley.edu</a><br>
>> 53. <a href="http://loris/">http://loris/</a><br>
>> 54. <a href="mailto:christine.rogers@mcgill.ca">mailto:christine.rogers@mcgill.ca</a><br>
>> 55. <a href="mailto:christine.rogers@mcgill.ca">mailto:christine.rogers@mcgill.ca</a><br>
> ---end quoted text---<br>
<br>
<br>
_______________________________________________<br>
Loris-dev mailing list<br>
Loris-dev@bic.mni.mcgill.ca<br>
<a href="https://mailman.bic.mni.mcgill.ca/mailman/listinfo/loris-dev">https://mailman.bic.mni.mcgill.ca/mailman/listinfo/loris-dev</a><br>
</div>
</span></font></div>
</body>
</html>