Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 12 of 41  Not logged in ELOG logo
Category:Info
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  65750   Thu Feb 21 08:04:50 2008 Reply Stefan Rittstefan.ritt@psi.chInfoWindowsELOG V2.7.Re: Message ID and trouble ticketing system

Richard Ecclestone wrote:

 

I tried the 'Preset ticket = TCK-#####' method to create unique numbers for our application. This worked very nicely until we replied to a earlier message, if we then create a new message the system creates a sequential number after the last message number we replied to. For example if we have 10 messages. If someone replies to message number #2 then when a new record is created it is then assigned number #3 not #11, thus making a duplicate entry for #3.

 Any ideas?


Yes. If you want this feature to work also for replies, you have to put following into your config file:

Preset ticket = TCK-#####
Preset on reply ticket = TCK-#####
  65777   Fri Mar 7 14:29:00 2008 Reply Stefan Rittstefan.ritt@psi.chInfoWindowsELOG V2.7.Re: Message ID and trouble ticketing system

Stefan Ritt wrote:

Richard Ecclestone wrote:

 

I tried the 'Preset ticket = TCK-#####' method to create unique numbers for our application. This worked very nicely until we replied to a earlier message, if we then create a new message the system creates a sequential number after the last message number we replied to. For example if we have 10 messages. If someone replies to message number #2 then when a new record is created it is then assigned number #3 not #11, thus making a duplicate entry for #3.

 Any ideas?


Yes. If you want this feature to work also for replies, you have to put following into your config file:

Preset ticket = TCK-#####
Preset on reply ticket = TCK-#####

When I was browsing this forum about my previous problem, I found 
this thread. A ticket number that applies to all entries in a 
thread, but is unique to that thread.

But I have the same problem as Richard Ecclestone reported, and the
"Preset on reply ticket" line from your reply has not had any effect.

