Demo
Discussion
Forum
Config Examples
Contributions
Vulnerabilities
Discussion forum about ELOG, Page 344 of 807
Not logged in
Find
|
Login
|
Help
Full
| Summary |
Threaded
-- All entries --
Last day
Last 3 Days
Last week
Last month
Last 3 Months
Last 6 Months
Last Year
-- Category --
Info
Bug report
Bug fix
Question
Request
Comment
Other
6454 Entries
Goto page
Previous
1
,
2
,
3
...
343
, 344,
345
...
805
,
806
,
807
Next
ID
Date
Icon
Author
Author Email
Category
OS
ELOG Version
Subject
Text
68795
Sat May 5 20:55:23 2018
Andreas Luedeke
andreas.luedeke@psi.ch
Bug report
Linux
2.9.2
Re: Elog ID entry bug at >99999 entries
Well, in my example the ID link worked
just fine.
There could be a string length
68796
Mon May 7 14:24:18 2018
Stefan Ritt
stefan.ritt@psi.ch
Bug report
Linux
2.9.2
Re: Elog ID entry bug at >99999 entries
As 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
Chris Rasmussen
chris.rasmussen@cern.ch
Bug report
Linux
2.9.2
Re: Elog ID entry bug at >99999 entries
ah 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
Joseph McKenna
joseph.mckenna@cern.ch
Bug report
Linux
2.9.2
Re: Elog ID entry bug at >99999 entries
Thank you all for your kind responses.
Please consider this thread resolved: no
bug in elog
68829
Fri Jul 13 19:14:21 2018
Lars Martin
lmartin@triumf.ca
Question
Linux
2.9.2
Re: Entry size too large for email notification
Wouldn'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
Stefan Ritt
stefan.ritt@psi.ch
Question
Linux
2.9.2
Re: Entry size too large for email notification
That's how it is implemented. If you
use
68973
Thu May 16 01:13:31 2019
Lesley Herren
lherren@lhs.org
Question
Windows
2.9.2
Windows Server 2012 - moving logs
We 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
Stefan Ritt
stefan.ritt@psi.ch
Question
Windows
2.9.2
Re: Windows Server 2012 - moving logs
Just stop the server. Move your elog directory
to the new server (including elogd.cfg, logbook
directories, ...). Then check that the elogd.cfg
Goto page
Previous
1
,
2
,
3
...
343
, 344,
345
...
805
,
806
,
807
Next
ELOG V3.1.5-3fb85fa6