| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1485
|
Mon Oct 24 19:33:41 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Other | 2.6.0 b4 | Re: Login screen reappears after correct login |
| Daniel Broers wrote: | | But why would one client have problems while others don't? |
You had the login expiration at 1 hour, and the time was off by one hour I guess. But each client's time is only accurate to a few minutes, so some of them had a difference to the server of 59 mins, and other had 1:01 mins. Since you had a login expiration of 1 hour, only the second one failed, while the first one should have worked for about one minute. |
|
1196
|
Fri Jun 17 20:30:53 2005 |
 | Gerfried Kumbartzki | kum@physics.rutgers.edu | Question | Linux | 2.6.0 | Cloning | Elog is installed on a laptop (Redhat Linux 2.4.20-8) for quite a while. I like to have a "base" of that logbook on a server and keep it
in sync. Mirroring seem to be the perfect solution. For that I updated to elog v2.6.0 yesterday.
The server is an Alpha running Linux Redhat 7.1. I compiled from elog-latest.tar and installed elog in the 'same' locations as on the laptop.
Created a user elog and a group elog, put elogd.cfg, themes, logbooks ... in /usr/local/elog, owned by elog. Started the elogd, tested,
all seems to work. The elogd.cfg has a read and write passwd set. Any user can access the logbook, read and write after providing the proper user id and password.
Next I wanted to clone the logbooks from the laptop to the server. As superuser I can start elogd -v -C http://latop:8080, but get stuck right away with "Cannot contact elogd at http://laptop:8080/"
As user it works as follows:
Remote configuration successfully received.
Option "Mirror server = http://wotan.rutgers.edu:8080" added to config file.
Logbook directory "logbooks" successfully created.
Created directory "demo"
Indexing logbook "demo" ... Found empty logbook "demo"
Created directory "tfexp"
Indexing logbook "tfexp" ... Found empty logbook "tfexp"
Retrieve remote logbook entries? [y]/n:
Retrieving entries from "http://wotan.rutgers.edu:8080/demo"...
ID1: Remote entry received
Retrieving entries from "http://wotan.rutgers.edu:8080/tfexp"...
Error accessing remote logbook
Cloning finished. Check elogd.cfg and start the server normally.
Allthough, tfexp contains a number of entries all owned by elog like the entry in demo.
Beside missing the real stuff everything ends up in the users home directory. I would like it in the general area (/usr/local/elog for instance).
The other option is to use synchronize after changing [global] from with in the browser. Start elogd, open the logbook and click on config,
enter a Mirror server = http://laptop:8080/
Clicking synchronize give "Error accessing remote logbook"
Again, the logbooks are on both machines in /usr/local/elog/logbooks (owner:group elog:elog). The tfexp in this case is passwd protected.
Any user can access the elogs in both machines, locally or remote. But, I'm unable to synchronize the two.
Maybe somebody can point me in the right direction.
Thank's Gerfried |
|
1197
|
Fri Jun 17 22:08:28 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.0 | Re: Cloning |
| Gerfried Kumbartzki wrote: | | The elogd.cfg has a read and write passwd set. Any user can access the logbook, read and write after providing the proper user id and password. |
This might be your problem. Try to temporarily remove the read and write password from you config file, then do the cloning, then put it back. Cloning works with a passowd file, but I haven't tested it with read/write passwords.
| Gerfried Kumbartzki wrote: | | Beside missing the real stuff everything ends up in the users home directory. I would like it in the general area (/usr/local/elog for instance). |
The cloning works in the current directory. So just go to /usr/local/elog and start "elogd -C ..." from there. Alternatively, copy your whole /usr/local/elog tree to the server manually. The "Synchronize" button then works again only with a password file. You need a "Mirror user = xxx" option in that case. |
|
1209
|
Wed Jun 22 18:34:18 2005 |
| Gerfried Kumbartzki | kum@physics.rutgers.edu | Question | Linux | 2.6.0 | Re: Cloning | Thank you for the suggestions; I commented the read and write passwd in elogd.cfg out and only then I was able to clone
(elogd -v -C http://laptop:8080) the logbook to the new server.
But this is only part of the story. The logbook on the labtop is owned by the
default user elog and default group elog, that is needed to start up the elogd. Only a user "elog" can do the cloning, unless temporarily the owner ship in /usr/local/elog is changed. I made it work by temporarily changing the owner ship on both machines, did the cloning, changed back to owner elog, started elogd and all was running.
I setup synchronizing and here too it works only if the read passwd in elogd.cfg is commented out.
Sync works fine from the RedHat linux laptop (rpm installed), but crashes the elogd on the alpha Linux machine (compiled from src) most of the time. elogd hast to be restarted and the sync had not finished.
So for now I settled to do the synchronize only from the laptop but have to remove the read passwd each time. That is tolerable but not
convenient.
Here I have another question: My Elog is passwd protected, encrypted passwd in elogd.cfg (read and write). When connecting to the elog the window
pops up asking for a user name and the passwd. I donot remember exactly, what was done to set name and passwd. But I find it "strange" that the user name can be anything as long as the passwd is right to access the ELog.
I think I have to learn more about the whole user and passwd protection schema.
Thanks again
Gerfried |
|
1214
|
Fri Jun 24 21:24:55 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.0 | Re: Cloning |
| Gerfried Kumbartzki wrote: | But this is only part of the story. The logbook on the labtop is owned by the
default user elog and default group elog, that is needed to start up the elogd. Only a user "elog" can do the cloning, unless temporarily the owner ship in /usr/local/elog is changed. I made it work by temporarily changing the owner ship on both machines, did the cloning, changed back to owner elog, started elogd and all was running. |
The /usr/local/elog files should be owned by user elog on both machines, and both elogd daemons should be started under user elog. Since only the two elogd daemons communicate with each other during synchronization, that should be fine. Only after the initial cloning (which you presumably do under your own user account), you have to do a "chmod" to change ownership of all files to uid/gid "elog/elog".
| Gerfried Kumbartzki wrote: | | I setup synchronizing and here too it works only if the read passwd in elogd.cfg is commented out. |
As I said, the read password is not really supported for synchronization. It is there historically, from the times when there was no user level password access. If you use synchronization, you should use that authentication (by putting a "password file = ..." into your config.
| Gerfried Kumbartzki wrote: | | Here I have another question: My Elog is passwd protected, encrypted passwd in elogd.cfg (read and write). When connecting to the elog the window pops up asking for a user name and the passwd. I donot remember exactly, what was done to set name and passwd. But I find it "strange" that the user name can be anything as long as the passwd is right to access the ELog. I think I have to learn more about the whole user and passwd protection schema. |
If you switch to user level password access, this problem goes away as well.
- Stefan |
|
1358
|
Thu Jul 28 15:33:21 2005 |
| Chris Howe | c.j.howe@rl.ac.uk | Bug report | Windows | 2.6.0 | Creating logbook by copying an existing one crashes elog | Hi,
Trying to create a new logbook from an existing one causes elog to crash.
output from DrMingw:
elogd.exe caused an Access Violation at location 00448c6e in module elogd.exe
Writing to location 6e206c65.
Registers:
eax=00240798 ebx=00000020 ecx=6e206c61 edx=00250088 esi=00000000 edi=69726500
eip=00448c6e esp=01c1a1d0 ebp=01c1a1f0 iopl=0 nv up ei ng nz ac po cy
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000297
Call stack:
00448C6E elogd.exe:00448C6E
00445F17 elogd.exe:00445F17
as the service restarts elog the browser then displays:
"Cannot open file elog.pwd: No such file or directory
Please use your browser's back button to go back"
If you try and create a new logbook from scratch (i.e. not a copy) then the browser displays:
"Cannot open file elog.pwd: No such file or directory
Please use your browser's back button to go back"
In both cases the new logbook is created.
any ideas?
Chris |
|
1362
|
Mon Aug 1 11:58:43 2005 |
| Kees Bol | kees.bol@wur.nl | Info | Linux | 2.6.0 | "full" only changes color | Hi,
I have the strange problem that when changing to "full"-diplaymode the output looks the same as with "summary", only the color is different. The texts don't appear.
Any idea what can cause this behaviour?
thanks
Kees Bol |
|
1364
|
Tue Aug 2 08:56:21 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Linux | 2.6.0 | Re: "full" only changes color |
| Kees Bol wrote: | I have the strange problem that when changing to "full"-diplaymode the output looks the same as with "summary", only the color is different. The texts don't appear.
Any idea what can cause this behaviour? |
Can you send me your elogd.cfg ?
Have you made sure that the entries do contain some text? The behaviour you describe usually happens if you have entries without any text. |
|