Re: Monitoring a logbook for changes, posted by Johan Forsberg on Wed Jan 13 20:08:04 2016
|
Aha, that's interesting too! I'll have to look more carefully through the documentation... :)
| Stefan Ritt wrote: |
|
You guys know that there is the possibility to execute an arbitrary script on each submission of a new messge? Just use "Execute new = <script>". In the script you have access to all parameters of the message. That's maybe simple than to watch the file set.
| Tamas Gal wrote: |
|
I just noticed that there are multiple messages per file, so I have to adapt the parser. I'll update this thread when I'm done!
| Johan Forsberg wrote: |
|
Yeah, I suppose something like that would be both faster and more efficient than polling ELOG itself. Fortunately the ELOG disk format looks easily parsed.
Thanks for the pointer!
| Tamas Gal wrote: |
|
I recommend monitoring directly on the server. Here is an example of a very simply Python script (https://github.com/tamasgal/elog-slack) which monitors the files very efficiently and immediately pushes notifications to Slack (slack.com). Just look at the code, it's pretty straight forward and very easy to adapt it to other (web) services.
Btw. here is an ELOG entry of it https://midas.psi.ch/elogs/Forum/68224
| Johan Forsberg wrote: |
|
Hi again!
I've another need that you probably already thought of :)
I'd like to be able to efficiently monitor a logbook for changes (new or edited posts) somehow. The most reasonable way I've found so far is to periodically poll a search that looks for posts after the time of the last poll. But that might note be very efficient, especially if the polling period gets short (or number of clients grows).
Is there some other feature that could be used for this? I was thinking maybe the ETag or Last-Modified HTTP header field could be used to show changes to a logbook by just reading the headers, but it would also require HEAD request support which does not seem to be there.
Cheers,
Johan
|
|
|
|
|
|
Escape character [ or ] doesn't work within [url], posted by Don on Fri Jul 15 19:46:26 2016
|
Here is the problem:
[url=http://example.com?arrays[]=v1&arrays[]=v2]click here[/url]
How can I escape [] inside url tag?
\[\] seems not working. |
Re: Escape character [ or ] doesn't work within [url], posted by Andreas Luedeke on Mon Jul 18 23:37:22 2016
|
The URL encoding of ']' as '%5D' appears to work:
[url=http://example.com?arrays[%5D=v1&arrays[%5D=v2]click here[/url]
Cheers, Andreas
| Don wrote: |
|
Here is the problem:
[url=http://example.com?arrays[]=v1&arrays[]=v2]click here[/url]
How can I escape [] inside url tag?
\[\] seems not working.
|
|
|
Re: Escape character [ or ] doesn't work within [url], posted by Don on Tue Jul 19 21:08:08 2016
|
| Andreas Luedeke wrote: |
|
The URL encoding of ']' as '%5D' appears to work:
[url=http://example.com?arrays[%5D=v1&arrays[%5D=v2]click here[/url]
Cheers, Andreas
| Don wrote: |
|
Here is the problem:
[url=http://example.com?arrays[]=v1&arrays[]=v2]click here[/url]
How can I escape [] inside url tag?
\[\] seems not working.
|
|
That tweak works!
Thanks |
|
string length limit in url tag, posted by Don on Wed Jul 20 16:03:24 2016
|
What is the string length limit in url tag and how to increase it?
For example,
[url=http://example.com?<text_string>]click here[/url]
When I provide very long <text_string>, it was truncated and showed partial link only. |
|
Re: string length limit in url tag, posted by Andreas Luedeke on Thu Jul 21 06:15:44 2016
|
Several strings in ELOG are limited to 256 chars. It is likely the limit for URLs, too.
The magic number "256" appears 285 times in the elogd.c file.
It is probaly easier if you compress long URLs with goo.gl
Cheers, Andreas
| Don wrote: |
|
What is the string length limit in url tag and how to increase it?
For example,
[url=http://example.com?<text_string>]click here[/url]
When I provide very long <text_string>, it was truncated and showed partial link only.
|
|
elogd dies upon search, posted by Christian Ludwig on Fri Jun 3 08:16:31 2016
|
Hi all,
ELOG V3.0.0-21dc563
Our elogd dies alwways when searching for full text:
elogd: src/elogd.c:465: xrealloc: Assertion `*((unsigned int *) (temp + old_size)) == 0xdeadc0de' failed.
elogd: src/elogd.c:465: xrealloc: Assertion `*((unsigned int *) (temp + old_size)) == 0xdeadc0de' failed.
The only change we did was adding/editing entries.
Does anyone else encounter the same issue ?
I did not find any hint in release notes that this issue would be fixed in a later version
Please don't get me wrong, I am not complaining. Elog does a great job for us since years.
Christian |
solved: elogd dies upon search, posted by Christian Ludwig on Fri Jun 3 08:59:49 2016
|
I would like to share my findings about the solution of our problem:
One of my collegues used elog in a way it was not intended for, he put an endry with 8021 lines of text.
So I grabbed the corresponding 160517a.log file from logdir, renamed it to a text file and created a new entry with the large textfile as attachment.
Since then, no more crash of elogs.
May this contribution be useful to other elog users...
Christian
| Christian Ludwig wrote: |
|
Hi all,
ELOG V3.0.0-21dc563
Our elogd dies alwways when searching for full text:
elogd: src/elogd.c:465: xrealloc: Assertion `*((unsigned int *) (temp + old_size)) == 0xdeadc0de' failed.
elogd: src/elogd.c:465: xrealloc: Assertion `*((unsigned int *) (temp + old_size)) == 0xdeadc0de' failed.
The only change we did was adding/editing entries.
Does anyone else encounter the same issue ?
I did not find any hint in release notes that this issue would be fixed in a later version
Please don't get me wrong, I am not complaining. Elog does a great job for us since years.
Christian
|
|