Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 658 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Categorydown OS ELOG Version Subject
  65774   Fri Mar 7 13:12:37 2008 Agree David PilgramDavid.Pilgram@epost.org.ukBug reportLinux2.7.3-2058Re: Quick filter by ID
> > Hi,
> > 
> > I've just upgraded from 2.6.2 to 2.7.3.
> > 
> > In my config file, I have
> > 
> > Quick filter: Date, ID.
> > 
> > When starting 2.7.3, across the top I now get 
> > 
> > "Error: Attribute "ID" for quick filter not found"
> > followed by an entry box.
> > 
> > If an ID is typed into that box, it sort of finds the right entry (+/- a few on occasion).
> > 
> > I cannot see any documented change that would affect how the Quick filter works.  Any clues?  Thanks.
> 
> Actually it is nowhere written the 'ID' for a quick filter should work. After investigating, I realize that it
> worked previously "by accident". I added in meantime some test so there is a warning for quick filter attributes
> which do not exist, and that's what you got. I loosened this test for 'ID' now in the current SVN version, so it
> can be used. It does however not display the single entry you want, but a page containing that entry (which then
> is displayed in bold). If you want exactly one entry, just add it's ID to the URL, like
> 
> https://midas.psi.ch/elogs/Forum/65767
> 
> for your previous entry.

Thanks Stefan!
  65813   Sat Apr 5 13:56:42 2008 Question Arno TeunisseA.teeling3@chello.nlBug reportWindows2.7.3-2058conditional options are not working in find

Hello

In my config file I have the following :

Options Head = AIX61{1},AIX53{2}, AIX52{3},HMC{4},CL_CLUSTER{5},VIRTUALIZATION{6},MICROCODE{7},BG_BLUEGENE{8}

{1} Options Topic = SECURITY, HIPER,TL00,TIPS
{2} Options Topic = SECURITY, HIPER,TL07,TL06,TL05,TL04,TL03,TL02,TL01 ,TIPS
{3} Options Topic = SECURITY, HIPER,TL10,TL09,TL08,TL07,TL06,TL05,TL04,TL03,TL02,TL01 ,TIPS
{4} Options Topic = HMC_CORRECTIVE, HMC_SECURITY,HMC_FIXES,HMC_INSTRUCT,HMC_MEDIA,HMC_DOCUMENT
{5} Options Topic = CL_DEEPCOMPUTING,CL_SYSMGMT,CL_GPFS,CL_LOADLEVELER,CL_ESSL,CL_PARALLEL_ESSL,CL_SWITCH,CL_RSCT,CL_PENV,CL_INIFINI
{6} Options Topic = PLM,VIOS_PM,VESS,VIOS,VIOS_WPM
{7} Options Topic = 2104-XU3,7017-S80,7017-S70,7020-40P,7025-F50,7025-F40,7025-F80,7026-B80,7026-H80,7026-M80,7028-6C4,7028-6E1,7029-6E3,7025-H50,702X-H70,7038-6M2,7039-651,7040-6X1,7043-140,7043-240,7043-260,7044-170,7248-43P,7043-150,704X-270,8203-E4A,8204-E8A,8844-3AZ,9076-SP,9110-510,9110-51A,9111-285,9111-520,9112-265,9113-550,9114-275,9115-505,9116-561,9117-570,9117-MMA,9118-575,9119-590,9119-595,9123-XXX,9124-XXX,9131-52A,9133-55A,9406-MMA,7037-A50,7047-185,ADAPTERS,DASD,DRIVES,CERTIFIED,OTHER
{8} Options Topic = BG_RELEASES,BG_FIXES,BG_COMPILERS,BG_REDBOOKS,BG_GPFS,BG_ESSL,BG_LOADLEVELER,BG_CSM

All is working fine when creating new entries. But when i use the  find command window,  i only see the Head options and selecting one of them,

the Topic options will not show up like they do when creating new entries.

I've installed the latest elog on Fedora ( version ELOG V2.7.3-2058 ) , but it's the same as the window version i'm using .

Would be nice if the user can search with the same items he used entering the data into the form.

Thanks for you're time.

greetings Arno Teunisse

 

 

 

  65817   Wed Apr 9 14:41:12 2008 Warning Yoshio ImaiBug reportLinux2.7.3-2072Problems with elog client

Hi!

 

Since our upgrade to elog 2.7.3, it is not possible any more to edit an existing elog entry using the elog client with -e <id> option. The only console output is "Error transmitting message". Submitting an entry via the client is not problem.

Running the server with -v option does not yield any output at the time of the edit attempt. Running the client with -v option also doesn't help, because whatever the other options, only the help page is printed out and nothing else done. Btw, there is now a conflict between -s for "use SSL" and -s for the "subdir" option.

 

Any ideas?

 

Yoshio

  65819   Wed Apr 9 23:03:53 2008 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.3-2072Re: Problems with elog client

