I improved the mentioned check for inline attachments. Now your page correctly shows both attachments. This fix is in SVN revision 2241. 

Hi,

I'm trying to synchronize an elog in my computer with my personal elog in my institute's server. The two elogd.cfg files are necessarily different since the elog in my institute is for many people's elogs, so I'm not completely sure this is supposed to work.  

I've copied the configuration of my (remote) elog into my local elogd.cfg file, and added in the global section of the local file:

Mirror server = https://www.pp.rhul.ac.uk:8080/

Mirror Config = 1

Mirror cron = 0 7-19 * * 0-5

Mirror user = ricardo

Password file = [my password file]

Then I relaunched my local elogd demon and tried both to synchronize the local elog and to wait for the cron job to do it. When I try to synchronize the "ATLAS Trigger" elog I get in the browser:

"Safari can’t open the page “https://localhost:8080/ATLAS+Trigger/?cmd=Synchronize” because Safari can’t establish a secure connection to the server “localhost”"

(the local elog is in https://localhost:8080/ATLAS+Trigger/)

When I wait for cron to update from the mirror this is what I get in the log:

28-Jul-2009 18:51:09 [] SSLServer listening on port 8080 ...

28-Jul-2009 18:50:00 [] Cron job started

28-Jul-2009 18:50:00 [] {ATLAS Trigger} MIRROR: Remote server is not an ELOG server

Yepp. Synchronizing over SSL does not yet work. I have it on my to-do list since quite some time, but can't find the time to implement it. So at the moment you have to synchronize without SSL. 

 Hi,

Ok, to see if I understand. You mean setting SSL = 0 in my cfg file and leaving the rest as it is, right? Then I synchronize by hand and I guess I'll be prompted for the password. Perhaps I should remove my local password file to avoid that the password is send unencrypted?

Cheers,

Ricardo

That's correct. The password will be sent unencrypted if you get prompted, but if you use the automatic scheme the password will be encrypted (but not the logbook entries of course). But your concerns are right, running this thing not over SSL is a bad thing these days...

 Ok, thanks a lot! I'll try asap and report back.

Cheers,

Ricardo

Unfortunately I only got 1/2 hour to go back to this... I was trying to avoid copying the whole remote elog server from 20 people (that's what I get with the automatic cloning, right?)

So, I set SSL=0 and removed the password file, but still got the same result. Then I looked in the code a bit, and can see that the problem happens in retrieve_remote_md5(...) in the lines:

   p = strstr(text, "ELOG HTTP ");
   if (!p) {
      if (isparam("debug"))
         rsputs(text);
      sprintf(error_str, loc("Remote server is not an ELOG server"));

in elogd.c, where I see text is filled by retrieve_url()

So what seems to fail is that retrieve_url() gets back a string from the remote server which doesn't include the string "ELOG HTTP ". But I don't know what that really means. Here is what I get if I try:

bash-3.2$ /usr/local/sbin/elogd -v -m -p 8080 -c /usr/local/elog/elogd.cfg -D

I get the following output:

Indexing logbook "ATLAS Trigger" in "/usr/local/elog/logbooks/ATLAS Trigger/" ... 

Config [ATLAS Trigger],                           MD5=1FAE83FC1D3B920AFDB3DC5F49C25FAF

Entries:

  ID   1, 090728a.log, ofs     0, thead, MD5=8D8E44C14FCFA9E2FC24CEC14E60D5ED

After sort:

  ID   1, 090728a.log, ofs     0

ok

Indexing logbook "Top physics and SLT" in "/usr/local/elog/logbooks/Top/" ... 

Config [Top physics and SLT],                           MD5=C6A82A4BD6FF708BFDA3EA8719ECE48C

Found empty logbook "Top physics and SLT"

Indexing logbook "Trigger Slices and Core SW" in "/usr/local/elog/logbooks/Slices/" ... 

Config [Trigger Slices and Core SW],                           MD5=316B8D7A8FBA661518FD61D3BAC39F3C

Entries:

  ID   2, 090727a.log, ofs     0, thead, MD5=AA8B0B0972718F9BD95F5BA89E70DD97

  ID   3, 090727a.log, ofs  3870, thead, MD5=A69E46D18074A59C4445B72EE72F025D

  ID   4, 090727a.log, ofs  8354, thead, MD5=0DC3AF86F2A88ACD76E766FA1AA08665

  ID   5, 090730a.log, ofs     0, thead, MD5=59299CDFA98983EB33EC08CF1A8FF7C0

  ID   6, 090730a.log, ofs 10120, thead, MD5=0039C61DA667AA36D06A5772F8E3D0FA

After sort:

  ID   2, 090727a.log, ofs     0

  ID   3, 090727a.log, ofs  3870

  ID   4, 090727a.log, ofs  8354

  ID   5, 090730a.log, ofs     0

  ID   6, 090730a.log, ofs 10120

ok

Retrieving entries from "https://www.pp.rhul.ac.uk:8080/ATLAS Trigger"...

Remote server is not an ELOG server

Your problem is here. I wrote that synchronization is not possible through SSL, but you try to access https://www.pp.rhul.ac.uk:8080 which is SSL (because you have https:// not http://).