After registering, elog displays a page with the message:

     Error: Command "Config" is not allowed for user ""

However, the registration is successful. This causes confusion, and results in users registering multiple times.

In the elogd.conf file, I have the directive:

     Allow Config = bergman

Any suggestions?

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;

Is there a way to setup a search, to search several log books but not all the logs books at one time?

Thanks

Carl

Is it possible to have many roots with one elogd (or run several elogds), such that you can seaparate different groups or themes from each other:

electronics

       trigger

       power

mechanics

       detector

       support

Thanks.

Christoph

Have a look at "top groups" in the documentation 

No. You can either search one logbook or all logbooks. There is however the way to have separate groups of logbooks, which are "invisible" from each other. Like running several elogd daemons at the same time. Then your search on all logbooks will only run on the logbooks of one group. Check the documentation for "top groups".

- Stefan

 Thanks. I got it working so far. One minor glitch:

I have one topgroup (with 2 subgroups),

  electronics

       trigger

       power

and onother topgroup (only 1 subgroup)

 mechanics

   detector

When I get the login screen for the second (with the only one subgroup) it says in the header:

   "Several logbooks are defined on this host. Please select the one to connect to:"

and below only the one group (detector)  is shown, so actually nothing to select.

This may be possibly achieved by not defining a subgroup for the second one and leaving it as a topgroup,

but I don't know how it behaves, when the group admin decides to create a subgroup. Can he do

without requiring superuser or elog permissions?

--

Christoph

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!