Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Dec 13 15:41

    NicolasCARPi on aalto

    login.js doesn't exist anymore (compare)

  • Dec 13 15:29

    NicolasCARPi on aalto

    use tsc in buildall (compare)

  • Dec 13 14:12

    NicolasCARPi on aalto

    add admin, editusers and change… (compare)

  • Dec 13 13:04
    NicolasCARPi labeled #1673
  • Dec 13 12:33
    maffiou1611 opened #1673
  • Dec 13 11:17
    NicolasCARPi labeled #1672
  • Dec 13 11:16
    NicolasCARPi commented #1672
  • Dec 13 11:16
    NicolasCARPi commented #1453
  • Dec 13 10:45
    maffiou1611 opened #1672
  • Dec 13 09:54
    maffiou1611 commented #1453
  • Dec 13 02:16
    codecov-io commented #1671
  • Dec 13 02:13
    claassistantio commented #1671
  • Dec 13 02:12
    dependabot-preview[bot] labeled #1671
  • Dec 13 02:12
    dependabot-preview[bot] labeled #1671
  • Dec 13 02:12
    dependabot-preview[bot] opened #1671
  • Dec 13 02:12

    dependabot-preview[bot] on composer

    Bump fzaninotto/faker from 1.9.… (compare)

  • Dec 12 17:44

    NicolasCARPi on aalto

    mostly working (compare)

  • Dec 12 12:18
    NicolasCARPi labeled #1670
  • Dec 12 12:18
    NicolasCARPi commented #1670
  • Dec 12 08:55
    Catastrophi opened #1670
