Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 510 of 808  Not logged in ELOG logo
ID Date Icondown Author Author Email Category OS ELOG Version Subject Text Attachments
  69290   Fri Jan 8 15:35:35 2021 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux | Windows3.1.2Re: Parsing log filesWell, you could put the old options back
to the config file, do the export, then remove
them again.
  
  69294   Thu Jan 14 14:05:19 2021 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.3Re: elog slownessHave you tried to restart the elogd server?
The CLOSE_WAIT could be dangling network
connections, which were not properly closed
  
  69296   Tue Feb 2 07:43:49 2021 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux | Windows3.1.4Re: Different Top Groups or Groups have the same logbook name Unfortunately you have to name these top
groups differently, because they are internally
used for the database name.
  
  69297   Tue Feb 2 08:17:15 2021 Reply MATT TERRONmatao11235@gmail.comQuestionLinux | Windows3.1.4Re: Different Top Groups or Groups have the same logbook name So both Top Group names and Logbook
names should be unique inside one .cfg file,
is that correct?
  
  69298   Tue Feb 2 08:25:46 2021 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux | Windows3.1.4Re: Different Top Groups or Groups have the same logbook name That's correct.




  
  69299   Wed Feb 3 17:28:16 2021 Reply Gabriel Lopezgabelopez@bnl.govBug reportLinux3.1.4Re: Path disclosure on unfound fileHello, This is coming up as a high vulnerability
in our scans. Are there plans to update the
rpm for this fix? If so is there an ETA?
  
  69301   Thu Feb 18 12:05:52 2021 Reply David PilgramDavid.Pilgram@epost.org.ukBug reportLinux3.1.4-2Re: elog server go to high CPU and hangsDear Stefano,

Try the entry I wrote some time ago elog:68655
  
  69302   Thu Feb 18 12:06:12 2021 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux3.1.4-2Re: elog server go to high CPU and hangsUsually a restart of the elogd server helps.
If the problem persists, one of the logbooks
might be corrupt. Try to disable one logbook
  
ELOG V3.1.5-3fb85fa6