| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
69419
|
Mon Nov 22 00:44:21 2021 |
 | Harry Martin | harrymartin772@gmail.com | Question | Linux | 3.1.2 | Re: Body of new messages not getting saved when submitted | Thank you for your quick response, Sebastion. The new version of ckeditor is 4.5.7 -- is this version compatible with elog 3.1.2? It is possible that I am using an outdated elog or outdated ckeditor due to the fact that this server is a bit old; I am looking to upgrade this machine soon, but I have several other issues to resolve first.
| Sebastian Schenk wrote: |
|
Hello Harry,
the elog server (elogd) is a standalone application written in C and contains a full webserver and logfile management system.
There are no other dependencies to apache or python.
You can use a webserver like apache or nginx in combination with elog to act as a proxy,
e.g. to handle the encryption part of the communication between your web browser and the elogd, but you don't need to.
Regarding the first part of your message:
The elog server worked normally; entries (including the text body) got saved correctly until the last update?
The only thing in your list of updates, I can think of making this problem could be the update of ckeditor as it is the text editor used by elog.
The other packages should not be related to elog... but I am not a package maintainer.
I compiled elog from source and it brings the necessary files with it.
Best wishes,
Sebastian
| Harry Martin wrote: |
|
I've been using elog for a few years now. I've had the current setup working for me up until today.
If I create a new message (entry, whatever they are called), or if I attempt to update an existing message, only the header information is saved. The body (the part I can see in the editor) does not get saved.
Yesterday, I did do some updates on the server machine. Among them was an update to apache2, but I am not using apache2 (I can disable apache2, and elogd continues serving elog on client machines). Also updated were several python3 packages; I ran into a compatibility problem with python3 with a different package, so I wonder if that could have some impact for elog also. About 50 packages were updated altogether.
Here are the packages that were updated yesterday (in case this is of interest to solving the issue):
[...]
This is a devuan ascii server only for clients on a local area network.
|
|
|
|
69420
|
Mon Nov 22 19:28:28 2021 |
| Harry Martin | harrymartin772@gmail.com | Question | Linux | 3.1.2 | Re: Body of new messages not getting saved when submitted | (disregard my recent post here about missing package -- that wasn't the elog server!)
I can see that ckeditor was upgraded 11/19, which is would be prior to my recent attempts to use elog. It was apparently a security update, so I am not sure it is sensible to downgrade. OTOH, I am the only person here, and I have all sides carefully barracaded, so I don't think it would be much of an issue. But please disabuse me of my ignorance if need be.
| Harry Martin wrote: |
|
Thank you for your quick response, Sebastion. The new version of ckeditor is 4.5.7 -- is this version compatible with elog 3.1.2? It is possible that I am using an outdated elog or outdated ckeditor due to the fact that this server is a bit old; I am looking to upgrade this machine soon, but I have several other issues to resolve first.
| Sebastian Schenk wrote: |
|
Hello Harry,
the elog server (elogd) is a standalone application written in C and contains a full webserver and logfile management system.
There are no other dependencies to apache or python.
You can use a webserver like apache or nginx in combination with elog to act as a proxy,
e.g. to handle the encryption part of the communication between your web browser and the elogd, but you don't need to.
Regarding the first part of your message:
The elog server worked normally; entries (including the text body) got saved correctly until the last update?
The only thing in your list of updates, I can think of making this problem could be the update of ckeditor as it is the text editor used by elog.
The other packages should not be related to elog... but I am not a package maintainer.
I compiled elog from source and it brings the necessary files with it.
Best wishes,
Sebastian
| Harry Martin wrote: |
|
I've been using elog for a few years now. I've had the current setup working for me up until today.
If I create a new message (entry, whatever they are called), or if I attempt to update an existing message, only the header information is saved. The body (the part I can see in the editor) does not get saved.
Yesterday, I did do some updates on the server machine. Among them was an update to apache2, but I am not using apache2 (I can disable apache2, and elogd continues serving elog on client machines). Also updated were several python3 packages; I ran into a compatibility problem with python3 with a different package, so I wonder if that could have some impact for elog also. About 50 packages were updated altogether.
Here are the packages that were updated yesterday (in case this is of interest to solving the issue):
[...]
This is a devuan ascii server only for clients on a local area network.
|
|
|
|
|
69421
|
Mon Nov 22 19:45:08 2021 |
| Harry Martin | harrymartin772@gmail.com | Question | Linux | 3.1.2 | Re: Body of new messages not getting saved when submitted | After downgrading ckeditor, my elog installation is working again. Thanks for your help.
| Harry Martin wrote: |
|
(disregard my recent post here about missing package -- that wasn't the elog server!)
I can see that ckeditor was upgraded 11/19, which is would be prior to my recent attempts to use elog. It was apparently a security update, so I am not sure it is sensible to downgrade. OTOH, I am the only person here, and I have all sides carefully barracaded, so I don't think it would be much of an issue. But please disabuse me of my ignorance if need be.
| Harry Martin wrote: |
|
Thank you for your quick response, Sebastion. The new version of ckeditor is 4.5.7 -- is this version compatible with elog 3.1.2? It is possible that I am using an outdated elog or outdated ckeditor due to the fact that this server is a bit old; I am looking to upgrade this machine soon, but I have several other issues to resolve first.
| Sebastian Schenk wrote: |
|
Hello Harry,
the elog server (elogd) is a standalone application written in C and contains a full webserver and logfile management system.
There are no other dependencies to apache or python.
You can use a webserver like apache or nginx in combination with elog to act as a proxy,
e.g. to handle the encryption part of the communication between your web browser and the elogd, but you don't need to.
Regarding the first part of your message:
The elog server worked normally; entries (including the text body) got saved correctly until the last update?
The only thing in your list of updates, I can think of making this problem could be the update of ckeditor as it is the text editor used by elog.
The other packages should not be related to elog... but I am not a package maintainer.
I compiled elog from source and it brings the necessary files with it.
Best wishes,
Sebastian
| Harry Martin wrote: |
|
I've been using elog for a few years now. I've had the current setup working for me up until today.
If I create a new message (entry, whatever they are called), or if I attempt to update an existing message, only the header information is saved. The body (the part I can see in the editor) does not get saved.
Yesterday, I did do some updates on the server machine. Among them was an update to apache2, but I am not using apache2 (I can disable apache2, and elogd continues serving elog on client machines). Also updated were several python3 packages; I ran into a compatibility problem with python3 with a different package, so I wonder if that could have some impact for elog also. About 50 packages were updated altogether.
Here are the packages that were updated yesterday (in case this is of interest to solving the issue):
[...]
This is a devuan ascii server only for clients on a local area network.
|
|
|
|
|
|
69536
|
Tue Jun 28 18:53:50 2022 |
 | Alan Grant | agrant@winnipeg.ca | Question | Windows | 3.1.2 | Slow performance | We're up to 30 logbooks, 3.2GB data total and Elog damen has now become slow. Performance stats show 100%CPU on startup then reduces. Searches and general UI activity is slow. It runs on a VM with 4GB memory allocated. Up to 15 concurrent users.
Trimming and archiving some data files may help but I gather overall this is underpowered hardware in this instance so what is recommended system requirements for a config like this? |
|
69537
|
Sat Jul 2 14:39:41 2022 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 3.1.2 | Re: Slow performance | We have 68 logbooks and currently 60 GB data total. We run it as well on a VM, in our case with 8GB RAM.
The speed of ELOG is mostly given by the filesystem: when we had AFS it was very slow. With NFS it was better. But we now use a local disk on the VM: that is much better.
If you want to have the best performance (upload of large files can still slow down all users) then I would recomment local SSD for the file system of elogd.
You might talk to your system administrator: they can likely provide a local SSD on the VM server host.
| Alan Grant wrote: |
|
We're up to 30 logbooks, 3.2GB data total and Elog damen has now become slow. Performance stats show 100%CPU on startup then reduces. Searches and general UI activity is slow. It runs on a VM with 4GB memory allocated. Up to 15 concurrent users.
Trimming and archiving some data files may help but I gather overall this is underpowered hardware in this instance so what is recommended system requirements for a config like this?
|
|
|
68209
|
Fri Dec 11 14:30:10 2015 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Windows | Other | 3.1.1-bc8310a | Re: If a Required Attribute starts with a number – No CKEditor | Hi David,
I can confirm a bug: changing the encoding does not work if you have a required attribute starting with a digit. The following minimal config reproduces the bug:
[global]
Default encoding = 1
[test]
Attributes = 7SWM
Options 7SWM = Name
Required Attributes = 7SWM
Whatever you choose as a default encoding you'll be stuck with. If you remove the "Required Attributes" it works again.
The workaround is very simple: do not use any attributes that do start with a digit :-)
Cheers, Andreas
| David Dunne wrote: |
| Hello, Is the below an issue or am I doing something incorrectly? Creating an attribute starting with a number and then including that attribute in the Required Attribute list prevents access to the CKEditior. This appears to be the case at least with FreeBSD (10.2 Rel) using Elog V3.1.0 and Windows 7 with Elog V3.1.1-3f311c5. The problem can be recreated using the Elog supplied sample config and adding the necessary attribute, sample config showing below. While attribute 7SWM is part of the Required Attributes the CKEditor fails to appear, remove 7SWM from the Required Attributes list and the CKEditor returns. [global] port = 8080 [demo] Theme = default Comment = General Linux Tips & Tricks Attributes = Author, Type, Category, Subject, 7SWM Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other Options Category = General, Hardware, Software, Network, Other Options 7SWM = Name-1, Name-2, Name-3 Extendable Options = Category Required Attributes = Author, Type, 7SWM Page Title = ELOG - $subject Reverse sort = 1 Quick filter = Date, Type Thank you, David Dunne |
|
|
Draft
|
Tue Sep 6 13:29:03 2016 |
| Daniel Sajdyk | daniel.sajdyk@gmail.com | Question | Windows | 3.1.1-3f311c5 | Hilight code | Hello :)
Is there any way to highlight code (for example php, SQL) in logs entries?
Best Regards
Daniel Sajdyk |
|
68413
|
Tue Sep 6 13:35:05 2016 |
| Daniel Sajdyk | daniel.sajdyk@gmail.com | Question | Windows | 3.1.1-3f311c5 | Highlight code? | Hello :)
Is there any way to highlight code (for example php, SQL) in elogs entries?
Best Regards
Daniel Sajdyk |
|