ELOG Forum

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.

2239

Fri Jun 1 08:43:23 2007

Re: how to supress checkboxes of all logbooks at registration?

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

2238

Fri Jun 1 08:40:13 2007

Re: config settings to ensure replies to author, thread contributors, admin?

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

2237

Thu May 31 23:46:31 2007

Mark Bergman

mark.bergman@uphs.upenn.edu

Question

Linux

V2.6.5

config settings to ensure replies to author, thread contributors, admin?

I'm having some difficulty configuring elog to ensure that the original author of an entry, any contributors to the thread, and a desginated administrator get e-mail notification for any change to the thread.

Here's a subset of the current elogd.cfg:

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 "Suppress default = 0" setting is used because many people mistakenly subscribe for automatic e-mail notification of all our logbooks when they self-register. I was hoping that the "Email All" directives would override the suppression of default mail.

This configuration works partially...in that if a user specifically selects addresses in the "CC E-mail To" field, those people do get mail.

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.

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

Thanks,

Mark

2236

Thu May 31 23:33:28 2007

Mark Bergman

mark.bergman@uphs.upenn.edu

Question

Linux

V2.6.5-186

how to supress checkboxes of all logbooks at registration?

2235

Wed May 30 22:32:03 2007

deletoille wrote:

I wrote a small program for another group and I have always the same problem of activation box who disappears when I upload a file. On the other hand, I noticed that the problem is only for the conditional attribute and not for the other. Here included the small program. an idea?

Ok, with your config I could reproduce the problem. I fixed it in revision 1865, the fix will be contained in the next release.

Goto page Previous 1, 2, 3 ... 535, 536, 537 ... 806, 807, 808 Next

ELOG V3.1.5-3fb85fa6