| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66325
|
Tue Apr 21 16:29:23 2009 |
 | Joseph Le | josephle9@gmail.com | Question | Windows | 2.7.6 | Is there a way to import old log messages |
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 |
|
66326
|
Tue Apr 21 20:32:10 2009 |
 | Hal Proctor | hproctor@mpm.com | Question | Windows | 2.7.5 | Re: Multi Logook Login RESOLVED |
| Stefan Ritt wrote: |
|
| Hal Proctor wrote: |
|
| Grant Jeffcote wrote: |
|
|
Hal Proctor wrote:
|
|
We have two logbooks, each with a different list of users.
The logbooks are open to all network users for read only.
A user with Write permisions logs into his designated logbook.
He then decides to view the other logbook, the one he does not have write permissions to by clicking on the tab to the other logbook.
He is immediately logged out of the logbook he has write permissions to.
He did not close his browser session, only clicked on the other logbook tab.
Is there Any way to keep that person logged into the logbook he has rights to without having the "keep me logged in Checkbox"?
Just like this site has Forum, Config Examples, etc.
Once you select another tab they are logged out of their logbook they just logged in to.
|
Have a look at this thread Hal, worked well for me: Link
|
thanks Grant, but I dont see the solution. your last entry still states users being logged out when switching logbooks.
Are you suggesting that every user within our orginization needs to be on the deny list of logbook1 if they have rights to logook2?
|
Can you try the following:
- Put your "password file = xxx" option from the [global] section in elogd.cfg into each individual logook, remove it from [global]
- Remove all cookies from your browser
- Try again to log in to the individual logbooks
The login is handled through cookies. Once you log in, you get two cookies unm (for user name) and upwd (for user password). Each cookie contains a "path" which controls to which URL the browser sends that cookie. If you "password file = xxx" statement is under [global], then "path=/", meaning the cookie is sent for all logbooks. This confuses you if you have different rights for different logooks. If "password file = xxx" is however in each individual loogbooks configuration, then you get "path=/<lobook>". You can check that by inspecting your browser's cookies. In that case the login name and password cookies are only sent to the URL for that specific logbook. I have not tested that extensively (different browsers, with/without Apache proxy), but if it works reliably, I will put this into the documentation.
|
This worked for us just fine! thanks! |
|
66327
|
Tue Apr 21 22:13:26 2009 |
 | Andreas Wilke | wilke4all@hotmail.de | Question | Windows | 2.7.5-2130 | Mirror Server Funktion |
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".......
|
|
66328
|
Fri Apr 24 09:03:05 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.6 | Re: Is there a way to import old log messages |
| Joseph Le wrote: |
|
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. |
|
66329
|
Fri Apr 24 12:25:16 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.6-219 | Re: mail to localhost? |
What was your problem (maybe others could benefit from this information...) ??? |
|
66330
|
Tue Apr 28 05:53:19 2009 |
| Rob Snihur | snihur@fnal.gov | Question | Linux | 2.7.2-3 | Re: Error: Failed dependencies: |
| Carl Shirey wrote: |
|
| Stefan Ritt wrote: |
|
| Carl Shirey wrote: |
|
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
|
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.
|
Thank you
I will look into it.
Carl
|
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 |
|
66331
|
Tue Apr 28 07:53:37 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.2-3 | Re: Error: Failed dependencies: |
| Rob Snihur wrote: |
|
| Carl Shirey wrote: |
|
| Stefan Ritt wrote: |
|
| Carl Shirey wrote: |
|
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
|
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.
|
Thank you
I will look into it.
Carl
|
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
|
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. |
|
66332
|
Tue Apr 28 21:25:31 2009 |
| Dongwook Jang | dwjang@fnal.gov | Question | Linux | 2.7.6 | elogd runs by a user but not by root |
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 |