Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 460 of 808  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Category OS ELOG Version Subject
  66140   Sat Jan 10 09:58:43 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.7.5Re: ELOG scalability

 

Devin Bougie wrote:

Hi, All.  We have been successfully using ELOG in a limited deployment for a couple years now.  However, we are about to embark on a new project that could run for up to 10 years, and are wondering what sort of scalability we can expect from ELOG.

Are there any problems we can expect to run into as the number of entries grow?  I see in a previous thread that "elog runs fine for a few 10000 entries. At 100000 entries it starts getting slow."  Is this still the case, or have any improvements been made?  What sort of problems would we expect to run into?  Any examples of existing large deployments would be very useful.

 

The above made statement is not true any more. Mainly due to the large CERN experiments, some speed improvements have been made in late 2007. So elog runs fine at least up to 100000 entries. The startup time might be a bit slow, since it parses all entries there, but beyond the maybe 20s startup time, there is not a big difference when browsing entries. The only peoblem left is if you try to search some text through 100000 entries, this could be a bit slow. I have not tried anhything beyond 100000 entries, because this was not requested so far. If logooks become too big, the entreis could be split into several logbooks. Even if there are several logbooks with 100000 entries each, the access time should not be slower than if there would be one logbook with 100000 entries.

  66139   Fri Jan 9 22:40:59 2009 Question Devin Bougiedab66@cornell.eduQuestionLinux2.7.5ELOG scalability

Hi, All.  We have been successfully using ELOG in a limited deployment for a couple years now.  However, we are about to embark on a new project that could run for up to 10 years, and are wondering what sort of scalability we can expect from ELOG.

Are there any problems we can expect to run into as the number of entries grow?  I see in a previous thread that "elog runs fine for a few 10000 entries. At 100000 entries it starts getting slow."  Is this still the case, or have any improvements been made?  What sort of problems would we expect to run into?  Any examples of existing large deployments would be very useful.

 

Many thanks,

Devin 

 

 

 

 

 

  66138   Fri Jan 9 13:20:25 2009 Question Michael Dannmeyermichael.dannmeyer@solvias.comQuestionWindows2.7.5-2130Import csv with another date

Hello,

i have problems with importing csv files. What i want to do is the following:

Import a list of log entries from a csv file with another date like the actual date

I tried to do this but the only thing which happend was that all the entries have the actual date in elog. Then i created a seperate Date column in the csv file an tried to import this.

It worked but in the default date column i have the import date and in a second date column i have the date from the csv file.

Is there a chance to get the csv column imported in the standard Date field? 

Or is there a possibility to hide/supress the default date field and only display the imported date field?

Thanks

Michael

  66137   Fri Jan 9 10:41:20 2009 Reply Niklasniklas@hoglund.pp.seBug reportLinux2.7.5 2142Re: Elogd crashes with: *** stack smashing detected ***

Stefan Ritt wrote:

 

Niklas wrote:

 

Stefan,

perhaps there should be something like the bold text below in elogd.c:

int process_http_request(const char *request, int i_conn)^M
...

   /* extract cookies */^M
   if ((p = strstr(request, "Cookie:")) != NULL) {^M
      p += 6;^M
      do {^M
         p++;^M
         while (*p && *p == ' ')^M
            p++;^M
         strlcpy(str, p, sizeof(str));^M
         for (i = 0; i < (int) strlen(str); i++)^M
            if (str[i] == '=' || str[i] == ';')^M
               break;^M
         if (str[i] == '=') {^M
            str[i] = 0;^M
            p += i + 1;^M
            for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n' && i < (int) sizeof(cookie); i++)
                      cookie[i] = *p++;

...

 

Wow, where did you get that long cookie from? Certainly not from elogd. You must run elogd under Apache, and have some other service next to it on your server which distributes this long cookies, that's why other people did not experience this problem yet. I appreciate your fix. It's alwasy nice to see users not only complain about things, but try to fix them. Your fix is almost correct, you need a

i<(int) sizeof(cookie)-1

since there is the trailing zero for terminating the cookie string. I applied your fix to SVN revision #2146.

 Just noticed that this fix does not work. Elog cookies e.g. "upwd" may be after other long cookies its not seen, as now it stops reading the cookie-string after 256 chars. There needs to be something that goes through the cookies and saves only elog cookies... Would probably be better if you code that, if you have time  =D

 

BR, niklas

  66136   Thu Jan 8 15:36:28 2009 Reply Stefan Kanitzskmainz@web.deQuestionWindowslatestRe: elogd hangs when Date format in elogd.cfg

Stefan Kanitz wrote:

Hi,

 

after setting

Date format = %Y-%m-%e

in elogd.cfg,

 

 

elogd hangs and must be restarted manually. Can anybody help me?

 

Thanks,

Steve

 I found my mistake:It must be

Date format = %Y-%m-%d

 

Steve

 

  66135   Thu Jan 8 14:42:34 2009 Question Stefan Kanitzskmainz@web.deQuestionWindowslatestelogd hangs when Date format in elogd.cfg

Hi,

 

after setting

Date format = %Y-%m-%e

in elogd.cfg,

 

 

elogd hangs and must be restarted manually. Can anybody help me?

 

Thanks,

Steve

  66134   Wed Jan 7 19:54:18 2009 Question kyoojosh@newgistics.comBug reportWindows2.7.5-2130Google Chrome issues

 I use Google Chrome for web browsing these days..  I've had serious issues with surfing some of the pages of our ELOG V2.7.5-2130 site.  For instance, I can surf directly to our url to create a new entry (http://changelog.company.com/Company+IT+Change+Log/?cmd=New) and see the page just fine.  But when I click on the header to go back to the main page (http://changelog.company.com/Company+IT+Change+Log/) I end up with this error:

 

 

 

This webpage is not available.

The webpage at http://changelog.company.com/Company+IT+Change+Log/ might be temporarily down or it may have moved permanently to a new web address.

 

Below is the original error message
Error 320 (net::ERR_INVALID_RESPONSE): Unknown error.

 

 

But when I visit the DEMO elog site (http://midas.psi.ch/elogs/Linux%20Demo/) it pulls right up just fine..  My site also works in IE without problems.

 

Any ideas?  I run our ELOG on windows server.. maybe that has something to do with it..

  66133   Tue Jan 6 15:11:53 2009 Reply Ben Shepherdbjs54@dl.ac.ukQuestionLinux2.7.5-2137Re: Tooltips for MOptions - not working?

Stefan Ritt wrote:

 

Ben Shepherd wrote:

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

 

The syntax for tooltips is

Tooltip <attribute option> = <tooltip>

but you have

Tooltip "<attribute>" "<attribute option>" = <tooltip>

which is not correct, but would make more sense, since you could have an attribut option being valid for several attributes. So I changed elogd to accept both syntax in revision 2158. Please note that you should not put "quotes" around attribute values or options.

 Thanks! I got rid of the quotes around everything, and it works now.

ben

ELOG V3.1.5-3fb85fa6