Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 717 of 796  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectup
  69397   Fri Oct 15 23:57:38 2021 Question Rob Calkinsrcalkins@smu.eduQuestionLinux3.1.4 Too many open files - issue?

Has anyone had issues with having too many files open? I'll setup my server and let it go but after a while, I end up with a lot of "cannot create socket: Too many open files" errors being reported.  I have a sync to another e-log going which I suspect is part of the cause since that e-log server hasn't had this issue. I suspect that there are files being opened, going into some return loop code and then never getting closed. I'm not a C programmer but I see lines like :

fh = open(tmp_filename, O_RDONLY);
      if (fh > 0) {
         read(fh, result, size - 1);
         close(fh);
      }

      /* remove temporary file */
      remove(tmp_filename);

This looks like it opens the file but unless the remove function closes the file, it will remain open even through the file has been deleted. Maybe this isn't the correct behaviour of 'remove' and I am mistaken?

There are also parts like :

 fh = open(textfile, O_RDONLY | O_BINARY);
      if (fh < 0) {
         printf("Message file \"%s\" does not exist.\n", textfile);
         return 1;
      }

      size = (INT) lseek(fh, 0, SEEK_END);
      lseek(fh, 0, SEEK_SET);

      if (size > (INT) (sizeof(text) - 1)) {
         printf("Message file \"%s\" is too long (%zd bytes max).\n", textfile, sizeof(text));
         return 1;
      }

This looks like for the second error, it will complain that the file is too long, return an error message but not close the file and would leave it open. Is this a reasonable avenue to pursue or am I mis-reading the code?   Thanks.

  69542   Tue Jul 19 11:01:00 2022 Question Tamas Galtgal@km3net.deQuestionLinux3.1.3Too many redirects when running behind load balancer?

We were running ELOG for many many years in our experiments and the instance was operated on a Debian XEN server as a container. I am now trying to migrate it into our Docker Swarm cluster and I am using the https://hub.docker.com/r/de1lz/elog-docker Docker image, which works very well with our logbooks when I run it as a single container. However, when I put the container behind my load balancer (HAProxy) using the simple HTTP mode (which works very well for all the other HTTP-based services) with this simple configuration:

backend be_elog.km3net.de
    mode http
    server-template km3net-elog- 1 km3net-elog_elog:8080 check resolvers docker init-addr libc,none

I get a "too many redirects" error when I try to access one of the logbooks. The starting page works fine, but every other link leads to a pile-up of redirects.

Here is the current instance running, where you can see the behaviour: https://elog.test.km3net.de (all log entries deleted and only two logbooks activated)

My question is: what kind of redirect could go wrong here? I don't know how the internal HTTP server of ELOG works, but maybe someone faced similar issues.

My ELOG configuration is also pretty basic, and as I wrote above, everything works when I run it without the load balancer (single instance at the moment). Here is the top part of the configuration, it contains a few dozens of logbooks but they are configured the very same way. 

;User Settings
;=============
Password file = login.xml
Admin user = km3net_admin
Self register = 0
Allow password change = 0
Allow config = km3net_admin

;Group Settings:
;====
Group ELOGKM3NET = Operations IT, Operations FR

[Operations IT]
Subdir = Operations_IT
Theme = default
Default encoding = 0
Comment = KM3NeT IT Detector Operations
Attributes = Author, Type, Subject
Options Author = A, B, C
Options Type = PPM-DOM, PPM-DU, Comment, Power cut, New run
Extendable Options = Type
Required Attributes = Author, Type, Subject
Page Title = ELOG - $subject
;Sort Attributes = Author, Type
Quick filter = Date, Type, Author
Resubmit default = 2
Reverse sort = 1
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config, Help, Logout
Preset on first reply Subject = Re: $Subject
Preset on reply author =

 

  2092   Sun Nov 26 22:15:34 2006 Cool Grant Jeffcotegrant@jeffcote.orgRequestWindows Tool Tips
Hi Stefan,

Is there a way to add a 'Tool Tips' to individual 'Options' similar to that currently available for Attributes? I have several checkboxes under an attribute for predefined email groups and would like to see if I can make the recipient list viewable via a mouse hover using the 'Tool tip' feature.
If not possible can it be added to the wishlist?

