Ich möchte meine "lokale" ELOG Installation mit einem Server in der Firma synchronisieren.

Dazu habe ich in der entfernten Firewall ein Portmapping auf den ELOG Server in der Firma eingerichtet.

Wenn ich von meiner "lokalen" Maschine im Browser  http://meinedomain.dyndns.xx:PORT aufrufe, kann ich auf den ELOG Server zugreifen.

Ich habe in meiner "lokalen" Installation in der Section [global] den Mirror-Server = http://meinedomain.dyndns.xx:PORT angeben.

Beim Synchornisieren bekomme ich jedoch den Hinweis "Fehler beim Zugriff auf entfertes Logbuch".......

Please let's stick to English. Let me try to understand your configuration. You have one elog server running and want to synchronize with itself? That does not work of course, synchronizing is done between two servers (normally on different computers).

I have a logbook named "Centaur" (instrument name) for a problem log on an instrument and a logbook named "CentaurNewLot" for

a logbook (Database Like - ELOG format) where we would log reagent lot number changes for that instrument.

The problem is that when I name the logbooks, like I have, it screws up the formatting (List page) of the second log book.

If I rename the second logbook something totally unrelated to the first logbook my originally intended formatting returns.

I tried to reproduce your problem but without success. In my case the "CentaurNewLot" looks fine:

so what is different in your case? Can you try with the simple example logbook from the distribution and the add one option after the other to see which one causes the trouble?

Hi,

I am trying the Preset text option from the documentation: like:

Attributes = Author, Type
Options Type = Network check{1}, System check{2}

{1} Preset text = network.txt
{2} Preset text = system.txt

I have two questions:

1. Where are the preset text files searched from ? I guess I could put them in the logbook (and specify a relative path like in this example) but it appeared only to work when I specifiy an abcolute path. That is even better in my case.

2. How do I specify line feeds in the file ? I tried Linux and Windows new line characters - but I always end up with just  one line in my e-log. I would really like a multi-line form.

Soren

Attributes = Author, Type
Options Type = Network check{1}, System check{2}

{1} Preset text = network.txt
{2} Preset text = system.txt

 Dear Soren,

Just use HTML (and call the file network.html to remember).

Attributes = Author, Type
Options Type = Network check{1}, System check{2}

{1} Preset text = network.txt
{2} Preset text = system.txt

Without path, the file must reside in the "scripts" subdirectory.

For the multi-line form, it depends how you want to format your elog entry. If you format in "plain", the simple line breaks are sufficient. If you format in HTML, your preset file must be in HTML as well, so a line break has to be a <br> tag. If you format in ELCode, a simple line break again would be ok. 

Attributes = Author, Type
Options Type = Network check{1}, System check{2}

{1} Preset text = network.txt
{2} Preset text = system.txt

 Thanks for the hints on the "scripts" dir.  For the formatting, that's clear. I started with the sample "network.txt" file from the doc and the default encoding (HTML), so that did (of course) not render correctly (before inserting a few tags).

Soren

Hi,

I really don't understand why elogd cannot run by root but it runs by a user.

I've put elog deamon in /etc/init.d. So it didn't bring up, but it runs if I run it by user interactively.

Thanks,

Dongwook

That's a security issue. If elogd runs under a user and gets hacked, the hacker obtains just the user rights, which can be limited. If it runs under root, the hacker will automatically get root rights, which is bad. Technically, there is no reason why elogd cannot be run as root. Just put

Usr = root

Grp = root

into elogd.cfg. 

 Hi,

I wonder how others manage this situation because deamons in /etc/init.d is excercuted by root. So I cannot run in /etc/init.d/elogd when the system starts up.

What do you think?

Thanks,

Dongwook

The normal situation is that elogd gets started by root under /etc/init.d/, then the configuration file contains "Usr = elog" and "Grp = elog", so after it has been started as root, the program falls back to the "elog" user, which only has restricted rights. 

Now I realized that it is not a problem in /etc/init.d, but deamon itself.

When I run the following command as a root, it didn't run

/mnt/wd500/jnj/products/elog/sbin/elogd -D -c /mnt/wd500/jnj/products/elog/elog/elogd.cfg

