Re: email notification for self register 2 3 and 4, posted by Stefan Ritt on Mon Jun 8 09:12:27 2020
|
STARTTLS is not supported natively by elog. You have to disable this in your SMTP server.
Stefan
| pierre brionnet wrote: |
|
Hi Stefan, I did run in verbose mode but only got this output with the 587 SMTP port from gmail
Email from <ELog@localhost.localdomain> to XXXX@gmail.com, SMTP host smtp.gmail.com:
220 smtp.gmail.com ESMTP n1sm6153685pfd.156 - gsmtp
EHLO localhost.localdomain
250-smtp.gmail.com at your service, [134.160.38.27]
250-SIZE 35882577
250-8BITMIME
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-CHUNKING
250 SMTPUTF8
AUTH LOGIN
530 5.7.0 Must issue a STARTTLS command first. n1sm6153685pfd.156 - gsmtp
However the mail command in my bash is working juste fine
Pierre
| Stefan Ritt wrote: |
|
Why don't you start elogd interactively with the "-v" flag (verbose) and watch the communication between elog and postfix. Maybe you see a specific error there.
Stefan
| pierre brionnet wrote: |
|
Hi,
I have set up my elog for testing and setup postfix to be able to send email notification for register of new user but whatever i try elog cannot set email. I try to sent test email in my bash and this is working without problem to my gmail account.
I have tried several configuration for my smtp client on my centos 7 but nothing is working in elog for the email. I also tried with several other email but no change either.
Is there a problem with the automatic sending of email ?
Best
Pierre
|
|
|
|
|
Re: SSL does not work, posted by Hisataka YOSHIDA on Thu Jun 11 08:23:01 2020
|
Dear Stefan,
Thank you for your comment. I successfuly compiled the latest elog from source code, and now elogd could work with SSL.
In fact, I reported the case of installation with rpm file. Maybe, the latest elog rpm doesn't support SSL, I guess.
The installtion with rpm file is easier to build the common environment, so I hope the next rpm will support the SSL.
best regards,
Hisataka YOSHIDA
| Stefan Ritt wrote: |
|
When you compile elog from the soruces, you need the OpenSSL library to be installed. The CMake build process will then find it and include it in the compile process. When you use the "make" build process, you have to make sure that SSL is enabled there:
USE_SSL = 1
To install the OpenSSL library, you can do on most systems something like "sudo yum install openssl-dev" or "sudo apt-get install openssl-dev"
/Stefan
| Hisataka YOSHIDA wrote: |
|
Hello.
I installed the latest elog (3.1.4-2) in CentOS 7, and it is working well without SSL.
When I enalbled SSL option (SSL = 1) in the "elogd.cfg", and tried to start the elogd, the message below was shown and failed to run.
SSL support not compiled into elogd
If I switched the elog to older one (3.1.4-1), I could successeed to run the elogd with SSL option.
Is there any other option required in the latest elog to run with SSL? Or is this bug in the latest version?
Thank you,
Hisataka YOSHIDA
|
|
|
bug in elog.spec, posted by Janusz Szuba on Mon Jul 6 19:09:48 2020
|
Hi,
in commit 1812e7c, specifying CFLAGS to make command in elog.spec, renders all other settings in Makefile void. That is, if I want to include any of KRB5, LDAP, PAM support, and change makefile accordingly, then when producing rpm they are not taken into account. Anyway, CFLAGS in Makefile are already set to the same defaults, so why it is redefined in spec file?
best
Janusz |
Re: bug in elog.spec, posted by Laurent Jean-Rigaud on Mon Jul 6 20:19:21 2020 
|
Hi,
You rights, CFLAGS should not be in specfile to take care of distrib env.
Btw, I sent in the past an update for build process of Stefan delivery to generate src.rpm file copatible to tarball version. I think Stefan did not have time yet to test and to check.
With the enclosed SPEC file, you can build ELOG with options at rpmbulld command w/o modifying sources. For exemple,
rpm -i elog-.....src.rpm
rpmbuild -bb --with ssl --with pam --with ldap --with krb5 ~/rpmbuild/SPECS/elog.spec
I enclosed also the SRPMS i used for my projects. Be careful, It's maybe not uptodate of last GIT version or PSI releases... but you can test it on your RPM distrib. It should be nice to hare your feedback.
Bye,
Laurent
| Janusz Szuba wrote: |
|
Hi,
in commit 1812e7c, specifying CFLAGS to make command in elog.spec, renders all other settings in Makefile void. That is, if I want to include any of KRB5, LDAP, PAM support, and change makefile accordingly, then when producing rpm they are not taken into account. Anyway, CFLAGS in Makefile are already set to the same defaults, so why it is redefined in spec file?
best
Janusz
|
|
|
Re: bug in elog.spec, posted by Janusz Szuba on Tue Jul 7 11:22:45 2020
|
Thanks for the answer, I will try with your specfile
best
Janusz
| Laurent Jean-Rigaud wrote: |
|
Hi,
You rights, CFLAGS should not be in specfile to take care of distrib env.
Btw, I sent in the past an update for build process of Stefan delivery to generate src.rpm file copatible to tarball version. I think Stefan did not have time yet to test and to check.
With the enclosed SPEC file, you can build ELOG with options at rpmbulld command w/o modifying sources. For exemple,
rpm -i elog-.....src.rpm
rpmbuild -bb --with ssl --with pam --with ldap --with krb5 ~/rpmbuild/SPECS/elog.spec
I enclosed also the SRPMS i used for my projects. Be careful, It's maybe not uptodate of last GIT version or PSI releases... but you can test it on your RPM distrib. It should be nice to hare your feedback.
Bye,
Laurent
| Janusz Szuba wrote: |
|
Hi,
in commit 1812e7c, specifying CFLAGS to make command in elog.spec, renders all other settings in Makefile void. That is, if I want to include any of KRB5, LDAP, PAM support, and change makefile accordingly, then when producing rpm they are not taken into account. Anyway, CFLAGS in Makefile are already set to the same defaults, so why it is redefined in spec file?
best
Janusz
|
|
|
testing the client: unclear it worked, posted by Jose Caballero on Thu Jul 30 17:03:12 2020
|
Hello,
I just gave it a quick try to the command line client, to see if I can use it to access our institution service.
[root@host ~]# cd /tmp/
[root@host ~]# mkdir elog
[root@host ~]# cd elog
[root@host ~]# wget https://elog.psi.ch/elog/download/RPMS/elog-3.1.4-2.el7.x86_64.rpm
[root@host ~]# rpm2cpio elog-3.1.4-2.el7.x86_64.rpm | cpio -idmv
[root@host ~]# cd usr/local/bin/
[root@host ~]# ./elog --help
[root@host ~]# ./elog -h <hostname> -l <logbook> -u <myusername> <mypassword> -w last
"Message successfully transmitted, ID=-1"
Is that the expected output? I was expecting to see info about the latest message in the server.
Cheers,
Jose |
|
Missing log files when rsync to replacement server., posted by VUIIS SysAdmin on Thu Jul 30 17:11:05 2020
|
I am moving from a Hyper-V host to a VMware host and created a new elog server. I installed the elog software and did an rsync to get the .cfg file and logbooks to the new server.
rsync -av root@old.elog.server:/usr/local/elog /usr/local/
On the new server all of the 2020 entries are missing and there does not appear to be a 2020 logbook on either server but I can still access the 2020 entries on the old server. Where might they be and how do I get them over to the new server.
Old server says version is ELOG V3.1.4-unknown and new server says version is ELOG V3.1.4-966e3dd
Bothe servers a fully updated CentOS 7. |
|
Re: testing the client: unclear it worked, posted by Stefan Ritt on Fri Jul 31 08:34:35 2020
|
The <hostname> you have to actually replace with your real host name. Same for logbook, username and password.
On my local test system I get (actual password hidden here with "...")
~$ elog -h localhost -p 8080 -l demo -u stefan ... -a Authort=SR -a Subject=test test
Message successfully transmitted, ID=5
~$
| Jose Caballero wrote: |
|
Hello,
I just gave it a quick try to the command line client, to see if I can use it to access our institution service.
[root@host ~]# cd /tmp/
[root@host ~]# mkdir elog
[root@host ~]# cd elog
[root@host ~]# wget https://elog.psi.ch/elog/download/RPMS/elog-3.1.4-2.el7.x86_64.rpm
[root@host ~]# rpm2cpio elog-3.1.4-2.el7.x86_64.rpm | cpio -idmv
[root@host ~]# cd usr/local/bin/
[root@host ~]# ./elog --help
[root@host ~]# ./elog -h <hostname> -l <logbook> -u <myusername> <mypassword> -w last
"Message successfully transmitted, ID=-1"
Is that the expected output? I was expecting to see info about the latest message in the server.
Cheers,
Jose
|
|
|