Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 495 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OSdown ELOG Version Subject
  67124   Tue Sep 20 04:46:55 2011 Warning Ryanryan.hoitt@intelsat.comBug reportLinux2.9.0-2411Memory Leak in V2.9.0-2411 (Mirroring Related)

I have two identical servers (IBM X337) setup on the same LAN with Ubuntu Linux 10.04 LTS with ELOGD running (Compiled from tarbell) with the same exact package install base. (Only difference between the two servers is the hostname, and the ELOGD.CFG global section)

I noticed after setting these servers up today that ELOGD crashed on the server configured to mirror. It looks like there may be a memory leak in the mirroring of ELOG.
SERVER 1 ELOGD.CFG
[global]
Mirror server = http://10.146.1.76
Mirror config = 1
Mirror cron = 0,5,10,15,20,25,30,35,40,45,50,55 * * * *
Mirror user = (* Removed for Web Post *)
port = 80
Allowed encoding = 1
Suppress default = 3
Mode commands = 1
Password file = password.pwd
Self register = 1
Admin user = (* Removed for Web Post *)
Time format = %d-%b-%y %H:%M UTC
Group 2009 = Station Log-09, DAT-09, Hours Logging-09
Group 2010 = Station Log 10, DAT-10, Hours Logging-10
Group 2011 = Station Log, DAT, Hours Logging, Operations Tasks, Viasat-1, OS-2
Group Cable Database = Cable Database
Group Provisioning = Provisioning
Group ECR = ECR
SERVER 1 SYSLOGD (cat /var/log/syslog |grep elog)
Sep 19 12:14:13 riverside-log elogd[8588]: elogd 2.9.0 built Sep 19 2011, 10:32:58
Sep 19 12:14:13 riverside-log elogd[8588]: revision 2411
Sep 19 12:14:13 riverside-log elogd[8588]: Falling back to default group "elog"
Sep 19 12:14:13 riverside-log elogd[8588]: Falling back to default user "elog"
Sep 19 12:14:13 riverside-log elogd[8588]: FCKedit detected
Sep 19 12:14:13 riverside-log elogd[8590]: Falling back to default group "elog"
Sep 19 12:14:13 riverside-log elogd[8590]: Falling back to default user "elog"
Sep 19 12:14:13 riverside-log elogd[8588]: Server listening on port 80 ...
Sep 19 19:55:05 riverside-log elogd[8588]: xmalloc: not enough memory
SERVER 1 (Set to mirror off server 2) Memory Usage over 1 hour (ps aux|grep elog)
elog      8760 11.6 3.4109240 35092 ?
elog      8760 12.2 3.9137852 40204 ?
elog      8760 11.6 4.4165448 45440 ?
elog      8760 10.7 5.4221652 55548 ?
elog      8760 9.9 5.9249752 60552 ?
elog      8760 10.1 6.4278364 65680 ?
elog      8760 9.5 6.8305712 70700 ?
SERVER 2 Memory Usage over 1 hour (ps aux|grep elog)
elog       799 2.1 2.6 31744 27116 ?
elog       799 2.0 2.6 31744 27116 ?
elog       799 2.1 2.6 31744 27116 ?
elog       799 2.0 2.6 31744 27116 ?
elog       799 2.0 2.6 31744 27116 ?
elog       799 2.0 2.6 31744 27116 ?
elog       799 2.1 2.6 31744 27116 ?
  67127   Mon Sep 26 08:13:10 2011 Entry Olivier CallotOlivier.Callot@cern.chBug reportLinux2418Spurious characters in the searched string

Hi,

We have a problem with the search command: Since our last upgrade to v2.9.0-2418 the searched string is pre- and postfixed with ASCII character expressed in % format, see the attached image. The searched string is prefied with %255E and postfxed by %2524 in the URL. And teh search fails. This affects searches from drop-down menus.

Thanks in advance.

Attachment 1: Capture.PNG
Capture.PNG
  67128   Mon Sep 26 10:38:59 2011 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2418Re: Spurious characters in the searched string

Olivier Callot wrote:

Hi,

We have a problem with the search command: Since our last upgrade to v2.9.0-2418 the searched string is pre- and postfixed with ASCII character expressed in % format, see the attached image. The searched string is prefied with %255E and postfxed by %2524 in the URL. And teh search fails. This affects searches from drop-down menus.

Thanks in advance.

Strange. In this forum it works without extra characters. Just try it yourself. Do you have any strange configuration? Can you send me a minimal elogd.cfg which produces that error, maybe derived from the example elogd.cfg from the distribution.

- Stefan 

  67129   Mon Sep 26 11:16:19 2011 Reply Olivier CallotOlivier.Callot@cern.chBug reportLinux2418Re: Spurious characters in the searched string

Stefan Ritt wrote:

Olivier Callot wrote:

Hi,

We have a problem with the search command: Since our last upgrade to v2.9.0-2418 the searched string is pre- and postfixed with ASCII character expressed in % format, see the attached image. The searched string is prefied with %255E and postfxed by %2524 in the URL. And teh search fails. This affects searches from drop-down menus.

Thanks in advance.

Strange. In this forum it works without extra characters. Just try it yourself. Do you have any strange configuration? Can you send me a minimal elogd.cfg which produces that error, maybe derived from the example elogd.cfg from the distribution.

- Stefan 

 Well, It may be our implementation of re-routing web requests: The requested string in elog  is prefixed by %5E (^) and postfixed by %24 ($). But in my case, the '%' is again escaped as %25 so the prefix becomes %255E that is not understood by elog as being '^' ...

