Re: Login screen reappears after correct login, posted by Daniel Broers on Mon Oct 24 14:50:58 2005
|
| Stefan Ritt wrote: |
| Daniel Broers wrote: | We are running elog perfectly on a solaris machine for some time now.
Except on some client pc's the login screen keeps reappearing after a succesfull login.
We upgraded to version 2.6.0 beta 4 but the problem persists.
Any suggestions? |
Do you have cookies disabled on these client pc's maybe? |
No, cookies are enabled. |
|
Re: Login screen reappears after correct login, posted by Stefan Ritt on Mon Oct 24 15:18:46 2005
|
| Daniel Broers wrote: | | No, cookies are enabled. |
Can you
- Delete all cookies on the client machine and try again
- If the problem persists: Tell you how you access your elogd. Do you use Apache as proxy? Which URL statement do you have in your elogd.cfg? What are the URLs shown in the address bar of your browser?
- Can you start elogd with the "-v" flag, and send me the output shown during an unsuccessful login
|
Re: Login screen reappears after correct login, posted by Daniel Broers on Mon Oct 24 16:20:37 2005 
|
| Stefan Ritt wrote: |
Can you
- Delete all cookies on the client machine and try again
- If the problem persists: Tell you how you access your elogd. Do you use Apache as proxy? Which URL statement do you have in your elogd.cfg? What are the URLs shown in the address bar of your browser?
- Can you start elogd with the "-v" flag, and send me the output shown during an unsuccessful login
|
|
|
Re: Login screen reappears after correct login, posted by Stefan Ritt on Mon Oct 24 16:41:20 2005
|
| Daniel Broers wrote: | | Output in attachment |
Your output shows:
Set-Cookie: unm=daniel; path=/Maldi; expires=Monday, 24-Oct-05 14:57:55 GMT;
Now I don't know when you made this entry, but it looks to me like either
- your time is set incorrectly on the server side
- your "login expiration" setting in elogd is set incorrectly
Can you check these two things? |
|
Re: Login screen reappears after correct login, posted by Daniel Broers on Mon Oct 24 17:14:59 2005
|
| Stefan Ritt wrote: |
| Daniel Broers wrote: | | Output in attachment |
Your output shows:
Set-Cookie: unm=daniel; path=/Maldi; expires=Monday, 24-Oct-05 14:57:55 GMT;
Now I don't know when you made this entry, but it looks to me like either
- your time is set incorrectly on the server side
- your "login expiration" setting in elogd is set incorrectly
Can you check these two things? |
Now it works!
- The time is (apparently) set incorect on the server side. But why would one client have problems while others don't?
- I changed the login expitation from 1 to 5 hours and now we can log in!
Thanks a lot for your quick support! |
|
Re: Login screen reappears after correct login, posted by Stefan Ritt on Mon Oct 24 19:33:41 2005
|
| 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. |
Cloning, posted by Gerfried Kumbartzki on Fri Jun 17 20:30:53 2005
|
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 |
|
Re: Cloning, posted by Stefan Ritt on Fri Jun 17 22:08:28 2005
|
| 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. |