But, it runs when I did as a user.

I really don't understand this strange behavior.

Thanks,

Stefan,

I am using the Database Like - ELOG format and on the list page, the the last two columns (on the right side) are, "Text" and "Attachments (the paperclip)".

Both of which I have deleted from the input page.

Is there anyway to remove them from the List page?

Thanks,      Mike

You need:

Show text = 0

Enable Attachments = 0

to supress the text entry box and the attachment field.

Display search = ID, Type, Location, Status

to show only the attributs of interest in the list display (your attributes could be different)

Summary lines = 0

to supress the text in the list display. At the moment, this still shows the paperclip colum, but I want to fix this in the next version.

I went to upgrade to the new version of elog I receive a error message that is.

error: Failed dependencies:
	libssl.so.6 is needed by elog-2.7.5-1.i386
	rtld(GNU_HASH) is needed by elog-2.7.5-1.i386

Do I need these dependencies for elog to work? If I do need them where do I get them for Suse 10.2.

Thank you for any help.

Carl

error: Failed dependencies:
	libssl.so.6 is needed by elog-2.7.5-1.i386
	rtld(GNU_HASH) is needed by elog-2.7.5-1.i386

 Starting from 2.7.5, elog needs libssl for any https:// connection. Just install the RPM like you install any other RPM. Now I'm not familar with SUSE, but I found links like that:

http://lenz.homelinux.org/RPMs/

from where you can obtain RPMs. You might have to adjust your YaST installation sources. The package you need should be named opensll-xxx where xxx is some number.

error: Failed dependencies:
	libssl.so.6 is needed by elog-2.7.5-1.i386
	rtld(GNU_HASH) is needed by elog-2.7.5-1.i386

 Thank you

I will look into it.

Carl

error: Failed dependencies:
	libssl.so.6 is needed by elog-2.7.5-1.i386
	rtld(GNU_HASH) is needed by elog-2.7.5-1.i386

 Hi,

I just tried to install the latest elog on linux Fedora 10.  I also get an error saying that libssl.so.6 is needed.

But I already have libssl.so.7 installed.  Should I also install libssl.so.6 ?

thx,

-rob

[snihur@nunllap01 ~]$ rpm -qa | grep ssl
qca-ossl-2.0.0-0.4.beta3.fc10.i386
openssl-0.9.8g-12.fc10.i686
docbook-style-dsssl-1.79-5.fc9.noarch
nss_compat_ossl-0.9.4-2.fc10.i386
openssl-devel-0.9.8g-12.fc10.i386
[snihur@nunllap01 ~]$ rpm -q --provides openssl
config(openssl) = 0.9.8g-12.fc10
lib4758cca.so 
libaep.so 
libatalla.so 
libchil.so 
libcrypto.so.7 
libcswift.so 
libgmp.so 
libnuron.so 
libssl.so.7 
libsureware.so 
libubsec.so 
openssl = 0.9.8g-12.fc10
openssl(x86-32) = 0.9.8g-12.fc10

error: Failed dependencies:
	libssl.so.6 is needed by elog-2.7.5-1.i386
	rtld(GNU_HASH) is needed by elog-2.7.5-1.i386

The RPM system is a bit picky about which version is required. I believe you have to install libssl.so.7 or compile elog from the sources, which is very simple. 

Initially I thought you had to specify a port number after localhost for emailing.

As it turns out just putting "localhost" as the email server in the elog config

file works just fine. We have a strange problem where our elog server is running.

our outgoing mail has to be routed through port 465 and SSL. I had to set up

postfix and stunnel to handle this arrangement.

 What was your problem (maybe others could benefit from this information...) ???

I update my elog from version 2.7.5 to 2.7.6 and mistakenly replace configuration file. so i have to reconfigure everything from ground up.  when my elog back online, old log messages are not show up. is there a way to import old log messages from old log book to new one.

thanks

You don't have to import old log book messages, they should be shown automatically (as long as you don't overwrite your configuration file mistakenly). If you had a different logbook name (not "demo") your files will still be there under c:\Program Files\ELOG\logbooks\<logbook name>.  Just add the proper name in elogd.cfg, restart elogd and you will see your old messages.