Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 344 of 807  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject Text Attachments
  68795   Sat May 5 20:55:23 2018 Reply Andreas Luedekeandreas.luedeke@psi.chBug reportLinux2.9.2Re: Elog ID entry bug at >99999 entriesWell, in my example the ID link worked
just fine.

There could be a string length
  
  68796   Mon May 7 14:24:18 2018 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.9.2Re: Elog ID entry bug at >99999 entriesAs Andreas said we have to reproduce the
problem. What is special in your case is
the elog:SequencerEvents/XXXXX.
  
  68797   Mon May 7 18:10:20 2018 Reply Chris Rasmussenchris.rasmussen@cern.chBug reportLinux2.9.2Re: Elog ID entry bug at >99999 entriesah yes, that was a helpful clue. Our elogd.cfg
file led me to a .js file which redefines
the ID to the elog:SequencerEvents/XXXXX
  
  68798   Tue May 8 16:17:28 2018 Agree Joseph McKennajoseph.mckenna@cern.chBug reportLinux2.9.2Re: Elog ID entry bug at >99999 entriesThank you all for your kind responses.
Please consider this thread resolved: no
bug in elog
  
  68829   Fri Jul 13 19:14:21 2018 Reply Lars Martinlmartin@triumf.caQuestionLinux2.9.2Re: Entry size too large for email notificationWouldn't it make sense for ELog (by
default) to still notify, but not send the
attachments by e-mail if the size limit is
  
  68837   Mon Aug 27 13:07:28 2018 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.9.2Re: Entry size too large for email notificationThat's how it is implemented. If you
use

  
  68973   Thu May 16 01:13:31 2019 Question Lesley Herrenlherren@lhs.orgQuestionWindows2.9.2Windows Server 2012 - moving logsWe are installing a new data center which
will be based on Windows 2012 servers. 
Our current center is on Windows 2008 and
  
  68974   Thu May 16 09:12:52 2019 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.9.2Re: Windows Server 2012 - moving logsJust stop the server. Move your elog directory
to the new server (including elogd.cfg, logbook
directories, ...). Then check that the elogd.cfg
  
ELOG V3.1.5-3fb85fa6