Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 201 of 806  Not logged in ELOG logo
    icon2.gif   Re: config settings to ensure replies to author, thread contributors, admin?, posted by Stefan Ritt on Fri Jun 1 08:40:13 2007 

Mark Bergman wrote:
Attributes = Author, Type, Category, Severity, Subject, Entry ID, Status, CC E-mail To
Display Email recipients = 1
Email All = $CC E-mail To
Email All = mark.bergman@uphs.upenn.edu
Email Format = 47
Suppress default = 0
Type CC E-mail To = museremail

The documentation states that there can be multiple "Email All" directives, so I thought they would be additive--causing the admin address and the author to always get mail.


There can be multiple "Email All" directives, but they have to be on one line, like
Email All = $CC E-mail To, mark.bergman@uphs.upenn.edu


Mark Bergman wrote:

Is there a setting to ensure that the original author of the thread is always notified upon any change?


You can do something like:
Attributes = ..., Author Email
Preset Author Email = $user_email
Email All = $Author Email, $CC E-mail to, mark.bergman@uphs.upenn.edu
...

An alternative (and that's what I usually do) is to keep "Suppress email to users = 0" and tell the users to remove their subscription if they don't like it. Note that you also can edit the password file manually (it's a XML file), and remove all subscriptions easily with an editor. Note that you have to do that when elogd is stopped, then edit the file, then restart elgod.

- Stefan
    icon2.gif   Re: how to supress checkboxes of all logbooks at registration?, posted by Stefan Ritt on Fri Jun 1 08:43:23 2007 

Mark Bergman wrote:
Is there a way to suppress the listing of all logbooks on the New User Registration page? We've got 100 logbooks (one for each server, cluster node, or major software package). The long list makes it difficult for users to find the bottom of the registration page, and no user needs to subscribe for automatic e-mail notification for every logbook.


No, this is currently not possible. But I wonder why you have so many logbooks. Instead of having an individual logbook for every server, you could have the server name as an attribute of a single logbook:
Attributes = Author, ..., Server
Options Server = server1, server2, ...
Quick filter = Server
...

Using the quick filter, you can select the subset of logbook entries belonging to one server very easily. In general it will make your life much easier if you have less logbooks.

- Stefan
    icon2.gif   Re: Post appearing twice, posted by Alan Grant on Mon Jun 4 22:30:44 2007 

Stefan Ritt wrote:

Dan Chitwood wrote:
We are having trouble on our logbook with posts appearing twice. Both posts contain the same ID number, time, etc. This most often occurs when the e-log entry is being written for an extended period of time (ie. more than 30 minutes), but I don't know if that is the root cause of the problem. It may also be related to posts that are edited after an initial posting. Could this be due to an improper setting in our config file?


Besides the trivial case that people hit the submit button twice I can only imagine one possible cause: If you edit an existing entry, there is a button Resubmit as new entry at the bottom. If that button is checked, the old entry gets deleted and a new one gets submitted. If the delete of the old entry fails for some reason, you could maybe get two entries.

May I suggest following: Use a very simple config file (like the demo one from the distribution) and see if you can reproduce the problem. If not, add you config options one by one to the config file, and see at which option the problem starts. This way you might find the cause of it.

Your problem has not been reported by anybody else so far, so chances are high that it's related to a config setting.


I was having a very similar problem. After clicking Submit, I was getting dialog box "Submit modified Elog entry?" (with Submit or Cancel options) even though it was a new entry. Whenever I clicked Submit, it added two identical lines (except for ID), but when I clicked Cancel, it added only one entry. This happened in both v2.6.3 and v2.6.5. I eventually deduced it down to the Required Attributes line in the cfg file. I removed almost all other lines and then started removing each required attribute until the field was identified. For some reason it didn't like field name called "Date/Time Reproted" and when I removed it, it added fine, although that one field had to be unrequired when it really should have been req'd. I didn't see anything in the cfg instuctions regarding the use of "/" (unless I missed it) but I assumed it has something to do with that "/". It's interesting to note however that fields by same name under other tabs work fine. It may be bug related.
    icon2.gif   Re: Post appearing twice, posted by Stefan Ritt on Fri Jun 8 10:44:14 2007 

Alan Grant wrote:
I was having a very similar problem. After clicking Submit, I was getting dialog box "Submit modified Elog entry?" (with Submit or Cancel options) even though it was a new entry. Whenever I clicked Submit, it added two identical lines (except for ID), but when I clicked Cancel, it added only one entry. This happened in both v2.6.3 and v2.6.5.


Can you try to reproduce your problem with a minimal configuration file and send it to me?
    icon2.gif   Re: Post appearing twice, posted by deletoille on Tue Jun 12 11:07:39 2007 

Stefan Ritt wrote:

Alan Grant wrote:
I was having a very similar problem. After clicking Submit, I was getting dialog box "Submit modified Elog entry?" (with Submit or Cancel options) even though it was a new entry. Whenever I clicked Submit, it added two identical lines (except for ID), but when I clicked Cancel, it added only one entry. This happened in both v2.6.3 and v2.6.5.


Can you try to reproduce your problem with a minimal configuration file and send it to me?


I had the same problem but by adding the "Use lock = 0" option to the configuration, confirmation disappear
    icon2.gif   Re: Post appearing twice, posted by Stefan Ritt on Tue Jun 12 17:13:28 2007 
I finally found and fixed the problem with the help of Alan Grant. It happens when three things are used together:

  1. Locking (via use lock = 1)
  2. Attributes containing '/' characters
  3. Required attributes are used with attributes containing '/'

The '/' in the attribute crashes actually the JavaScript code for checking the required attributes and thus you have two submissions.

The bug is fixed in SVN revision 1866 and will be contained in the next release.
    icon2.gif   Re: Preset Date and Time, posted by Stefan Ritt on Fri Jun 15 18:54:10 2007 

David Egolf wrote:
Is there a way to have the preset date and time and add a set additional time? I do Preventative maintenance and want to add a default 30 days or 90 days to the preset date and time in a datetime field.


No, this is not possible. You have to use the build in calendar to set the correct date. But since you can flip months with a button, this should be straight forward.
    icon2.gif   Re: How long should it taken for new entry with attachments?, posted by Stefan Ritt on Wed Jun 20 18:20:01 2007 

An Thai wrote:
I try to re-produce the problem and find out that elog service needs very long to serve an entry with attachments.

Normally it takes about 3 seconds after the button SUBMIT is clicked to open the confirm page (ca. 20 recipients).

But when an user tries to enter a new entry and attach a file (about 500 Kb or greater) or some files (total of 500 Kb or greater), it takes several minutes and his browser displays "the page can not be opened"
In this time intervall, elog service runs with 100% CPU server recource.


This can be related you your email server. Attachments are converted into some ASCII form (base64 encoding), which increases their size by 2-3x. Some email servers are slow in receiving multi-MB data. Can you try to switch off the email attachments in the notification with
Email format = 111

This does not send attachments in email, just their names. If your performance gets much better then, it is related to your email server, and I cannot do anything. So just keep it then turned off.
ELOG V3.1.5-3fb85fa6