Hi there,

our host running ELOG crashed. I installed ELOG at another host with copying backup files / folders to new installation. New installation looks fine and seems to be working. But one big problem occurs I only can see some of former existing logbooks. Are there any suggestions how to build an new ELOG with old data?

Many thanks Mario

Hi there,

our host running ELOG crashed. I installed ELOG at another host with copying backup files / folders to new installation. New installation looks fine and seems to be working. But one big problem occurs I only can see some of former existing logbooks. Are there any suggestions how to build an new ELOG with old data?

Many thanks Mario

Hi,

We've made changes in our network and now we have to use port 587 instead of port 25, how can i edit that parameter?

Thanks

Hello,

I have just installed elog onto an ubuntu focal server using <sudo make install> and I am unable to create new entries.

When I access the log via a windows PC connected to the local network, I can see the demo logbook with the 1 test post, but I cannot create or edit anything.

Attempting to post throws the error:

New entry cannot be written to directory "/usr/local/elog/logbooks/demo/"

Please check that it exists and elogd has write access and disk is not full.

Please point me in the right direction to correctly set permissions and create aditional log books.

Thanks,

Dan

How can I skip the need for an email address when registering and logging in? Our IT dept will not give an email address to each guy I want on the log.

   I would like to implement ELOG as a logbook for our Windows 2000 
servers.  After making the recommendation, my supervisor replied: 

"The problem and perhaps the only problem is what happens when the server 
is down. Electronic log books should be able to replicate from more than 
one source so you can document let’s say from your laptop – and upload to 
the server later."

   Can anyone help me out here with some scenarios to improve fault-
tolerance?  

   Perhaps installing it on multiple servers and synchronizing the data 
and config folders with the NT File Replication Service?  

   Or installing it on one server and each administrator's laptop and 
using Offline Files to synchronize the data?

Any feedback would be appreciated,

Shawn Larson

An experiment's ELOG installation, using the default theme, names logbooks after its subsystem's acronyms.  One subsystem is referred to as KTAG, but when this name (or its lowercase version) is used for a logbook name, the logbook appears unformatted.  Changing the name, even to K-TAG, works fine.  Nothing close to KTAG appears in elog.css.  Does anyone know why this happens and whether it is possible or worth the while to get around the "problem"?