Max Logbooks for Email notify, posted by Oliver Kleinau on Wed Apr 8 11:40:27 2015
|
Hi,
we've got 109 logbooks in Elog. Whenever I set a notify for all logbooks in configuration menu it is limited to 73 entrys. After saving the changes the rest of the entrys are cut off.
I've already searched in the sourcecode if I can find some limitation for that but without success.
When I change the password file by hand, it is working as long as I don't change anything in the configuration that rewrites the file.
Regards,
Oliver
|
Re: Max Logbooks for Email notify, posted by Oliver Kleinau on Fri Apr 10 08:37:19 2015
|
It seems to be the GET buffer of the elog-Server. The GET statement is cut off after &sub_lb72=1&sub_ eg. 1000 chars.
| Oliver Kleinau wrote: |
|
Hi,
we've got 109 logbooks in Elog. Whenever I set a notify for all logbooks in configuration menu it is limited to 73 entrys. After saving the changes the rest of the entrys are cut off.
I've already searched in the sourcecode if I can find some limitation for that but without success.
When I change the password file by hand, it is working as long as I don't change anything in the configuration that rewrites the file.
Regards,
Oliver
|
|
|
Re: Max Logbooks for Email notify, posted by Oliver Kleinau on Fri Apr 10 09:59:42 2015
|
It was str variable in function process_http_request in elogd.c.
This should have the size of received buffer.
PROBLEM SOLVED!!!
| Oliver Kleinau wrote: |
|
It seems to be the GET buffer of the elog-Server. The GET statement is cut off after &sub_lb72=1&sub_ eg. 1000 chars.
| Oliver Kleinau wrote: |
|
Hi,
we've got 109 logbooks in Elog. Whenever I set a notify for all logbooks in configuration menu it is limited to 73 entrys. After saving the changes the rest of the entrys are cut off.
I've already searched in the sourcecode if I can find some limitation for that but without success.
When I change the password file by hand, it is working as long as I don't change anything in the configuration that rewrites the file.
Regards,
Oliver
|
|
|
User based theme selection , posted by Oliver Kleinau on Thu Sep 3 07:09:33 2015
|
| Hi,
is it somehow possible to use different themes for different users?
Perhaps editing the password XML file?
Thanks,
Oliver |
|
Re: automated email notification did not work for me, posted by Oliver Kirsebom on Thu Oct 17 14:23:06 2013
|
| Stefan Ritt wrote: |
|
| Jianglai Liu wrote: |
|
Hi,
I am setting up an elog to organize my lab activities. I installed elog 2.8.0 on the latest CentOS 5.5, 32 bit. I got into trouble setting up the automated email notification.
According to the elog manual, I setup the smtp setting in the elogd.cfg as follows:
SMTP host = smtp.gmail.com
SMTP username = jianglai.liu
I then used "elogd -t" to encode the password into the configuration file.
But when I submit an entry, I always received: "Error sending Email via "smtp.gmail.com": 5.7.0 Must issue a STARTTLS command first. y17sm867489wfd.15"
If I switched to use my university email servers, similar things happened.
SMTP host = smtp.sjtu.edu.cn
SMTP username = jianglai.liu
I got "Error sending Email via "smtp.sjtu.edu.cn": 5.7.8 Error: authentication failed: another step is needed in authentication"
I also switched to use one of my old work server
SMTP host = smtp-server.its.caltech.edu
SMTP username = jliu
and ended up with the same error message.
I did a google search on this without much progress. I would appreciate it very much if someone could shed light on how do I fix this.
Thanks much!
|
elog only supports basic authentication, not TLS or SSL. These days more and more SMTP servers require this however. I will put this on my to-do list. In meantime you can maybe configure your CentOS machine acting as an SMTP server, and then not using TLS or SSL there. That's what most people do.
|
Hi, has this problem been fixed? (i.e does ELOG now support TLS or SSL?) Thanks, Oliver |
|
elog editor loses all text, posted by Kontantin Olchanski on Wed Aug 4 23:46:34 2010
|
I just typed a long text into this elog, clicked "submit" and it bombed with "you must select an Icon", returned me to the editor with all my text gone gone gone. I do not want to select icons, I just want to report a problem with elog. Well, 2 problems, now.
K.O.
|
|
elog keeps recreating preview .png files?, posted by Kontantin Olchanski on Wed Aug 4 23:52:08 2010
|
Hi, I rsync an elog database from CERN to TRIUMF every few months and I notice that rsync keeps copying preview files (xxx.png.png, xxx.gif.png, etc) from very old entries. I guess that elogd creates these files from scratch each time they are needed, overwriting any previously existing preview files. This creates extra rsync network traffic and rsync takes longer to complete. Is there any way to avoid this? K.O.
|
Incomplete SSL proxy instructions, insecure result., posted by Konstantin Olchanski on Fri Mar 22 19:41:31 2013
|
The instructions for securing elogd using an SSL proxy are incomplete.
http://midas.psi.ch/elog/adminguide.html#secure
http://midas.psi.ch/elogs/contributions/11
If you follow these instructions, elogd will still listen for and accept non-SSL connections on it's own TCP port bypassing the SSL proxy.
(True, the elogd TCP port number is somewhat secret, so there is some security-by-obscurity here).
To secure the elogd TCP port against connections that bypass the SSL proxy, elogd has to be started
with the "-n localhost" command line options.
To add this option, one has to edit /etc/init.d/elogd. I do not know if this change will be lost when the elog rpm package is updated.
It would be better if this option could have been specified through elogd.conf.
The "-n" command line option is not documented here
http://midas.psi.ch/elog/adminguide.html#config
but is visible if you run "elogd -h".
P.S. Even with "-n localhost", users of the local machine can bypass the SSL proxy.
K.O. |