Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 222 of 801  Not logged in ELOG logo
ID Date Icon Authordown Author Email Category OS ELOG Version Subject
  1877   Thu Jul 13 15:25:44 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.6.1-1681Re: Elogd.exe crashes on windows

Tim Fowler wrote:
I have elog setup to send emails based on the priority of one of the attributes. When a new entry is created, the emails are sent successfully, however if the entry is edited or if you changed the attribute, elogd.exe will crash with a memory access error.

I have tried this and received the same results on different computers and different versions on Elog down to versions 2/6.0 beta 5. (it works correctly in that version).

The attribute in question is setup something like below:

Attributes = Ticket #, Site, Shift, Type, Area, System Name, Description, Priority, Status, Total Down Time, Last Revision

...(omitted config)

Options Priority = High, Medium, Low

...(omitted config)

Use Email Subject = $Site -- $System Name $Description
Use Email From = testuser@myexample.com

;Send email if priority is set to high
Email Priority High = testuser2@myexample.com

Display Email recipients = 1
Email Format = 14


This problem has now been fixed in version 2.6.2.
  1880   Sat Jul 15 17:58:46 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.6.2-1702Re: astonished icon

Elaine Cristina Franchini dos Anjos wrote:
Hi Stefan,

I've been trying to use the astonished icon, but the preview or entry
display shows only a broken image.

I found in the elogd.c at line 5556 :
{"8o", "<img src=\"%sicons/eek.png\">"}

I copied the "astonished.png" to "eek.png" and it worked.

Is it the reason of the problem ? ?)


Actually the C code should be "astonished.png" instead of "eek.png". I changed that in revision 1704. BTW, thanks for the Brazilian translation. Astonished
  1883   Mon Jul 17 13:49:37 2006 Reply Stefan Rittstefan.ritt@psi.chCommentLinux2.6.2-1706Re: Duplicate of a reply should be a reply

Gerald Ebberink wrote:
Hello everybody

This weekend I found that if I duplicate a reply it does not become a reply it self.
Is this on purpouse?
I have been through the source a little (not much time for that) and I can not find a reason where the "in reply to" value is dropped.

Could anyone give me an pointer?


This is on purpuse. The Duplicate functionality is ment to "clone" an existing entry, to save some typing work if an existing entry contains most of what one wants in a new entry. If one duplicates a reply, it is detached from the original thread, so there is not entry to attach the duplicate to. I guess you want to make a new reply to an existing entry, and then have another existing reply as a template for that, but this is not possible. If I would not drop the "in reply to" value, the duplicate would point to the wrong entry.
  1885   Wed Jul 19 12:35:16 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux Re: Use Email From = <string>

Dimitrios Tsirigkas wrote:
My users have complained about the multiple "I'm away from xxx until xxx" automated replies that they get when they post an entry and notifications are sent with their email in the "From" field.


Yes, I had the same problem with this forum.


Dimitrios Tsirigkas wrote:
Is there a way to override that default and always use the setting of the option Use Email From?


Sure. You override the default by setting the Use Email From. In the forum I set it now to Use Email From = noreply@psi.ch which is a nonexisting address. While now this is ok, our former email server did not accept this because the user noreply does not exist at our institute. So you have to figure out if this works at CERN.
  1889   Wed Aug 9 19:40:42 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionWindowsV2.6.2-169Re: Retain original ELOG id when moving an entry to an archive weblog

Fergus Lynch wrote:
We have a number of weblogs where we regular archive off 'completed' entries to a separate archive weblog:

Is it possible to retain the original ELOG id when moving an entry to an archive weblog, or have a locked field which holds the original id which we could subsequently reference in the archive?


First of all, a reference to the original ELOG entry would not help if it's moved into another logbook (archive). Keeping the id is not possible technically, since it severs as a kind of primary key, which must be unique etc. There is however the possibility to create a "secondary" ID, using the Preset xxx = ### functionality. The attribute xxx will have increasing numbers just like the primary ID. You even can combine this with the current year or month (see documentation). The problem now is how to reference such an entry. You cannot just type elog:123 as this only references the primary ID. You would have to do a "hidden" search such as

http://midas.psi.ch/elogs/Forum/?xxx=###

where ### is your secondary id. This will of course be slower because if you click on such a reference, your whole archive will be searched for.
  1892   Sun Aug 13 11:15:49 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.6.2Re: Cannot get email to work at all, configuation problem?

Checker Anderson wrote:
I an new to elog and the only thing I cannot seem to configure correctly is my SMTP information. Here is a sample of my config file:

SMTP host = checkeranderson.com
SMTP username = Checker@realchecker
SMTP Password = eWFod2Vo

I host my own mail server which uses authentication and my password was set using -t on the command line. With SMTP host = I have tried smtp.checkeranderson.com (which is how my mail program puts it) and mail.checkeranderson.com which is how my DNS server has it. The user name and password are correct. When I edit or reply to any topic I get the message "Error sending Email via "checkeranderson.com"" I have struggled with this for hours and I know I must be missing something that would be obvious to anyone else. Can anyone help me?


Start the ELOG server manually in a DOS box with the "-v" flag, like

> cd \Program Files\ELOG
> elogd.exe -v

(you first might have to stop the elog service via "net stop elogd"). Now you see all communication between the browser and elog and between elog and the SMTP server. If you now try to send an email, you will see the detailed error information returned by your SMTP server.
  1897   Tue Aug 15 13:04:21 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.2Re: Substitutions in "Email all" do not work

Ben Shepherd wrote:
Email All = $Cc


Substitution was not enabled for email addresses, but I added this for you. It's in SVN revision 1712 if you build elog yourself from the SVN, otherwise it will be contained in the next release.
  1899   Tue Aug 15 13:09:18 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.2Re: Substitutions in "Email all" do not work

Ben Shepherd wrote:

Stefan Ritt wrote:

Ben Shepherd wrote:
Email All = $Cc


Substitution was not enabled for email addresses, but I added this for you. It's in SVN revision 1712 if you build elog yourself from the SVN, otherwise it will be contained in the next release.


Great! Thanks very much. And quick too! Any idea when the next release will be available? Is there a mailing list I can sign up to to get notifications?


You are on the mailing list Wink, there is only this list. But you can check out the SVN version as described in the documentation.
ELOG V3.1.5-3fb85fa6