ELOG Forum

using elog client in secure mode

Hi,

I am trying to enter a log record in secure mode into a log book hosted on an apache server (v2.7.2).

After reading this forum I have recompiled the client using revision 2100 (well actually the head of svn).

But entering the record still does not work.

This is what I get

[atlt0dev@voatlas04]~% elog -v -s -h prod-grid-logger.cern.ch -p 443 -u myuser -w mypassword -d elog -l "ATLAS+Tier0+Operations+Logbook" -a Subject=foobar
Successfully connected to host prod-grid-logger.cern.ch, port 443
Request sent to host:
POST /elog/ATLAS%2BTier0%2BOperations%2BLogbook/ HTTP/1.0
Content-Type: multipart/form-data; boundary=---------------------------66AA3F62643F505F6F319FE6
Host: voatlas04.cern.ch
User-Agent: ELOG
Content-Length: 840

Content sent to host:
---------------------------66AA3F62643F505F6F319FE6
Content-Disposition: form-data; name="cmd"

Submit
---------------------------66AA3F62643F505F6F319FE6
Content-Disposition: form-data; name="unm"

myuser
---------------------------66AA3F62643F505F6F319FE6
Content-Disposition: form-data; name="upwd"

LXc=
---------------------------66AA3F62643F505F6F319FE6
Content-Disposition: form-data; name="exp"

ATLAS+Tier0+Operations+Logbook
---------------------------66AA3F62643F505F6F319FE6
Content-Disposition: form-data; name="encoding"

ELCode
---------------------------66AA3F62643F505F6F319FE6
Content-Disposition: form-data; name="Subject"

foobar
---------------------------66AA3F62643F505F6F319FE6
Content-Disposition: form-data; name="Text"

mypassword
---------------------------66AA3F62643F505F6F319FE6

Response received:
HTTP/1.1 302 Found
Date: Mon, 19 May 2008 13:33:29 GMT
Server: ELOG HTTP 2.7.2-2012
Location: https://prod-grid-logger.cern.ch/elog/ATLAS+Tier0+Operations+Logbook/?fail=1
Connection: close
Content-Type: text/plain; charset=UTF-8

<html>redir</html>

Error: Invalid user name or password

<<<<

the man pages seem to be out of sync and anyway mention two passwords to be usable, so they are not very helpful/clear

if somebody could tell me the right combination of options

and/or confirm/deny that this combination of client and server can work at all

I would be very grateful.

many thanks,

Luc

67335

Fri Sep 14 17:59:44 2012

ELOG crashes when editing threads

2.9.2-2455

Hi,

I am experiencing repeated crashing of the elog daemon.

If I go into select mode while in threaded view, I can select an entire thread by selecting the top entry.

When I do so then press the Edit button, the server crashes.

I have to manually restart it. Syslog shows no error.

This does not happen under Summary or Full view.

Running Ubuntu 12.04, ELOG 2.9.2-2455

I can provide my elog.cfg if necessary.

Cheers!

Louis

P.S. i just crashed the forums ELOG following those same steps!! Sorry!! At least it was restarted in no time.

67377

Wed Nov 7 20:48:03 2012

Request

Re: Support for modern Linux

2.9.2

Vinícius Ferrão wrote:

Hello folks,

Can we have a better support under modern Linux distributions?

I'm trying to install elog in our webserver and it's becoming a boring task. First of all theres only RPM packages. And we really don't like the Red Hat method, so we use Debian Servers. More package mainteners would be nice.

The software appears to be working correctly, but there are some bugs (or perhaps missing dependencies?); the init script put in /etc/rc.d/init.d is broken under Debian:

First of all because it's in /etc/rc.d.

The second problem is in this line:

# Source function library.

#. /etc/rc.d/init.d/functions

The file doesn't even exists.

The Debian init script contributed here has been working quite well for me for the last few Ubuntu versions. Unless you edit it, it sets the elog base directory to /etc so that's where you have to put your themes dir, resources, .conf file, scripts, logbooks, etc. I use symlinks to actually store my logbooks elsewhere.

