I have been using elog for over 10 years. Suddenly my elog installation has changed (probably from a recent update. My /etc/elogd.cfg has changed to the original demo configuration. Even after changing it to my configuration from backup none of the entries for the logbooks apper even though the tabs for the logboos are ther all logbooks are empty. I have looced at the logbook files and the entries seem to be there but are not showing on the web interface. Has something changed? Is there a new location for the logbooks and other files? Is there a change from the 32-bit to the 64-bit version that will cause this. I am running CentOS 7 fully patched and updated. Will there be a CentOS 8 compatible version?

• Use the new ViewCVS gateway. This gateway now can also directly produce tarballs for the current repository snapshot
  
• Use anonymous Subversion access:
  
  svn checkout svn+ssh://svn@savannah.psi.ch/afs/psi.ch/project/meg/svn/elog/trunk elog
  svn@midas.psi.ch's password: svn
  (you might have to enter the password several times...)
  svn checkout svn+ssh://svn@savannah.psi.ch/afs/psi.ch/project/meg/svn/mxml/trunk mxml
  svn@midas.psi.ch's password: svn
  (you might have to enter the password several times...)
  

Recently I have had problems with ELOG not accepting the certificates (in this case from https://letsencrypt.org/) probably due to the old version of the SSL library of the binary distribution for Windows.
I have tried to follow the instructions to set up ELOG to work with Apache but they are probably old.
I have a simple solution for the Apache installation of XAMPP, the example is for two separate logbooks using each its own ELOG service on the same server:

1. I have set up the two ELOG to run as http://my.server.example.com:8080/ and as http://my.server.example.com:8081/

2. in c:\xampp\apache\conf\httpd.conf I have enabled the following (I am not sure if all the modules are really needed but this works for me):

LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule headers_module modules/mod_headers.so
LoadModule proxy_html_module modules/mod_proxy_html.so
LoadModule xml2enc_module modules/mod_xml2enc.so

3. still in c:\xampp\apache\conf\httpd.conf, at the very end of the file I added the following:

ProxyRequests off

Redirect permanent /app1 https://my.server.example.com/app1/
ProxyPass /app1/ http://my.server.example.com:8080/
ProxyHTMLURLMap http://my.server.example.com:8080 /app1

Redirect permanent /app2 https://my.server.example.com/app2/
ProxyPass /app2/ http://my.server.example.com:8081/
ProxyHTMLURLMap http://my.server.example.com:8081 /app2

This way I can now connect to the two ELOG using https://my.server.example.com/app1/ and https://my.server.example.com/app2/ without troubles and no additional setting to either the configuration files of ELOG nor any need for virtual hosts, ...

I hope this might be of use.

In the past couple of days, I seem to have developed a problem with making entries into elog's displayed with Chrome (the latest, 31.0.1650.63) on 
Mac OS (10.9.1, the latest).  The problem occurs with attempting to edit or enter HTML encoded pages with fckedit; although pages render correctly 
in list mode, if you try to edit or enter an entry, the page is blank, the cursor is missing, you can't see text or type new text.  I ran elogd -v by hand, 
and there were no obvious problems, and I looked at the developer consoles in Chrome, and the only place I see any hint of what the problem might 
be is the Javascript console which says this:

event.returnValue is deprecated. Please use the standard event.preventDefault() instead.
Uncaught SecurityError: Blocked a frame with origin "http://localhost:8080" from accessing a frame with origin "chrome-
extension://pioclpoplcdbaefihamjohnefbikjilc".  The frame requesting access has a protocol of "http", the frame being accessed has a protocol of 
"chrome-extension". Protocols must match.
 fckeditorcode_gecko.js:36

It works ok in Safari, but it would be nice to use Chrome, and it was working ok until recently.  I don't think the problem occurred when I updated to 
Mac OS 10.9.1, but I don't keep careful track of the Chrome version.  It's not critical, but I pretty much exhausted what I knew how to debug.  I have 
close to the latest elog (2.9.2-2455), although I see the same phenomenon on this elog (.2.9.2-2475) and I think it's related to this thread:

http://productforums.google.com/forum/#!msg/maps/hQhwWA56NbA/2XL35dU7le4J

I tried the prescription in the October 22 entry, but it didn't seem to help, although I wasn't sure I had really tested it with compressed javascript and 
cache and what have you.

The ELOG repository has been moved from Subversion to GIT. While the old repository will be visible for some time, all new development is done on the GIT repository. To download the repository, do a

git clone https://bitbucket.org/ritt/elog.git
git clone https://bitbucket.org/tmidas/mxml.git


or access it online at https://bitbucket.org/ritt/elog/

/Stefan 

Hi,

I'd like to use ELOG as personal work logbook and database with search facilities

(e.g. record work progress, updates, plots, results, meeting schedule, outcome, TODO, etc...).

I will use it ONLY on my laptop, and I'd need to read the files when I don't have internet connection too.

I have no need to retrive files from elsewhere with a Web Browser, and I'd prefer not to open ports on the laptop.

Would this be feasible?

What's the setting I have to specify in elogd.cfg file?

Is there an example of such a ELOG use you could provide?

Thanks a lot

Sara

ELOG seems to enter a loop when you do certain opeations on certain messages: I moved a message to a different logbook and the deamon just gets stuck.

If I restart the daemon, the message was in fact moved: I can move it back to its original destination without problems.

I started in GDB and break with ctrl-C when the process gets stuck, to be told :

Program received signal SIGINT, Interrupt.
0x000000000040a968 in find_thread_head ()

I then made a core dump.

I put the files here: http://cern.ch/poulsen2/elog-error-report-110430.zip (they are too big to upload).

I get into the same problem in other circumstances such as when opening some threads (maybe because they contain "Reply-to" references to non-existing messages, but I have problems reproducing this on the test installation.

I should maybe also submit the incriminating thread.

Soren

 Hi,

I am experiencing repeated crashing of the elog daemon.

If I go into select mode while in threaded view, I can select an entire thread by selecting the top entry.

When I do so then press the Edit button, the server crashes.

I have to manually restart it. Syslog shows no error.

This does not happen under Summary or Full view.

Running Ubuntu 12.04, ELOG 2.9.2-2455

I can provide my elog.cfg if necessary.

Cheers!

Louis

P.S. i just crashed the forums ELOG following those same steps!! Sorry!! At least it was restarted in no time.