Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 697 of 808  Not logged in ELOG logo
icon1.gif   Spurious characters in the searched string, posted by Olivier Callot on Mon Sep 26 08:13:10 2011 Capture.PNG

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.

    icon2.gif   Re: Spurious characters in the searched string, posted by Stefan Ritt on Mon Sep 26 10:38:59 2011 

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 

    icon2.gif   Re: Spurious characters in the searched string, posted by Olivier Callot on Mon Sep 26 11:16:19 2011 

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?

    icon2.gif   Re: Spurious characters in the searched string, posted by Olivier Callot on Mon Sep 26 14:49:48 2011 

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

icon5.gif   elogd crash for special query, posted by Andreas Luedeke on Thu Oct 27 11:29:08 2011 elogd.cfg
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;
icon4.gif   undesired side effect of using an attribute "Entry", posted by Andreas Luedeke on Thu Oct 27 14:05:35 2011 
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.
icon8.gif   Global Synchronization with 2.9.0, posted by Steve Nahn on Wed Nov 9 20:15:38 2011 

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!

icon4.gif   Elog does not work after installing MS12-006/MS12-012 on Win 7, posted by Allen on Wed Jan 11 22:19:49 2012 

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

ELOG V3.1.5-3fb85fa6