The problem was resolved. I forgot to do this statement...

https://elog.psi.ch/elog/adminguide.html
Because elogd uses links to itself (for example in the email notification and the redirection after a submit), it has to know under which URL it is running. If you run it under a proxy, you have to add the line:

    URL = http://your.proxy.host/subdir/

into elogd.cfg.

After inserting the URL in elogd.cfg, elog works correctly with Reverse Proxy Setting of Apache 2.4.

Hello,

I just upgraded to elog 2.7.5 from 2.6.4 on my Debian system. Here is some feedback:

1) "make" fails if libssl-dev package is not installed. Documentation does not mention SSL library requirements.

2) /etc/init.d/elogd: line 10: /etc/rc.d/init.d/functions: No such file or directory (I fixed this by commenting
out that line).

3) Starting elogd: /etc/init.d/elogd: line 34: echo_success: command not found (Fixed by search/replace "echo_"
to "echo ").


Hope this helps.

George.

> The elogd (or elogd.init in the distribution) is written for RedHat based systems where echo_success gives the 
> typical output with a green [OK] at the end of the line. For Debian, there is (was) in principle a Debian package 
> which has it's own startup script. Since the package maintainer is not active any more (I guess), the Debian 
> updates are heavily old. Once elog gets managed inside Debian again, that should get better again, but until then 
> one has to follow 2) and 3) from above. If I would remove it, the Scientific Linux users would complain. 

That makes sense. Might be worth adding a short Debian section to the installation instructions page?

FYI, Elog is no longer in Debian as of 2008-05-12.


Thanks,

George.

Dear all,

I had some difficulty to upload large files (>20MB) with SSL connection. I think it is also related to https://elog.psi.ch/elogs/Forum/68636

During debuging, I found that, when uploading large files, ssl connection is dropped since 'SSL_read' function returns -1.

But it doesn't alway mean broken connection. It may be "SSL_ERROR_WANT_READ".

I changed the "server_loop" function in the source code to "continue" when it is SSL_ERROR_WANT_READ. And it fixed the problem.

Here is my code.

## elogd.c "server_loop" function L30031

                        if (FD_ISSET(_sock, &readfds)) {
#ifdef HAVE_SSL
                          if (_ssl_flag){
                            i = SSL_read(_ssl_con, net_buffer + len, net_buffer_size - len);
                            if(i<=0){
                              int ssl_error=SSL_get_error(_ssl_con,i);    ## check ssl error code
                              if(ssl_error==SSL_ERROR_WANT_READ||ssl_error==SSL_ERROR_WANT_WRITE) continue;    ## if ssl wants more, continue
                            }
                          }
                          else
#endif
                            i = recv(_sock, net_buffer + len, net_buffer_size - len, 0);
 

I am ignorant about networking. Some experts on ssl connection would know a better way to deal with this problem.

Best,

HyonSan Seo

How do I preset the reply date to an empty box(es)?

In 2.5.x it worked as

Preset on reply Plan Date = ""

gave me an empty date, which is what I wanted. Now in 2.6.3 I get some date in there (...1969) and have to
manually set it to empty again ?

Thanks

Does anyone know whether ELOG has limit number of entries or it can create new entries as many as it can go?  Thanks.

I have tried to set Email Format = 111 but still receiving attachments in the notification emails.  Does anyone know how to configure?  So the notification email will not include attachments.

Thanks in advance,

H. Dao

I have been using v2.6.  I works fine so far for what I need except that I could not disable the attachments in the notification emails.  Now I need to upgrade to a latest version v2.9.  However, with this latest version, I've received this error when navigate pages:  "Error: Too many parameters (> 120). Cannot perform operation".   What does this error mean?  Should I do to fix it?  I also have tested other version 2.7 and 2.8 as well.  The problem exists.