I will see with my experts in routing if this is something that can be fixed in our configuration. But when elog processes the input string, it should un-escape these characters and find back the '^', no?

  67131   Mon Sep 26 14:49:48 2011 Reply Olivier CallotOlivier.Callot@cern.chBug reportLinux2418Re: Spurious characters in the searched string

Olivier Callot wrote:

Stefan Ritt wrote:

Olivier Callot wrote:

Hi,

We have a problem with the search command: Since our last upgrade to v2.9.0-2418 the searched string is pre- and postfixed with ASCII character expressed in % format, see the attached image. The searched string is prefied with %255E and postfxed by %2524 in the URL. And teh search fails. This affects searches from drop-down menus.

Thanks in advance.

Strange. In this forum it works without extra characters. Just try it yourself. Do you have any strange configuration? Can you send me a minimal elogd.cfg which produces that error, maybe derived from the example elogd.cfg from the distribution.

- Stefan 

 Well, It may be our implementation of re-routing web requests: The requested string in elog  is prefixed by %5E (^) and postfixed by %24 ($). But in my case, the '%' is again escaped as %25 so the prefix becomes %255E that is not understood by elog as being '^' ...

I will see with my experts in routing if this is something that can be fixed in our configuration. But when elog processes the input string, it should un-escape these characters and find back the '^', no?

 It turned out to be a setting of our re-routing of requests that re-escaped the '%'. Sorry for the noise. Cheers

  67132   Wed Sep 28 22:10:30 2011 Question Graham Medlinglmedlin@ncsu.eduQuestionLinux2.9.0-2411Digest page or email?

We have about 10 logbooks running on the same Elog that all get fair use. Many people have turned off new entry emails because they were filling up inboxes, but are still interested in what's new. I saw the option to add "?last=1" to the start page, although I'm afraid using it might cause confusion over how to get to the older posts.

I was trying to figure out a way of creating a "digest" of sorts, a list of entry subjects posted in the past day or week, something similar to what's generated by "?last=1?mode=threaded", but for every logbook (similar layout to the selection page with nested logbooks). This could either be a page, or a regular email.

Is there way to generate such a cross-logbook page? What about a scheduled email formatted based on a given filter?

PS: The elog has been invaluable to us, a big thanks to all involved!

  67133   Thu Sep 29 10:12:40 2011 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.9.0-2411Re: Digest page or email?

Graham Medlin wrote:

We have about 10 logbooks running on the same Elog that all get fair use. Many people have turned off new entry emails because they were filling up inboxes, but are still interested in what's new. I saw the option to add "?last=1" to the start page, although I'm afraid using it might cause confusion over how to get to the older posts.

I was trying to figure out a way of creating a "digest" of sorts, a list of entry subjects posted in the past day or week, something similar to what's generated by "?last=1?mode=threaded", but for every logbook (similar layout to the selection page with nested logbooks). This could either be a page, or a regular email.

Is there way to generate such a cross-logbook page? What about a scheduled email formatted based on a given filter?

PS: The elog has been invaluable to us, a big thanks to all involved!

What we do is use the RSS feed of elog. This gives you nice summaries without going through your email inbox. Most browsers have RSS readers, there are also tons of stand-alone programs for that. Attached is a screenshot from the Google Reader subscribed to this logbook and to the "contributions' logbook. You see nice one-line summaries, you can expand them, and you can go directly to the logbook if you click on the arrow. The second image is from the Firefox using what they call "live bookmarks", but it's basically a RSS reader.

To make this work, I installed the RSS extension of Google Chrome (Firefox has this under "Bookmarks"/"Subscribe to this page"), then go to the elog page, then click on the RSS icon, then clicked on "Subscribe to this" via Google Reader. Just a few clicks.

 

Hope this is what you want.

 

- Stefan

Attachment 1: Screen_Shot_2011-09-29_at_9.58.02_.png
Screen_Shot_2011-09-29_at_9.58.02_.png
Attachment 2: Screen_Shot_2011-09-29_at_10.06.52_.png
Screen_Shot_2011-09-29_at_10.06.52_.png
  67134   Thu Sep 29 16:55:25 2011 Reply Graham Medlinglmedlin@ncsu.eduQuestionLinux2.9.0-2411Re: Digest page or email?

Stefan Ritt wrote:

Graham Medlin wrote:

We have about 10 logbooks running on the same Elog that all get fair use. Many people have turned off new entry emails because they were filling up inboxes, but are still interested in what's new. I saw the option to add "?last=1" to the start page, although I'm afraid using it might cause confusion over how to get to the older posts.

I was trying to figure out a way of creating a "digest" of sorts, a list of entry subjects posted in the past day or week, something similar to what's generated by "?last=1?mode=threaded", but for every logbook (similar layout to the selection page with nested logbooks). This could either be a page, or a regular email.

Is there way to generate such a cross-logbook page? What about a scheduled email formatted based on a given filter?

PS: The elog has been invaluable to us, a big thanks to all involved!

What we do is use the RSS feed of elog. This gives you nice summaries without going through your email inbox. Most browsers have RSS readers, there are also tons of stand-alone programs for that. Attached is a screenshot from the Google Reader subscribed to this logbook and to the "contributions' logbook. You see nice one-line summaries, you can expand them, and you can go directly to the logbook if you click on the arrow. The second image is from the Firefox using what they call "live bookmarks", but it's basically a RSS reader.

To make this work, I installed the RSS extension of Google Chrome (Firefox has this under "Bookmarks"/"Subscribe to this page"), then go to the elog page, then click on the RSS icon, then clicked on "Subscribe to this" via Google Reader. Just a few clicks.

 

Hope this is what you want.

 

- Stefan

 Perfect! I didn't not know there was RSS support. I will probably use something like rss2email, but this is exactly what I needed. Thanks!

ELOG V3.1.5-3fb85fa6