| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67129
|
Mon Sep 26 11:16:19 2011 |
 | Olivier Callot | Olivier.Callot@cern.ch | Bug report | Linux | 2418 | Re: Spurious characters in the searched string |
| Stefan Ritt wrote: |
|
| Olivier Callot wrote: |
|
Hi,
We have a problem with the search command: Since our last upgrade to v2.9.0-2418 the searched string is pre- and postfixed with ASCII character expressed in % format, see the attached image. The searched string is prefied with %255E and postfxed by %2524 in the URL. And teh search fails. This affects searches from drop-down menus.
Thanks in advance.
|
Strange. In this forum it works without extra characters. Just try it yourself. Do you have any strange configuration? Can you send me a minimal elogd.cfg which produces that error, maybe derived from the example elogd.cfg from the distribution.
- Stefan
|
Well, It may be our implementation of re-routing web requests: The requested string in elog is prefixed by %5E (^) and postfixed by %24 ($). But in my case, the '%' is again escaped as %25 so the prefix becomes %255E that is not understood by elog as being '^' ...
I will see with my experts in routing if this is something that can be fixed in our configuration. But when elog processes the input string, it should un-escape these characters and find back the '^', no? |
|
67131
|
Mon Sep 26 14:49:48 2011 |
| Olivier Callot | Olivier.Callot@cern.ch | Bug report | Linux | 2418 | Re: Spurious characters in the searched string |
| Olivier Callot wrote: |
|
| Stefan Ritt wrote: |
|
| Olivier Callot wrote: |
|
Hi,
We have a problem with the search command: Since our last upgrade to v2.9.0-2418 the searched string is pre- and postfixed with ASCII character expressed in % format, see the attached image. The searched string is prefied with %255E and postfxed by %2524 in the URL. And teh search fails. This affects searches from drop-down menus.
Thanks in advance.
|
Strange. In this forum it works without extra characters. Just try it yourself. Do you have any strange configuration? Can you send me a minimal elogd.cfg which produces that error, maybe derived from the example elogd.cfg from the distribution.
- Stefan
|
Well, It may be our implementation of re-routing web requests: The requested string in elog is prefixed by %5E (^) and postfixed by %24 ($). But in my case, the '%' is again escaped as %25 so the prefix becomes %255E that is not understood by elog as being '^' ...
I will see with my experts in routing if this is something that can be fixed in our configuration. But when elog processes the input string, it should un-escape these characters and find back the '^', no?
|
It turned out to be a setting of our re-routing of requests that re-escaped the '%'. Sorry for the noise. Cheers |
|
67138
|
Thu Oct 27 11:29:08 2011 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Linux | 2.9.0-2414 | elogd crash for special query | A query to a logbook can crash the demon.
Query:
https://pc8059.psi.ch:444/SwissFEL+Injector/?jcmd=Find&m0a=10&d0a=27&y0a=2011&npp=1&reverse=0
gdb dump:
SSLServer listening on port 444 ...
Program received signal SIGSEGV, Segmentation fault.
show_elog_list (lbs=0xae72618, past_n=0, last_n=0, page_n=0, default_page=1, info=0x0) at src/elogd.c:20797
20797 message_id = msg_list[index].lbs->el_index[msg_list[index].index].message_id; |
| Attachment 1: elogd.cfg
|
[global]
SMTP host = mail.psi.ch
Language = german_UTF8
charset = UTF-8
SSL = 1
Port = 444
Authentication = Kerberos, File
Password file = passwd.txt
Admin user = luedeke
Allow password change = 0
Self register = 0
Allowed encoding = 5
Allow HTML = 1
Suppress execute default = 0
Tab cellpadding = 2
Logfile = elog.log
Date format = %a %d-%b-%Y
Time format = %a %d-%b-%y %H:%M
[SwissFEL Injector]
Default encoding = 2
Comment = SwissFEL Injector Beam Development
Guest Menu commands = New, Find, List, Login, Help
Guest List Menu commands = New, Find, Login, Help
Restrict edit time = 48
Admin user = luedeke, robot
Login expiration = 8
Reverse sort = 1
Thumbnail size = 792>
Attributes = When, Author, Entry, Status, System, Downtime, Beamtime, Coordinator, Shiftleader, Operators, Participants, Title
List display = ID, When, Author, Entry, Status, System, Title
Thread display = $entry time, $Author, $Entry, $Status, $System, "$Title"
Quick filter = When, Entry, Status
Start page = ?rsort=When
Use Email Subject = ELOG $logbook: $Entry: $Title
# When
Type When = datetime
Preset When = $date
# Author
#Preset Author = $long_name
#Preset on reply Author = $long_name
Preset on first reply Titel = Re: $Titel
#Locked Attributes = Author
Preset Author = $shell(if [ $short_name = "Anonym" ] ;then echo $Author;else echo \"$long_name, $Author\";fi)
Preset on reply Author = $long_name
# Entry
Options Entry = Problem{1}, Measurement{2}, Shift-Summary{3}, Info{4}, Alarms{5}
# depending on Entry, but not specific to one attribute
{1,5} Show Attributes Edit = When, Author, Entry, Status, System, Title
{1,5} Show Attributes = When, Author, Entry, Status, System, Title
{2,4} Show Attributes Edit = When, Author, Entry, System, Title
{2,4} Show Attributes = When, Author, Entry, System, Title
{3} Show Attributes Edit = When, Author, Entry, Coordinator, Shiftleader, Operators, Participants, Downtime, Beamtime, Title
{3} Required attributes = Coordinator, Shiftleader, Operators, Downtime, Beamtime, Title
{3} Preset Title = Shift on $date
{1,2,4,5} Preset Title =
{1,5} Required attributes = When, Author, Entry, Status
# Status
{1} Options Status = open, work-in-progress, closed
{1} Preset Status = open
{5} Options Status = canceled, disabled, enabled
{5} Preset Status = disabled
# System
{1,4,5} Options System = Beamdynamics, Controls, Diagnostics, Mains
#{2} System = free text for measurement software, incl. version
Show Attributes Edit = When, Author, Entry, Title
# Downtime (only for Shift-Summary{3})
Type Downtime = numeric
Comment Downtime = hours of shift not usable (waiting for repair, etc.)
Format Downtime = 0, attribname, attribvalue, 8, 3
# Beamtime (only for Shift-Summary{3})
Type Beamtime = numeric
Comment Beamtime = hours of shift useable for measurements
Format Beamtime = 1, attribname, attribvalue, 8, 3
# Text
{1,2,4,5} Preset Text = /usr/local/elog/logbooks/inc/clear.html
{3} Preset Text = /usr/local/elog/logbooks/inc/FIN-summary.html
|
|
67139
|
Thu Oct 27 14:05:35 2011 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | All | 2.9.0 | undesired side effect of using an attribute "Entry" | If you use an attribute "Entry" then the internal variable "entry time" will expand to the last value of
"$Entry"+" time", e.g. if you use it in "Thread display = $entry time, ..."
One side effect is, that the logbook selection page defaults to use
Last submission = $entry time by $author
Which then expands to an undesired result.
This is not really a bug, rather something you'll need to keep in the back of your mind. |
|
67146
|
Wed Nov 9 20:15:38 2011 |
 | Steve Nahn | nahn@mit.edu | Bug report | Linux | 2.9.0 | Global Synchronization with 2.9.0 | Hi
I just updated my mirror server, which I just use as a backup to my main server, to 2.9.0 and found that after logging in (the selection page is not protected, but the individual logbooks are) and coming back to the selection page I no longer get the "Synchronize all logbooks" even though I am an admin user. The relevant code is in elogd.c in the show_selection_page() routine:
/* only admin user sees synchronization link */
if (is_admin_user("global", getparam("unm"))) {
rsprintf("<tr>\n");
rsprintf("<td colspan=13 class=\"seltitle\">\n");
rsprintf("<a href=\"?cmd=Synchronize\">%s</a></td>\n", loc("Synchronize all logbooks"));
rsprintf("</tr>\n");
}
what is happening is that after logging in to a logbook and coming back to the selection page, the "unm" parameter is not set, so getparam("unm") returns NULL, who clearly is not in the admin user list. The strange thing is that in an individual logbook the unm (and uname) parameters are working fine, and I have admin rights - can change the global config file, do an individual synchronization, etc. It is just from the selection page that the unm parameter is not working.
In fact, I commented out the if statement above, just to see if I could get synchronized using the link, and that failed too, with a message "No user name supplied for remote access" even though I do have a "mirror user" statement in my config. Again, if I do each one individually it all works. In addition, the cron synchronization (i.e. mirror cron) also works fine.
Obviously this isn't crucial, just a pain that can be worked around, but if anyone has any ideas I'd be glad to hear them.
Steve
PS Another feature request: when you forget to set an icon in this forum and then use the "back button" it shouldn't force you to rewrite the whole message over again! |
|
67160
|
Wed Jan 11 22:19:49 2012 |
| Allen | bastss@rit.edu | Bug report | Windows | 2.9.0-2396 | Elog does not work after installing MS12-006/MS12-012 on Win 7 | After patching a windows 7 computer with MS12-006, can no longer connect to elog, get page cannot be displayed
See
http://support.microsoft.com/kb/2643584 |
|
67161
|
Thu Jan 12 19:34:28 2012 |
| Allen | bastss@rit.edu | Bug report | Windows | 2.9.0-2396 | Re: Elog does not work after installing MS12-006/MS12-012 on Win 7 |
A little more information here
We are running elog on an Ubuntu server
Elog was working fine, then, on a windows 7 machine, MS12-006 was installed, rebooted, and could no longer connect to the elog web page.
Discovered that in Internet Explorer 8, by unchecking the use TLS 1.0 in options advanced tab, and making sure that SSL 3.0, TLS 1.1, TLS 1.2 were checked, that the page once again worked. I'm guessing the elog does not support SSL 3.0, otherwise, I assume I would have to uncheck that as well. Things do appear to still work on XP, thus far, only Windows 7 appears to break. While we have a work around, ideally we would like to see a bug fix so that (for legacy reasons), elog will still work with TLS 1.0 on Windows 7.
|
|
67162
|
Thu Jan 12 19:37:52 2012 |
| Allen | bastss@rit.edu | Bug report | Windows | 2.9.0-2396 | Re: Elog does not work after installing MS12-006/MS12-012 on Win 7 |
| Allen wrote: |
|
A little more information here
We are running elog on an Ubuntu server
Elog was working fine, then, on a windows 7 machine, MS12-006 was installed, rebooted, and could no longer connect to the elog web page.
Discovered that in Internet Explorer 8, by unchecking the use TLS 1.0 in options advanced tab, and making sure that SSL 3.0, TLS 1.1, TLS 1.2 were checked, that the page once again worked. I'm guessing the elog does not support SSL 3.0, otherwise, I assume I would have to uncheck that as well. Things do appear to still work on XP, thus far, only Windows 7 appears to break. While we have a work around, ideally we would like to see a bug fix so that (for legacy reasons), elog will still work with TLS 1.0 on Windows 7.
|
Also, strangely, I am able to use the elog forum page https://midas.psi.ch/elogs/Forum while TLS 1.0 is checked. I notice the version number is 2.9.0-2425, while we are using 2.9.0-2396, so wondering if this is fixed in this newer version. |
|