| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67102
|
Mon Aug 15 11:36:02 2011 |
 | Kester Habermann | kester.habermann@gmail.com | Bug report | Other | 2.9.0 | SEGV after upgrade from 2.7.8 to 2.9.0 | Hello,
We've been using ELOG 2.6.5 to 2.7.8 for 4 years without any major problems.
Recently we upgraded to version 2.9.0 and since we've had the daemon frequently crash with SEGV.
I've detached debugging output from one time when ELOG the crashed. We've had many crashes
it was a different logbook each time. Platform is Solaris 10 5/08 on SPARC.
Has anyone else experienced problems with 2.9.0?
Best Regards
Kester
|
| Attachment 1: elog-2.9.0-dbx.txt
|
signal SEGV (no mapping at the fault address) in show_elog_list at line 19781 in file "elogd.c"
19781 message_id = msg_list[index].lbs->el_index[msg_list[index].index].message_id;
(dbx)
(dbx) list
19781 message_id = msg_list[index].lbs->el_index[msg_list[index].index].message_id;
19782
19783 if (filtering) {
19784 status = el_retrieve(msg_list[index].lbs, message_id, date, attr_list, attrib, lbs->n_attr, text,
19785 &size, in_reply_to, reply_to, attachment, encoding, locked_by);
19786 if (status != EL_SUCCESS)
19787 break;
19788
19789 /* apply filter for attributes */
19790 for (i = 0; i < lbs->n_attr; i++) {
(dbx) print index
index = 0
(dbx) where
=>[1] show_elog_list(lbs = 0x1180200, past_n = 0, last_n = 0, page_n = 0, default_page = 1, info = (nil)), line 19781 in "elogd.c"
[2] interprete(lbook = 0xffbd89f8 "Galileo-Coord", path = 0xffbd8648 ""), line 27213 in "elogd.c"
[3] decode_get(logbook = 0xffbd89f8 "Galileo-Coord", string = 0xffbfe896 ""), line 27253 in "elogd.c"
[4] process_http_request(request = 0x13a4eb8 "GET /Galileo-Coord/", i_conn = 1), line 28001 in "elogd.c"
[5] server_loop(), line 28926 in "elogd.c"
[6] main(argc = 5, argv = 0xffbffb8c), line 29947 in "elogd.c"
(dbx) print n_msg
n_msg = 49
(dbx) print *msg_list
*msg_list = {
lbs = 0x1195dd0
index = 1667786092
string = "\001\017��-D"
number = 0
in_reply_to = 0
}
(dbx) print msg_list[index].lbs->el_index[msg_list[index].index].message_id
dbx: cannot access address 0x18da195b00
(dbx) print ms(dbx) [index].lbs->el_index[msg_list[index].index].message_id
(dbx) print msg_list[index].lbs
msg_list[index].lbs = 0x1195dd0
(dbx) print msg_list[index].lbs->el_index
msg_list[index].lbs->el_index = (nil)
(dbx) pr(dbx) g_list[index].lbs->el_index
(dbx) print *msg_list[index].lbs
*msg_list[index].lbs = {
name = ""
name_enc = ""
data_dir = ""
top_group = ""
el_index = (nil)
n_el_index = (nil)
n_attr = 0
pwd_xml_tree = (nil)
}
(dbx) print msg_list[1].lbs
msg_list[1].lbs = (nil)
(dbx) print msg_list[2].lbs
msg_list[2].lbs = (nil)
(dbx) print msg_list[3].lbs
msg_list[3].lbs = (nil)
(dbx) exit
|
|
68173
|
Fri Oct 30 18:20:22 2015 |
 | Kester Habermann | kester.habermann@gmail.com | Bug report | All | 3.1.1 | restrict edit time and autosave | Hello,
When using restrict edit time together with autosave, there is the following problem: The counter for restrict edit time seems to start after the autosave. If the time is up, it is no longer possible to submit the report.
It is also not possble to edit old drafts if restrict edit has elapsed since the creation of the save.
Autosave is definitively a nice new feature. However, I think it would be better if the counter for restrict edit time only started after the "submit" of the report and allowed edits to drafts no matter how old they are. As it is one needs to either set a really high value for restrict edit time or turn off autosave.
The issue seems to be related to: https://midas.psi.ch/elogs/Forum/68103
Regards
Kester
|
|
68897
|
Mon Feb 25 17:03:50 2019 |
 | Kester Habermann | kester.habermann@gmail.com | Bug report | Linux | 3.1.4-1 | elogd hangs on self referencing log entry | Hello,
Somehow when replying to a log entry, a log entry was created that was referring to itself. How this happened, I have no idea. The effect was that each time this enty was loaded, the elogd started to hang, going to 100% load and not responding to any http requests anymore. This problem can be reproduced by manually creating such a self-referencing log entry (see attachment). The problem entry that leads to the crash can be made by editing any elog entry and adding a line "Reply to: X" and a line "In reply to: X" where X is the MID of this entry.
1) Maybe it is possible to add a check when writing files that ensure, that is a log entry does not reference itself.
2) Maybe when loading files are preparing the thread view, elogd can detect cycles and abort.
|
| Attachment 1: 011108a.log
|
$@MID@$: 1
Date: Thu Nov 08 18:37:57 2001
Reply to: 1
In reply to: 1
Author: Stefan Ritt
Type: Routine
Category: General
Subject: Welcome
Attachment:
Encoding: ELCode
========================================
[B]Congratulations for installing ELOG sucessfully!
[/B]
This is a demo entry to ensure the elogd server is working correctly.
Click [I]"New"[/I] to add new pages and [I]"Delete"[/I] to delete this page.
|
|
67180
|
Thu Feb 2 16:51:32 2012 |
| Kenneth Nielsen | k.nielsen81@gmail.com | Question | Linux | 2.9 | Migrate to elog | Hallo and thanks for a great program.
At my work we have previously been using another program (Rednotebook) for our lab journals, but now we wish to migrate to elog because it is more configurable and because it runs in a browser.
We would off course like to move all of our old log entries with us. Luckily Rednotebook uses a standard module (YAML) for data storage, so I can easily access the data (e.g. with python) and I have already done do, and I have exchanged the native markup with html.
Now I would prefer it if I can make the elog data files directly, in stead of using the elog command, because that makes it possible and easy to revert the change, and also to not have to handle escaping html string before feeding them to elog on the commandline. I have actually already written the program that produces the elog data files, but now I have a few questions:
1) Is there an overall way of validating the datafiles, to make sure elog doesn't choke on them at some point in the future when I try to open one of the old entries. Along the same lines, does elog parse all the files when the demon is started, so if it starts then I'm ok?
2) What exactly are the requirements for the HTML content
2a) Will any valid html do, or are there some speciel requirements (e.g. like at blank lines)
2b) Does it require a particular version of html, because then I could at least validate it against that doctype beforehand
3) Is there a log from elog where I can see if it encounters something it doesn't like?
I hope the you can answer some of my questions.
Regards Kenneth |
|
66693
|
Sun Jan 24 18:00:11 2010 |
 | Kenneth McFarlane | kenneth.mcfarlane@hamptonu.edu | Comment | Windows | 2.7.8 | first install comments | I am testing Elog for personal and group use. I am starting with a Windows install on a PC. (I came across Elog when doing a shift on ATLAS at CERN.)
It took me some time to discover how to access a local logbook and create a new one. I suggest adding short sections in a prominent place in the guides:
User guide:
"Accessing a logbook: To access a logbook, point your Web browser at the appropriate URL. The default for a local Elog is http://localhost:8080/logbookname. Logbook files are stored in directory logbookname which is a sub-directory of the logbook root directory, defined by the administrator. See the administrator guide on how to create a new logbook."
Admin guide:
"Creating a logbook: A logbook is created in three steps: 1) The logbook root directory is defined as an option of the elogd start command; 2) A sub-directory, of the logbook root directory, named logbookname is created; and 3) The elogd.cfg file is edited to define the logbook's attributes and options. No files are created in the sub-directory; that is done when entries are made."
Regards,
Ken McF |
|
65681
|
Tue Jan 8 22:30:45 2008 |
 | Kenneth Andersson | kenneth.h.andersson@telia.com | Question | Windows | V2.7.0-196 | Re: Summary view - Umlauts |
| |