Large log file size, posted by Alan Grant on Mon Aug 30 03:08:15 2021
|
Can the size of the application log file affect performance? |
|
Log4j exploit, posted by Alan Grant on Tue Dec 14 19:16:57 2021
|
Is there any potential impact/concern with the Log4j exploit in Elog applications?
|
|
Slow performance, posted by Alan Grant on Tue Jun 28 18:53:50 2022
|
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? |
Re: FCKeditor not active, posted by Alain Hugentobler on Wed Apr 2 01:27:20 2008
|
| Kevin O'Sullivan wrote: |
|
I'm using ELOG version 2.7.3-2058 and have been trying to get FCKeditor to work. This, to my understanding from the documentation, is supposed to be a part of elog by default after version 2.7.0 and from looking at the configuration syntax manual, it looks as though FCKeditor should be on with the default settings. I done nothing to turn it off and none of the obvious fixes seem to do anything. I've posted the text of my configuration file below, what did I do wrong?
|
Got the same problem, solved by manually unzipping "scripts/fckeditor.zip" from the sources to the installation directory (/usr/local/elog/scripts)
A better solution is to modify the Makefile :
@unzip -q -f scripts/fckeditor.zip -d $(ELOGDIR)/scripts/
which doesn't work on my Ubuntu 8.04; however changing to:
@unzip -q scripts/fckeditor.zip -d $(ELOGDIR)/scripts/
does... |
|
Trouble with Find and Conditional attributes, posted by Adam Fairbrother on Thu Apr 28 22:38:00 2016
|
I seem to be having some trouble with Find when using conditional attributes.
when I change the primary attribute in the find field, the corrispnding secondary attribute dosn't refresh properly with the list of values.
I am able to use the conditional options as expected when creating a new logbook.
I am using version ELOG V3.1.1-0767eb0 running on debian wheezey (compiled from sid sources) |
|
Re: Trouble with Find and Conditional attributes, posted by Adam Fairbrother on Thu Apr 28 22:54:08 2016
|
This may be due to how I have my config file setup
Example:
Attributes = A, B
Options B = Please Select A
Options A = One{1}, Two{2}
{1} Options B = 1, 2,
{2} Options B = 3, 4,
| Adam Fairbrother wrote: |
|
I seem to be having some trouble with Find when using conditional attributes.
when I change the primary attribute in the find field, the corrispnding secondary attribute dosn't refresh properly with the list of values.
I am able to use the conditional options as expected when creating a new logbook.
I am using version ELOG V3.1.1-0767eb0 running on debian wheezey (compiled from sid sources)
|
|
|
Re: Trouble with Find and Conditional attributes, posted by Adam Fairbrother on Fri Apr 29 20:37:04 2016
|
Uppon closer inspection, removing the option to preset the secondary attribute as a Option list dosn't do anything for the find page.
This:
Attributes = A, B
Options A = One{1}, Two{2}
{1} Options B = 1, 2
{2} Options B = 3, 4
Still fails to set attribute B to a option list on the find page.
| Adam Fairbrother wrote: |
|
This may be due to how I have my config file setup
Example:
Attributes = A, B
Options B = Please Select A
Options A = One{1}, Two{2}
{1} Options B = 1, 2,
{2} Options B = 3, 4,
| Adam Fairbrother wrote: |
|
I seem to be having some trouble with Find when using conditional attributes.
when I change the primary attribute in the find field, the corrispnding secondary attribute dosn't refresh properly with the list of values.
I am able to use the conditional options as expected when creating a new logbook.
I am using version ELOG V3.1.1-0767eb0 running on debian wheezey (compiled from sid sources)
|
|
|
|
Attribute substitution in email configuration, posted by Adam Blandford on Wed Jan 18 02:22:44 2006
|
In the logbook config file I am not able to use attribute substitution in the <string> tag forUse Email Heading = <string> Attribute substitution does work however forUse Email Subject = <string> e.g.Use Email Subject = ELOG $logbook entry; $Category: $Subject will result in an email subject of: "ELOG Forum entry; Bug Report; Attribute substitution in email configuration"
Use Email Heading = A new entry has been submitted by $long_name on $remote_host on $date will result in an email heading of: "A new entry has been submitted by $long_name on $remote_host on $date"
Not sure if this functionality is intended or is a bug. An comment/feedback/suggestion would be appreciated. |