Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 52 of 806  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject
  69052   Mon Oct 21 19:31:17 2019 Reply Johnsecondcomingtechnologies@fastmail.comQuestionLinuxV3.1.2-bd75964Re: How to get Elog server to produce web server log files in Linux.

Thank you soo much Sebastian once again for helping me!! This is something that will help me very much in the future with other situations similiar!

John :)

Sebastian Schenk wrote:

Hi,
that Sebastian would be me. I replied to the first entry, as it was a draft (site reloaded incorretly...) and now I can't see the post anywhere. But this is off topic.

We have elog running on port 8000 and forward the traffic via Apache to it. Apache handles the SSL and other sites on the server.
All you need is a apache site configuration like the following. The parameter you want is CustomLog. (Have a look in the internet for options.)
I have also used nginx as webserver and know it can also handle this proxy setup.
If you use the following config, the elog config needs the URL attribute in the (global) config.

Best wishes,
Sebastian

<VirtualHost *:443> # change 443 to  80, if you don't use SSL
        ServerName your.server.name

        # delete the next 3 lines, if you don't use SSL
        SSLEngine on
        SSLCertificateFile /path/to/your/ssl.crt
        SSLCertificateKeyFile /path/to/your/ssl.key

        ProxyPreserveHost On
        ProxyPass / http://127.0.0.1:8000/
        ProxyPassReverse / http://127.0.0.1:8000/

        # Possible values include: debug, info, notice, warn, error, crit, alert, emerg.
        LogLevel warn
        CustomLog ${APACHE_LOG_DIR}/access.log combined
        ErrorLog ${APACHE_LOG_DIR}/error.log

</VirtualHost>

John wrote:

Hi again everyone; a Sebastian suggested I use a reverse proxy to complete my need to have logs show up when someone 'lands' on my first entry page. I see that Elog will only start recording logs when someone has actually started to do some work.. like login, read a post, etc... but NOT when they first enter the login page or 'listings' pages. I have tried fowarding from my router (both lighty and Apache) but so for no good. I will also look into  a vhost option and shareing the same port (very difficult- if even possible)  to  solve my dilema.

John :)

Stefan Ritt wrote:

Have you tried

Logfile = ...
Logging level = 3

John wrote:

Hi, I have been trying for a long time to get my web server logs to record when someone accesses my Elog server. I've tried Apache2, Lighttpd, and others, all with no luck. Either the web servers complain that the port I have Elog on is in use, or I just don't get any readings. I need to see who is accessing my  Elog from the web, and I hope there is a way.

Thanks again for such a wonderful program,

John

 

 

 

 

  68549   Sat Jan 14 08:27:42 2017 Warning Andreas Warburtonawarburt@physics.mcgill.caBug reportLinuxV3.1.2Re: elogd crashes during SSL Mirror operations involving attachments

For the time being, I am deeming ELOG 3.1.2 unusable with https (SSL = 1) functionality on my "Debian GNU/Linux 7 (wheezy)" server with "OpenSSL 1.0.1t", due to the described apparent issues with SSL.  Reverting to http (SSL = 0) brings back my ability to upload attachments and synchronize with a remote elogd running on a MacOS laptop.

Interestingly, my records indicate that I suffered a problem with very similar symptoms back in 2011, with version 2.8.0.  The problem at that time, which is acknowledged in the Changelog as "Fixed bug with SSL connection shutdown", got fixed in version 2.9.0.  Perhaps, when the "Replaced insecure SSLv23 with TLSv1 method" change was implemented for version 3.0.0, a similar issue was (re-)introduced?

It would of course be best if this issue were resolvable soon, due to the security vulnerabilities of http versus https.  Thank you in advance for any efforts!

Best regards,

Andreas Warburton

Andreas Warburton wrote:

When I switch from SSL = 1 to SSL = 0 and I use http:// instead of https://, the ability to upload attachments to logbook entries returns.  With both Chrome and Safari browsers, with SSL = 1 the file upload hangs after only a small percentage of the file has been uploaded.  I ran the following openssl diagnostic on my elogd port.  Would anyone have advice on what might be causing such errors?

tapajo [/usr/local/elog/elog-latest] openssl s_client -connect elog.hep.xxx.xx:80xx -state -nbio | grep "^SSL"

SSL_connect:before/connect initialization