Nicolas CARPi
@NicolasCARPi
then the mysql port will only be exposed to the elabftw container, and not to the outside network
Tru Huynh
@truatpasteurdotfr
Hello, I am installing the docker based elabftw on centos7 for the 1st time
if selinux is enabled, /usr/local/bin/elabctl info keeps reporting:
elabftw   /run.sh                       Restarting        
mysql     docker-entrypoint.sh mysqld   Restarting
only when I setenforce 0, I get:
elabftw   /run.sh                       Up      0.0.0.0:443->443/tcp             
mysql     docker-entrypoint.sh mysqld   Up      0.0.0.0:3306->3306/tcp, 33060/tcp
Tru Huynh
@truatpasteurdotfr
[centos@localhost ~]$ docker ps -a
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                               NAMES
b414f0d5263e        mysql:5.7           "docker-entrypoint..."   51 minutes ago      Up 51 minutes       0.0.0.0:3306->3306/tcp, 33060/tcp   mysql
581096b03d67        elabftw/elabimg     "/run.sh"                51 minutes ago      Up 51 minutes       0.0.0.0:443->443/tcp                elabftw
[centos@localhost ~]$ getenforce 
Permissive
[centos@localhost ~]$ ps -eZ | grep mysql
system_u:system_r:container_t:s0:c268,c613 6523 ? 00:00:07 mysqld
[centos@localhost ~]$ ps -eZ | grep run
system_u:system_r:container_t:s0:c99,c626 6624 ? 00:00:00 run.sh
[centos@localhost ~]$ uname -a
Linux localhost.localdomain 3.10.0-1062.4.1.el7.x86_64 #1 SMP Fri Oct 18 17:15:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
[centos@localhost ~]$ sudo aureport -a
...
79. 11/08/2019 14:31:14 chown system_u:system_r:container_t:s0:c99,c626 260 dir setattr unconfined_u:object_r:var_t:s0 denied 1181
80. 11/08/2019 14:32:40 mysqld system_u:system_r:container_t:s0:c268,c613 2 dir write system_u:object_r:var_t:s0 denied 1183
81. 11/08/2019 14:32:40 mysqld system_u:system_r:container_t:s0:c268,c613 2 dir add_name system_u:object_r:var_t:s0 denied 1183
82. 11/08/2019 14:32:40 mysqld system_u:system_r:container_t:s0:c268,c613 82 dir remove_name system_u:object_r:var_t:s0 denied 1184
83. 11/08/2019 14:32:40 mysqld system_u:system_r:container_t:s0:c268,c613 82 file rename system_u:object_r:var_t:s0 denied 1184
84. 11/08/2019 14:57:13 mysqld system_u:system_r:container_t:s0:c268,c613 2 file read system_u:object_r:var_t:s0 denied 1201
85. 11/08/2019 14:57:13 mysqld system_u:system_r:container_t:s0:c268,c613 2 file open system_u:object_r:var_t:s0 denied 120
Nicolas CARPi
@NicolasCARPi
hello @truatpasteurdotfr
I run elab on centos with selinux enabled and don't have this issue
so elab CAN run with selinux enabled !
if you want I can privately share my ansible scripts if you're interested
as for your particular issue, I'm afraid my selinux skills won't be of much help....
Tru Huynh
@truatpasteurdotfr
thanks for the offer, and yes I am interested.
Tru Huynh
@truatpasteurdotfr
hello from irc.gitter.im
Florian
@BarryJive_twitter
Hi there, my first users are now actively testing eLab and a question has come up relating to comments in database items. Items in their case describe lab equipment and comments should be used to indicate changes, repairs, and so on. Consequently, the order of comments which is oldest first by default is not ideal. Is there a possibility we just don't see to change the order of comments to newest first?
Nicolas CARPi
@NicolasCARPi
hello Florian
I wouldn't use comments to indicate changes and so on. Just add it in the body, so you can order it the way you want.
Florian
@BarryJive_twitter
I'll propose that to my users.
I can, however, tell you one objection they are going to have: database objects should not be added and edited by all users. Changes or repairs of existing systems will be done by everyone.
Thanks ;)
Nicolas CARPi
@NicolasCARPi
well, it's a design choice, all database items are editable by users of the team, but maybe with the next permission system this can be better improved
Florian
@BarryJive_twitter
I offered them the workaround, communicated your position and will get back to you if more of our users start clamoring ;)
Thanks again for your quick response (, the software in general of course) and have a pleasant evening
Florian
@BarryJive_twitter
Probably an easy fix: I just installed the update to version 3.3.12. Sys-admin panel still shows the newest version to be 3.3.11 and asks me to update while actually showing that the server is running 3.3.12^^
Nicolas CARPi
@NicolasCARPi
ah yeah thanks I thought about it yesterday but was in my bed and then forgot about it, I just need to rebuild the elabget image
ok done
there used to be a webhook for that but I've been too lazy to look into it...
Ari Paavo Seitsonen
@apsi_gitlab

Hello, I am struggling with the SMTP: I have tried to use both local MTA or our SMTP server - latter naturally strongly preferred - but the system does not get the mails sent. The account on the SMTP server works for example when used via ThunderBird for example. The error message that I see is (from "elabctl php-log"):

2019/11/22 11:05:17 [error] 65#65: *19 FastCGI sent in stderr: "PHP message: [2019-11-22T11:05:17.107527+01:00] elabftw.ERROR: [{"userid":"1"},{"exception":"[object] (Swift_TransportException(code: 0): Connection to tcp://mail.Chimie.ens.fr:465 Timed Out at /elabftw/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/AbstractSmtpTransport.php:473)\n[previous exception] [object] (Swift_IoException(code: 0): Connection to tcp://mail.Chimie.ens.fr:465 Timed Out at /elabftw/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/StreamBuffer.php:166)"}] []" while reading response header from upstream, client: 129.199.33.88, server: cpmv-labbook.chimie.ens.fr, request: "POST /app/controllers/SysconfigAjaxController.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.sock:", host: "cpmv-labbook.chimie.ens.fr"

This is the latest version of eLabFTW, installed yesterday.

Nicolas CARPi
@NicolasCARPi
hello @apsi_gitlab
are you sure 465 is the correct port?
if the connection is timing out it's probably not a problem from elab itself, as it's just trying to connect where you say it should
Nicolas CARPi
@NicolasCARPi
I discussed a bit with Jacques and he told me that the chimie smtp server was not accessible from everywhere, maybe that's your issue?
Ari Paavo Seitsonen
@apsi_gitlab

