| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66129
|
Tue Dec 23 12:31:39 2008 |
 | Stefan Kanitz | skmainz@web.de | Question | Windows | 2.7.5-2140 | Re: Problems with execute delete |
| Stefan Ritt wrote: |
|
| 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.
|
Thank you! |
|
66130
|
Mon Dec 29 17:27:13 2008 |
| Barend | b.vandevrande@amtc2.com | Question | Windows | 2.7.5-2130 | Re: Standard login Screen - bottom text |
| Stefan Ritt wrote: |
|
| Barend wrote: |
|
Stefan,
I have defined the "Bottom Text Login = ..." in each Logbook Configuration section. But when I use this option in the Global Section, ELOG fails to start.
Barend
|
That's strange. I just tried myself following configuration file:
[global]
port = 8080
Bottom text = Hello
Bottom text login = Login Hello
Password file = passwd
[demo1]
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Page Title = ELOG - $subject
[demo2]
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
and everything works fine as can be seen from the login screen:
so can you check if above file works for you?
|
Hi Stefan,
Hope you have enjoyed the Christmas week.
Sorry for the delay.... I have tested your configuration and it worked for me as well.
In order to determine, which of my settings is causing the problem, I had to activate each individual entry "one by one" and check if the error re-occured. I finally identified following entry "Protect Selection page = 1"
The error also occurs if I change your configuration into:
[global]
port = 8080
Bottom text = <center>Hello</center>
Bottom text login = <center>Login Hello</center>
Password file = passwd
Protect Selection page = 1
[demo1]
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Page Title = ELOG - $subject
[demo2]
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Can you advise if I'm missing an entry in order for "Protect Selection page = 1" to work?
"Schönen Rutsch ins neue Jahr".
Regards,
Barend |
|
66132
|
Wed Dec 31 11:31:49 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | Windows | 2.7.5 | Re: Problems with SSL and Synchronization |
| 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  |
|
66133
|
Tue Jan 6 15:11:53 2009 |
| Ben Shepherd | bjs54@dl.ac.uk | Question | Linux | 2.7.5-2137 | Re: Tooltips for MOptions - not working? |
| Stefan Ritt wrote: |
|
| 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.
|
Thanks! I got rid of the quotes around everything, and it works now.
ben |
|
66136
|
Thu Jan 8 15:36:28 2009 |
| Stefan Kanitz | skmainz@web.de | Question | Windows | latest | Re: elogd hangs when Date format in elogd.cfg |
| Stefan Kanitz wrote: |
|
Hi,
after setting
Date format = %Y-%m-%e
in elogd.cfg,
elogd hangs and must be restarted manually. Can anybody help me?
Thanks,
Steve
|
I found my mistake:It must be
Date format = %Y-%m-%d
Steve
|
|
66137
|
Fri Jan 9 10:41:20 2009 |
| Niklas | niklas@hoglund.pp.se | Bug report | Linux | 2.7.5 2142 | Re: Elogd crashes with: *** stack smashing detected *** |
| Stefan Ritt wrote: |
|
| Niklas wrote: |
|
Stefan,
perhaps there should be something like the bold text below in elogd.c:
int process_http_request(const char *request, int i_conn)^M
...
/* extract cookies */^M
if ((p = strstr(request, "Cookie:")) != NULL) {^M
p += 6;^M
do {^M
p++;^M
while (*p && *p == ' ')^M
p++;^M
strlcpy(str, p, sizeof(str));^M
for (i = 0; i < (int) strlen(str); i++)^M
if (str[i] == '=' || str[i] == ';')^M
break;^M
if (str[i] == '=') {^M
str[i] = 0;^M
p += i + 1;^M
for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n' && i < (int) sizeof(cookie); i++)
cookie[i] = *p++;
...
|
Wow, where did you get that long cookie from? Certainly not from elogd. You must run elogd under Apache, and have some other service next to it on your server which distributes this long cookies, that's why other people did not experience this problem yet. I appreciate your fix. It's alwasy nice to see users not only complain about things, but try to fix them. Your fix is almost correct, you need a
i<(int) sizeof(cookie)-1
since there is the trailing zero for terminating the cookie string. I applied your fix to SVN revision #2146.
|
Just noticed that this fix does not work. Elog cookies e.g. "upwd" may be after other long cookies its not seen, as now it stops reading the cookie-string after 256 chars. There needs to be something that goes through the cookies and saves only elog cookies... Would probably be better if you code that, if you have time =D
BR, niklas |
|
66140
|
Sat Jan 10 09:58:43 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.5 | Re: ELOG scalability |
| 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. |
|
66141
|
Sat Jan 10 23:43:36 2009 |
| John Rouillard | rouilj+elog@cs.umb.edu | Bug report | Linux | Windows | 2.7.5-2130 | Re: Google Chrome issues | > Any ideas? I run our ELOG on windows server.. maybe that has something to do with it.
I am running the server on kubuntu 8.x, and have the same issue with chrome 1.x.
Is is possible the corporate elog server is running behind apache or in some
other proxy config while the one you are having issues with is being connected
to directly by chrome?
-- rouilj |
|