| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68789
|
Wed Apr 18 12:30:51 2018 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 3.1.1 | Re: Email Config |
SMTP host = ...
as written in the documentation!
Automatic email after expiration is not possible.
| Stefan Werler wrote: |
|
Hi,
I´m new in ELOG,
Can u explain me how i config the Mailing?
in my Configuration i do have not the ability to set an Email Host/Server. or i didn´t find it....
I have to use ELOG as ticket system, is it possible to send an email automatically after expiration of a period?
|
|
|
68790
|
Wed Apr 18 13:18:07 2018 |
 | Stefan Werler | stefan.werler@ah-senden.de | Comment | Windows | 3.1.1 | Re: Email Config |
many thanks
| Stefan Ritt wrote: |
|
SMTP host = ...
as written in the documentation!
Automatic email after expiration is not possible.
| Stefan Werler wrote: |
|
Hi,
I´m new in ELOG,
Can u explain me how i config the Mailing?
in my Configuration i do have not the ability to set an Email Host/Server. or i didn´t find it....
I have to use ELOG as ticket system, is it possible to send an email automatically after expiration of a period?
|
|
|
|
68791
|
Wed Apr 18 13:43:36 2018 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 3.1.1 | Re: Email Config |
SMTP host = ...
MUST be set in the [global] section of your configuration - it will likely not work when you try to set it for a specific logbook.
I don't see how ELOG can send an automatic email after a date expired.
But you could set-up a script that checks for expired entries, and if there are any it'll send out an email. You can use any http connection to do the query using the find command (e.g. curl).
To get the right URL, just make the find from the web form and copy the URL that gives you the desired result.
Hope that helps.
Andreas
| Stefan Werler wrote: |
|
Hi,
I´m new in ELOG,
Can u explain me how i config the Mailing?
in my Configuration i do have not the ability to set an Email Host/Server. or i didn´t find it....
I have to use ELOG as ticket system, is it possible to send an email automatically after expiration of a period?
|
|
|
1877
|
Thu Jul 13 15:25:44 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.6.1-1681 | Re: 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. |
|
65936
|
Wed Jul 30 10:06:57 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.73-1.exe | Re: Elogd.exe crashes almost everyday |
| jh wrote: |
|
My Elog running on windows 2003 sp1 is crashing with this error " Faulting application elogd.exe, version 0.0.0.0, faulting module elogd.exe, version 0.0.0.0, fault address 0x00061330." the version of elogd.exe is has a built date of 2/22/2008. Will upgrading to the latest windows binary resolve this issue? Thanks!!
|
I would give it a try! |
|
445
|
Sun Oct 26 17:04:59 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.3.9 | Re: Elogd.exe Crashes When There are too Many Replies to Replies... |
> We have been using Elog successfully as a shiftlog book for over a month
> now, but I recently ran into an annoying bug, I think.
> We had a thread that was created and was being replied to over several
> days. We first replied to the original thread and then each subsequent
> reply was a reply of the previous reply. When the thread reached above 13
> of these, the elogd.exe would crash everytime a user attempted to select
> the logbook that contained the enormous thread.
> I found the only workaround was to manually delete the offending entry
> from the log file and to instruct my users to not reply to replies unless
> absolutely necessary. I have been able to replicate this error across the
> rest of my logbooks as well. If there is any more information you may
> need, please feel free to contact me.
Sorry my late reply, I was pretty busy these days...
I tried to reporduce your problem, but without success. Have a look at
http://midas.psi.ch/elogdemo/Linux/32
where I replied 20 times producing a very long thread without any problem. So
can you reproduce your problem? I suspect that there was some other problem,
since the number of replies is internally not limited in any way. If you
again get into a situation where elodg.exe crashes on the *DISPLAY* of some
message, you can send me the offending file xxxxxxa.log directly by email and
I can analyze it. Only if I can reproduce a problem, I can fix it.
- Stefan |
|
448
|
Tue Nov 11 13:49:50 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.3.9 | Re: Elogd.exe Crashes When There are too Many Replies to Replies... |
I found a stack overflow if there are too many replies. This has been fixed in
the current CVS verson of elogd.c and will be incorporated into the next release. |
|
456
|
Fri Nov 21 07:59:50 2003 |
| Christopher Jones | cjjones@zombieworld.com | Bug report | Windows | 2.3.9 | Re: Elogd.exe Crashes When There are too Many Replies to Replies... |
> I found a stack overflow if there are too many replies. This has been fixed in
> the current CVS verson of elogd.c and will be incorporated into the next release.
Many thanks for your quick reply to this issue. I have also noticed that when
moving a log entry that contains as few as 4 replies to replies with the "Move to"
command that the elog server will crash. I ran into this issue many times when I
created a new logbook and was trying to move some of the longer threads into it.
Please let me know if you would like me to send some sample entries from our
logbook that illustrate this.
Thanks,
Chris |