Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 117 of 808  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
IDdown Date Icon Author Author Email Category OS ELOG Version Subject
  68910   Thu Mar 14 06:38:12 2019 Question Johnsecondcomingtechnologies@fastmail.comQuestionLinux3.13How to edit Elog landing pages.

Hi and thanx for such a wonderful program! I was wondering how I might edit, change or add to the landing pages. In other words the first pages that show up (or any for that matter) when you login to a book. I can view the code ok in my browser using that function, but when I search for the actual page and it's locale, I cannot find it. Is it created on the fly by the server? If so, how can I change them.. as I want to add for instance javascripts to manipulate the pages and data more, without actually loosing the main essence of the program (log books). Thanx

  68909   Mon Mar 11 11:18:02 2019 Question Heinz Junkesjunkes@fhi-berlin.mpg.deBug reportAllelogd 3.1.4elog program does not respect "Allow edit" list

submissions via the elog - program can overwrite entries even if the user has no edit rights

  68908   Sun Mar 10 01:07:53 2019 Entry Ederagedera@gmx.frBug reportLinux3.1.4Very long URLs in message list corrupt layout

First, thank you so much for elog;
after using it for about 3 years, it has proven really handy and reliable.

When there is a very long URL in a message in "plain" encoding,
and this message is displayed in a list of messages,
a very long scrollbar appears at the bottom (same "scroll width" as the URL)
and some tabs and and dropdowns (filters) are unreachable without scrolling.

This does not happen if

  • the message is displayed in single message page
  • the message has a ELCode encoding
The exact version used is
0b9f7ed0 Merge branch 'develop'

There are no relevant instructions in elog.css for .messagelist,
and I did not find any obvious fix in the source code.

  68907   Wed Mar 6 05:10:28 2019 Reply Xuan Wuwux@ihep.ac.cnQuestionLinux3.1.3Re: elog hanged when uploading photo failed

That make sense. Is there a way to recovery when hung except restart elogd? On the other hand, whether could  prompt for reloading attachment when interpreter detect error but not hang?

Wu Xuan

Stefan Ritt wrote:

The problem is you have some weird characters in your file name R2BLM15 ? ? ? ? ? .PNG which confuses the interpreter. There should not be any special character or blanks in attached images.

Stefan

Xuan Wu wrote:

Hi all,

  We came across a problem recently when clicking "Upload" button, then elog hanged and never being accessed. I have checked the elog logs and find that it seems that elog didn't get the path of the picture for some reason. So is it a bug or our operation isn't correct?

 

 

  68906   Tue Mar 5 20:48:51 2019 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.3Re: elog hanged when uploading photo failed

The problem is you have some weird characters in your file name R2BLM15 ? ? ? ? ? .PNG which confuses the interpreter. There should not be any special character or blanks in attached images.

Stefan

Xuan Wu wrote:

Hi all,

  We came across a problem recently when clicking "Upload" button, then elog hanged and never being accessed. I have checked the elog logs and find that it seems that elog didn't get the path of the picture for some reason. So is it a bug or our operation isn't correct?

 

  68905   Mon Mar 4 18:55:09 2019 Question Michal Falowskimichal.falowski@uj.edu.plQuestionLinux3.1.3-2 EPELChain certificate

I tried to run elog with SSL so I created key and crt files. In crt file I added client certificate and intermediate certifacte. Unfortunately, when I try to run openssl s_client -showcerts -connect myexample.com:443 I got only the first certificate from the chain. Anyone has idea why this happens?

  68904   Mon Mar 4 13:35:13 2019 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows3.1.4Re: Mirror synchronization and file servers

Sounds really strange to me. The remote server does not "know" that "S:\" is a network drive, so the syncing process should work exactly as before. The only idea I have is that the access to the network files take pretty long, and you run into a timeout during syncing. We had this in the past (for AFS netwhor shares, not Windows shares), where sometimes we have a blocking behaviour where the file access lasted 10-20 seconds, and the server process was simply blocked. Since then I do not recommend to put logbook on network shares.

Stefan

Frank Baptista wrote:

We have a number of temperature chambers – each has its own laptop running a local ELOG server, with unique logbook for each.  Using the mirror feature, these individual logbooks periodically synchronize to a single remote desktop server, which has a copy of each of the logbooks.  All of that works great, as long as each of the ELOG servers are storing the logbook(s) to their respective local hard drive.

I wanted the remote server to store its copy of the logbooks on the network file server.  I changed the global options of the elogd.cfg file, adding the following:

               Logbook dir = S:\SHARED\LOGBOOKS

That change worked fine on the remote desktop server – new logbook entries were now being stored on the network file server.

Unfortunately, I lost the ability to sync from the individual logbooks to the remote desktop server.  During synchronization, I now get the following error message: “Error sending local entry: Error transmitting message". 

Has anyone run into this? Does this make sense? Am I missing something? Is there a workaround? Is there a wrong time to drink beer? wink

Thanks,

Frank

 

  68903   Fri Mar 1 19:18:53 2019 Question Frank Baptistacaffeinejazz@gmail.comQuestionWindows3.1.4Mirror synchronization and file servers

We have a number of temperature chambers – each has its own laptop running a local ELOG server, with unique logbook for each.  Using the mirror feature, these individual logbooks periodically synchronize to a single remote desktop server, which has a copy of each of the logbooks.  All of that works great, as long as each of the ELOG servers are storing the logbook(s) to their respective local hard drive.

I wanted the remote server to store its copy of the logbooks on the network file server.  I changed the global options of the elogd.cfg file, adding the following:

               Logbook dir = S:\SHARED\LOGBOOKS

That change worked fine on the remote desktop server – new logbook entries were now being stored on the network file server.

Unfortunately, I lost the ability to sync from the individual logbooks to the remote desktop server.  During synchronization, I now get the following error message: “Error sending local entry: Error transmitting message". 

Has anyone run into this? Does this make sense? Am I missing something? Is there a workaround? Is there a wrong time to drink beer? wink

Thanks,

Frank

ELOG V3.1.5-3fb85fa6