Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 182 of 806  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icondown Author Author Email Category OS ELOG Version Subject
  2015   Mon Oct 23 12:53:08 2006 Reply Dimitrios Tsirigkasdimitrios.tsirigkas@cern.chQuestion  Re: Problem with large entry size
Hi Stefan,

A lot of performance-related trouble for us comes from the ability of users to click on "All" and display thousands of entries on the same page. Is there a way to disable that? Even if the ELCode parsing performance of Elog increases greatly, the combination of "Full" mode and "All" will still cause trouble, will it not?

Thanks,
Dimitris
  2016   Tue Oct 24 21:58:54 2006 Reply Stefan Rittstefan.ritt@psi.chQuestion  Re: Problem with large entry size

Dimitrios Tsirigkas wrote:
Hi Stefan,

A lot of performance-related trouble for us comes from the ability of users to click on "All" and display thousands of entries on the same page. Is there a way to disable that? Even if the ELCode parsing performance of Elog increases greatly, the combination of "Full" mode and "All" will still cause trouble, will it not?

Thanks,
Dimitris


What about a threshold for the "All" display? If a logbook contains less than, let's say, 500 entries, the "All" link is displayed, and above 500 entries it's hidden. Would that make sense?
  2017   Wed Oct 25 17:20:27 2006 Reply An Thaithaithan@gmx.deQuestionWindows2.6.2-1722Re: Error Sending Email

Stefan Ritt wrote:

Ibrahim Genc wrote:
There is a free e-mail service at mail.softhome.net. It provides smtp and pop3 services. You can use this for testing if you want.


I tried but I was unable to obtain a free account. Furthermore, the problem is probably related to your SMTP server's authentication method. There are many methods and ELOG only supports a subset. So I would have to try with your specific SMTP server. So the only recommendation I can give you is to find an SMTP server without authentication. That one will certainly work with elog.




Dear all WINDOWS users,

Good news.
you can send email to any SMTP server with authentification !!! Just install component Windows IIS (Internet Information Services). You need the Windows Professional installation CD to install it.

How it works:
ELOG -> Default SMTP Virtual Server -> SMTP with authentification (your email provider/ company mail server)


How to configurate Default SMTP Virtual Server:

Right mouse click on icon My Computer -> Manage
Expand Services and Apllications -> IIS
Right mouse click on Default SMTP Virtual Server -> Properties
Select Delivery tab
Click the button Outbound Security ->Select Basic authentification and enter your user/password which you got from your Email-provider/Company -> OK
Click the button Advanced... -> type your SMTP host in the fields "smart host" and "Full-qualified... ", i.e. smtp.gmx.net

