Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 731 of 796  Not logged in ELOG logo
ID Date Icon Authordown Author Email Category OS ELOG Version Subject
  67196   Tue Feb 14 14:54:06 2012 Reply Andreas Luedekeandreas.luedeke@psi.chBug fixLinux | Windows2.9.0Re: ssl problems

John Doroshenko wrote:

 

[...] The elog server is running SL5.5 (updates applied).  As you suggested, I ran firefox 3.6.26 on the elog server via https://localhost:port and it worked fine.   Downloaded firefox 10.0.1 and retried

on elog server and get error again:  The connection was Reset; The connection to the server was reset while the page was loading.

-John

Finally I was able to reproduce the problem. I don't know why FF10 worked locally on the ELOG host last weekend, maybe I shouldn't have worked on it during a night shift. I can now confirm that ELOG has problems with firefox 10.0.1.

For those who need a quick workaround: you can set-up apache to access elog via a reverse proxy (like I do and like Stefan does for the ELOG forum does). That 'll work fine with new browsers like FF10.0.1 (at least for apache 2.2) ;-)

Some guidance how to set it up can be found here: https://midas.psi.ch/elogs/Contributions/11

A shorter (but may be incomplete) summary:

  • add in httpd.conf
    • Listen 443
      LoadModule proxy_module modules/mod_proxy.so
    • ServerName <fully-qualified-host-name>
    •  
  • add in ssl.conf
    • <VirtualHost _default_:443>

ErrorLog logs/ssl_error_log
TransferLog logs/ssl_access_log
LogLevel warn
SSLEngine on
SSLProxyEngine on
ProxyPreserveHost On
<Location />
    ProxyPass         https://<fully-qualified-host-name>:444/
    ProxyPassReverse  https://<fully-qualified-host-name>:444/
    SSLRequireSSL
</Location>
SSLProtocol all -SSLv2
SSLCipherSuite ALL:!ADH:!EXPORT:!SSLv2:RC4+RSA:+HIGH:+MEDIUM:+LOW
SSLProxyCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
SSLCertificateFile "<cert-file>"
SSLCertificateKeyFile "<cert-key-file>"
</VirtualHost> 

  • And in the ELOG configuration [global] section
    •  port = 444
    • URL = https://<fully-qualified-host-name>                 

Cheers

Andreas

 
Detect language » English
 
  67290   Wed Jun 20 16:16:56 2012 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux2.9.1-2435Re: author field in reply

Ken Harvey wrote:

A. Tuttle wrote:
Look in https://midas.psi.ch/elog/config.html
--
Fun things to set are:
Preset on first reply <attribute> = <string>
and
Preset on reply <attribute> = <string>


I am a newbie to being the administrator to ELog, but have used it for a while now. We just updated and have the same issue with the reply now. Unfortunatley I am not much of a programmer, yet, still learning. In our config file it has "Preset Name = $long_name", "Preset Author = $long_name", "Preset on reply Author = $long_name". By looking in the Syntax of elogd.cfg section, it seems to be correct, but I am not sure. Can you give me a suggestion on how it should look? Or tell me why it is not working and lead me in the right direction on how to correctly set it up? Thank you for your time.


A common mistake is to think that "Author" is some kind of keyword: it is not.
You can use any defined attribute, if you want to use "Author" this attribute needs to be defined in the "Attributes=" command line.
Attributes = Author, ...
Then you can use the "Preset" command.
Preset Author = $long_name
Preset on reply Author = $long_name


I've just tested it with 2.9.0-2435 and it works fine.
If the following 4 line minimal logbook configuration does not work for 2.9.1, then please post again:
Attributes = Author
Preset Author = $long_name
Preset on reply Author = $long_name
Locked Attributes = Author

Cheers
Andreas
  67297   Wed Jul 4 14:04:10 2012 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindows2.9.0-2396Re: Problems with Autorization

Michael Dannmeyer wrote:

Hello,

we used Admin and write passwords. Now this is no longer supported in ELOG 2.9.0 and I tried to change to File or Kerberos Autentication. But nothing worked. I tried the following lines in elog.cfg

[Serverlogbuch]
Authentication = File
Password file = C:\Program Files\ELOG\logbooks\Serverlogbuch\pwd.txt
Self Authentication = 1

So the self Autentication site opens and I can put in all informations. But if I click on save he tries to save the information in the password file and after a time he stops and Internet Explorer says that the page cannot be reached.

The file is not saved. If I remove the 3 lines the logbook opens without any problems.

I tried also kerberos but it didn't work. But there I think some entries in the krb5.ini are wrong.

Would you please help solving the File password problem?

[...]

