| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67218
|
Thu Mar 29 13:01:17 2012 |
 | leen smit | leen.smit@gmail.com | Info | Linux | All | ELOG V2.9. | RSS Feed |
| Hi All,
Just a quick message in the hope of helping other find an answer to the question: How to reach the RSS Feed???
I spend hours trying to find out what the correct URL is to reach the feed. The documentation on this is non-existent - at least we could't find this anywhere in the docs.
Answer: Just add elog.rdf at the end of the URL of the logbook!!
eg. http://midas.psi.ch/elogs/Forum/elog.rdf
Leen |
|
67219
|
Thu Mar 29 13:01:26 2012 |
| leen smit | leen.smit@gmail.com | Info | Linux | All | ELOG V2.9. | RSS Feed |
Hi All,
Just a quick message in the hope of helping other find an answer to the question: How to reach the RSS Feed???
I spend hours trying to find out what the correct URL is to reach the feed. The documentation on this is non-existent - at least we could't find this anywhere in the docs.
Answer: Just add elog.rdf at the end of the URL of the logbook!!
eg. http://midas.psi.ch/elogs/Forum/elog.rdf
Leen |
|
67221
|
Thu Mar 29 15:38:43 2012 |
 | leen smit | leen.smit@gmail.com | Info | Linux | All | ELOG V2.9. | Re: RSS Feed |
I've just tested with Firefox, Chromium and IE, but no such icon appears. And for me this icon doesn't really help at all, as I'm using the feed to parse the logs
Besides, there is no mention of this Addon in the documentation, so the problem is still there: there is no easy way to find the feed URL.
|
|
68553
|
Sat Jan 28 22:23:46 2017 |
 | Lee Burnside | lee.burnside@ttu.edu | Bug report | Linux | 3.1.2 | Elog crashing at random intervals |
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?
|
|
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?
|
|
|
66360
|
Thu May 14 14:26:36 2009 |
 | larbi benouahi | lbenouahi.2008@gmail.com | Bug report | Windows | 2 | can't send form |
Hi,
when i try to send a form after edit or create an entry i got this message : Connection closed by remote server
is there any idea
thanks |
|
1778
|
Thu Mar 23 14:49:07 2006 |
| Lars Jorgensen | lars.jorgensen@jppol.dk | Request | Linux | | Re: implement 'hide attribute' and 'sort attribute' |
> > Only the sorting (of the entry mask!) is missing! :)
>
> Ok, I put that on my wish list. So once the second or third person asks for it, I will
> implement it (;-)
I'm asking! :-)
I have a few Extendable Options attributes, and it would be extremely nice if they got sorted as users put them
in. So that when you select the drop-down box, alle options are sorted.
Lars |
|
65656
|
Sat Nov 24 03:16:46 2007 |
| lance | lance1.hayward@yahoo.com | Info | Windows | ELOG V2.7. | Message ID and trouble ticketing system |
I am trying to create a trouble ticket system however when you do a reply you get a new message ID. I was hoping to use the message ID as a ticket number and just wanted to use the reply as an append to the orginal message id, however each reply creates a new message id. This would be a nightmare to track and if I closed the ticket I would have to close every log entry related to this.
Does anyone know how to either make the reply and appended reply (appended to the orignal message id) or how to create a field that automatically gives it a new trouble ticket number.
Has anyone configured a trouble ticket system that I could look at to get some ideas?
Thanks,
Lance |