Resubmit-as-new-entry behaviour when synchronizing/mirroring, posted by Andreas Warburton on Fri Nov 24 23:08:33 2006
|
Hello,
I am running two ELOG installations: one on my Windows laptop; the other on a Debian linux web server. I have mirroring set up between the two installations. This has worked well for over a year. I am hoping that someone can help me regarding the following odd behaviour.
1. I edit (create) an entry on my Windows laptop. This entry gets mirrored or synchronized to the Linux machine.
2. I can view the entry fine both on the Windows side and on the Linux side.
3. I then edit the entry on the Linux side. After saving, the revised entry is visible on the Linux side.
4. I then have the same entry number available on both installations, but the two have different content due to my edit.
5. If I then synchronize, the original (unedited) entry is preserved along with the new entry, so both the Windows and Linux installations now have TWO entries each, representing the unedited and edited versions. The time stamps are identical, but the edited version is given a new ID number.
As a check, I explicitly added the line "Resubmit default = 0", which I know refers to editing and not synchronization, to my config file. The weird thing is that the synchronize/mirror operation seems to be acting with a "Resubmit default = 2" kind of behaviour.
Has anyone observed this happening?
Thanks for any comments or insights.
Cheers,
Andreas |
|
elog (2.6.1+r1642 ubuntu/debian) regularly becomes non-responsive (w/o crashing), posted by Peter Kovac on Mon Nov 27 17:29:41 2006
|
Greetings~
First, the problem. Fairly regularly (at least once a week, perhaps more), our elog daemon seems to quietly die. The process is still running but anyone attempting to access the server gets "connection refused." The elog log doesn't show anything and the apache logs just show "proxy: Error reading from remote server returned by [path]". Calling a daemon restart doesn't seem to kill the daemon -- I get a "could not bind to port" error. Using kill and then starting the daemon again fixes the problem for a few days and then we start over.
The particulars:
We are running elog on an Ubuntu (6.06 Dapper Drake LTS) web server.
It's currently version 2.6.1+r1642 pulled via apt-get from the Debian repositories.
elog is hiding behind an apache2+SSL proxy.
Any thoughts? Has anyone else seen this behavior? My next step is probably to compile 2.6.2 and remove the packaged flavor but I wanted to see if this was a known bug...
Thanks,
-Peter |
Re: elog (2.6.1+r1642 ubuntu/debian) regularly becomes non-responsive (w/o crashing), posted by Stefan Ritt on Tue Nov 28 10:34:54 2006
|
| Peter Kovac wrote: | First, the problem. Fairly regularly (at least once a week, perhaps more), our elog daemon seems to quietly die. The process is still running but anyone attempting to access the server gets "connection refused." The elog log doesn't show anything and the apache logs just show "proxy: Error reading from remote server returned by [path]". Calling a daemon restart doesn't seem to kill the daemon -- I get a "could not bind to port" error. Using kill and then starting the daemon again fixes the problem for a few days and then we start over.
The particulars:
We are running elog on an Ubuntu (6.06 Dapper Drake LTS) web server.
It's currently version 2.6.1+r1642 pulled via apt-get from the Debian repositories.
elog is hiding behind an apache2+SSL proxy.
Any thoughts? Has anyone else seen this behavior? My next step is probably to compile 2.6.2 and remove the packaged flavor but I wanted to see if this was a known bug... |
There are three reasons why an elog server can go into an infinite loop:
- A bug which has been fixed in meantime. If you can give a try to 2.6.2-1750 or so that could help. I'm not sure if this version is already in the Debian distribution since I'm not the maintainer there.
- A corrupted log file. If one of the YYMMDDa.log file get some garbage (maybe due to hard disk problems etc.) the elogd server can run into an infinite loop. In that case examine all log files to see if there is anything wrong. If so, edit it manually and restart elogd.
- Some not yet found bug. One never can exclude this of course, but at this forum I have elogd running under similar conditions like you, and it runs for months without problems.
|
|
Re: Resubmit-as-new-entry behaviour when synchronizing/mirroring, posted by Stefan Ritt on Tue Nov 28 12:50:19 2006
|
| Andreas Warburton wrote: | | Thanks for any comments or insights. |
This problem was introduced a couple of months ago. It is now fixed in the new version 2.6.3. |
Re: Email notification (bug tracking system), posted by Bertram Metz on Thu Nov 30 16:07:54 2006
|
| Stefan Ritt wrote: |
| Bertram Metz wrote: | Hello,
I'd like to use ELOG like a bug tracking system. I've created an attribute with the name AssignedTo. The attribute type is set to userlist. The value of AssignedTo is set to the full name of the selected user. There is no simple relationship between the full name and the email address on our system. Is it possible to get the email address of a user from the full name?
Attributes = Author, Category, Hardware, Software, Subject, Keywords, Status, AssignedTo
Options Category = Bug Report{1}, Observation{2}, Other{3}
Type AssignedTo = userlist
Show Attributes = Author, Category, Hardware, Software, Subject, Keywords
{1} Show Attributes = Author, Category, Hardware, Software, Subject, Keywords, Status, AssignedTo
Required Attributes = Author, Hardware, Software, Category
Options Status = new, open, confirmed, closed
;the following line does not work, since $AssinedTo contains the full name of the user
Email Category Bug Report = $AssignedTo@company.com
Kind regards,
Bertram |
I implemented the attribute type useremail for you. This can be used like:
Attributes = Author, Catorory, AssignedTo
Type AssignedTo = useremail
Email Category Bug Report = $AssignedTo
You will see only the email address of the people in the list, but since the email address usually contains the name this might be enough. A different system would have been too difficult to implement. The new feature is contained in SVN revision 1754. |
Thank you very much Stefan,
that works fine for me!
Bertram |
|
Preset reply date to nothing, posted by herman on Mon Dec 11 18:02:12 2006
|
How do I preset the reply date to an empty box(es)?
In 2.5.x it worked as
Preset on reply Plan Date = ""
gave me an empty date, which is what I wanted. Now in 2.6.3 I get some date in there (...1969) and have to
manually set it to empty again ?
Thanks |
|
Re: Preset reply date to nothing, posted by Stefan Ritt on Tue Dec 12 15:45:48 2006
|
> How do I preset the reply date to an empty box(es)?
>
> In 2.5.x it worked as
>
> Preset on reply Plan Date = ""
>
> gave me an empty date, which is what I wanted. Now in 2.6.3 I get some date in there (...1969) and have to
> manually set it to empty again ?
>
> Thanks
I fixed that in SVN revision 1777 again, so it will be included in the next release. |
How many topgroups can be defined?, posted by Exaos Lee on Sat Jan 13 17:35:45 2007 
|
I defined 6 top groups in my cfg file as the attachment.
But ... It doesn't work as I wanted.
The 4th and 5th groups need login. But when I clicked the 4th or 5th group, the login isn't needed.
And the 4th and 5th password files are not generated automatically. |
|