SSL_connect:SSLv2/v3 write client hello A

SSL_connect:error in SSLv2/v3 read server hello A

SSL_connect:unknown state

depth=0 C = EU, ST = SomeState, L = SomeCity, O = SomeOranization, OU = SomeOrganizationUnit, CN = localhost

verify error:num=18:self signed certificate

verify return:1

depth=0 C = EU, ST = SomeState, L = SomeCity, O = SomeOranization, OU = SomeOrganizationUnit, CN = localhost

verify return:1

SSL_connect:unknown state

SSL_connect:unknown state

SSL_connect:unknown state

SSL_connect:unknown state

SSL_connect:unknown state

SSL_connect:unknown state

SSL_connect:error in unknown state

SSL_connect:error in unknown state

SSL_connect:unknown state

SSL_connect:unknown state

SSL handshake has read 1733 bytes and written 871 bytes

SSL-Session:

SSL3 alert read:warning:close notify

SSL3 alert write:warning:close notify

Andreas Warburton wrote:

The attached screenshot shows the behaviour after doing a synchronization (with Mirror simulate = 1) following first having ensured that the local (Mac) and remote (linux) ELOGs initially showed "All entries identical" when doing a simulated synchronization, and then having edited local entries 9707 and 9709 by uploading (different) attachments to them.

The fact that the synchronization is suggesting to renumber two different entry IDs to the same number looks like a bug.

Best regards,

Andreas W.

Andreas Warburton wrote:

My MacOS (10.12.2) elogd version V3.1.2 is a recent git commit (edc5e85), due to the fix to my earlier-described issue solved in the thread here: https://midas.psi.ch/elogs/Forum/68519.

I am trying to (re-)set up Mirror functionality with a linux server running the standard public (V3.1.2-bd75964).  I had initially updated the linux server so that it also had the latest git commit (edc5e85), but could then not even add new logbook entries that involved attachments to it.  I therefore rolled the linux server back to the standard public 3.1.2 version.

On the remote Mac, synchronizations usually look like they are going to work fine, with Mirror simulate = 1 switched on.  After I set Mirror simulate = 0, and if the server and remote logbook are already identical, I *occasionally* get the proper "All Entries Identical" synchronization result.  Unfortunately, this is very rare, and usually there is a failure whereby the remote (Mac) logbook decides that a significant fraction of its entries (usually sequential, from some seemingly random entry all the way up to the last entry) are missing on the linux server and need to be submitted back to the server from the remote Mac.

When the local and remote logbooks are not identical, and a record in need of synchronization contains an attachment, there is again destructive behaviour similar to that described above, except that the Mac elogd executable usually crashes.  (As in the case of the already-identical synchronizations described above, I only tested this after observing the correct expected behaviour first with Mirror simulate = 1.)

I'd be grateful for some help/suggestions.  My current testing suggests that my problems are likely not elog-content dependent.  (The logbook now undergoing synching has less than 10 entries in it.)

More generally, the issue of having things behave fine with Mirror simulate = 1, but then experiencing corruption/damage when switching to Mirror simulate = 0 seems serious to me.

Many thanks, Andreas

 

 

 

 

  68552   Thu Jan 19 12:56:51 2017 Warning Andreas Warburtonawarburt@physics.mcgill.caBug reportLinuxV3.1.2Re: elogd crashes during SSL Mirror operations involving attachments

Further to my comment in https://midas.psi.ch/elogs/Forum/68549, if the described synchronization requires attachment(s) to be transferred from my Mac laptop to the Debian linux server (with SSL = 0 set), it fails in all the tests that I tried.

To check whether these problems are linked to the OpenSSL version on the linux server, we also tried building an elogd executable using 1.0.2j instead of 1.0.1t.  This did not appear to change/improve the behaviour.

I'd like to keep using ELOG into the foreseeable future.  Don't hesitate to contact me if you'd like me to beta test any upcoming releases.  I'd appreciate having the earlier mirroring and attachment-handling functionality back again.

Best regards,

Andreas W.

 

Andreas Warburton wrote:

For the time being, I am deeming ELOG 3.1.2 unusable with https (SSL = 1) functionality on my "Debian GNU/Linux 7 (wheezy)" server with "OpenSSL 1.0.1t", due to the described apparent issues with SSL.  Reverting to http (SSL = 0) brings back my ability to upload attachments and synchronize with a remote elogd running on a MacOS laptop.