I would also vote for a sane deb package. Right now, when I upgrade ELOG, I don't even run make install, I just copy the compiled binaries to their respective directories (/usr/bin or /usr/sbin). The rest stays the same.

67002

Wed Jan 26 19:35:48 2011

Request

Working Ubuntu 10.10 ELOG binaries

2.8.1

Hello,

Can anyone please send me, or publicly provide, working Ubuntu 10.10 binaries (64-bit) for ELOG?

I have compiled and installed the program. While the core functionalities are OK, I have run into irritating bugs in filtering and config editing that are not present in the online demo (but are in my local demo and logbook).

Hence I suspect compilation to be the cause.

For the curious:

Saving the config within ELOG scrambles the elog.conf file

Theme = default

Comment = Louis's Lab Book

Attributes = Project, Type, Category, Subject

after saving becomes

Them = defaultt

Commnt = Louiss's Lab Book

Attribute = Prroject, Type, Category, Subject

In the Find page, drop-down filters for attributes are ignored, but text is searched
In the threaded view, Quick filters "dissociate" posts and replies, so that all rows are now in reverse chronological order

Cheers!

Louis

67003

Wed Jan 26 19:38:58 2011

Request

Re: Working Ubuntu 10.10 ELOG binaries

2.8.1

Louis de Leseleuc wrote:

Hello,

Can anyone please send me, or publicly provide, working Ubuntu 10.10 binaries (64-bit) for ELOG?

Hence I suspect compilation to be the cause.

For the curious:

Saving the config within ELOG scrambles the elog.conf file

Theme = default

Comment = Louis's Lab Book

Attributes = Project, Type, Category, Subject

after saving becomes

Them = defaultt

Commnt = Louiss's Lab Book

Attribute = Prroject, Type, Category, Subject

In the Find page, drop-down filters for attributes are ignored, but text is searched
In the threaded view, Quick filters "dissociate" posts and replies, so that all rows are now in reverse chronological order

Cheers!

Louis

Hmm actually that last bug is also present in the demo. Any hope of fixing that?

True, some posts may not match the filters, leaving replies "orphan". I suggest that any orphan reply be either attached to the nearest upper level, or if not possible, be styled as a post instead of a reply (no arrow or indent) so as not to mistake it for a reply to the message above.

The benefit would be to be able to follow threads matching certain categories.

67027

Tue Mar 15 21:38:01 2011

2.9.0

Cleaning up attachments

I noticed a behavior that might be irritating.

After attaching/uploading files to an entry and before submitting it, one might press 'Back' or close the browser window.

This in effect cancels the entry and sends into oblivion. HOWEVER the attachments and their thumbnail files remain on the server forever.

Would there be a way to either delete attachments after some time if they don't show up in an entry? Or some other magic trick with the browser? My logbook directories are already full of orphan files that I need to seek and destroy.

Also, any thoughts on automatically cleaning up a logbook directory when the damage is done?

Louis

67031

Mon Mar 21 17:42:15 2011

Re: Cleaning up attachments

2.9.0

Stefan Ritt wrote:

Louis de Leseleuc wrote:

I noticed a behavior that might be irritating.

After attaching/uploading files to an entry and before submitting it, one might press 'Back' or close the browser window.

This in effect cancels the entry and sends into oblivion. HOWEVER the attachments and their thumbnail files remain on the server forever.

Also, any thoughts on automatically cleaning up a logbook directory when the damage is done?

Louis

Well, this is not so easy. When you leave the browser (via 'Back' or just by closing), it has no way to communicate with the elog server. I could put in some JavaScript, but if people switch off JavaScript there is no way. On the other hand it might be simple to write just a little shell script, which goes through all files on the server and checks if the file name occurs in some elog entry. This can probably be done with some combination of "find" and "grep", but I'm not a shell script expert.

How about this:

Whenever a new file is uploaded, it would first be stored in a temporary directory. When the entry gets submitted, the files would be moved to the logbook directory and the entry edited accordingly.

Any wrongfully stored file would remain in that temp dir. Starting/restarting the daemon would cleanup that directory. Seems like a simpler approach and does not involve scripting the browser.

67075

Wed Jun 1 18:17:36 2011