Problems with Autorization, posted by Michael Dannmeyer on Wed Jun 27 10:42:20 2012
|
Hello,
we used Admin and write passwords. Now this is no longer supported in ELOG 2.9.0 and I tried to change to File or Kerberos Autentication. But nothing worked. I tried the following lines in elog.cfg
[Serverlogbuch]
Authentication = File
Password file = C:\Program Files\ELOG\logbooks\Serverlogbuch\pwd.txt
Self Authentication = 1
So the self Autentication site opens and I can put in all informations. But if I click on save he tries to save the information in the password file and after a time he stops and Internet Explorer says that the page cannot be reached.
The file is not saved. If I remove the 3 lines the logbook opens without any problems.
I tried also kerberos but it didn't work. But there I think some entries in the krb5.ini are wrong.
Would you please help solving the File password problem?
Best Regards
Michael
|
Re: Problems with Autorization, posted by Michael Dannmeyer on Thu Jul 5 11:18:40 2012
|
| Andreas Luedeke wrote: |
|
| Michael Dannmeyer wrote: |
|
Hello,
we used Admin and write passwords. Now this is no longer supported in ELOG 2.9.0 and I tried to change to File or Kerberos Autentication. But nothing worked. I tried the following lines in elog.cfg
[Serverlogbuch]
Authentication = File
Password file = C:\Program Files\ELOG\logbooks\Serverlogbuch\pwd.txt
Self Authentication = 1
So the self Autentication site opens and I can put in all informations. But if I click on save he tries to save the information in the password file and after a time he stops and Internet Explorer says that the page cannot be reached.
The file is not saved. If I remove the 3 lines the logbook opens without any problems.
I tried also kerberos but it didn't work. But there I think some entries in the krb5.ini are wrong.
Would you please help solving the File password problem?
[...] |
Just two hints:
- The file mentioned as "Password file" should be writeable for the "elogd" process. It is needed for both, Kerberos and File authentication. Better not specify the full path, it should assume the file in the logbook directory.
- The command "Self Authentication = 1" does not exist. Maybe you mean "Self register = 1"?
|
Thank you for the answer, but it didn't solve the problem.
- I used Self Register instead of Self Authentication. I deleted the complete path and only used the Filename.
-
The Account which is used to start the Elogd process is local system. System has full right at the logbook directory
Should I use an Admin Account for the elogd process? The error message is always the same (page not reachable) The File is also not created in the logbook dir.
|
Re: Problems with Autorization, posted by Michael Dannmeyer on Fri Jul 13 15:12:07 2012
|
| Stefan Ritt wrote: |
|
| Michael Dannmeyer wrote: |
|
| Andreas Luedeke wrote: |
|
| Michael Dannmeyer wrote: |
|
Hello,
we used Admin and write passwords. Now this is no longer supported in ELOG 2.9.0 and I tried to change to File or Kerberos Autentication. But nothing worked. I tried the following lines in elog.cfg
[Serverlogbuch]
Authentication = File
Password file = C:\Program Files\ELOG\logbooks\Serverlogbuch\pwd.txt
Self Authentication = 1
So the self Autentication site opens and I can put in all informations. But if I click on save he tries to save the information in the password file and after a time he stops and Internet Explorer says that the page cannot be reached.
The file is not saved. If I remove the 3 lines the logbook opens without any problems.
I tried also kerberos but it didn't work. But there I think some entries in the krb5.ini are wrong.
Would you please help solving the File password problem?
[...] |
Just two hints:
- The file mentioned as "Password file" should be writeable for the "elogd" process. It is needed for both, Kerberos and File authentication. Better not specify the full path, it should assume the file in the logbook directory.
- The command "Self Authentication = 1" does not exist. Maybe you mean "Self register = 1"?
|
Thank you for the answer, but it didn't solve the problem.
- I used Self Register instead of Self Authentication. I deleted the complete path and only used the Filename.
-
The Account which is used to start the Elogd process is local system. System has full right at the logbook directory
Should I use an Admin Account for the elogd process? The error message is always the same (page not reachable) The File is also not created in the logbook dir.
|
I once had problems with the local system account, so I used my own account to start the service and that worked. For trial, you can also start the elogd.exe program manually (not as a service) in a DOS box and see if it can create the password file.
|
That worked for me. Used an Account instead of local system and everything is OK. Thanks for your help. |
|
Re: Synchronization using https, posted by Marcus Hauser on Tue Feb 13 15:11:18 2007
|
| Stefan Ritt wrote: |
| Alexandre Lindote wrote: | | Now we want to have several servers set up (in different institutions), and have them synchronized automatically. |
Synchronization works such that the "client" elogd (the one on which the synchronization is started) "emulates" a browser and accesses the other elogd server. Since SSL is not built into elogd, it can only use the http protocol, not https. If you want secure synchronization, the only chance you have is to make a SSH tunnel on which you run the http protocol for synchronization. |
Would it be possible to use rsync to syncronise two elogd servers on different servers via secure synchronization on the file level?
E.g.
rsync -av -e ssh /var/lib/elog/logbooks/ elog.remote.de:/var/lib/elog/logbooks/ |
Anyone else running elogd on redhat ES 8 having random crashes?, posted by mathew goebel on Tue Oct 4 20:43:28 2022
|
For the last couple of months we are getting a random elogd crash once in a while we are getting something like the following in the middle of the night
> Sep 29 20:45:07 elog kernel: server_name686835]: segfault at 7ffd7f5a0000 ip 00007fceaeabbf06 sp 00007ffd7f577348 error 6 in libc-2.28.so[7fceaea8a000+1bc000]
I'm going to try and see if it will leave a coredump file, just thought I would ask if anyone else had seen this before?
Thanks,
Matt
|
|
Re: Anyone else running elogd on redhat ES 8 having random crashes?, posted by mathew goebel on Wed Oct 5 20:39:16 2022
|
Thanks for the info!
| Stefan Ritt wrote: |
|
Most likely these are some currupt logbook files. If you get a coredump (or stack trace) you can maybe figure out which file it was. These are plain ASCII files (YYMMDDa.log) and you can see with an editor if someting there is not in order.
Stefan
| mathew goebel wrote: |
|
For the last couple of months we are getting a random elogd crash once in a while we are getting something like the following in the middle of the night
> Sep 29 20:45:07 elog kernel: server_name686835]: segfault at 7ffd7f5a0000 ip 00007fceaeabbf06 sp 00007ffd7f577348 error 6 in libc-2.28.so[7fceaea8a000+1bc000]
I'm going to try and see if it will leave a coredump file, just thought I would ask if anyone else had seen this before?
Thanks,
Matt
|
|
|
|
once a week we are having elogd segault?, posted by mathew goebel on Fri Jul 18 17:46:43 2025
|
Jul 17 20:36:21 elog kernel: elogd[179095]: segfault at 7ffda4d82000 ip 00007f97033a1406 sp 00007ffda4d58c38 error 6 in libc-2.28.so[7f9703374000+1cd000]
Elog version ELOG V3.1.5-30ada1df
Running on a Rehdat 8 enterprise server
compiled with a Makefile change :: change -Wno-unused-result to -Wno-unused-value
Wondering if anyone has been seeing this? |
|
Re: once a week we are having elogd segault?, posted by mathew goebel on Wed Aug 6 17:08:46 2025
|
We have since discovered that the security team is scanning the box in question once a week when the service crashes, with nexpose.
So if you see something similar then you might want to explore that.
| mathew goebel wrote: |
|
Jul 17 20:36:21 elog kernel: elogd[179095]: segfault at 7ffda4d82000 ip 00007f97033a1406 sp 00007ffda4d58c38 error 6 in libc-2.28.so[7f9703374000+1cd000]
Elog version ELOG V3.1.5-30ada1df
Running on a Rehdat 8 enterprise server
compiled with a Makefile change :: change -Wno-unused-result to -Wno-unused-value
Wondering if anyone has been seeing this?
|
|