Thank your very much for your work on this - as i mentioned this is a minor issue.

Kind Regards Finn

Hi,

sorry for bugging you with this, but I could not find any information for making migration of elog system from one server to another.
The migration should be done from one server version (CentOS 6.10 to CentOS 7.6). Also we are talking about migration from one subdomain to another. Example subdomain1.example.com to subdomain2.example.com. Old elog application version is 3.1.2 and I would like to migrate to the latest version 3.1.4 

Is the migration from one system to another possible?  What are the prerequisites for migration?
Are there any instructions how to do it?

Thank you in advance and have yourself a lovely day,
Warmest regards
 

To move an elog instance, just stop the old server, move the configuration file elogd.cfg and the logbook directory to the new server, and start the new server. If the URL of the server changes, you have to adjust it in elogd.cfg. 

Stefan

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?

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?

Thanks,

Frank

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

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?

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