| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
69409
|
Thu Nov 4 13:48:00 2021 |
 | David Stops | djs@star.sr.bham.ac.uk | Question | Linux | elog-3.1.4-2 | Re: results of security scan | Thanks, I'll try that and see what happens
David
| Stefan Ritt wrote: |
|
The elgod.c progarm itself is rather weak in SSL, since I just don't have time to catch up with the latest SSL enhancements. The safest you can do is to put an industry-strenth web server like Apache in front of elogd and let that server handle the SSL layer.
Stefan
| David Stops wrote: |
|
Recently central IT scanned our elog server and reported the following "vulnerabilities"
- 42873 (1) - SSL Medium Strength Cipher Suites Supported (SWEET32)
- 51192 (1) - SSL Certificate Cannot Be Trusted
- 65821 (1) - SSL RC4 Cipher Suites Supported (Bar Mitzvah)
- 85582 (1) - Web Application Potentially Vulnerable to Clickjacking
Is there any easy way of preventing these
Thanks and Best Wishes
David
|
|
|
|
69249
|
Sun Oct 25 06:26:49 2020 |
 | Daniel Kohl | dkol@yaani.com | Question | Linux | Windows | Mac OSX | All | Other | 3.1.4 | MEG style elog configuration | Hello,
I'm new to elog software and I could not find a solution to my configuration issue. I would like to setup a configuration file similar to MEG experiment's elog.
https://elog.psi.ch/elogs/meg/
I'm interested in creating similar to the structure: "General", "Collaboratoin", "Sub-groups (with sub-sub groups "Software", "Hardware" etc). I cannot tell if this was created by using Top Group feature.
Can someone explain how this design structure can be achieved?
Thanks,
Daniel |
|
66854
|
Thu Jul 22 00:31:54 2010 |
| David McKee | dmckee@phys.ksu.edu | Question | All | 2.7 | What *exactly* do "clone" and "mirror" do? | We have been hosting logbook far (geographically and in internet hops) from our experimental site. Recently we have (finally!) gotten reliable on-site internet, and would like to host the log book on-site.
I have a suspicion that some combination of the -C, -m, and -M flags will allow me to migrate the logbook automagically and with a minimum risk of trouble from concurrent operation on the logbook, and to maintain the existing version as a mirror of the new official on-site version. But documentation is not being very helpful. Can someone say a few more words about what these options do?
I've been experimenting as I compose this and have a suggestion for language that might be useful somewhere in the documentation:
In this context "to clone" means to copy the configuration file and all data files associated with a log book so that I can host an identical logbook on a new host (that is this is the command to migrate a logbook). After cloning the two installation are identical, but no effort is made to keep them so: if you continue to run both copies post made to one will not be reflected in the other.
Is this correct?
I'm still not clear on what the -m and -M options do. |
|
66984
|
Fri Jan 14 00:07:01 2011 |
 | JacekK | doctor99@poczta.onet.pl | Bug report | All | 2.8.0 | New entries are not visible from other logbooks based on the same logbook dir through Subdir | Hi,
