| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
65872
|
Tue May 6 21:47:32 2008 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.3-2058 | Re: any support of encrypted logfiles? |
| Bill Pier wrote: |
|
I'm sure this topic has been visited previously, but a search of this forum didn't show any results.
Is there are support or already proven method of encrypting the logfiles that Elog serves up?
|
There is no native support for encryption inside ELOG, but you can use some external tool to achieve encryption. You can for example use TrueCrypt to mount a virtual encrypted drive, where you store your log files. |
|
65887
|
Mon May 19 16:02:23 2008 |
 | Luc Goossens | lucreplacemegoossens@cern.ch | Question | Linux | | 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
|
|
65894
|
Mon Jun 2 12:17:53 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | | Re: using elog client in secure mode |
| Luc Goossens wrote: |
|
I am trying to enter a log record in secure mode into a log book hosted on an apache server (v2.7.2).
[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
|
Your problem is the wrong password parameter. The "-w" password is only if a write password is defined in the config file. If the user level access is chosen however, you have to specify the username/password pair only separated by a blank such as in
elog ... -u myuser mypwassword ...
|
|
65916
|
Mon Jun 30 10:55:29 2008 |
| Steve Williamson | StephenWilliamson@Barnsley.gov.uk | Question | Linux | 2.7.4 | Sorting Museremail |
We use elog for (amongst other things) a simple change management log. About two dozen users allowed to do updates and their email addresses are listed at the bottom of the page to allow any of them to be included on circulation for a change request. The email addresses appear in the order that they were added (i.e. apparently random). Is there any way to sort these, ideally by Last part of Full Name/First part of Full Name, but login name or email address would be OK?
Thanks for a great piece of software.
Steve |
|
65919
|
Thu Jul 3 08:57:32 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.4 | Re: Sorting Museremail |
| Steve Williamson wrote: |
|
We use elog for (amongst other things) a simple change management log. About two dozen users allowed to do updates and their email addresses are listed at the bottom of the page to allow any of them to be included on circulation for a change request. The email addresses appear in the order that they were added (i.e. apparently random). Is there any way to sort these, ideally by Last part of Full Name/First part of Full Name, but login name or email address would be OK?
|
Ok, I added sorting for "museremail" and "muserlist" type of attributes. Sorting is simply done by sorting the email addresses and first part of full name, respectively. The change is implemented in SVN revision #2115. |
|
65921
|
Wed Jul 9 19:57:50 2008 |
 | Yoshio Imai | | Bug report | Linux | 2.7.3-2104 | Error messages while creating thumbnails |
Hi again!
I have recently noticed that elog often creates large accumulations of the following group of error messages in our syslog:
Jul 9 19:05:00 elogd[27009]: Falling back to default group "elog"
Jul 9 19:05:00 elogd[27009]: Falling back to default user "elog"
Jul 9 19:05:02 elogd[27009]: Cannot restore original GID/UID.
Jul 9 19:05:02 elogd[27009]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Jul 9 19:05:05 elogd[27013]: Falling back to default group "elog"
Jul 9 19:05:05 elogd[27013]: Falling back to default user "elog"
Jul 9 19:05:05 elogd[27013]: Cannot restore original GID/UID.
Jul 9 19:05:05 elogd[27013]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Jul 9 19:05:05 elogd[27016]: Falling back to default group "elog"
Jul 9 19:05:05 elogd[27016]: Falling back to default user "elog"
Jul 9 19:05:06 elogd[27016]: Cannot restore original GID/UID.
Jul 9 19:05:06 elogd[27016]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
I have further found out that these coincide with the generation of attachment thumbnails (i.e. every time a user displays an entry generated before the advent of ImageMagick support for the first time, and every time the preview pictures are scaled/rotated while editing an entry).
The PID-file is indeed owned by the root user and not elog, but is correctly cleaned up at termination of the elog server.
Jul 9 19:47:08 elogd[27335]: elogd server aborted.
Jul 9 19:47:16 elogd[27359]: elogd 2.7.3 built Apr 18 2008, 14:08:31
Jul 9 19:47:16 elogd[27359]: revision 2104
Jul 9 19:47:16 elogd[27359]: Falling back to default group "elog"
Jul 9 19:47:16 elogd[27359]: Falling back to default user "elog"
Jul 9 19:47:16 elogd[27360]: Falling back to default group "elog"
Jul 9 19:47:16 elogd[27360]: Falling back to default user "elog"
Jul 9 19:47:16 elogd[27360]: Cannot restore original GID/UID.
Jul 9 19:47:16 elogd[27360]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Jul 9 19:47:16 elogd[27359]: ImageMagick detected
Does this point at some sort of problem?
Another question concerning the thumbnails of multi-page PDF-files: would it make sense to restrict the thumbnail generation to the first page? Since this is the title page, which in most cases is the only relevant page (really reading the file from the thumbnails is usually not possible anyway), this could help keep the attachment display less crowded ...
Thanks for the work and continuing support!
Yoshio |
|
65927
|
Thu Jul 17 01:16:49 2008 |
 | Jesse Wodin | jwodin@slac.stanford.edu | Question | Linux | 2.7.4-2111 | Elog crashing with "segfault" during file upload |
Hi there, I just compiled and installed elog on a machine running the newest Ubuntu server. Everything went fine - no problems. Running elog on it's own (no apache). I moved over a bunch of logbooks from an older elog, which seemed to work. Now, elog seems to crash when people are uploading files. Here is a snip from my syslog, and you can see each time it crashes with "error 4."
Jul 16 14:02:45 GrattaLab3old elogd[4526]: elogd 2.7.4 built Jul 15 2008, 18:44:44
Jul 16 14:02:45 GrattaLab3old elogd[4526]: revision 2111
Jul 16 14:02:45 GrattaLab3old elogd[4526]: FCKedit detected
Jul 16 14:02:45 GrattaLab3old elogd[4526]: ImageMagick detected
Jul 16 14:02:45 GrattaLab3old elogd[4526]: Server listening on port 8080 ...
Jul 16 16:02:42 GrattaLab3old kernel: [10631.276626] elogd[4526]: segfault at b4466000 eip 080adf19 esp bfa281d0 error 4
Jul 16 16:05:24 GrattaLab3old elogd[5509]: elogd 2.7.4 built Jul 15 2008, 18:44:44
Jul 16 16:05:24 GrattaLab3old elogd[5509]: revision 2111
Jul 16 16:05:24 GrattaLab3old elogd[5509]: FCKedit detected
Jul 16 16:05:24 GrattaLab3old elogd[5509]: ImageMagick detected
Jul 16 16:05:35 GrattaLab3old elogd[5509]: Server listening on port 8080 ...
Jul 16 16:06:06 GrattaLab3old kernel: [10834.637427] elogd[5509]: segfault at 091d7000 eip 080adf19 esp bfc313f0 error 4
Jul 16 16:07:10 GrattaLab3old elogd[5517]: elogd 2.7.4 built Jul 15 2008, 18:44:44
Jul 16 16:07:10 GrattaLab3old elogd[5517]: revision 2111
Jul 16 16:07:10 GrattaLab3old elogd[5517]: FCKedit detected
Jul 16 16:07:10 GrattaLab3old elogd[5517]: ImageMagick detected
Jul 16 16:07:10 GrattaLab3old elogd[5517]: Server listening on port 8080 ...
Jul 16 16:07:49 GrattaLab3old kernel: [10937.923301] elogd[5517]: segfault at b7c0d000 eip 080adf19 esp bffc1780 error 4
I run elog as:
Usr = elog
Grp = elog
/usr/local/sbin/elog -p 8080 -c /usr/local/elog/elogd_exo.cfg -D
where elogd_exo is my config file. Nothing special in my config file. |
|
65928
|
Fri Jul 18 08:18:18 2008 |
| Jesse Wodin | jwodin@slac.stanford.edu | Question | Linux | 2.7.4-2111 | Re: Elog crashing with "segfault" during file upload |
| Jesse Wodin wrote: |
|
Hi there, I just compiled and installed elog on a machine running the newest Ubuntu server. Everything went fine - no problems. Running elog on it's own (no apache). I moved over a bunch of logbooks from an older elog, which seemed to work. Now, elog seems to crash when people are uploading files. Here is a snip from my syslog, and you can see each time it crashes with "error 4."
Jul 16 14:02:45 GrattaLab3old elogd[4526]: elogd 2.7.4 built Jul 15 2008, 18:44:44
Jul 16 14:02:45 GrattaLab3old elogd[4526]: revision 2111
Jul 16 14:02:45 GrattaLab3old elogd[4526]: FCKedit detected
Jul 16 14:02:45 GrattaLab3old elogd[4526]: ImageMagick detected
Jul 16 14:02:45 GrattaLab3old elogd[4526]: Server listening on port 8080 ...
Jul 16 16:02:42 GrattaLab3old kernel: [10631.276626] elogd[4526]: segfault at b4466000 eip 080adf19 esp bfa281d0 error 4
Jul 16 16:05:24 GrattaLab3old elogd[5509]: elogd 2.7.4 built Jul 15 2008, 18:44:44
Jul 16 16:05:24 GrattaLab3old elogd[5509]: revision 2111
Jul 16 16:05:24 GrattaLab3old elogd[5509]: FCKedit detected
Jul 16 16:05:24 GrattaLab3old elogd[5509]: ImageMagick detected
Jul 16 16:05:35 GrattaLab3old elogd[5509]: Server listening on port 8080 ...
Jul 16 16:06:06 GrattaLab3old kernel: [10834.637427] elogd[5509]: segfault at 091d7000 eip 080adf19 esp bfc313f0 error 4
Jul 16 16:07:10 GrattaLab3old elogd[5517]: elogd 2.7.4 built Jul 15 2008, 18:44:44
Jul 16 16:07:10 GrattaLab3old elogd[5517]: revision 2111
Jul 16 16:07:10 GrattaLab3old elogd[5517]: FCKedit detected
Jul 16 16:07:10 GrattaLab3old elogd[5517]: ImageMagick detected
Jul 16 16:07:10 GrattaLab3old elogd[5517]: Server listening on port 8080 ...
Jul 16 16:07:49 GrattaLab3old kernel: [10937.923301] elogd[5517]: segfault at b7c0d000 eip 080adf19 esp bffc1780 error 4
I run elog as:
Usr = elog
Grp = elog
/usr/local/sbin/elog -p 8080 -c /usr/local/elog/elogd_exo.cfg -D
where elogd_exo is my config file. Nothing special in my config file.
|
Another funny problem. When I'm uploading a file, the syslog says this:
Jul 17 23:12:52 exo-elog elogd[4745]: Falling back to default group "elog"
Jul 17 23:12:52 exo-elog elogd[4745]: Falling back to default user "elog"
Jul 17 23:12:52 exo-elog elogd[4745]: Cannot restore original GID/UID.
Jul 17 23:12:52 exo-elog elogd[4745]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Jul 17 23:12:52 exo-elog elogd[4749]: Falling back to default group "elog"
Jul 17 23:12:52 exo-elog elogd[4749]: Falling back to default user "elog"
Jul 17 23:12:52 exo-elog elogd[4749]: Cannot restore original GID/UID.
Jul 17 23:12:52 exo-elog elogd[4749]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Jul 17 23:12:56 exo-elog elogd[4753]: Falling back to default group "elog"
Jul 17 23:12:56 exo-elog elogd[4753]: Falling back to default user "elog"
Jul 17 23:12:56 exo-elog elogd[4753]: Cannot restore original GID/UID.
Jul 17 23:12:56 exo-elog elogd[4753]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Jul 17 23:12:56 exo-elog elogd[4757]: Falling back to default group "elog"
Jul 17 23:12:56 exo-elog elogd[4757]: Falling back to default user "elog"
Jul 17 23:12:56 exo-elog elogd[4757]: Cannot restore original GID/UID.
Jul 17 23:12:56 exo-elog elogd[4757]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Jul 17 23:12:56 exo-elog elogd[4761]: Falling back to default group "elog"
Jul 17 23:12:56 exo-elog elogd[4761]: Falling back to default user "elog"
Jul 17 23:12:56 exo-elog elogd[4761]: Cannot restore original GID/UID.
Jul 17 23:12:56 exo-elog elogd[4761]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Jul 17 23:12:56 exo-elog elogd[4765]: Falling back to default group "elog"
Jul 17 23:12:56 exo-elog elogd[4765]: Falling back to default user "elog"
Jul 17 23:12:56 exo-elog elogd[4765]: Cannot restore original GID/UID.
Jul 17 23:12:56 exo-elog elogd[4765]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Jul 17 23:13:00 exo-elog elogd[4769]: Falling back to default group "elog"
Jul 17 23:13:00 exo-elog elogd[4769]: Falling back to default user "elog"
Jul 17 23:13:00 exo-elog elogd[4769]: Cannot restore original GID/UID.
Jul 17 23:13:00 exo-elog elogd[4769]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Jul 17 23:13:00 exo-elog elogd[4773]: Falling back to default group "elog"
Jul 17 23:13:00 exo-elog elogd[4773]: Falling back to default user "elog"
Jul 17 23:13:00 exo-elog elogd[4773]: Cannot restore original GID/UID.
Jul 17 23:13:00 exo-elog elogd[4773]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Jul 17 23:13:39 exo-elog kernel: [ 127.737506] elogd[4510]: segfault at b7b43000 eip 080adf19 esp bfdeeb00 error 4
and then crashes! |