Hi Yvan,

Files perms look strange on ccqserv126:

fjammes@ccqserv126:~$ ls -rtl /qserv/data/mysql/
total 20684
drwx------ 2 schoffel qserv       10 Sep 11 16:20 test/
-rw-r--r-x 1 schoffel qserv  5242880 Sep 11 21:43 ib_logfile1*
drwx---r-x 2 schoffel qserv   135168 Sep 12 01:09 LSST/
drwx------ 2 schoffel qserv     4096 Sep 12 01:09 mysql/
drwx------ 2 schoffel qserv       81 Sep 12 01:09 qservw_worker/
drwx------ 2 schoffel qserv       27 Sep 12 01:09 scisql/
drwx------ 2 schoffel qserv     4096 Sep 12 01:09 scisql_demo/
drwx------ 2 schoffel qserv       27 Sep 12 01:09 scisql_test/
drwx------ 2 schoffel qserv       55 Sep 16 17:37 q_memoryLockDb/
srwxrwxrwx 1 schoffel qserv        0 Feb  8 22:11 mysql.sock=
drwx------ 2 schoffel qserv       27 Feb  8 22:11 qservScratch/
-rw-r--r-x 1 schoffel qserv  5242880 Feb  8 22:11 ib_logfile0*
-rw-r--r-x 1 schoffel qserv 10485760 Feb  8 22:11 ibdata1*


Everything belongs to schoffel,

fjammes@ccqserv126:~$ id schoffel
uid=1000(schoffel) gid=124(atlas) groups=116(hera1),124(atlas)

It should belongs to Qserv instead...

The cause is that Qserv userid inside container and host system are no 
more equal.

SOLUTION: Having uid=1000 for Qserv user on host would be the easiest fix.

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1