Hello Nicolas, thank you for yours responses. Yes, 465 is the correct port, and both the virtual machines holding eLabFTW and the SMTP server and inside the network of the Department. Could be some firewall in Docker...? In any case, without SSL/TLS and now using the port 25 the sending seems to work (even if I would prefer a verification...). Except that when a new user wants to register and does not choose the "Default team" we get "division by zero"??

2019/11/22 18:07:42 [error] 65#65: *174 FastCGI sent in stderr: "PHP message: PHP Warning: Division by zero in /elabftw/src/classes/UserStats.php on line 98PHP message: PHP Warning: Division by zero in /elabftw/src/classes/UserStats.php on line 98PHP message: PHP Warning: Division by zero in /elabftw/src/classes/UserStats.php on line 98PHP message: PHP Warning: Division by zero in /elabftw/src/classes/UserStats.php on line 98" while reading response header from upstream, client: 129.199.34.60, server: cpmv-labbook.chimie.ens.fr, request: "GET /profile.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.sock:", host: "cpmv-labbook.chimie.ens.fr"

Nicolas CARPi
@NicolasCARPi
thanks for the bug report about the division, anyway it's unrelated to the mail issue and is minor but I'll look into it
there is no firewall in Docker, if you want to troubleshoot further, I'd suggest using openssl to connect directly to the smtp server from the container:
docker exec -it elabftw bash openssl s_client -connect mail.chimie.ens.fr:465 smtp or something similar. Maybe it's a certificate error or something. At least you'll see if it's possible to connect to it with another tool
note: it should have been two commands, not one single line!
Tru Huynh
@truatpasteurdotfr
`[centos@localhost ~]$ docker exec -t elabftw bash -c 'echo -n| openssl s_client -connect mail.Chimie.ens.fr:465'
[centos@localhost ~]$ docker exec -t elabftw bash -c 'echo -n| openssl s_client -connect mail.Chimie.ens.fr:465'
Ari Paavo Seitsonen
@apsi_gitlab

Thank you. Indeed with this command I can see a response from the server:
CONNECTED(00000005)
... (certificate chain) ...
DONE

So it is something delicate inside eLabFTW how it handles the SMTP protocol...?

It is not urgent, as we can send without an account, using the port 25 without the SSL.
Nicolas CARPi
@NicolasCARPi
No there is nothing fancy about it, it's using the SwiftMailer library to send emails through SMTP, and it seems to work fine. The thing I don't understand is that you get a timeout, not like an error. Could it be something on your network dropping the connection?
Tru Huynh
@truatpasteurdotfr
maybe stupid question about the email configuration for docker based elabftw...
the [local MTA] option is using the host MTA? or do I need to install postfix inside one of the docker image?
the host docker is properly configured to send email, but I am not receiving the "test email" from the elabftw web interface
elabctl logs is not showing anything related to mail
Tru Huynh
@truatpasteurdotfr
ok I got it :P
using plain smtp:25 as @apsi_gitlab did just works :D
Nicolas CARPi
@NicolasCARPi
yeah the local mta option should not really be used in docker I guess
AGMOI
@AGMOI
Hi, I'm testing today for the first time the creation of laboratory protocols.
Unfortunately, I do not understand why HMTL commands such as. "<input type =" date "id =" gebdat ">" are displayed correctly in the HTML preview, but they are finally deleted after saving. Can one help? Sorry, it's all new to me.
quintam23
@quintam23
can someone ralk about the different type of code sample that can be inserted into a template?
I am trying to understand what this does?
Nicolas CARPi
@NicolasCARPi
hello @AGMOI you cannot add such things! It's by design: input tags are stripped.
@quintam23 you can add code samples for the following languages: https://github.com/elabftw/elabftw/blob/master/web/app/js/src/edit.js#L337-L353
it's just doing syntax highlighting, nothing more.