| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
69841
|
Fri Nov 15 09:55:11 2024 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | All | ELOG V3.1.5-fc6 | Re: choosing the default font ? |
Check elog/themes/default/elog.css and look for font-family.
If you just want the elog entries in monospaced font, you can swith to "plain" encoding at the bottom of the entry form. You can also make this a default (check the docu).
Stefan
| Pavel Murat wrote: |
|
Dear All,
is there a way to choose the default "style" for the HTML encoding ? - I'd like to set it to "Typewriter" but couldn't find the corresponding option in the available docs/ sample config files...
-- many thanks, regards, Pasha
|
|
|
69840
|
Wed Nov 13 18:12:34 2024 |
 | Pavel Murat | murat@fnal.gov | Question | All | ELOG V3.1.5-fc6 | choosing the default font ? |
Dear All,
is there a way to choose the default "style" for the HTML encoding ? - I'd like to set it to "Typewriter" but couldn't find the corresponding option in the available docs/ sample config files...
-- many thanks, regards, Pasha |
|
69839
|
Tue Nov 5 15:51:26 2024 |
| Dominic | dominic@nowhere.co | Bug report | Linux | Windows | Mac OSX | ELOG V3.1.5 | Re: Equation Editor does not work |
is there any update on this bug? Has anyone else observed the same problem?
| Dominic wrote: |
|
Hi!
I am not sure if this is a know issue: it seems that the equation editor does not work anymore. Is there any fix or alternative method to type latex formula in the log?
Thank you!
|
|
|
69838
|
Tue Nov 5 15:44:57 2024 |
 | Dominic | dominic@nowhere.co | Bug report | Linux | 3fb85fa6 | Re: Crash on attachment upload |
Does this issue occur only on Ubuntu systems? as I've experienced the same on my Raspberry Pi 5 running Ubuntu too ...
| jaro mrazek wrote: |
|
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
|
|
|
69837
|
Wed Sep 25 16:00:06 2024 |
| Nick Sauerwein | nick.sauerwein@luxtelligence.ai | Bug report | Linux | Windows | Mac OSX | ELOG V3.1.5 | Re: Equation Editor does not work |
We have observed the same issue. Did the CodeCogs api change?
Thanks for the help.
| Dominic wrote: |
|
Hi!
I am not sure if this is a know issue: it seems that the equation editor does not work anymore. Is there any fix or alternative method to type latex formula in the log?
Thank you!
|
|
|
69836
|
Wed Sep 25 15:02:16 2024 |
| Patrick Upson | patrick.upson@dfo-mpo.gc.ca | Question | Windows | 2.9.2 | Re: Looking for version update advice |
I ran a test (using Windows) and you're correct about the subfolder and file naming. I don't think that'll be an issue, but it's good to be aware of. If we end up having to revert to 2.9.2 for whatever reason, I think it sould still work fine if what logs we have are just copied up a directory (i.e /home/logfiles/2023/23mmdda.log ==> /home/logfiles/23mmdda.log)
The difference in the directory structure doesn't matter for my purposes.
| David Pilgram wrote: |
|
I use linux elog, and if you upgrade to v3.x.x, it's difficult to go back to v2.9.x. This is because the log files get grouped in year sub directories at v3.x.x.
In 2.9.x, the logfiles are store as (made up example) /home/logfiles/yymmdda.log
In 3.x.x they are stored as /home/logfiles/2024/24mmdda.log /home/logfiles/2023/23mmdda.log etc. I think I got the labelling of the subdirectories correct, Stefan will no doubt correct if I am wrong.
I assume the same is true for the Windows version as it would be weird for a split in the program by OS for something important but trivial to impliment for all OS.
It's a bore to sort that out if you have to revert to 2.9.x - I know, I've done it - but I don't recall any change in format in the individual yymmdda.log files with an early v3.x.x version I tried. There may be additions to the log files made in much more recent v3.1.x or so versions, but I guess you are ok with whatever they may be as you've checked the change log.
| Patrick Upson wrote: |
|
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.
|
|
|
|
|
|
69835
|
Wed Sep 25 14:21:33 2024 |
| David Pilgram | David.pilgram@epost.org.uk | Question | Windows | 2.9.2 | Re: Looking for version update advice |
I use linux elog, and if you upgrade to v3.x.x, it's difficult to go back to v2.9.x. This is because the log files get grouped in year sub directories at v3.x.x.
In 2.9.x, the logfiles are store as (made up example) /home/logfiles/yymmdda.log
In 3.x.x they are stored as /home/logfiles/2024/24mmdda.log /home/logfiles/2023/23mmdda.log etc. I think I got the labelling of the subdirectories correct, Stefan will no doubt correct if I am wrong.
I assume the same is true for the Windows version as it would be weird for a split in the program by OS for something important but trivial to impliment for all OS.
It's a bore to sort that out if you have to revert to 2.9.x - I know, I've done it - but I don't recall any change in format in the individual yymmdda.log files with an early v3.x.x version I tried. There may be additions to the log files made in much more recent v3.1.x or so versions, but I guess you are ok with whatever they may be as you've checked the change log.
| Patrick Upson wrote: |
|
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.
|
|
|
|
|
69834
|
Wed Sep 25 13:26:07 2024 |
| Patrick Upson | Tahpatrick.upson@dfo-mpo.gc.ca | Question | Windows | 2.9.2 | Re: Looking for version update advice |
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.
|
|
|