| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
326
|
Wed May 7 17:27:51 2003 |
 | Kevin Ellwood | kevin_ellwood@yahoo.com | Question | | | Re: |
> > I have upgraded elog from version 2.2.4 to 2.3.6 and then entry "Number
> > Attachments =" is not being read. Looking at the changelog, I found that
> > "Number Attachments" has been removed in favor of "enable attachments". I
> > tried looking in the documentation but I can't find a discription of the way
> > in which multiple attachments are handled. Can someone give me a pointer?
>
> Just upload one attachment at a time by hitting the "Upload" button, your
> message text stays there. Once you are finished, hit "Submit". Sorry, I
> thought this would be obvious, since most providers use this for their mail
> web interface.
No need to say sorry. It is probably obvious to pretty much everyone. -- It
the story of my life.
Thanks
Kevin |
|
66041
|
Tue Nov 11 16:45:04 2008 |
 | Kester Habermann | kester.habermann@gmail.com | Bug report | Other | 2.7.5 | elogd dies after receiving second SIGHUP |
elogd continues to run after a SIGHUP. If a second SIGHUP is received the daemon terminates.
This was observed on Solaris 10 (SPARC).
The documentation states that elogd should re-read configuration after receiving SIGHUP. |
|
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.
|
|
68144
|
Thu Oct 15 12:32:19 2015 |
| kenzo Abrahams | kenzoabrahams@gmail.com | Question | Linux | 3.1.1 | How does one create a html template for an entry |
Good Day
I am new to elog and have a question. This is best explain with an example. If I have two logbooks named "home" and "work" and I would like all the entries of home to be of a specific html format (for example a table containing
a set amount of rows and columns) and work can be any plain text entry how would I go about doing this? I saw the documentation mention something about html templates but i cant seem to find the section about where they are stored
or how they are created and applied to a specific logbook. I know how to restrict the entry encoding to either html, elcode or plain text for a logbook. Any help would be appreciated.
Regard
Kenzo Abrahams |
|
68149
|
Mon Oct 26 11:06:46 2015 |
| kenzo Abrahams | kenzoabrahams@gmail.com | Question | Linux | 3.1.1 | Logging entries from the command line |
Good Afternoon
Im trying to automatically post an entry using information saved in a text file. I have followed the example in the users guide but i always seem to get a error message saying transmission failed. Lets say for instance I have a user named John and his password is Blue and he wants to log into a logbook called home from a textfile the command im using to log a message from the file is
elog -h localhost -p 8080 -u John Blue -l home -a Author=John -m textfile
I cant seem to figure out why i keep getting this error message. I even tried deleting the password file because i thought it might be an authentication issue.
Can anybody assist me please it would be much appreciated.
Regards |
|
68150
|
Mon Oct 26 11:16:54 2015 |
| kenzo Abrahams | kenzoabrahams@gmail.com | Question | Linux | 3.1.1 | Re: How does one create a html template for an entry |
> > Good Day
> >
> > I am new to elog and have a question. This is best explain with an example. If I have two logbooks named "home" and "work" and I would like all the entries of home to be of a specific html format (for example a table containing
> > a set amount of rows and columns) and work can be any plain text entry how would I go about doing this? I saw the documentation mention something about html templates but i cant seem to find the section about where they are stored
> > or how they are created and applied to a specific logbook. I know how to restrict the entry encoding to either html, elcode or plain text for a logbook. Any help would be appreciated.
> >
> > Regard
> > Kenzo Abrahams
>
> So-called "custom" entry/view forms are a bit for experienced people. You should be fluent with HTML and JavaScript. The (minimal) documentation is here: https://midas.psi.ch/elogs/Forum/66909
>
> If you want a table style input form, better use Google Spreadsheets.
>
> Stefan
Thank you Stephan this really helped me. |