Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 744 of 806  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  383   Mon Jun 30 14:15:52 2003 Question Robert Keeneybrassrlk@yahoo.comQuestionLinuxelog-2.3.6-1Email Notification
Is there a way to configure elog so users that have their email notification
on only get notified for updates to logs they have access to? I've looked
all through the documentation and I can't seem to find a way to do this.

If not is there some way I can work around this without to much trouble?  I
have lots of logs and would really hate to have to make configuration
changes in all of them .

Having the message body mailed to you is very convenient but some of my
users only get to see their logs. If the body gets mailed to them they get
to see everything anyway. 

When I had to use separate password files this wasn't an issue.
  68788   Wed Apr 18 12:07:50 2018 Question Stefan Werlerstefan.werler@ah-senden.deQuestionWindows3.1.1Email Config

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?

Attachment 1: config.txt
Theme = default
CSS = tiny.css
Display mode = summary
Suppress default = 3
Self register = 2
Entries per page = 100
Filtered browsing = 0
Entries per page = 8
Reverse sort = 1
Restrict edit = 1
Summary lines = 1
Display Email recipients = 0
Comment = AH-Senden Ticketsystem
List Display = ID, Author, Auftraggeber, Kategorie, Arbeitsbeschreibung, Standort, Rechnername, Priorität, Status, erstellt am, Fertigstellung bis, fertiggestellt am
Thread Display = $Auftraggeber $Standort, $Arbeitsbeschreibung, $erstellt am, $Fertigstellung bis, $fertiggestellt am,
#Start Page = ?Status=2-offen&mode=threaded&sort=Standort
#Start Page = ?wpwd=1&mode=threaded&Status=1-To Do&sort=Standort
Date Format = %A, %B %d, %Y
Time Format = %A, %B %d, %Y, %H:%M
Message Height = 6
Attributes = Auftraggeber, Kategorie, Standort, Rechnername, Priorität, Status, erstellt am, in Bearbeitung seit, warten auf Freigabe seit, Fertigstellung bis, fertiggestellt am, fertiggestellt durch, Arbeitsbeschreibung, Author
Type To Do = Time
Type Date Entered = time
Type Date Closed = time
Options Kategorie = Netzwerk, TK-Anlage, Internet, SAN, ELO, Zeiterfassung, Exchange,Domäne, W-LAN DHCP, DHCP, Backup
Options Priorität = 1-sehr hoch, 2-hoch, 3-mittel, 4-niedrig, 99-alt,
Options Status = 1-To Do{1}, 2-offen{2}, 3-fertiggestellt{3}, 4-in Bearbeitung seit{4}, 5-warten auf Freigabe{5}
{1} Preset To Do = $Date
{2} Preset erstellt am = $Date
{3} Preset fertiggestellt am = $Date
{4} Preset in Bearbeitung seit = $Date
{5} Preset warten auf Freigabe seit =$Date
Options Standort = Geilenkirchen, Kerpen, Mönchengladbach, Kaarst, sonstige, alle
Extendable options = Standort, Kategorie, Priorität
Page Title = Ticketsystem Senden - $subject
Option Author = Filled In Automatically
Subst Author = $long_name
#Menu Commands = Back, New, Edit, Delete, Reply, Find, Select, Copy to, Move to,

Reverse sort = 1
Quick Filter = Auftraggeber, Standort, Status, Fertigstellung bis

Subst on reply subject = Re: $Arbeitsbeschreibung
Thread display = $subject, posted by $author on $Entry time
Thread icon = Icon
Remove on reply = Author, Author Email
Date format = %B %d, %Y
Preset Author = $long_name
Preset Author Email = $user_email
Locked Attributes = Author
Quick filter = Date, Category, Status
  1817   Thu May 4 16:01:29 2006 Question Tim Fowlertimfowler1@gmail.comBug reportWindows2.6.1-1681Elogd.exe crashes on windows
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
  65935   Tue Jul 29 17:50:51 2008 Warning jhjon.huang@ses-americom.comBug reportWindows2.73-1.exeElogd.exe crashes almost everyday

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!!

 

  437   Sun Oct 12 08:37:00 2003 Warning Christopher Jonescjjones@zombieworld.comBug reportWindows2.3.9Elogd.exe Crashes When There are too Many Replies to Replies...
Hi,

  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.

Thanks,
Chris Jones
  67906   Thu May 14 02:35:15 2015 Question Francois CloutierFrancois@fcmail.caQuestionWindows3.1.0Elogd synchronisation with remote server
I came accross the admin guide and I was reading / searching for a way to sync logbooks across sites...
elogd mention "-m" and "-M" ... not elog but elogd... with that description :
synchronize logbook(s) with remote server

Does it sync all logbooks ? is there any examples somewhere or advice ?

Thanks :)
  66879   Thu Aug 19 15:26:35 2010 Warning Mike Zubermdz0739@yahoo.comBug reportWindows2.8Elogd service crashes on "reply" with percent character in subject line

My logbook kept crashing whenever I tried to reply to an existing entry. I found that the percent sign "%", when used in the subject line, will crash the elogd service when you try to reply to the entry. This appears to only happen with windows installations. I tested this on your Linux logbook and it didn't crash.

Here is the message taken from the Windows event viewer after the crash:
An unhandled win32 exception occurred in elogd.exe [5224].

Thank you for Elog, you have done a good job with it.  It is a great logbook.

Mike

  67366   Tue Oct 30 22:47:15 2012 Question David Walliswallis@aps.anl.govQuestionLinux2.9.2Elogd hangs while uploading bmp attachment

I'm running elog 2.9.2 on a Red Hat 6.3 server. This installation has been running for some time on a Solaris server, and was recently moved to the RHEL server.

When a user tries to upload a .bmp attachment, the upload never completes, eventually timing out with a proxy error. At that point, the elogd process stops responding to requests and needs to be restarted. Nothing is in the log file other than a "Listening" message when elogd starts up. Png and pdf attachments seem to work fine. I was able to convert an image from .bmp to .png and upload, but that's not practical for my user.

ImageMagick 6.5.4-7 is installed on the server. Everything else seems to be working normally.

Is this a known problem, or have I missed something that needs to be installed on the RHEL server?

ELOG V3.1.5-3fb85fa6