Hello Alan,

I tried with a new logbook with an attribute without "date" name, but unfortunately I got the same error. Any other suggestions?

Thanks

Still no luck. Tried your URL and still works fine for me:

Here is my full elogd.cfg:

[global]
port = 8080

[65 nm]
Attributes = Record date
Type Record date = datetime
Preset Record date = $date
List Display = Record date
Start page = ?sort=Record date

Anything else I coudl try to reproduce your error?

Ok I found it!

Was tricky. In my development environment (XCode) it worked fine. Only when I compiled elogd under Sierra on the command line, the probelm occured. That's why I did not see it earlier. It has to do with some functions Apple apparently changed ("strlcpy"). These function now have a new "functionality": When two parameters overlap, the function just aborts the process. This is specific to Sierre, so on any other Linux this does not happen. I changed now the soruce code to take care of the modified functions, and now it works fine. Please update to the newest GIT revision of elogd and recompile.

Stefan

I haven't found any reporterd issues in the forum similar yet, but it appears there is a bug in Elog when logging into logbooks. If I leave Username and Password null and click Submit the daemon crashes. We've been having this problem off and on and after some verbose logging level 3 I was drawn to these recurring lines in the log:

16-Dec-2016 18:20:22 [172.23.113.4] {SER Reports} LOGIN user "" (attempt)
16-Dec-2016 23:15:52 [] Server listening on port 8080 ..
16-Dec-2016 23:18:05 [172.23.113.4] {Daily Request Log} LOGIN user "dmorrison" (attempt)

Ups. This bug must have lingered there since the beginning of time. Funny that nobody noticed in the last ten years or so. I have fixed it in the current git revision.

Thanks for the speedy fix.

FYI, our other Elog instances which are running ealrier versions do not exhibit this problem, as I confirmed that entering null ID/password returns "Invalid Username or password" as expected. This may be why it wasn't mentioned by anyone else before. Maybe something got inadvertently dropped in the newer version.

My MacOS (10.12.2) elogd version V3.1.2 is a recent git commit (edc5e85), due to the fix to my earlier-described issue solved in the thread here: https://midas.psi.ch/elogs/Forum/68519.

I am trying to (re-)set up Mirror functionality with a linux server running the standard public (V3.1.2-bd75964).  I had initially updated the linux server so that it also had the latest git commit (edc5e85), but could then not even add new logbook entries that involved attachments to it.  I therefore rolled the linux server back to the standard public 3.1.2 version.

On the remote Mac, synchronizations usually look like they are going to work fine, with Mirror simulate = 1 switched on.  After I set Mirror simulate = 0, and if the server and remote logbook are already identical, I *occasionally* get the proper "All Entries Identical" synchronization result.  Unfortunately, this is very rare, and usually there is a failure whereby the remote (Mac) logbook decides that a significant fraction of its entries (usually sequential, from some seemingly random entry all the way up to the last entry) are missing on the linux server and need to be submitted back to the server from the remote Mac.

When the local and remote logbooks are not identical, and a record in need of synchronization contains an attachment, there is again destructive behaviour similar to that described above, except that the Mac elogd executable usually crashes.  (As in the case of the already-identical synchronizations described above, I only tested this after observing the correct expected behaviour first with Mirror simulate = 1.)

I'd be grateful for some help/suggestions.  My current testing suggests that my problems are likely not elog-content dependent.  (The logbook now undergoing synching has less than 10 entries in it.)

More generally, the issue of having things behave fine with Mirror simulate = 1, but then experiencing corruption/damage when switching to Mirror simulate = 0 seems serious to me.

Many thanks, Andreas

The attached screenshot shows the behaviour after doing a synchronization (with Mirror simulate = 1) following first having ensured that the local (Mac) and remote (linux) ELOGs initially showed "All entries identical" when doing a simulated synchronization, and then having edited local entries 9707 and 9709 by uploading (different) attachments to them.

The fact that the synchronization is suggesting to renumber two different entry IDs to the same number looks like a bug.

Best regards,

Andreas W.