ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
68554
|
Mon Jan 30 12:03:36 2017 |
| Lee Burnside | lee.burnside@ttu.edu | Bug report | Linux | 3.1.2 | Re: Elog crashing at random intervals |
Never mind, version from github solved issue.
Lee
Lee Burnside wrote: |
We're running Elog 3.1.2 om SL 7.2 and keep getting random crashes, sometimes when no one is accessing a logbook. The following is from /var/log/messages with debugging turned on after the latest crash.
Jan 28 12:43:56 archer elogd[9629]: POST /PHYS3305Spring2017/ HTTP/1.1
Jan 28 12:43:56 archer elogd[9629]: Received unknown cookie "ajs_anonymous_id"
Jan 28 12:43:56 archer elogd[9629]: Received unknown cookie "ajs_user_id"
Jan 28 12:43:56 archer elogd[9629]: Received unknown cookie "ajs_group_id"
Jan 28 12:43:56 archer elogd[9629]: Received unknown cookie "__utma"
Jan 28 12:43:56 archer elogd[9629]: Received unknown cookie "__utmz"
Jan 28 12:43:56 archer elogd[9629]: Received unknown cookie "elc"
Jan 28 12:43:56 archer elogd[9629]: Received unknown cookie "_ga"
Jan 28 12:43:56 archer kernel: elogd[9629]: segfault at 0 ip 000000000042237e sp 00007ffe50fcfdc0 error 4 in elogd[400000+8b000]
Jan 28 12:43:56 archer systemd: elogd.service: main process exited, code=killed, status=11/SEGV
Jan 28 12:43:56 archer systemd: Unit elogd.service entered failed state.
Jan 28 12:43:56 archer systemd: elogd.service failed.
Nothing odd in the logbooks, no real activity happening at the time of any crash. Crashes after any amount of time from 1 hour to 24 hours, with littleAny clues?
|
|
68567
|
Tue Jan 31 17:49:16 2017 |
| Christine Quicot | c.quicot@free.fr | Info | Linux | commit a6e5962 | Empty mxml directory in commit a6e5962 |
Hello,
I wonder if it's normal that in the sources files, new created mxml directory is empty.
In commit # a6e5962 4 files are deleted but not moved:
- src/mxml.c
- src/mxml.h
- src/strlcpy.c
- src/strlcpy.h
Thank you
|
68569
|
Tue Jan 31 21:29:05 2017 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Linux | commit a6e5962 | Re: Empty mxml directory in commit a6e5962 |
The mxml package has been converted into a submodule in the git repository. At http://midas.psi.ch/elog/download.html you see that you need a "--recursive" flag to clone it. If you have already checked out the sources, you need a
git submodule update --init --recursive
/Stefan
Christine Quicot wrote: |
Hello,
I wonder if it's normal that in the sources files, new created mxml directory is empty.
In commit # a6e5962 4 files are deleted but not moved:
- src/mxml.c
- src/mxml.h
- src/strlcpy.c
- src/strlcpy.h
Thank you
|
|
68572
|
Tue Feb 7 18:45:08 2017 |
| Christine Quicot | c.quicot@free.fr | Question | Linux | commit a6e5962 | Is it possible change content of the notifying mail content (attachements...) ? |
Hello all,
I would like to configure the email that is sent to notify users, when an entry is submitted:
- Is it possible to attach to the mail the files attached to the entry ?
- Is it possible to configure a string (with entry keywords) that will appear in the mail content instead of the default content ?
Thank you!
Christine
|
68573
|
Tue Feb 7 18:54:00 2017 |
| Stefan Ritt | nder stefan.ritt@psi.ch | Question | Linux | commit a6e5962 | Re: Is it possible change content of the notifying mail content (attachements...) ? |
Please look in the manual under "Email Format" and "Use Email Subject".
Christine Quicot wrote: |
Hello all,
I would like to configure the email that is sent to notify users, when an entry is submitted:
- Is it possible to attach to the mail the files attached to the entry ?
- Is it possible to configure a string (with entry keywords) that will appear in the mail content instead of the default content ?
Thank you!
Christine
|
|
68574
|
Wed Feb 8 09:34:39 2017 |
| Christine Quicot | c.quicot@free.fr | Question | Linux | commit a6e5962 | Re: Is it possible change content of the notifying mail content (attachements...) ? |
Hello,
I'm sorry but that's a part of the manual I've read many times, and I'm not interested in changing the subject of the email, but only body and attachements.
I guess that if I didn't find these answers in the manual, it's because the answer for both questions is no ?
Thank you
Stefan Ritt wrote: |
Please look in the manual under "Email Format" and "Use Email Subject".
Christine Quicot wrote: |
Hello all,
I would like to configure the email that is sent to notify users, when an entry is submitted:
- Is it possible to attach to the mail the files attached to the entry ?
- Is it possible to configure a string (with entry keywords) that will appear in the mail content instead of the default content ?
Thank you!
Christine
|
|
|
68575
|
Wed Feb 8 13:09:58 2017 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | commit a6e5962 | Re: Is it possible change content of the notifying mail content (attachements...) ? |
I'm sorry but you are only half right. The mail contenct cannot be changed. But if your email notifications are sent as HTML, they contain a 1:1 copy of the elog entry, which does not make sense to change. For the attachment to be attached to the email, you need the flags of "Email Format". The default there is 63, which means that elog attachments ARE sent as mail attachments.
Christine Quicot wrote: |
Hello,
I'm sorry but that's a part of the manual I've read many times, and I'm not interested in changing the subject of the email, but only body and attachements.
I guess that if I didn't find these answers in the manual, it's because the answer for both questions is no ?
Thank you
Stefan Ritt wrote: |
Please look in the manual under "Email Format" and "Use Email Subject".
Christine Quicot wrote: |
Hello all,
I would like to configure the email that is sent to notify users, when an entry is submitted:
- Is it possible to attach to the mail the files attached to the entry ?
- Is it possible to configure a string (with entry keywords) that will appear in the mail content instead of the default content ?
Thank you!
Christine
|
|
|
|
68576
|
Wed Feb 8 16:38:15 2017 |
| fbretel | nothx@hello.com | Bug report | Linux | 3.1.1 | Possible misuse of email headers Message-Id and In-Reply-To |
Hi,
As mentionned before, we happen to fail to receive email messages related to updates on elog entries at our site. My understanding is that the SMTP header Message-Id MUST be unique for each email message. Whereas all elogd email messages get something like <logbook>-<entryId>@<domain>. See source code. For this header to become unique, there should be a random part in it.
Having the same Message-Id in multiple email messages results in only the first one being delivered on some email systems.
Moreover, elogd sets the In-Reply-To: header in the same manner (<logbook>-<entryId>@<domain>). Which is incorrect because this header relates to email messages, not elog entries, and should contain the email Message-Id of the email message to which it replies, itself handled by the email messaing system. But elogd hasn't received any email messsage in the first place. So I believe this header should simply be dropped.
I think I can provide a pull request on bitbucket for the Message-Id issue, and probably also for the In-Reply-To: if you decide it can be removed.
Cheers |