Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 798 of 807  Not logged in ELOG logo
    icon2.gif   Re: Looking for version update advice, posted by Patrick Upson on Wed Sep 25 13:26:07 2024 

Thanks. I did eveuntaully find the change log and made the decision to upgrade the at-sea machines. So far the configuration file we update for each mission still works. I have a copy of the 2.9.2 installer that if something catostrophic happens I can remove the new version and take it back, but I don't think it'll be a problem. We archive logbooks at the end of a mission, but each mission basically starts from a fresh install like state anyway.

Stefan Ritt wrote:

If 3.1.4 runs safely on your laptop, there should be no problem to update the 2.9.2 one. But first do it on a copy of your logbooks from the at-sea. The get converted automatically into a newer format but that should be transparent.

On the other hand you don't really need a new system if your old installation works fine and you don't need any of hte new features.

The changelog ist here: https://elog.psi.ch/elog/download/ChangeLog

Stefan

Patrick Upson wrote:

I've inherited a position that includes deploying elog for an at-sea mission. Once at sea there's no gauntee of internet connection so I have to be sure things are going to work before hand. The machines I currently have (we have several backup machines) are running elog version 2.9.2 and I'm looking for a change log, or feature list to determine if it's safe to update the at-sea laptops to the latest version of elog.

On one hand, I could leave things as they are and I'm sure it will just work, on the other hand, I hate seeing things get out of date to the point that something just stops working some day and there's no ability to get support for old software.

I'm already running elog 3.1.4 on my personal machine I use for configuration development and testing and it seems to work well. The config file is pretty simple and seems to work with 2.9.2 on the at-sea machines, but I don't want to run into any suprises if there ends up being a compatibility issue at sea.

 

 

    icon2.gif   Re: elog2sql - a script to convert elog logbooks to a MySQL database, posted by Pelle on Sat Apr 23 14:32:38 2011 

> > I know this thread was started 2003 but if anyone have this MySQL export script please attach it to this thread. > > Thanks, > > Pelle

 

Sorry, found it in the contribution list https://midas.psi.ch/elogs/Contributions/5

    icon2.gif   Re: Need help with permission, posted by Stefan Ritt on Mon Sep 26 12:38:29 2022 

Permissions are handled by the operating system and have nothing to do with elog. Make sure you run elog under an account which has write access to the desired directories. Consult Ubuntu documentation how to do that. Sometimes it's helpful to start elog interactively with the -v flag to see some verbose output. Maybe you can spot something there.

Stefan

Mikkel D. Lund wrote:

Hi all,

I have the same problem on Ubuntu 22.04. I have compiled from the latest tarball and copied all our logbooks from our old Ubuntu 18.04 server to a new Ubuntu 22.04. The logbooks does however not appear when I log in, so I assume ELOG doesn't have read access either?
Any hints on how to set the permissions correctly would be greatly appreciated.

Thanks,
Mikkel

Dan Witteman wrote:

Hello,

I have just installed elog onto an ubuntu focal server using <sudo make install> and I am unable to create new entries.

When I access the log via a windows PC connected to the local network, I can see the demo logbook with the 1 test post, but I cannot create or edit anything.

Attempting to post throws the error:

New entry cannot be written to directory "/usr/local/elog/logbooks/demo/"

Please check that it exists and elogd has write access and disk is not full.

 

 

Please point me in the right direction to correctly set permissions and create aditional log books.

 

Thanks,

Dan

 

 

    icon2.gif   Re: Restricting entries view by user, posted by Stefan Ritt on Thu Nov 2 11:46:42 2023 

No, this is not possible with the current version of Elog, so indeed everybody needs their own logbook.

Stefan

Leonardo Tacconi wrote:

Good morning,

I would like to ask you whether it is feasible to establish a logbook that limits access to entries, enabling each user to view only their own.
Although creating a logbook per user is an apparent solution, it does not meet my requirements.

Thank you in advance.

Leonardo

 

    icon2.gif   Re: Anyone else running elogd on redhat ES 8 having random crashes?, posted by Stefan Ritt on Wed Oct 5 08:21:12 2022 

Most likely these are some currupt logbook files. If you get a coredump (or stack trace) you can maybe figure out which file it was. These are plain ASCII files (YYMMDDa.log) and you can see with an editor if someting there is not in order.

Stefan

mathew goebel wrote:

For the last couple of months we are getting a random elogd crash once in a while we are getting something like the following in the middle of the night

> Sep 29 20:45:07 elog kernel: server_name686835]: segfault at 7ffd7f5a0000 ip 00007fceaeabbf06 sp 00007ffd7f577348 error 6 in libc-2.28.so[7fceaea8a000+1bc000]

I'm going to try and see if it will leave a coredump file, just thought I would ask if anyone else had seen this before?

Thanks,
Matt

 

 

 

 

    icon2.gif   Re: no availability of el8 and el9 rpm, posted by Stefan Ritt on Mon Feb 26 17:39:56 2024 

Many thanks for your files and instructions. I integrated this into the official elog pipeline, so now the RPMs can be downloaded from https://elog.psi.ch/elog/download.html and they will be updated automatically after each commit. If you succeed with any Debian/Ubunto I'm happy to add that. What's missing now is an easy way to compile for Windows (which I don't have anymore).

Stefan

    icon2.gif   Re: New elog version 3.1.5, posted by Antonio Bulgheroni on Fri Feb 3 20:26:46 2023 

Looking forward to the windows installer. 

Thanks a lot and keep up the good work!

 

cheers,

toto

Stefan Ritt wrote:

A new version 3.1.5 of elog has been released with all accumulated fixes over the past actually few years. I made a tar file, a RPM, but I could not compile yet a windows version.

https://elog.psi.ch/elog/download.html

Best,
Stefan

 

    icon2.gif   Re: Segfault on elog-3.1.5-1 when uploading file., posted by Stefan Ritt on Tue Jan 7 20:41:13 2025 

It is in the usual download area which is referenced at https://elog.psi.ch/elog/download.html

Stefan

Evinrude Motor wrote:

When will the new source be in the standard download area ? I'm on ubuntu .

gary holman wrote:

Thanks Stefen!

I built from source (ELOG V3.1.5-3a5f2f00) and I confirmed as fixed.
 

Stefan Ritt wrote:

Thanks to your stack trace, I found a case where a string might get overwritten, but only if the attachment file name is longer than 256 chars. I fixed the code and made a new RPM:

  https://www.dropbox.com/scl/fi/r37qx9aka5ytt3j7vn4km/elog-3.1.5-20241213.el8.x86_64.rpm?rlkey=knct99pdltggunrbmyr2hpfe5&st=pkre24aq&dl=0

Alternatively, you can compile from sources. Give it a try.

Stefan

 

 

 

ELOG V3.1.5-3fb85fa6