Interestingly, my records indicate that I suffered a problem with very similar symptoms back in 2011, with version 2.8.0.  The problem at that time, which is acknowledged in the Changelog as "Fixed bug with SSL connection shutdown", got fixed in version 2.9.0.  Perhaps, when the "Replaced insecure SSLv23 with TLSv1 method" change was implemented for version 3.0.0, a similar issue was (re-)introduced?

It would of course be best if this issue were resolvable soon, due to the security vulnerabilities of http versus https.  Thank you in advance for any efforts!

Best regards,

Andreas Warburton

Andreas Warburton wrote:

When I switch from SSL = 1 to SSL = 0 and I use http:// instead of https://, the ability to upload attachments to logbook entries returns.  With both Chrome and Safari browsers, with SSL = 1 the file upload hangs after only a small percentage of the file has been uploaded.  I ran the following openssl diagnostic on my elogd port.  Would anyone have advice on what might be causing such errors?

tapajo [/usr/local/elog/elog-latest] openssl s_client -connect elog.hep.xxx.xx:80xx -state -nbio | grep "^SSL"

SSL_connect:before/connect initialization

SSL_connect:SSLv2/v3 write client hello A

SSL_connect:error in SSLv2/v3 read server hello A

SSL_connect:unknown state

depth=0 C = EU, ST = SomeState, L = SomeCity, O = SomeOranization, OU = SomeOrganizationUnit, CN = localhost

verify error:num=18:self signed certificate

verify return:1

depth=0 C = EU, ST = SomeState, L = SomeCity, O = SomeOranization, OU = SomeOrganizationUnit, CN = localhost

verify return:1

SSL_connect:unknown state

SSL_connect:unknown state

SSL_connect:unknown state

SSL_connect:unknown state

SSL_connect:unknown state

SSL_connect:unknown state

SSL_connect:error in unknown state

SSL_connect:error in unknown state

SSL_connect:unknown state

SSL_connect:unknown state

SSL handshake has read 1733 bytes and written 871 bytes

SSL-Session:

SSL3 alert read:warning:close notify

SSL3 alert write:warning:close notify

Andreas Warburton wrote:

The attached screenshot shows the behaviour after doing a synchronization (with Mirror simulate = 1) following first having ensured that the local (Mac) and remote (linux) ELOGs initially showed "All entries identical" when doing a simulated synchronization, and then having edited local entries 9707 and 9709 by uploading (different) attachments to them.

The fact that the synchronization is suggesting to renumber two different entry IDs to the same number looks like a bug.

Best regards,

Andreas W.

Andreas Warburton wrote:

My MacOS (10.12.2) elogd version V3.1.2 is a recent git commit (edc5e85), due to the fix to my earlier-described issue solved in the thread here: https://midas.psi.ch/elogs/Forum/68519.

I am trying to (re-)set up Mirror functionality with a linux server running the standard public (V3.1.2-bd75964).  I had initially updated the linux server so that it also had the latest git commit (edc5e85), but could then not even add new logbook entries that involved attachments to it.  I therefore rolled the linux server back to the standard public 3.1.2 version.

On the remote Mac, synchronizations usually look like they are going to work fine, with Mirror simulate = 1 switched on.  After I set Mirror simulate = 0, and if the server and remote logbook are already identical, I *occasionally* get the proper "All Entries Identical" synchronization result.  Unfortunately, this is very rare, and usually there is a failure whereby the remote (Mac) logbook decides that a significant fraction of its entries (usually sequential, from some seemingly random entry all the way up to the last entry) are missing on the linux server and need to be submitted back to the server from the remote Mac.

When the local and remote logbooks are not identical, and a record in need of synchronization contains an attachment, there is again destructive behaviour similar to that described above, except that the Mac elogd executable usually crashes.  (As in the case of the already-identical synchronizations described above, I only tested this after observing the correct expected behaviour first with Mirror simulate = 1.)

I'd be grateful for some help/suggestions.  My current testing suggests that my problems are likely not elog-content dependent.  (The logbook now undergoing synching has less than 10 entries in it.)

More generally, the issue of having things behave fine with Mirror simulate = 1, but then experiencing corruption/damage when switching to Mirror simulate = 0 seems serious to me.

