Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 791 of 795  Not logged in ELOG logo
IDup Date Icon Author Author Email Category OS ELOG Version Subject
  69751   Mon Mar 4 10:10:50 2024 Reply Laurent Jean-Rigaudlollspam@free.frQuestionLinux | OtherLatest versionRe: no availability of el8 and el9 rpm

Hi Stefan,

Some updates for Windows version.

I spent last WE to try to build ELOG on Windows from MSVCODE, MSCV, crosschain tool under linux etc, but in vain.

ELOG MSVC projects file are obsolete for last MS C++, and after migration, so much error or missing libs for SSL/Ldap/krb5 which should be built... I drop the sponge :-P

With mingw64 under Linux (docker/Debian), the code has also to be updated (C++11), but I don't get a build after all (also libs missing and must be built).

Finally, I can build Windows version from Windows with CygWin gcc-c++ as I did in the past. All the dependencies are available from CygWin installer. I got problems with strlcpy file missing, need to drop inlcude from elog.c and elogd.h as mxml doesn't include it anymore...

I find a Win64 CI/CD solution on AppVeyor which is free for OSS project. After creating account and add link to my ELOG test Bitbucket repo, ad new files (appveyor.yml, buildming script, update NSIS script for CygWin DDL, add tool for service), it builds automatically an elog-ver-release.exe artifact : (current build from GIT with SSL/LDAP/KRB5 available on month up to March 3, 2024 : https://ci.appveyor.com/api/buildjobs/logp7r8f0kcjq9pp/artifacts/elog-3.1.5-a720145.exe)

I installed this NSIS bundle on my PC and it's starting fine as a service.

The link info from EXE :

$ ldd /cygdrive/c/Program\ Files\ \(x86\)/ELOG/elogd.exe
        ntdll.dll => /cygdrive/c/Windows/SYSTEM32/ntdll.dll (0x7ffdb1fb0000)
        KERNEL32.DLL => /cygdrive/c/Windows/System32/KERNEL32.DLL (0x7ffdb0dc0000)
        KERNELBASE.dll => /cygdrive/c/Windows/System32/KERNELBASE.dll (0x7ffdaf950000)
        cygwin1.dll => /cygdrive/c/Program Files (x86)/ELOG/cygwin1.dll (0x7ffcedc30000)
        cygkrb5-3.dll => /cygdrive/c/Program Files (x86)/ELOG/cygkrb5-3.dll (0x3fe0a0000)
        cyglber-2.dll => /cygdrive/c/Program Files (x86)/ELOG/cyglber-2.dll (0x3fe040000)
        cygldap-2.dll => /cygdrive/c/Program Files (x86)/ELOG/cygldap-2.dll (0x3fdf20000)
        cygssl-3.dll => /cygdrive/c/Program Files (x86)/ELOG/cygssl-3.dll (0x3fd0d0000)
        cyggcc_s-seh-1.dll => /cygdrive/c/Program Files (x86)/ELOG/cyggcc_s-seh-1.dll (0x3ff1d0000)
        cygstdc++-6.dll => /cygdrive/c/Program Files (x86)/ELOG/cygstdc++-6.dll (0x3fcee0000)
        cygk5crypto-3.dll => /cygdrive/c/Program Files (x86)/ELOG/cygk5crypto-3.dll (0x3fe170000)
        cygkrb5support-0.dll => /cygdrive/c/Program Files (x86)/ELOG/cygkrb5support-0.dll (0x3fe080000)
        cygcom_err-2.dll => /cygdrive/c/Program Files (x86)/ELOG/cygcom_err-2.dll (0x3ffe90000)
        cygintl-8.dll => /cygdrive/c/Program Files (x86)/ELOG/cygintl-8.dll (0x3fe450000)
        cygcrypto-1.1.dll => /cygdrive/c/Program Files (x86)/ELOG/cygcrypto-1.1.dll (0x3ffbc0000)
        cygsasl2-3.dll => /cygdrive/c/Program Files (x86)/ELOG/cygsasl2-3.dll (0x3fd3e0000)
        cygssl-1.1.dll => /cygdrive/c/Program Files (x86)/ELOG/cygssl-1.1.dll (0x3fd170000)
        cygcrypto-3.dll => /cygdrive/c/Program Files (x86)/ELOG/cygcrypto-3.dll (0x3ff800000)
        cygiconv-2.dll => /cygdrive/c/Program Files (x86)/ELOG/cygiconv-2.dll (0x3fe540000)
        cygz.dll => /cygdrive/c/Program Files (x86)/ELOG/cygz.dll (0x3fc790000)

I will send you the files/patchs if AppVeyor could be used for Windows CI/CD in your project.

Bye,

Laurent

NB: the AppVeyor build log enclosed, need some cleanup...

 

Stefan Ritt wrote:
Laurent Jean-Rigaud wrote:

For Windows target, It's supported in Bitbucket but only with private agent :-(

So I tried to build using docker hub MSVC image (abrarov/msvc-2019) but pipeline fails to retrieve the image. Maybe I need to swipe on alternative images, or these images with MS software are unaccepted from Atlassian...

Also, I tried to crosscompiling ELOG Win32 from Linux with g++-mingw-w64-x86-64, but Makefile/sources need to be patched to manage this 'platform'... For the moment, it fails. :-(

Next solution : use Wine in Debian image to build Elog with mingwin as I know that it works (under Windows :-)). Will be tested after all...

For Windows it's more than just getting the .exe. Users want an installer. I used the Nullsoft Scriptable Installer (NSI), but I have no clue if this still works today. But there is still the elog.nsi script in the repository. Next, users want elogd as a service running in the background as a "service". I'm pretty sure the old way of doing that has changed and one would at least have to test this. Unfortunatley I switched to MacOSX about ten years ago (actually most of ELOG has been developed under Windows, but these days are gone), so I'm kind of illiterate in the Windows world now and don't have any time to change that.

Stefan

 

 

  69752   Thu Mar 7 08:55:49 2024 Question Andreas Warburtonandreas.warburton@mcgill.caBug reportMac OSX3.1.5-23df00d9Runaway bogus attachment counts in Summary view attachment column

On a new MacBook Pro (Silicon M3), I installed version 3.1.5 build 23df00d9.  The application appears to work normally, except that, after a short while, the indicated attachment count (paperclips in the attachment column of the Summary view) starts to increment fairly rapidly with each time that I visit the page.  Attachment counts appear even for records that don't have any attachments.  When I access records individually, either those with or without real attachments, everything looks OK.  Any insights as to what might be causing this, and how to correct?

Installation went smoothly using the (now longstanding) MacOS installation instructions, with one small exception: When doing the "sudo launchctl load ..." step, there is occasionally an I/O error of some kind.  (Sorry, I don't have an exact transcript of the error at the moment, but it appears to refer to line 5 of a script.)

Many thanks,

Andreas W.

  69753   Thu Mar 7 12:22:54 2024 Question iman haddadiman.haddad@espci.frQuestionWindowsV3.1.4-2e1708b5Change an entry to a reply for an other entry

Hi Everybody,

I import a logbook from csv file, with a number for laboratory's notebook, which can be use by multiple intern. I'd like to add a "reply to" when the number is the same, it's like a "move to" but in the same logbook.

Thanks in advance for your help

  69754   Fri Mar 8 13:09:31 2024 Question scottUsershiva.ps@stfc.ac.ukQuestionLinux | Other3.1.5use LDAP and elog.pwd file

Hi Members,

I have compiled and installed ELOG in Ubuntu 22.04. My ELOG version is 3.1.5 revision fc6679b. I would like to use both the password file (../logbooks/elog.pwd) and the LDAP for authentication purpose. In addition to this, new users should be able to register and existing users should be able to reset their password.

Anyone could shed some light on how to do this in the configuration file?

Thanks,
Scott

  69755   Sat Mar 9 17:04:13 2024 Reply Andreas Warburtonandreas.warburton@mcgill.caBug reportMac OSX3.1.5-23df00d9Re: Runaway bogus attachment counts in Summary view attachment column

A quick follow-up concerning the secondary matter I mentioned in my last post, namely the issues I had with the deprecated "sudo launchctl load ..." and "sudo launchctl unload ..." subcommands currently provided in the ELOG installation instructions for MacOS.  I found a solution to this -- will post it in a separate thread.

The strangely auto-incrementing attachment counts in the Summary view are still present, and I'm curious if anyone else has experienced those.  Also, I could not find a way to customize the Summary view such that the final (rightmost) column with the attachment counts can be suppressed.  That would at least put the problem out of sight until a developer can intervene and fix the bug.

Andreas Warburton wrote:

On a new MacBook Pro (Silicon M3), I installed version 3.1.5 build 23df00d9.  The application appears to work normally, except that, after a short while, the indicated attachment count (paperclips in the attachment column of the Summary view) starts to increment fairly rapidly with each time that I visit the page.  Attachment counts appear even for records that don't have any attachments.  When I access records individually, either those with or without real attachments, everything looks OK.  Any insights as to what might be causing this, and how to correct?

Installation went smoothly using the (now longstanding) MacOS installation instructions, with one small exception: When doing the "sudo launchctl load ..." step, there is occasionally an I/O error of some kind.  (Sorry, I don't have an exact transcript of the error at the moment, but it appears to refer to line 5 of a script.)

Many thanks,

Andreas W.

 

  69756   Sat Mar 9 17:14:09 2024 Reply Stefan Rittstefan.ritt@psi.chBug reportMac OSX3.1.5-23df00d9Re: Runaway bogus attachment counts in Summary view attachment column

I'm traveling right now and will only next week be able to look into that, so please be patient for a few more days.

Stefan

  69757   Sat Mar 9 17:17:02 2024 Idea Andreas Warburtonandreas.warburton@mcgill.caRequestMac OSX3.1.5Suggestion to update Mac OS X instructions in ELOG Administrator's Guide

The section of the ELOG Administrator's Guide https://elog.psi.ch/elog/adminguide.html describing how to build and install ELOG on a Mac OS X system has worked well for me for several years, even though there have been warnings that the "load" and "unload" subcommands of the "launchctl" command have been deprecated for some time.  After trying my luck again on a new Mac with the latest operating system, I encountered errors of the type "Load failed: 5: Input/output error" when attempting to follow these instructions.

After a bit of searching around, I used information at the page https://www.alansiu.net/2023/11/15/launchctl-new-subcommand-basics-for-macos/ to deploy the more current subcommands as follows:

sudo launchctl enable system/ch.psi.elogd
sudo launchctl bootstrap system /Library/LaunchDaemons/ch.psi.elogd.plist 

sudo launchctl disable system/ch.psi.elogd

Once the above can be verified, perhaps the instructions in the Administrator's Guide can be updated accordingly.

 

  69758   Sun Mar 10 04:25:43 2024 Reply Andreas Warburtonandreas.warburton@mcgill.caRequestMac OSX3.1.5Re: Suggestion to update Mac OS X instructions in ELOG Administrator's Guide

Here's a more complete/correct set of the updated commands:

sudo launchctl enable system/ch.psi.elogd
sudo launchctl bootstrap system /Library/LaunchDaemons/ch.psi.elogd.plist 

sudo launchctl bootout system /Library/LaunchDaemons/ch.psi.elogd.plist
sudo launchctl disable system/ch.psi.elogd

Cheers,
Andreas

Andreas Warburton wrote:

The section of the ELOG Administrator's Guide https://elog.psi.ch/elog/adminguide.html describing how to build and install ELOG on a Mac OS X system has worked well for me for several years, even though there have been warnings that the "load" and "unload" subcommands of the "launchctl" command have been deprecated for some time.  After trying my luck again on a new Mac with the latest operating system, I encountered errors of the type "Load failed: 5: Input/output error" when attempting to follow these instructions.

After a bit of searching around, I used information at the page https://www.alansiu.net/2023/11/15/launchctl-new-subcommand-basics-for-macos/ to deploy the more current subcommands as follows:

sudo launchctl enable system/ch.psi.elogd
sudo launchctl bootstrap system /Library/LaunchDaemons/ch.psi.elogd.plist 

sudo launchctl disable system/ch.psi.elogd

Once the above can be verified, perhaps the instructions in the Administrator's Guide can be updated accordingly.

 

 

ELOG V3.1.5-fe60aaf