Many thx.
  66121   Fri Dec 19 14:15:28 2008 Question Ben Shepherdbjs54@dl.ac.ukQuestionLinux2.7.5-2137Tooltips for MOptions - not working?

Hi,

One of my logbooks is a fault reporting system; it emails a group of people when a fault is reported. There is an MOption 'Technical Groups', and I want to have a tooltip for each checkbox which shows who is referred to by each group name. However, individual tooltips for each MOption attribute don't seem to work. I've looked at the HTML code, and there's no 'title' attribute for the checkboxes, so it's not a browser problem. I've attached my config file. Any idea what's going wrong?

ben

Attachment 1: elogd.cfg
Data dir = /web/Elog/ERLP/logbooks/erlpfaults
Summary page title = ALICE Faults
List page title = ALICE Faults
Page title = ALICE Faults: $Title
RSS title = $message ID: $Title
Comment = ALICE Faults
Menu commands = List, New, Edit, Reply, Delete, Find, Config, Admin, Logout, Help
Guest Menu commands = List, Find, Login, Help
Find Menu commands = List, New, Select, Find, Config, Admin, Logout, Help
Guest Find Menu commands = List, Find, Login, Help
Attributes = Submitted by, Title, Personnel, Technical Groups, Cc, Machine Areas, Priority
MOptions Technical Groups = Accelerator Physics, Magnets, RF, Vacuum, Cryogenics, Power Supplies, Controls, Diagnostics, Photoinjector, Engineering, Health & Safety, Services, Personnel Safety System
Comment Technical Groups = Emails will be sent out<BR>to the specified groups.
Comment Cc = Additional email addresses;<BR>separate using commas.
MOptions Machine Areas = laser, gun, transfer line 1, booster, transfer line 2, linac, arc 1, compressor, FEL, arc 2, dump
ROptions Priority = critical, high, normal, low, fixed
Extendable Options = Personnel

Use Email From = dlerlp@example.com
#email goes to each of the people listed here, for entries where the technical group is specified
Email "Technical Groups" "Accelerator Physics" = susan.smith@example.com, yuri.saveliev@example.com
Tooltip "Technical Groups" "Accelerator Physics" = "Susan Smith, Yuri Saveliev"
Email "Technical Groups" Magnets = neil.thompson@example.com, ben.shepherd@example.com
Email "Technical Groups" RF = peter.mcintosh@example.com, andrew.moss@example.com
Tooltip "Technical Groups" RF = "Pete McIntosh, Andy Moss"
Email "Technical Groups" Vacuum = thomas.weston@example.com, keith.middleman@example.com
Email "Technical Groups" Cryogenics = shrikant.pattalwar@example.com, bob.bate@example.com, andy.goulden@example.com
Email "Technical Groups" "Power Supplies" = stephen.griffiths@example.com, chris.white@example.com
Email "Technical Groups" Controls = adrian.oates@example.com, ralph.rotheroe@example.com
Email "Technical Groups" Diagnostics = rob.smith@example.com, steven.jamison@example.com
Email "Technical Groups" Photoinjector  = susan.smith@example.com, rob.smith@example.com
Email "Technical Groups" Engineering = phil.atkinson@example.com, paul.hindley@example.com
Email "Technical Groups" "Health & Safety" = andy.goulden@example.com, stephen.hill@example.com
Email "Technical Groups" Services = andy.goulden@example.com, rachael.buckley@example.com
Email "Technical Groups" "Personnel Safety System" = john.alexander@example.com, christopher.chorlton@example.com
Email All = $Cc, $user_email
Use Email Subject = $Title (ALICE Fault Notification)
Preset Submitted by = $long_name
Preset on reply Submitted by = $long_name
Preset Priority = normal
Locked Attributes = Submitted by
Quick filter = Date, Technical Groups, Machine Areas, Priority

List display = ID, Date, Title, Technical Groups, Machine Areas, Priority
Summary lines = 0
  1743   Thu Mar 2 23:32:25 2006 Question Steve Jonessteve.jones@freescale.comRequestAll2.6.1Top Groups and logbook directorys
