> I get the following compiler warnings about sprintf() buffer overflows. I suggest sprintf() should be replaced by std::string msprintf() from 
> midas. K.O.

I started to convert some sprintf() to snprintf(), but I still have 824 cases to go... Ideally, all should be converted to std::string. Will be some job for my retirement ;-)

Stefan

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

Currently have multiple logbooks hosted with elogd. One book is having an issue with Categories. The user regulary uses the category filtering to see one subject for the whole month. This past week it hasn't been working properly. When choosing a drop down category to filter there are not logs found. I've notice the fields under the categories change randomly. Sometimes it would add a % sign where there should be --. Some other fields go from displaying -- Subject -- to just the dashes, thats when the filtered eLogs do not show. Clearing out the erroneous characters can eventually load the specified logs. Has anyone else seen this? Should I just upgrade the system and hope for the best?

PS. while writing this I was able to mitigate the issue by removing the troubled fields from the quick filter section. I'm pretty sure this will not be an issue for my end user but any input is appreciated.

Hi all,

Quick question -- I was wondering if the current Windows Binary/Installer is now compiled for compatibility for Windows 11?  

I did look through the Forum, but the the answer wasn't really clear.  

Thanks!
Frank B.

I have the same problem with Ubuntu 24 on a Raspberry Pi system; it crashed whenever I uploade an attachment.  Thanks!

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.

I am on ubuntu 24.04.1, I needed to git clone, make and make install,

HEAD is 3fb85fa6 - (HEAD -> master, origin/master, origin/HEAD) Fixed compiler warning (3 weeks ago)

It crashes on every attachment:  thank you. Jaro

root@vaio:~# systemctl status elogd
× elogd.service - The ELOG Server
     Loaded: loaded (/usr/lib/systemd/system/elogd.service; enabled; preset: ena>
     Active: failed (Result: core-dump) since Thu 2024-09-12 10:39:23 CEST; 3s a>
   Duration: 5.402s
       Docs: man:elogd(8)
             man:elog(8)
    Process: 724285 ExecStart=/usr/local/sbin/elogd -D -c /usr/local/elog/elogd.>
   Main PID: 724286 (code=dumped, signal=ABRT)
        CPU: 32ms

Sep 12 10:39:18 vaio systemd[1]: Starting elogd.service - The ELOG Server...
Sep 12 10:39:18 vaio elogd[724286]: elogd 3.1.5 built Sep 11 2024, 17:02:36
Sep 12 10:39:18 vaio elogd[724286]: revision 3fb85fa6
Sep 12 10:39:18 vaio elogd[724286]: File "/var/run/elogd.pid" exists, overwritin>
Sep 12 10:39:18 vaio systemd[1]: Started elogd.service - The ELOG Server.
Sep 12 10:39:18 vaio elogd[724286]: CKeditor detected
Sep 12 10:39:18 vaio elogd[724286]: ImageMagick detected
Sep 12 10:39:18 vaio elogd[724286]: Server listening on port 9000 ...
Sep 12 10:39:23 vaio systemd[1]: elogd.service: Main process exited, code=dumped>
Sep 12 10:39:23 vaio systemd[1]: elogd.service: Failed with result 'core-dump'.
root@vaio:~# systemctl restart elogd
 

Hello,

I'm trying to create config file for simple incident logbook. It should has 3 attributes:

1. source (source of incident) with options: 
   1. email
   2. jira_id
   3. ezd_id
2. Tactics (from MITRE but for simplicity I wrote only this):
   1. aaa,
   2. bbb,
3. Technics (also from MITRE but also for simplicity I wrote only this):
   1. tactics1, tactics2,
   2. tactics3, tactics4

And this is not working.

For me it looks that choosing first attribute - Source - causes problems, because after that I cannot choose third - Technics - attribute.

When I will start filling attributes from the second - Tactics - then Technics options are avaiable. 

Below is config file:

Theme = default
Page Title = ELOG - $Theme

Attributes = Source, Technics, Tactics

Options Source = Email{a}, Jira{b}, EZD{c}
{a} Attributes = Source, Adres_email, Technics, Tactics
{b} Attributes = Source, JIRA_ID, Technics, Tactics
{c} Attributes = Source, EZD_ID, Technics, Tactics

Options Technics = aaa{1}, bbb{2}
{1} Options Tactics = tactics1, tactics2
{2} Options Tactics = tactics3, tactics4

Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Source, Technics, Tactics

I will appreciate any help.

Best Regards