Hello Hien,

If you are sharing ELOG with users on the same network, here's something you can try.  First, on the machine running ELOG, you need to find the "Computer name".   To do this, locate "This PC", and right click it to get to "Properties" in the drop-down menu.  You need to jot down the "Computer name".  Now, users on the same network should be able to view ELOG by entering the following:

http://computer-name:(port number)

If you are using port 80 (instead of the default 8080) for ELOG, then there is no need to enter the port number.

Give that a try -- that is working well for us.

Cheers!
Frank

> Dear experts, > > I am trying to use ELOG for my projects which we want to record every daily activities. > I have successful installed the ELOG to the computer (Windows10 -64 bit). > However, I don't know how to make it public or online, that people can access it from their computers. > I am a very newer to the ELOG. > Could you help me on it, please? > > Best regards, > Hien.

Hi Sebatian,

Thank you for taking the time to answer...very much appreciated!

Although I'm running Windows OS, I do understand your approach, and will work on an analogous solution.

Our setup is interesting -- we're running many temperature chambers, each one having a dedicated computer running a unique instance of ELOG, each of which is regularly updated to let users know what the progress is for the lengthy temperature testing.  All of these individual logbooks regularly synchronize to a common 'mirror' ELOG server, which shows all the logbooks in one location.  Users can view all the logbooks on one screen, by connecting to the mirror server.  Since this can be done remotely, it also makes it convenient to add "updates" remotely to the mirror server, which eventually synchronizes with each individual computer at the temperature chambers.  As you might imagine, if there is a user doing an update at the temperature chamber computer while another user enters an update remotely to the mirror server, there is a chance of having a record conflict.

I was trying to avoid conflicts by having real-time mirroring, where a change on either end is detected and immediately "synchronized", thereby reducing or eliminating conflicts.

In any case, if I do come up with a good solution for Windows, I'll be sure to share what I did.

Cheers,
Frank

Hi Sebastian,

You're absolutely correct that the users at the chambers could directly use the remote ELOG server (without having a local server), and I did originally think about this.  Unfortunately, there are times that our network "goes down" (for maintenance and other issues), and it was important to maintain the users' ability to perform regular 'local' updates at the temperature chambers, regardless of the network status.

In our situation, having a remote server also became particularly useful in the event that the 'local' computer at a specific temperature chamber "went down".  The user can continue to update the respective logbook at the remoter server, knowing that it would eventually synchronize with the respective local server(s).

Thanks for the great feedback!
Frank

Hi all,

Quick question -- I was wondering if the current Windows Binary/Installer is now compiled for compatibility for Windows 11?  

I did look through the Forum, but the the answer wasn't really clear.  

Thanks!
Frank B.

Hello,

I've been successfully using elog as a daemon since several years on a Linux machine. For some reasons recently I had to switch to a Windows 7 machine. Here, setting up the elog daemon doesn't work for me:

(a) running the command:

"...\ELOG\elog.exe" -c "...\ELOG\elogd.cfg"

in a windows shell works perfectly fine - logbook is up and running as set up in the cfg-file.

(b) However, starting the windows service manually (start->control panel->system and security->administrative tools->services) that was set up automatically during installation of elog leads to an error message:

"Error 1053: The service did not respond to the start or control request in a timely fashion"

From the service settings I can verify that the service is running exactly the same command that works in (a).

Could someone please share the windows service settings? Thanks in advance.

Cheers, Christian

Hi Stefan,

you were right - running the service by an authorized user solved the problem.

Thanks a lot.

Cheers, Christian

Hi,

Maybe the post is outdated already, but I want to share my experience anyway. I faced the same problem as Daniel: The most recent ImageMagick package was not detected by elogd even though it was installed. I could trace back the problem to the following issue:

Stefan mentioned that the ImageMagick software is detected via the 'convert' command. Since ImageMagick V7, however, the 'convert' command is no longer supported. So, when installing ImageMagick V6 the detection works.

@Stefan: Maybe you could adapt the software detection at some point? Thanks.

Christian

Update:

While the image scaling via ImageMagick works when running elog manually it doesn't when running elog as a service. The service is hosted in the same user environment that allows image scaling with elog started manually. What else could go wrong?

Christian