I am re-working our elog setup and am seriously looking at using the "Top Group" feature. What I like best is the ability to create [global] configurations for a group (or type) of logbook when I host multiple types on the same server. I also like being able to specify a different password file, etc.

A limitation that I run into is I would really like the actual directory names used for storing the logbooks for the different types to be identical - which isn't possible when all logbooks (regardless of context) exist at the same directory level. For example, I might have:

3 physical locations: ABC, DEF, GHI

For each location I want to maintain two *groups* of logbooks - CircuitTests and BoardTests. What I would like to end up with is:
- CircuitTests
----ABC
----DEF
----GHI
- BoardTests
----ABC
----DEF
----GHI

Under current elog this is not possble as far as I know. Since each logbook is a physical directory, each logbook requires a unique name. The concept of a named [global] area fills the bill for all things but it would be nifty if one could do:
[global circuittests]
Logbook dir = circuittestlogbooks

[global boardtests]
Logbook dir = boardtestlogbooks

I suppose the poorman's way of doing this is for each logbook to do the following:
[ABC]
Subdir = boardtestlogbooks/ABC
[DEF]
Subdir = boardtestlogbooks/DEF
[GHI]
Subdir = boardtestlogbooks/GHI

or something like that, but I was hopic for something a little more integrated - like creating the hierarchical stuff via the GUI. Anyway, this probably sounds like a major overhaul, which definitely wouldn't be worth it unless I have completely missed something glaringly obvious.

Thanks!
  1379   Fri Aug 5 02:27:15 2005 Angy Chris Greengreenc@fnal.govBug reportLinux2.6.0-CVSTop Groups, Show Top Groups, password file and Protect Selection page have nasty interaction
Hi,

Just as our ELOG went into production, I tripped over a couple of related (I think) bugs.

First, the easy one: line 21368 of src/elogd.c has a compile warning which looks non-benign. I fixed it in my local copy with:

Index: elogd.c
===================================================================
RCS file: /usr/local/cvsroot/elog/src/elogd.c,v
retrieving revision 1.739
diff -r1.739 elogd.c
21368,21369c21368
< sprintf(str, "?fail=1", user);
< redirect(lbs, str);
---
> redirect(lbs, "?fail=1");

Regardless (ie if I use the original CVS code or the patched version), a hard-to trace problem occurs with my configuration whereby users are denied access after password entry at the logbook selection page (even when details are verifiably correct), and users are dropped through to the next (non-protected) Top Group page. This problem goes away if "Protect Selection Page" is turned off.

A kind of "shadow" of this problem occurs if you create a new logbook from the Change Config File page, whereby after creating the new logbook one is dropped through to the next Top Group's selection page after saving the configuration (and the url has ?fail=1 added to it, althoguh line 21368 above is hardly the only place where this could have occurred).

I think all these things are linked. I'd be grateful if you could review this section of this code for possible causes of these problems. While we can operate for now with non-logged-in users able to see our list of logbooks, that is not something we want for the long term.

Thanks for your help,
Chris.
  1919   Thu Aug 31 21:46:15 2006 Warning Steve Jonessteve.jones@freescale.comBug reportAll2.6.2-1714Top Text and Bottom Text only show "text" --- no files
Just compiled 2.6.2-1714 and "Top text" and "Bottom text" interpret everything as "text" --- nothing is interpreted as a file to be included, unless there is a new syntax.
  66155   Tue Jan 20 15:09:54 2009 Entry Michael Ambrusambrmi09@gmail.comBug reportWindows2.7.5Top group causes: Internal error, no valid header!

Having "Top group" in a config-file for Windows will cause:

 

GET / HTTP/1.1
Host: eudr6j03j:8084
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.0.5) Gecko/20
08120122 Firefox/3.0.5
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: sv-se,sv;q=0.8,en-us;q=0.5,en;q=0.3
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Cookie: unm=mambrus; upwd=U2lzc2kx; urem=0
Cache-Control: max-age=0


Internal error, no valid header!

 

Removing "top group" makes elogd.exe work. The error is repeatable and the same config file works on the same version of Elog on Linux. Elog was compiled with Cygwin.

ELOG V3.1.5-fe60aaf