Re: Tooltips for MOptions - not working?, posted by Stefan Ritt on Mon Dec 22 08:52:20 2008
|
| Ben Shepherd wrote: |
|
Hi,
One of my logbooks is a fault reporting system; it emails a group of people when a fault is reported. There is an MOption 'Technical Groups', and I want to have a tooltip for each checkbox which shows who is referred to by each group name. However, individual tooltips for each MOption attribute don't seem to work. I've looked at the HTML code, and there's no 'title' attribute for the checkboxes, so it's not a browser problem. I've attached my config file. Any idea what's going wrong?
ben
|
The syntax for tooltips is
Tooltip <attribute option> = <tooltip>
but you have
Tooltip "<attribute>" "<attribute option>" = <tooltip>
which is not correct, but would make more sense, since you could have an attribut option being valid for several attributes. So I changed elogd to accept both syntax in revision 2158. Please note that you should not put "quotes" around attribute values or options. |
|
Re: Display Revisions field in single entry but not in list view, posted by Stefan Ritt on Mon Dec 22 11:59:09 2008
|
The "Show Attributes" option is for the single entry view, while the "List Display" option is for the list view. So what you need is:
Attributes = Author, Type, Category, Subject
Show Attributes = Revisions
Locked attributes = Revisions
Subst on Edit Revisions = $Revisions $date by $long_name
List Display = ID, Date, Author, Type, Category, Subject |
|
Re: Problems with execute delete, posted by Stefan Ritt on Tue Dec 23 11:34:25 2008
|
| Stefan Kanitz wrote: |
|
i have problems with execute delete (execute new works fine) in following config (the attribute 'Counter' will not evaluated). Can anybody help me?
|
Attribute substitution on 'execute delete' was not implemented, since I thought that the ELOG message ID would be used as the primary key in an SQL database, so one would not need the attributes. I added howver this functrionality in SVN revision 2159, so the next release will contain this fix. |
|
Re: Problems with execute delete, posted by Stefan Ritt on Tue Dec 23 12:22:51 2008
|
| Stefan Kanitz wrote: |
|
| Stefan Ritt wrote: |
|
| Stefan Kanitz wrote: |
|
i have problems with execute delete (execute new works fine) in following config (the attribute 'Counter' will not evaluated). Can anybody help me?
|
Attribute substitution on 'execute delete' was not implemented, since I thought that the ELOG message ID would be used as the primary key in an SQL database, so one would not need the attributes. I added howver this functrionality in SVN revision 2159, so the next release will contain this fix.
|
This sounds very good! Thank you very much (Could you please add this functionality for execute edit too? Please :-))
|
For 'execute edit' this worked from the beginning. |
|
Re: Problems with SSL and Synchronization, posted by Stefan Ritt on Wed Dec 31 11:31:49 2008
|
| Mark Langkau wrote: |
|
I installed ELOG on a Linux server (CentOS 5.2) and a WinXP laptop.
- If I set both servers to non-SSL, I can synchronize with no problems.
- If I set both servers to use SSL, synchronization fails with "Error code: ssl_error_rx_record_too_long"
- If I set one to ssl and the other non-ssl, synchronization fails with "Remote server is not an ELOG server"
Is anyone synchronizing or mirroring two ELOG servers with SSL? When either or both servers are set to use SSL, I can use either site. but I can't synchronize.
|
Synchronization with SSL does not yet work. I have to find some time to implement it. Since you are already the second one mentioning this, it slipped higher on my to-do list  |
|
Re: ELOG scalability, posted by Stefan Ritt on Sat Jan 10 09:58:43 2009
|
| Devin Bougie wrote: |
|
Hi, All. We have been successfully using ELOG in a limited deployment for a couple years now. However, we are about to embark on a new project that could run for up to 10 years, and are wondering what sort of scalability we can expect from ELOG.
Are there any problems we can expect to run into as the number of entries grow? I see in a previous thread that "elog runs fine for a few 10000 entries. At 100000 entries it starts getting slow." Is this still the case, or have any improvements been made? What sort of problems would we expect to run into? Any examples of existing large deployments would be very useful.
|
The above made statement is not true any more. Mainly due to the large CERN experiments, some speed improvements have been made in late 2007. So elog runs fine at least up to 100000 entries. The startup time might be a bit slow, since it parses all entries there, but beyond the maybe 20s startup time, there is not a big difference when browsing entries. The only peoblem left is if you try to search some text through 100000 entries, this could be a bit slow. I have not tried anhything beyond 100000 entries, because this was not requested so far. If logooks become too big, the entreis could be split into several logbooks. Even if there are several logbooks with 100000 entries each, the access time should not be slower than if there would be one logbook with 100000 entries. |
|
Re: Top group causes: Internal error, no valid header!, posted by Stefan Ritt on Tue Jan 20 15:17:04 2009
|
| Michael Ambrus wrote: |
|
Having "Top group" in a config-file for Windows will cause:
GET / HTTP/1.1
Host: eudr6j03j:8084
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.0.5) Gecko/20
08120122 Firefox/3.0.5
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: sv-se,sv;q=0.8,en-us;q=0.5,en;q=0.3
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Cookie: unm=mambrus; upwd=U2lzc2kx; urem=0
Cache-Control: max-age=0
Internal error, no valid header!
Removing "top group" makes elogd.exe work. The error is repeatable and the same config file works on the same version of Elog on Linux. Elog was compiled with Cygwin.
|
Please supply your full configuration file for error analysis. |
|
Re: Stack error when email notification is active, posted by Stefan Ritt on Tue Jan 20 15:37:19 2009
|
| Michael Ambrus wrote: |
|
Stack error is caused when an entry is submitted in a e-mail notification enabled log when a new entry is submitted. This error does not happen on linux (same Elog version, same config file).
Please let me know if there is anything I can do to help.
-----------------------------2916890032591
Content-Disposition: form-data; name="attfile"; filename=""
Content-Type: application/octet-stream
-----------------------------2916890032591--
timezone: 0, offset: 0
6 [main] elogd 2816 _cygtls::handle_exceptions: Error while dumping state
(probably corrupted stack)
Segmentation fault (core dumped)
|
Cygwin is not officially supported. Can you try the Windows binaries? |
|