Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 438 of 808  Not logged in ELOG logo
icon5.gif   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
    icon2.gif   Re: Problems with Autorization, posted by Michael Dannmeyer on Thu Jul 5 11:18:40 2012 


    
        
            Andreas Luedeke wrote:
        
        
            
  
    icon14.gif   Re: Problems with Autorization, posted by Michael Dannmeyer on Fri Jul 13 15:12:07 2012 


    
        
            Stefan Ritt wrote:
        
        
            
      
    icon5.gif   Re: Synchronization using https, posted by Marcus Hauser on Tue Feb 13 15:11:18 2007 
[quote="Stefan Ritt"][quote="Alexandre Lindote"] Now we want to have several servers set up (in different institutions), and have them synchronized automatically.[/quote]

Synchronization works such that the "client" elogd (the one on which the synchronization is started) "emulates" a browser and accesses the other elogd
icon8.gif   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]
    icon2.gif   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
icon8.gif   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 
    icon2.gif   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
ELOG V3.1.5-3fb85fa6