It appears that on starting a new thread (which is to have that
ticket number), the ticket number is just incremented by one from
that of the previous (as in previous ID number) entry.  This is
fine if each thread is completed before a new one started, but if
there are more than one active thread, which can be progressed
further in any order, new threads are likely to be issued with a
ticket number which has already been issued (see Richards's example).

An alternative source of unique numbers would be the Entry number (as
in "696 Entries", top right of the midas.psi.ch/elogs/Forum page),
which would be the seed for the ticket number on new entry.  Not sure
of the syntax for that, or for the replies to have *that* number for
the config file.  I know there is a problem if you move a number of
threads away, but the only alternative (that I can think of) is to
store the seed number somewhere, and increment it every time a new
thread is started.

Or have I got something wrong here? 
Thanks.

Regards,

David.

  65778   Fri Mar 7 14:45:02 2008 Reply Stefan Rittstefan.ritt@psi.chInfoWindowsELOG V2.7.Re: Message ID and trouble ticketing system

David wrote:

When I was browsing this forum about my previous problem, I found this thread. A ticket number that applies to all entries in a thread, but is unique to that thread. But I have the same problem as Richard Ecclestone reported, and the "Preset on reply ticket" line from your reply has not had any effect. It appears that on starting a new thread (which is to have that ticket number), the ticket number is just incremented by one from that of the previous (as in previous ID number) entry. This is fine if each thread is completed before a new one started, but if there are more than one active thread, which can be progressed further in any order, new threads are likely to be issued with a ticket number which has already been issued (see Richards's example).

An alternative source of unique numbers would be the Entry number (as in "696 Entries", top right of the midas.psi.ch/elogs/Forum page), which would be the seed for the ticket number on new entry. Not sure of the syntax for that, or for the replies to have *that* number for the config file. I know there is a problem if you move a number of threads away, but the only alternative (that I can think of) is to store the seed number somewhere, and increment it every time a new thread is started.

Or have I got something wrong here? Thanks. Regards, David.

I cannot reproduce your problem. Assume we have following config file:

[demo]
Theme = default
Attributes = Ticket, Author, Subject
Preset Ticket = TCK-####

The the first entry gets TCK-0001. Any reply to that stays with TCK-0001. Then I do another "new" entry, which gets TCK-0002. Even if I then do another reply to the first thread, that will just stay with TCK-0001. So avoid using 'Preset on reply Ticket". The post from Richard was different, he wanted a new number also for replies (if I understand correctly).

  65779   Fri Mar 7 20:42:39 2008 Reply Stefan Rittstefan.ritt@psi.chInfoWindowsELOG V2.7.Re: Message ID and trouble ticketing system

Ok, now I got the point, also Richard had the same problem. Assume we have 10 threads, and thus ticket numbers 1-10. Now we get a reply to #2, which then pops up to the top of the list. A new message increments the top entry of all entries, and then wrongly gives a new #3, instead of #11.

I fixed this in SVN revision 2073, where elogd searches all logbook entries for the largest index, then increments this one by one. The fix will be contained in the next release.

  66055   Mon Nov 17 11:42:46 2008 Reply Stefan Rittstefan.ritt@psi.chInfoLinux2.7.5Re: Installation problems
> I'm actually using elog on Debian and have been rolling my own ".deb" for a while now (starting with the old 
Debian
> Maybe you could add the Debian /etc/init.d/elog script to the "contrib"
> directory, with a suitable note in the README or something like that? That script has not changed in a long 
time and
> is still functional - and doing so would make it easier for people who would like to install elog on a Debian 
(or
> Debian-based, e.g. Ubuntu) system. I'll attach the script.

The problem is not putting this into the "conrib" area, but supporting it. Since I don't have a Debian system, 
may I suggest that you put it yourself into the elog:Contributions/ logbook. If people then get problems in the 
future, they can contact you directly ;-)
  66212   Wed Feb 18 20:14:04 2009 Reply Stefan Rittstefan.ritt@psi.chInfoWindows2.7.5Re: How to share with others

 

Nuruzzaman wrote:

Please tell me how to share my elog with people.

 

 Connect your PC to the internet and tell everybody the URL. Make sure the Windows Firewall allows remote access.

  66281   Thu Mar 26 17:30:23 2009 Idea Stefan Rittstefan.ritt@psi.chInfoAll2.5.7-2187Email notifications not working properly

 I just found out that email notifications only worked for the first 50 users of this forum. So if you registered only recently, you might not have received any notification. This was a bug inside elogd which I hope to have fixed now (this entry notification will show...). If you get the first notification and do not want this, log in to the ELOG Forum, click on "Config" and remove the checkmarks from the logbooks you do not want to get notifications.

  66399   Mon Jun 15 16:44:35 2009 Reply Stefan Rittstefan.ritt@psi.chInfoWindowsV2.7.6-219Re: Dropdown boxes and Moptions

Arno Teunisse wrote:

Hello

I have a config file  :

Attributes = Author, Author Email, Category, Customer, server,HPSD_ID, Cust_ID ,Subject ,  Change Window
; which fields will be shown !!
List display = ID,Author, Category, Customer, server, HPSD_ID, Cust_ID,Subject ,  Change Window

Type Change Window  = datetime
# Type Change Window End = datetime
Options Category = Network , Server ,
Options Customer = Arag{A}, Frieslandbank{B}, Super de Boer{C}, NRE{D}

{A} Options server = arag-lin1,arag-lin2,arag-lin3,arag-lin4, arag-lin5, arag-lin6, arag-lin7
{B} Options server = rc1upas02, rc1upas22,rc1upas03,rc1upas04,rc1uptsm01,rc1upas07,rc1upas08
{C} Options server = xia61031,xia61032 ,xia61033,xia61034,xia61035,xia61036,xia61037,xia61038,xia61039,xia61040,xia61032 ,xia61033,xia61034,xia61035,xia61036,xia61037,xia61038,xia61039,xia61040
{D} Options server = server27,server32,server34 ,server37,server38,server40
Extendable options = Category , Customer,server
Required Attributes = server , customer, Subject, Change window Begin , Change Window End
 

This works OK, However when I change the {A} Options  to {A} Moptions in the above code i get an error which tells me that a required field is not selected. So, with the pull down it works, with Moptions ( select boxes )  it will say that a required field is not selected.  Any hints ?

regards Arno

Thanks for reporting this bug. I fixed it in SVN revisoin 2213. 

ELOG V3.1.5-3fb85fa6