Many thanks, Andreas

 

 

 

 

 

  69359   Fri Apr 30 07:27:31 2021 Entry Faithfaithlessangel85@gmail.comBug reportLinuxV3.1.2[Bug?] Admin restrict edit time

I would like to know, if the command "Admin restrict edit time = " does really work as intended.

In my case I have the following global configuration:

Admin user = <me>
Restrict edit = 1
Restrict edit time = 1
Admin restrict edit time = 10000

And every time, when I want to edit an entry (as admin), that is older than 1 hour, i get the following error message:

"Entry can only be edited 1 hours after creation"

 

  68037   Thu Jun 25 16:39:06 2015 Entry David PilgramDavid.Pilgram@epost.org.ukBug reportLinuxV3.1.1-f613012Minor bug in the emails generated by elog.

In the emails generated by anyone making an entry in this log book, every apostrophe is followed by a semi-colon.  So the text "I don't think..."  appears in the email as "I don';t think...", and possibly that comment will appear in the email as "I don';;t think...." - not sure on the last bit.  It has been around in the past few versions of elog, but don't recall precisely when this started occurring.  It was fine back in February, with v2.9.2 (presumably) running.

  68068   Tue Aug 4 13:57:28 2015 Reply Stefan Rittstefan.ritt@psi.chBug reportLinuxV3.1.1-f613012Re: Minor bug in the emails generated by elog.

Apostrophes are encoded as "&#39;" inside the CKEditor used by elog, which sents the raw HTML text as email notification. You can test this by pressing the "Source" button at the top left menu in the CKEditor, then you see it. In my mail program (both Apple Mail and Thunderbird) this HTML enocding is correctly shown as the original apostroph, so I suspect that your mail program has an issue interpreting HTML encodings.

David Pilgram wrote:

In the emails generated by anyone making an entry in this log book, every apostrophe is followed by a semi-colon.  So the text "I don't think..."  appears in the email as "I don';t think...", and possibly that comment will appear in the email as "I don';;t think...." - not sure on the last bit.  It has been around in the past few versions of elog, but don't recall precisely when this started occurring.  It was fine back in February, with v2.9.2 (presumably) running.

 

  68179   Thu Nov 5 16:59:34 2015 Entry Simon Dästerdaesters@phys.ethz.chBug reportLinuxV3.1.1-b4dPaste figure from Clipboard, CKEditor 4.5.1 and Firefox 42

I tried to paste an Image from Clipboard into the CKEditor 4.5.1. Unfortunatelly, that doesn't work. I used Firefox, version 42. When I  looked in the javascript error console, it reported that "TypeError: b is undefined, ckeditor.js:1139:112". The variable  d.config.filebrowserImageUploadUrl could not be found.

I set the variable in the file ckeditor-config.js in the folder scripts, but that didn't solve the problem. As far as I can tell, Pasting Image from Clipboard does not work in this forum neither, but I don't know whether this is in purpose.

Pasting via the button "Paste from Word" works as it inserts a 64base formated image, but that's not what I'm searching for. Also normal upload of files works fine and puts the file in the correct folder (logbook/year/)

 

 

  68185   Tue Nov 10 14:08:47 2015 Reply Stefan Rittstefan.ritt@psi.chBug reportLinuxV3.1.1-b4dRe: Paste figure from Clipboard, CKEditor 4.5.1 and Firefox 42

That seems a CKEditor problem. Can you see if it works on their site (ckeditor.com). The current version is 4.5.4. Maybe they fixed it. You can upgrade CKEditor yourself in elog by just copying the new verson over the old /elog/scripts/ckeditor directory.

Simon Däster wrote:

I tried to paste an Image from Clipboard into the CKEditor 4.5.1. Unfortunatelly, that doesn't work. I used Firefox, version 42. When I  looked in the javascript error console, it reported that "TypeError: b is undefined, ckeditor.js:1139:112". The variable  d.config.filebrowserImageUploadUrl could not be found.

I set the variable in the file ckeditor-config.js in the folder scripts, but that didn't solve the problem. As far as I can tell, Pasting Image from Clipboard does not work in this forum neither, but I don't know whether this is in purpose.

Pasting via the button "Paste from Word" works as it inserts a 64base formated image, but that's not what I'm searching for. Also normal upload of files works fine and puts the file in the correct folder (logbook/year/)

 

 

 

ELOG V3.1.5-3fb85fa6