Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 354 of 807  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Collapse | Expand  Show only new entries    6456 Entries 
Goto page Previous  1, 2, 3 ... 353, 354, 355 ... 805, 806, 807   Next  
    icon2.gif   Re: Problems with ELOG and Internet Explorer, posted by Stefan Ritt on Wed Jan 18 13:31:32 2006 
Have you tried another browser, like Firefox? Do you have the same problems with Firefox? Can you try the following:

Start elogd manually with the "-v" flag, like
elogd -c <your config path> -v -p 8080
and watch the output carefully. When you submit an entry, elogd does redirection. You will see that in the HTTP header you have an entry like
...
Location: https://...
...
This location is taken from the URL statement of your config file. If it's wrong (like if you mixed http:// and https://), your browser will try to load the page from a non-existion location.
    icon2.gif   Re: Problems with Autorization, posted by Andreas Luedeke on Wed Jul 4 14:04:10 2012 

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"?
    icon2.gif   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.

 

    icon2.gif   Re: Problems with Autorization, posted by Stefan Ritt on Fri Jul 13 09:03:02 2012 

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. 

    icon14.gif   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.

    icon2.gif   Re: Problems with 2.3.2, posted by Stefan Ritt on Thu Mar 13 17:33:58 2003  
> Ive just installed the RPM of Elog 2.3.2 and ive found a bug relating to 
> port bindings, basically im running elog bound to port 81 and when i 
> install the new RPM it refuses to bind to this port, i tried port 8080 and 
> that worked fine
> 
> Any ideas ?

This is a bug I discovered myself just today, so we are working on it. I 
expect this to be fixed by tomorrow or somewhen during this weekend.

- Stefan
    icon2.gif   Re: Problems with 2.3.2, posted by Stefan Ritt on Fri Mar 14 10:30:25 2003  
> > Ive just installed the RPM of Elog 2.3.2 and ive found a bug relating to 
> > port bindings, basically im running elog bound to port 81 and when i 
> > install the new RPM it refuses to bind to this port, i tried port 8080 
and 
> > that worked fine

The bug has been fixed in V 2.3.3 which has been released today.
    icon2.gif   Re: Problems when trying to set up mirror elog , posted by Stefan Ritt on Wed Jul 29 09:33:16 2009 

Ricardo Goncalo wrote:

Any ideas of what I'm doing wrong? 

Yepp. Synchronizing over SSL does not yet work. I have it on my to-do list since quite some time, but can't find the time to implement it. So at the moment you have to synchronize without SSL. 

Goto page Previous  1, 2, 3 ... 353, 354, 355 ... 805, 806, 807   Next  
ELOG V3.1.5-3fb85fa6