(Don't forget to check the tab Access -> Connection and Relay buttons -> Select "All accept the list")



How to configurate your Elog.cfg file:
SMTP host = xxxx

Normally xxxx is your personal computer name by right click on the icon "My Computer" -> Properties -> Tab "Computer Name"
OR
xxxx: the name what you see by expand Services and Apllications -> IIS -> Default SMTP Virtual Server -> Domains -> Domain Name


GOOD LUCK
  2019   Wed Oct 25 19:44:11 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux Re: ELCode

Alexandre Lindote wrote:
can you think of any obvious reason why the ELCode would not work in the logbooks I set up?


There is a good reason why this forum contains a ELOG Version tag which you are supposed to fill out for new entries. Without knowing which version you are using I cannot help you. Probably you have an old version which does not support the Allowed encoding.
  2020   Wed Oct 25 21:52:13 2006 Reply Alexandre Lindotealex@lipc.fis.uc.ptQuestionLinux2.6.2-1699Re: ELCode

Stefan Ritt wrote:

Alexandre Lindote wrote:
can you think of any obvious reason why the ELCode would not work in the logbooks I set up?


There is a good reason why this forum contains a ELOG Version tag which you are supposed to fill out for new entries. Without knowing which version you are using I cannot help you. Probably you have an old version which does not support the Allowed encoding.


Sorry about that... it's 2.6.2-1699, so a very recent one.
  2021   Thu Oct 26 21:54:40 2006 Reply Steve Jonessteve.jones@freescale.comBug reportOther2.6.2-1714SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode (was SVN1714 will not run in 'daemon" mode on Solaris8)

Stefan Ritt wrote:

Steve Jones wrote:
There are also strange system calls that differ, and I thought it might be due to the setuid(60001) -nobody- but the the non-daemn mode also sets to nobody and works fine.


The elogd program opens the port (which might be below 1024 and thus needs privileges), then either become daemon or not, then changes to the user and group specified in elogd.cfg. So this behaviour should be the same on both cases.



Steve Jones wrote:
I just compiled SVN1723 and tried the generic elogd.cfg -- of course *that works!*. Something in my complex config that causes elog to barf when it is attempting to fork the daemon process.


That's a good starting point. Take your config file, strip one option after the other, and see which is the offending one. This helps us tracking down the problem.



Steve Jones wrote:
I have no idea what "/var/run/syslog_door" is.


I have not either. But one thing which is different in the daemon mode that all output is redirected to the syslog facility via the function call redirect_to_syslog();. This routine was not written by myself so I don't know 100% what it's doing, just under Linux it works fine. Try to outcomment this function and try again.



Steve Jones wrote:

Ok, I've narrowed down the problem to a single attribute. I edited elogd_fancy.cfg as it ships with SVN1723 and found a real bug and an issue:

BUG: In the initial comment section of elogd_fancy.cfg the line
# This [global] section contains settings common to all logbooks
is not parsed correctly as a comment and the embedded [global] is picked up and confuses elogd, eg., elogd will not pickup the port=8080 option. Taking "[global]" out of the comment restores fucntionality. I recommend checking to make sure that the config file checking routine ignores *entire* lines starting with a comment char;

ISSUE: The option
Logbook dir = 
causes an enormous amount of problems, and this may be limited to elog installs that exist in NFS space (as opposed to local disk). If the default is left alone elogd appears to work fine; Try and override and the fun begins. The previous attached traces show that once going into daemon mode none of the logbook dirs can be found nor indexed. The workaround is to use the default "logbooks" dir. Perhaps the routine that creates the default (if not found) should be the same as the one that creates the override (?).

I reproduced this behavior using the elogd_fancy.cfg that ships.

  2022   Fri Oct 27 13:02:50 2006 Reply Alexandre Lindotealex@lipc.fis.uc.ptQuestionLinux2.6.2-1699Re: ELCode

Alexandre Lindote wrote:
Hi,

can you think of any obvious reason why the ELCode would not work in the logbooks I set up?


Ok, I think I found the problem... For some reason the elcode.js file was only in /usr/local/elog/scripts, but it was supposed to be in
/usr/local/elog/themes/default/ as well.
Creating a symlink between the two solved that problem. I can now do most things with the ELCode, but inserting images is still failing. I get this message from the firefox javascript console:

text.value has no properties (line 32 of elcode.js)

Any thoughts?

Alex
  2024   Sun Oct 29 16:04:05 2006 Reply Steve Jonessteve.jones@freescale.comBug reportAll2.6.2-1723Re: Interesting behavior with $shell

Steve Jones wrote:
eLog does not do math so I am trying to leverage the $SHELL function to perform the math. I am using GAWK to perform the math -- I started trying to use CONDITIONAL ATTRIBUTES to assign numeric values to attributes but with loading up the ATTRIBUTES with all of the options brings elog to its knees in terms of performance -- the parsing of attributes is simply too string intensive.

So, I embedded the numeric score in the OPTIONS of the ATTRIBUTE and leveraged the text processing prowess of GAWK:
Options WhoIsEffected =   1:...Single User, 5:...Project, 10:...Department, 50:...Site
Options ServiceOutage =   1:...0-1 Minutes, 2:...10 Minutes, 10:...20 Minutes, 30:...30 Minutes, 100:...gt60 

Then pass the following command to GAWK:
Preset TotalScore = $shell(gawk 'BEGIN{split(\"$WhoIsEffected:$ServiceOutage\",scores,\":\");print scores[1]+scores[3]}' )

The interesting result is this works - the proper summation is returned but apparently elog parsing also returns everything after the first ')' as something that also needs to be returned. So the resulting contents of TotalScore is
2;print scores[1]+scores[3]}' ) 
assuming one chose the first option of both attributes (the output pasted here are real results).

Before getting to this point I tried using the GAWK internal variable of $0 - but this did not work because apparently $0 in elog is defined as the OS shell!

Stefan, is it possible for you to try creating a logbook on the elog demo site that shows people how to perform math and in the process discover what the $SHELL function is doing?




Steve Jones wrote:

So, in order to quickly get around the problem I did the following:
Preset TotalScore = $shell(echo \"$WhoIsEffected:$ServiceOutage\" | gawk -f <gawkscript>' )

This works since all of the script logic is contained in an external script but removes the logic from the elog config, so if anything changes one has to remember to change the script (which is in a comment).
ELOG V3.1.5-3fb85fa6