Just two hints:

  • The file mentioned as "Password file" should be writeable for the "elogd" process. It is needed for both, Kerberos and File authentication. Better not specify the full path, it should assume the file in the logbook directory.
  • The command "Self Authentication = 1" does not exist. Maybe you mean "Self register = 1"?
  67298   Wed Jul 4 14:18:21 2012 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux2.8.1-2350Re: move a type of entries to another logbook

Ze Li wrote:

[...] I have logbook A and logbook B.  Is it possible to move one type of entries in logbook A to logbook B?  If yes, may I know how you do it?  Thank you.[...]

  •  You can add the "Move to = B" command in logbook A.
  • Then you add "select" in "List Menu commands = ..., select, ...".
  • Now you "Find" all entries of the type you want (for convenience choose "Display 9999 entries per page").
  • You press "toggle all" and then "Move to B"
  67307   Fri Aug 10 11:47:49 2012 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux2.9.0-2411Re: Authentication problem with wget and links (text browser)

cowden wrote:

Hello,

I'm not able to authenticate to a logbook using my text based browser links, so I've started investigating with wget hoping solving the problem one will lead to a solution for the other.  I've seen some examples on how to use wget to parse logbook entries in this forum, but my attempts keep returning the login page.  Any advice would be helpful and appreciated.  Here are a couple of the command line arguments I've tried:

wget --save-cookies cookie.txt --keep-session-cookies -d "http://hostname/LOGBOOK?unamee=YYY&upassword=XXX" -O elog.txt

wget --save-cookies cookie.txt --keep-session-cookies -d --post-data="redit=&uname=YYY&upassword=XXX&remember=1" -e robots=off "http://hostname/LOGBOOK" -O elog.txt

After these executions, my cookies.txt file remains empty.  Running subsequent command with "--load-cookies=cookies.txt" still points me to the login page.

Many Thanks,

Chris

I've just checked that 'wget --no-check-certificate --save-cookies cookie.txt --keep-session-cookies -d "https://elog-gfa.psi.ch/SLS?uname=uuu&upassword=ppp" -O elog.txt'

created a file cookie.txt. The file contains three lines of data if uname and upassword are a valid login, and it is empty (beside of three comment lines) if they are not a valid login (wrong user or wrong password).

Could it be related to the set-up of your particular logbook?

  67334   Wed Sep 12 10:50:40 2012 Reply Andreas Luedekeandreas.luedeke@psi.chBug reportWindows2.9Re: Type <attribute> = Date - Issue

Garret Delaronde wrote:

 I haven't found anything in the forums about this. Apologies if its a duplicate.

I am fairly familiar with ELog, use it for multiple purposes on 5 different Virtual Servers at work. 

Currently looking to do some updates to one of the instances with the Date Type setting.

We have 17,000 entries all which have had manual entries for a Date Attribute for the last year and 8 months.

Due to regular entry errors on part of our contractors using it, (Eg: using "Aug" instead of "08", or using "-" instead of "/"), I want to change over to using the date type attribute (Type <attribute> = Date).

However the problem i found, the moment i save this in the config, and go to the list of entries, the date has changed on all of the entries to 12/31/1969. Which is BAD for our operation. So after removing the Type Date Setting the dates go back to normal.

Is there anyway to retain those dates so they display as they are and then only new entries would fall under the new date type setting?

Syntax manual didn't help much for this issue.

The problem is, that the existing entries have a string content for this specific attribute.
An attribute with a "date" type content should contain a integer number, which represents the seconds of the epoch (starting with zero on 1-Jan-1970 at 00:00:00).
 
What you need to do is writing a script that reads all *a.log files in the logbook directory and converts lines of the type:
<attribute>: <text>
to lines like
<attribute>: $(date -d "<text>" +%s)
 
Unfortunately elog does not provide you with such a tool.
But since you have to write it now anyway now, you could submit your code to this forum
 
Andreas
  67338   Mon Sep 17 09:16:38 2012 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionAll2.9.2Re: HTML editor

Josef Uher wrote:

 [...] maybe I missed something in the configuration, but how do I get this nice editor for HTML like the one available on this forum?[...]

The fckeditor is already installed with the elog package. All you need to do is to enable HTML in ELOG and Javascript in your browser.
The ELOG command "Allowed encoding = 7" gives you the same encoding choices as in this forum.
  67341   Tue Sep 18 10:05:27 2012 Reply Andreas Luedekeandreas.luedeke@psi.chBug reportLinux2.9.2-2473Re: Mysterious Emboldened lines in threaded (collapsed) mode
> I upgraded my system, including the version of Firefox.
> [...]
> Sorry this is a bit rambling, but its very hard to describe!

A picture can say more than thousand words.
Can you reproduce this with a simple configuration?
If yes, can you attach the configuration, the *a.log files,
a description of what firefox version you're using and please:
some screenshots of "before" and "after"?

Thanks!
Andreas
ELOG V3.1.5-2eba886