I have two logbooks based on the same data directory through "Subdir" option and when I add new
entry in one logbook, then that entry is not visible in other logbook.
I suppose it is a bug in el_submit function, where I think the new message should be added to
message index of every logbook based on the same data directory as the one, where the message was physically
created.
There is a piece of code, which I think should do this automatically
/* if other logbook has same index, update pointers */
but it seems the other logbooks does not have the same index.
I'm new to elog and the sources are also new to me, so my guess to the ground of the problem may be wrong.
Let me know is this bug possible to fix in near future.
Best regards,
Jacek |
|
66246
|
Wed Mar 11 11:28:27 2009 |
| Dominique Bolla | dominique.bolla@synchrotron-soleil.fr | Bug report | Linux | V2.7.5-214 | Elogd crash | Hello,
Please could you help me.
We have 2 elog servers synchronized every minute via Elog mirroring function.
2 or 3 times a week, the slave crashes and we have to restart Elogd. I have found in /var/log/messages the same message every time elogd crash :
xmalloc: not enough memory
Thanks.
Dominique Bolla. |
|
67669
|
Thu Feb 27 15:15:55 2014 |
| Donald | don.drummel@gmail.com | Question | Windows | 2.9.2-2475 | XML import Error | Hi
I've written a powershell script parse a html table that contains old log book data that i would like to import to a elog book. I've attached a example of the output.
When i attempt a import i get this error
"XML file does not contain <ENCODING> element"
The file does contain an encoding for utf-8 I've tried converting the xml to ANSI and ISO-8859-1 encodings but i get the same error.
is there something obvious that I'm missing?
here is the config of the log book:
[WLTST]
Theme = default
Comment = Test Logbook
Attributes = Author, Object, Action
Comment Author = Username
Comment Action = What
Comment Text = Why
Required Attributes = Author, Object, Action, Text
Page Title = Test Logbook
Reverse sort = 1
Quick filter = Date, Type |
| Attachment 1: new__2.xml
|
<?xml version="1.0" encoding="UTF-8"?>
<ELOG_LIST>
<ENTRY>
<MID>
2
</MID>
<DATE>
2014-02-24 22:28
</DATE>
<OBJECT>
Archived Client:
</OBJECT>
<ACTION>
Archived Client:
Archived Client to Manual_Archive and took a full backup of it
</ACTION>
<TEXT>
ticket: 123456
Decommission of client.
</TEXT>
<AUTHOR>
bob
</AUTHOR>
</ENTRY>
<ENTRY>
<MID>
3
</MID>
<DATE>
2014-02-20 20:15
</DATE>
<OBJECT>
Added client:
</OBJECT>
<ACTION>
Added client:
Added client to VMware policy
</ACTION>
<TEXT>
Ticket 1919191
New DHCP server needed to be backed up.
</TEXT>
<AUTHOR>
bob
</AUTHOR>
</ENTRY>
</ELOG_LIST>
|
|
67671
|
Tue Mar 4 19:48:02 2014 |
| Donald | don.drummel@gmail.com | Question | Windows | 2.9.2-2475 | Re: XML import Error |
| Andreas Luedeke wrote: |
|
| Donald wrote: |
|
Hi
I've written a powershell script parse a html table that contains old log book data that i would like to import to a elog book. I've attached a example of the output.
When i attempt a import i get this error
"XML file does not contain <ENCODING> element"
The file does contain an encoding for utf-8 I've tried converting the xml to ANSI and ISO-8859-1 encodings but i get the same error.
is there something obvious that I'm missing?
here is the config of the log book:
[WLTST]
Theme = default
Comment = Test Logbook
Attributes = Author, Object, Action
Comment Author = Username
Comment Action = What
Comment Text = Why
Required Attributes = Author, Object, Action, Text
Page Title = Test Logbook
Reverse sort = 1
Quick filter = Date, Type
|
Hi Donald,
yes, the import function gave me some headache in the past, too.
⇄
English (auto-detected) » English
Here it appears that <ENCODING> </ENCODING> became somehow mandatory. But it has a different meaning then what you expect: it is the type of code in the text field, one out of HTML, ELCode or plain.
(Stefan: is this needed to be mandatory? Couldn't you just have some default ?)
In your case: you can just add the XML code "<ENCODING> </ENCODING>" before the <TEXT> token.
My problems were always related to the date format: elogd is very restrictive about what date format it is accepting. that will be your next pproblem ;-)
I hope this helps.
|
Hi Andreas
That worked, thank you so much. now I'm on to a new error.
Now every time i try to do the import it crashed the elogd.
OS is windows server 2008 R2. I have the elogd installed as a service.
here is the even log:
Faulting application name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Faulting module name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Exception code: 0xc0000417
Fault offset: 0x000682da
Faulting process id: 0x558
Faulting application start time: 0x01cf37d8870fc9a1
Faulting application path: D:\Program Files (x86)\ELOG\elogd.exe
Faulting module path: D:\Program Files (x86)\ELOG\elogd.exe
Report Id: defc3f39-a3cb-11e3-9dd5-005056954c86
I have attached the Data file I'm using to generate the fault every time. same config as before. Any Ideas?
|
| Attachment 1: new__2.xml
|
<?xml version="1.0" encoding="UTF-8"?>
<ELOG_LIST>
<ENTRY>
<MID>
2
</MID>
<DATE>
2014-02-24 22:28
</DATE>
<OBJECT>
Archived Client:
</OBJECT>
<ACTION>
Archived Client:
Archived Client to Manual_Archive and took a full backup of it
</ACTION>
<ENCODING>plain</ENCODING>
<TEXT>
ticket: 123456
Decommission of client.
</TEXT>
<AUTHOR>
bob
</AUTHOR>
</ENTRY>
<ENTRY>
<MID>
3
</MID>
<DATE>
2014-02-20 20:15
</DATE>
<OBJECT>
Added client:
</OBJECT>
<ACTION>
Added client:
Added client to VMware policy
</ACTION>
<ENCODING>plain</ENCODING>
<TEXT>
Ticket 1919191
New DHCP server needed to be backed up.
</TEXT>
<AUTHOR>
bob
</AUTHOR>
</ENTRY>
</ELOG_LIST>
|
|
67677
|
Tue Mar 11 15:17:36 2014 |
| Donald | don.drummel@gmail.com | Question | Windows | 2.9.2-2475 | Re: XML import Error |
| Donald wrote: |
|
| Andreas Luedeke wrote: |
|
| Donald wrote: |
|
Hi
I've written a powershell script parse a html table that contains old log book data that i would like to import to a elog book. I've attached a example of the output.
When i attempt a import i get this error
"XML file does not contain <ENCODING> element"
The file does contain an encoding for utf-8 I've tried converting the xml to ANSI and ISO-8859-1 encodings but i get the same error.
is there something obvious that I'm missing?
here is the config of the log book:
[WLTST]
Theme = default
Comment = Test Logbook
Attributes = Author, Object, Action
Comment Author = Username
Comment Action = What
Comment Text = Why
Required Attributes = Author, Object, Action, Text
Page Title = Test Logbook
Reverse sort = 1
Quick filter = Date, Type
|
Hi Donald,
yes, the import function gave me some headache in the past, too.
⇄
English (auto-detected) » English
Here it appears that <ENCODING> </ENCODING> became somehow mandatory. But it has a different meaning then what you expect: it is the type of code in the text field, one out of HTML, ELCode or plain.
(Stefan: is this needed to be mandatory? Couldn't you just have some default ?)
In your case: you can just add the XML code "<ENCODING> </ENCODING>" before the <TEXT> token.
My problems were always related to the date format: elogd is very restrictive about what date format it is accepting. that will be your next pproblem ;-)
I hope this helps.
|
Hi Andreas
That worked, thank you so much. now I'm on to a new error.
Now every time i try to do the import it crashed the elogd.
OS is windows server 2008 R2. I have the elogd installed as a service.
here is the even log:
Faulting application name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Faulting module name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Exception code: 0xc0000417
Fault offset: 0x000682da
Faulting process id: 0x558
Faulting application start time: 0x01cf37d8870fc9a1
Faulting application path: D:\Program Files (x86)\ELOG\elogd.exe
Faulting module path: D:\Program Files (x86)\ELOG\elogd.exe
Report Id: defc3f39-a3cb-11e3-9dd5-005056954c86
I have attached the Data file I'm using to generate the fault every time. same config as before. Any Ideas?
|
Anyone have any luck reproducing the error? or have suggestions on how to fix it? |
|