Yoshio Imai wrote:

Since our upgrade to elog 2.7.3, it is not possible any more to edit an existing elog entry using the elog client with -e <id> option. The only console output is "Error transmitting message". Submitting an entry via the client is not problem.

Running the server with -v option does not yield any output at the time of the edit attempt. Running the client with -v option also doesn't help, because whatever the other options, only the help page is printed out and nothing else done. Btw, there is now a conflict between -s for "use SSL" and -s for the "subdir" option.

 

Any ideas?

The problem had to do with the integration of native SSL into elog/elogd. I tried to fix it in revision 2099. Please give it a try. I have not tried yet the SSL mode, but I changed the -s for "subdir" to -d not to collide with SSL.

  65822   Thu Apr 10 14:21:13 2008 Reply Yoshio ImaiBug reportLinux2.7.3-2099Re: Problems with elog client
I have tried the new revision, recompiling both client and server.
Unfortunately, the overall situation has not changed. We can still create new entries using the elog client, but editing an existing entry still does not work. However, thanks to your patch, the -v option now works again for the client side:
> elog -s -h <elog server> -p 443 -l current -u <user> <password> -a <Attributes> "TEST ENTRY"
Message successfully transmitted, ID=1

> elog -s -h <elog server> -p 443 -l current -u <user> <password> -e 1 "EDIT THIS ENTRY" -v
Successfully connected to host <elog server>, port 443
Request sent to host:
GET /current/1?cmd=download HTTP/1.0
User-Agent: ELOG
Cookie: unm=<user>;upwd=<password>;


Response received:
ET
Error transmitting message
Again, there is no output on the server side even when running with -v in console mode. There is the expected output when an entry is successfully created using the elog client. One aspect about this output is strange, though: the "Return" statement
==== Return ================================
HTTP/1.1 302 Found
contains the wrong "Location" header. It is not
Location: https://elog-server.domainname/logbook/ID
but rather
Location: https://client-host.domainname/logbook/ID
where "client-host" is the hostname of the computer where the elog client was called. But, since the logbook entry is correctly created, this is perhaps not a problem at all.



Another thing: I have noticed that when using conditional preset texts, the "Preset Text =" statements have to be declared for each logbook of a logbook group; it is not sufficient to only declare it in the "[global]" section of the logbook group. This means that we only need to declare the conditions once, e.g.
Options Category = .... , Shift {1} , ....
{1} Options Subject = Shift start {a}, Shift end {b}, ....

but the preset text declarations
{1&a} Preset text = shift_checklist.txt
{1&b} Preset text = shift_summary.txt
have to be declared in every individual logbook section for the logbooks of this group. Is this expected behaviour, or a bug?

Cheers

Yoshio
  65823   Thu Apr 10 15:39:26 2008 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.3-2099Re: Problems with elog client

Yoshio Imai wrote:
> elog -s -h elog -p 443 -l current -u <user> <password> -e 1 "EDIT THIS ENTRY" -v
Successfully connected to host elog, port 443


As I wrote in my previous message, the "SSL part has not been tested" (=means: does not work). I just fixed this today, so try revision 2100.
  65824   Thu Apr 10 15:56:12 2008 Agree Yoshio ImaiBug reportLinux2.7.3-2100Re: Problems with elog client

Stefan Ritt wrote:
As I wrote in my previous message, the "SSL part has not been tested" (=means: does not work).


Sorry for the misunderstanding. I was probably confused because the creation of new entries already worked, even with SSL.
Now, the editing also works.

Thank you very much!

Yoshio
  65831   Tue Apr 15 20:34:49 2008 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.3-2099Re: Problems with elog client

Yoshio Imai wrote:
Another thing: I have noticed that when using conditional preset texts, the "Preset Text =" statements have to be declared for each logbook of a logbook group; it is not sufficient to only declare it in the "[global]" section of the logbook group. This means that we only need to declare the conditions once, e.g.
Options Category = .... , Shift {1} , ....
{1} Options Subject = Shift start {a}, Shift end {b}, ....

but the preset text declarations
{1&a} Preset text = shift_checklist.txt
{1&b} Preset text = shift_summary.txt
have to be declared in every individual logbook section for the logbooks of this group. Is this expected behaviour, or a bug?


I cannot reproduce your problem. I just tried following file:
[global]
port = 8000
password file = passwd
Options Category = Other , Shift {1} , Routine
Attributes = Author, Category, Subject
{1} Options Subject = Shift start {a}, Shift end {b}
{1&a} Preset text = shift_checklist.txt
{1&b} Preset text = shift_summary.txt

[demo1]
Comment = General linux tips & tricks

[demo2]
Comment = General linux tips & tricks

and it worked as expected. Can you try it? If it works for you as well, then try to morph this file towards your config file, and figure out when the unexpected behavior starts.
ELOG V3.1.5-3fb85fa6