Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 140 of 238  Not logged in ELOG logo
icon5.gif   elog (2.6.1+r1642 ubuntu/debian) regularly becomes non-responsive (w/o crashing), posted by Peter Kovac on Mon Nov 27 17:29:41 2006 
Greetings~

First, the problem. Fairly regularly (at least once a week, perhaps more), our elog daemon seems to quietly die. The process is still running but anyone attempting to access the server gets "connection refused." The elog log doesn't show anything and the apache logs just show "proxy: Error reading from remote server returned by [path]". Calling a daemon restart doesn't seem to kill the daemon -- I get a "could not bind to port" error. Using kill and then starting the daemon again fixes the problem for a few days and then we start over.

The particulars:
We are running elog on an Ubuntu (6.06 Dapper Drake LTS) web server.
It's currently version 2.6.1+r1642 pulled via apt-get from the Debian repositories.
elog is hiding behind an apache2+SSL proxy.

Any thoughts? Has anyone else seen this behavior? My next step is probably to compile 2.6.2 and remove the packaged flavor but I wanted to see if this was a known bug...

Thanks,
-Peter
    icon2.gif   Re: elog (2.6.1+r1642 ubuntu/debian) regularly becomes non-responsive (w/o crashing), posted by Stefan Ritt on Tue Nov 28 10:34:54 2006 

Peter Kovac wrote:
First, the problem. Fairly regularly (at least once a week, perhaps more), our elog daemon seems to quietly die. The process is still running but anyone attempting to access the server gets "connection refused." The elog log doesn't show anything and the apache logs just show "proxy: Error reading from remote server returned by [path]". Calling a daemon restart doesn't seem to kill the daemon -- I get a "could not bind to port" error. Using kill and then starting the daemon again fixes the problem for a few days and then we start over.

The particulars:
We are running elog on an Ubuntu (6.06 Dapper Drake LTS) web server.
It's currently version 2.6.1+r1642 pulled via apt-get from the Debian repositories.
elog is hiding behind an apache2+SSL proxy.

Any thoughts? Has anyone else seen this behavior? My next step is probably to compile 2.6.2 and remove the packaged flavor but I wanted to see if this was a known bug...


There are three reasons why an elog server can go into an infinite loop:

  • A bug which has been fixed in meantime. If you can give a try to 2.6.2-1750 or so that could help. I'm not sure if this version is already in the Debian distribution since I'm not the maintainer there.
  • A corrupted log file. If one of the YYMMDDa.log file get some garbage (maybe due to hard disk problems etc.) the elogd server can run into an infinite loop. In that case examine all log files to see if there is anything wrong. If so, edit it manually and restart elogd.
  • Some not yet found bug. One never can exclude this of course, but at this forum I have elogd running under similar conditions like you, and it runs for months without problems.
       icon2.gif   Re: elog (2.6.1+r1642 ubuntu/debian) regularly becomes non-responsive (w/o crashing), posted by Kevin O'Sullivan on Fri Jan 16 23:54:46 2009 
I'm actually still having this issue in Ubuntu and I'm running elog version 2.7.5. In fact, now it's worse in 2.7.5 than in previous version because sometimes I have to restart the machine to get elog working again.

Is there anything I can do to help you find potential bugs with Ubuntu?




Stefan Ritt wrote:

Peter Kovac wrote:
First, the problem. Fairly regularly (at least once a week, perhaps more), our elog daemon seems to quietly die. The process is still running but anyone attempting to access the server gets "connection refused." The elog log doesn't show anything and the apache logs just show "proxy: Error reading from remote server returned by [path]". Calling a daemon restart doesn't seem to kill the daemon -- I get a "could not bind to port" error. Using kill and then starting the daemon again fixes the problem for a few days and then we start over.

The particulars:
We are running elog on an Ubuntu (6.06 Dapper Drake LTS) web server.
It's currently version 2.6.1+r1642 pulled via apt-get from the Debian repositories.
elog is hiding behind an apache2+SSL proxy.

Any thoughts? Has anyone else seen this behavior? My next step is probably to compile 2.6.2 and remove the packaged flavor but I wanted to see if this was a known bug...


There are three reasons why an elog server can go into an infinite loop:

  • A bug which has been fixed in meantime. If you can give a try to 2.6.2-1750 or so that could help. I'm not sure if this version is already in the Debian distribution since I'm not the maintainer there.
  • A corrupted log file. If one of the YYMMDDa.log file get some garbage (maybe due to hard disk problems etc.) the elogd server can run into an infinite loop. In that case examine all log files to see if there is anything wrong. If so, edit it manually and restart elogd.
  • Some not yet found bug. One never can exclude this of course, but at this forum I have elogd running under similar conditions like you, and it runs for months without problems.
          icon2.gif   Re: elog (2.6.1+r1642 ubuntu/debian) regularly becomes non-responsive (w/o crashing), posted by John Rouillard on Sat Jan 17 08:16:19 2009 

Kevin O'Sullivan wrote:
I'm actually still having this issue in Ubuntu and I'm running elog version 2.7.5. In fact, now it's worse in 2.7.5 than in previous version because sometimes I have to restart the machine to get elog working again.

Is there anything I can do to help you find potential bugs with Ubuntu?


What does "lsof -p pid" on the elogd process show, how about "strace -p pid"?

Since you are using elogd with an apache providing reverse proxy, I wonder if one of
the httpd processes isn't properly closing it's connection when it's done. That would
hang the elogd process since it's single threaded and non forking (IIRC).

Also why do you need to restart the box, does killing and restarting the elogd process not work?
When you kill elogd, does 'sudo netstat -anp' show anything listening at the elogd port?

-- rouilj
icon5.gif   Display Revisions field in single entry but not in list view, posted by Dan C. on Wed Dec 17 19:43:25 2008 
Hello,

   Thank you for such a great software package!

   I would like to ask how I can display the Revisions field in the single entry view but not in the list view. I followed the FAQ instructions and added the following to my elodg.cfg:

   Attributes = Author, Type, Category, Subject, Revisions
   Locked attributes = Revisions
   Subst on Edit Revisions = $Revisions
$date by $long_name This configuration shows the Revisions field in both the list view and the single entry view. This was a problem because certain entries are changed a lot so they took up a lot of horizontal space in the list view. I tried to remove the Revisions field in the list view but keep them in the single entry view with the following: Attributes = Author, Type, Category, Subject Show Attributes = Author, Type, Category, Subject, Revisions Locked attributes = Revisions Subst on Edit Revisions = $Revisions
$date by $long_name This took the Revisions field out of the list view and also the single entry view. However, the fields that were shown in the single entry view ended up as Author, Type, Category, Subject, Author (again). The last attempt were with the following configuration lines: Attributes = Author, Type, Category, Subject Show Attributes = Revisions Locked attributes = Revisions Subst on Edit Revisions = $Revisions
$date by $long_name This showed Author, Type, Category, Subject in the list view but only the Author field in the single entry view. How can I configure Elog to show the Revisions field in the single entry view but no the list view? Thanks, - Dan
    icon2.gif   Re: Display Revisions field in single entry but not in list view, posted by Stefan Ritt on Mon Dec 22 11:59:09 2008 
The "Show Attributes" option is for the single entry view, while the "List Display" option is for the list view. So what you need is:
Attributes = Author, Type, Category, Subject
Show Attributes = Revisions
Locked attributes = Revisions
Subst on Edit Revisions = $Revisions $date by $long_name
List Display = ID, Date, Author, Type, Category, Subject
       icon2.gif   Re: Display Revisions field in single entry but not in list view, posted by Dan C. on Thu Jan 15 22:25:05 2009 
Hello Stefan,

Thanks for your reply.

Maybe it was the way that I worded my original post but to reiterate, I wanted to have ID, Date, Author, Type, Category, Subject in the list display and Author, Type, Category, Subject, and Revision in the single entry view.

To get the desired results, I had to use the following:
Attributes = Author, Type, Category, Subject, Revisions
Show Attributes = Author, Type, Category, Subject, Revisions
Locked attributes = Revisions
Subst on Edit Revisions = $Revisions $date by $long_name
List Display = ID, Date, Author, Type, Category, Subject

Thank you again for your help and the great software package!
- Dan


Stefan Ritt wrote:
The "Show Attributes" option is for the single entry view, while the "List Display" option is for the list view. So what you need is:
Attributes = Author, Type, Category, Subject
Show Attributes = Revisions
Locked attributes = Revisions
Subst on Edit Revisions = $Revisions $date by $long_name
List Display = ID, Date, Author, Type, Category, Subject
icon5.gif   Google Chrome issues, posted by kyoo on Wed Jan 7 19:54:18 2009 

 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..

    icon2.gif   Re: Google Chrome issues, posted by John Rouillard on Sat Jan 10 23:43:36 2009 
> Any ideas? I run our ELOG on windows server.. maybe that has something to do with it.

I am running the server on kubuntu 8.x, and have the same issue with chrome 1.x.
Is is possible the corporate elog server is running behind apache or in some
other proxy config while the one you are having issues with is being connected
to directly by chrome?

-- rouilj
       icon2.gif   Re: Google Chrome issues, posted by kyoo on Sun Jan 11 22:48:38 2009 
> > Any ideas? I run our ELOG on windows server.. maybe that has something to do with it.
> 
> I am running the server on kubuntu 8.x, and have the same issue with chrome 1.x.
> Is is possible the corporate elog server is running behind apache or in some
> other proxy config while the one you are having issues with is being connected
> to directly by chrome?
> 
> -- rouilj

So, is your kubuntu elog server internal only, as well?  My elog server on windows is an internal only server.. 
and there is no proxy or firewall between chrome and the elog server.. I didn't set it up, but I think elogd runs 
it's own web service.. probably apache within the win32 port.

It's good to know someone else has the issue, at least.  I'd like to find a publicly available elog server so 
that the elog developers could recreate the issue and thusly fix the issue.  Or at the very least send the broken 
URL to Google Chrome developers to see if it's a bug in the browser or not.

I ran wireshark to capture what happens at the ethernet level, and it seems that the HTTP response doesn't come 
through properly.  My response packets to the TCP response packets seems to be:

"Acknowledgment number: Broken TCP. The acknowledge field is nonzero while the ACK flag is not set"
My system never receives enough TCP packets to reassemble it to a properly formatted HTTP response.


The stream goes like this:
GET /Company+IT+Change+Log/ HTTP/1.1 
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/525.19 (KHTML, like Gecko) 
Chrome/1.0.154.42 Safari/525.19 
Referer: http://changelog.Company.com/Company+IT+Change+Log/?cmd=New 
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 
Accept-Encoding: gzip,deflate,bzip2,sdch 
Cookie: unm=Name; upwd=amhpbGoijoihbmQ=; urem=1 
Accept-Language: en-US,en 
Accept-Charset: ISO-8859-1,*,utf-8 
Host: changelog.Company.com 
Connection: Keep-Alive 
 
HTTP/1.1 200 Document follows 
Server: ELOG HTTP 2.7.5-2130 
Content-Type: text/html;charset=ISO-8859-1 
Set-Cookie: elmode=Summary; path=/Company+IT+Change+Log; expires=Tuesday, 09-Jun-20 12:31:45 GMT; 
 path=/Company+IT+Change+Log; 
Connection: Keep-Alive 
Keep-Alive: timeout=60, max=10 
Pragma: no-cache 
Expires: Fri, 01 Jan 1983 00:00:00 GMT 
Content-Length: 24455 
 
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
<title>ELOG Company IT Change Log</title>
<link rel="stylesheet" type="text/css" href="default.css">
<link rel="shortcut icon" href="favicon.ico" />
<link rel="icon" href="favicon.png" type="image/png" />
<link rel="alternate" type="application/rss+xml" title="ELOG Company IT Change Log" href="elog.rdf" />
</head>
<body>
<form name="form1" method="GET" action=".">

<table class="frame" cellpadding="0" cellspacing="0"><!-- show_standard_title -->

<tr><td class="tabs">
<span class="sltab"><a href="../Company+IT+Change+Log/" title="Company 
TI">Company&nbsp;IT&nbsp;Change&nbsp;Log</a></span>
</td></tr>

<tr><td><table width="100%" border="0" cellpadding="0" cellspacing="0">
<tr><td class="title1">&nbsp;&nbsp;Company TI, Page 1 of 272&nbsp;</td>
<td class="title2">Logged in as "My Name"</td>
<td class="title3"><img border=0 src="elog.png" alt="ELOG logo" title="ELOG logo"></td>
</tr></table></td></tr>

<tr><td class="menuframe"><span class="menu1">
&nbsp;<a href="?cmd=New">New</a>&nbsp;|
&nbsp;<a href="?cmd=Find">Find</a>&nbsp;|
&nbsp;<a href="?select=1">Select</a>&nbsp;|
&nbsp;<a href="?cmd=Import">Import</a>&nbsp;|
&nbsp;<a href="?cmd=Config">Config</a>&nbsp;|
&nbsp;<a href="?cmd=Logout">Logout</a>&nbsp;|
&nbsp;<a href="?cmd=Help">Help</a>&nbsp;
</span></td></tr>

<tr><td class="menuframe">
<table width="100%" border=0 cellpadding="0" cellspacing="0">
<tr>
<td class="menu2a">
&nbsp;<a href="?mode=full">Full</a>&nbsp;|&nbsp;Summary&nbsp;|&nbsp;<a href="?
mode=threaded">Threaded</a>&nbsp;</td>
<td class="menu2b">
<a href="?new_entries=1"><img align="middle" border="0" src="new_entry.png" alt="Show only new entries" 
title="Show only new entries"></a>&nbsp;&nbsp;<select title="Select period" name=last 
onChange="document.form1.submit()">
<option value="_all_">-- All entries --
<option  value=1>Last day
<option  value=7>Last week
<option  value=31>Last month
<option  value=92>Last 3 Months
<option  value=182>Last 6 Months
<option  value=364>Last Year
</select>
<select title="Select Type" name="Type" onChange="document.form1.submit()">
<option value="_all_">-- Type --
<option value="^Hardware$">Hardware
<option value="^Software$">Software
<option value="^Database$">Database
<option value="^Network$">Network
<option value="^NGS Applications$">NGS Applications
<option value="^Storage$">Storage
<option value="^Monitor$">Monitor
<option value="^VMware$">VMware
</select> 
<noscript>
<input type=submit value="Search">
</noscript>
&nbsp;<b>5429 Entries</b>&nbsp;</td></tr></table></td></tr>

<tr><td class="menuframe"><span class="menu3">
Goto page 
1, 
<a href="page2">2</a>, 
<a href="page3">3</a>&nbsp;...&nbsp;<a href="page270">270</a>, 
<a href="page271">271</a>, 
<a href="page272">272</a>&nbsp;&nbsp;
<a href="page2">Next</a>&nbsp;&nbsp;</span></td></tr>
<tr><td><table class="listframe" width="100%" cellspacing=0>
<tr>
<th  class="listtitle"><a href="?sort=ID">ID</a></th>
<th  class="listtitle"><a href="?sort=Date">Date</a></th>
<th  class="listtitle"><a href="?sort=Author">Author</a></th>
<th  class="listtitle"><a href="?sort=Author+Email">Author Email</a></th>
<th  class="listtitle"><a href="?sort=Type">Type</a></th>
<th  class="listtitle"><a href="?sort=Category">Category</a></th>
<th  class="listtitle"><a href="?sort=Subject">Subject</a></th>
<th  class="listtitle"><a href="?sort=Last+Revision">Last Revision</a></th>
<th  class="listtitle"><a href="?sort=Reason+for+Change">Reason for Change</a></th>
<th class="listtitle">Text</th>
<th class="listtitle"><img src="attachment.png" alt="Attachments" title="Attachments"</th></tr>

<tr><td class="list2">
<a href="../Company+IT+Change+Log/5431">&nbsp;&nbsp;5431&nbsp;&nbsp;</a>
</td>

<td class="list2" nowrap><a href="../Company+IT+Change+Log/5431">1/9/2009 4:40:54 PM</a></td>
<td class="list2"><a href="../Company+IT+Change+Log/5431">Gary</a></td><td class="list2"><a 
href="../Company+IT+Change+Log/5431"><a href="gmercier@Company.com">gmercier@Company.com</a></a></td><td 
class="list2"><a href="../Company+IT+Change+Log/5431">Applications</a></td><td class="list2"><a 
href="../Company+IT+Change+Log/5431">Patch - Hotfix</a></td><td class="list2"><a 
href="../Company+IT+Change+Log/5431">PRN 18718 Update</a></td><td class="list2"><a 
href="../Company+IT+Change+Log/5431"></a>&nbsp;</td><td class="list2"><a 
href="../Company+IT+Change+Log/5431"></a>&nbsp;</td><td class="summary">A</td>
<td class="listatt">&nbsp;&nbsp;</td><tr><td class="list1">
<a href="../Company+IT+Change+Log/5430">&nbsp;&nbsp;5430&nbsp;&nbsp;</a>
</td>

<td class="list1" nowrap><a href="../Company+IT+Change+Log/5430">1/9/2009 4:37:01 PM</a></td>
<td class="list1"><a href="../Company+IT+Change+Log/5430">Gary</a></td><td class="list1"><a 
href="../Company+IT+Change+Log/5430"><a href="gary@compan


Then the stream just aborts, apparently.
          icon2.gif   Re: Google Chrome issues, posted by John Rouillard on Mon Jan 12 05:12:42 2009 
> > > Any ideas? I run our ELOG on windows server.. maybe that has something to do with it.
> > 
> > I am running the server on kubuntu 8.x, and have the same issue with chrome 1.x.
> > Is is possible the corporate elog server is running behind apache or in some
> > other proxy config while the one you are having issues with is being connected
> > to directly by chrome?
>
> It's good to know someone else has the issue, at least.  I'd like to find a publicly available elog server so 
> that the elog developers could recreate the issue and thusly fix the issue.  Or at the very least send the broken 
> URL to Google Chrome developers to see if it's a bug in the browser or not.

I just brought up the current head release of elog, and the problem is fixed. Looks like it 
was some sort of cookie issue IIRC the log entry.

So build a new elogd and you should be all set.

- rouilj
             icon2.gif   Re: Google Chrome issues, posted by kyoo on Mon Jan 12 05:33:04 2009 
> > > > Any ideas? I run our ELOG on windows server.. maybe that has something to do with it.
> > > 
> > > I am running the server on kubuntu 8.x, and have the same issue with chrome 1.x.
> > > Is is possible the corporate elog server is running behind apache or in some
> > > other proxy config while the one you are having issues with is being connected
> > > to directly by chrome?
> >
> > It's good to know someone else has the issue, at least.  I'd like to find a publicly available elog server so 
> > that the elog developers could recreate the issue and thusly fix the issue.  Or at the very least send the broken 
> > URL to Google Chrome developers to see if it's a bug in the browser or not.
> 
> I just brought up the current head release of elog, and the problem is fixed. Looks like it 
> was some sort of cookie issue IIRC the log entry.
> 
> So build a new elogd and you should be all set.
> 
> - rouilj

Thanks.  I'll have to wait for someone else to build the win32 binary, as I'm not set up to compile it myself.
                icon2.gif   Re: Google Chrome issues, posted by kyoo on Mon Jan 12 21:00:27 2009 
> > > > > Any ideas? I run our ELOG on windows server.. maybe that has something to do with it.
> > > > 
> > > > I am running the server on kubuntu 8.x, and have the same issue with chrome 1.x.
> > > > Is is possible the corporate elog server is running behind apache or in some
> > > > other proxy config while the one you are having issues with is being connected
> > > > to directly by chrome?
> > >
> > > It's good to know someone else has the issue, at least.  I'd like to find a publicly available elog server so 
> > > that the elog developers could recreate the issue and thusly fix the issue.  Or at the very least send the broken 
> > > URL to Google Chrome developers to see if it's a bug in the browser or not.
> > 
> > I just brought up the current head release of elog, and the problem is fixed. Looks like it 
> > was some sort of cookie issue IIRC the log entry.
> > 
> > So build a new elogd and you should be all set.
> > 
> > - rouilj
> 
> Thanks.  I'll have to wait for someone else to build the win32 binary, as I'm not set up to compile it myself.

I installed the latest Windows build (didn't realize I missed a build in November), and it now works in Chrome.  Thanks!
icon5.gif   ELOG scalability, posted by Devin Bougie on Fri Jan 9 22:40:59 2009 

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 

 

 

 

 

 

    icon2.gif   Re: ELOG scalability, posted by Stefan Ritt on Sat Jan 10 09:58:43 2009 

 

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.

icon5.gif   elogd hangs when Date format in elogd.cfg, posted by Stefan Kanitz on Thu Jan 8 14:42:34 2009 

Hi,

 

after setting

Date format = %Y-%m-%e

in elogd.cfg,

 

 

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

 

Thanks,

Steve

    icon2.gif   Re: elogd hangs when Date format in elogd.cfg, posted by Stefan Kanitz on Thu Jan 8 15:36:28 2009 

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

 

icon5.gif   Tooltips for MOptions - not working?, posted by Ben Shepherd on Fri Dec 19 14:15:28 2008 elogd.cfg

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

    icon2.gif   Re: Tooltips for MOptions - not working?, posted by Stefan Ritt on Mon Dec 22 08:52:20 2008 

 

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.

       icon2.gif   Re: Tooltips for MOptions - not working?, posted by Ben Shepherd on Tue Jan 6 15:11:53 2009 

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

icon5.gif   Standard login Screen - bottom text, posted by Barend on Fri Oct 17 20:40:39 2008 

Hi Stefan.

I have been "playing" around with this great tool and found an interesting "issue" ...

I use multiple logbooks and have both "Protect Selection page = 1" and "Expand Selection Page = 1".

When I open my elog, I get a Standard Login Screen with the Standard Bottom Text "ELOG V2.7.5-2130" which will link to your this website.

When I "Logout" and "Login" again from the Logbook page, I get another Login Screen with my own "Bottom text login" which will link to my own elog page.

How can I apply my own Bottom Text to the Standard Login Screen ?

Thanks & Regards, Barend
 

    icon2.gif   Re: Standard login Screen - bottom text, posted by Stefan Ritt on Thu Oct 30 04:28:05 2008 

 

Barend wrote:

Hi Stefan.

I have been "playing" around with this great tool and found an interesting "issue" ...

I use multiple logbooks and have both "Protect Selection page = 1" and "Expand Selection Page = 1".

When I open my elog, I get a Standard Login Screen with the Standard Bottom Text "ELOG V2.7.5-2130" which will link to your this website.

When I "Logout" and "Login" again from the Logbook page, I get another Login Screen with my own "Bottom text login" which will link to my own elog page.

How can I apply my own Bottom Text to the Standard Login Screen ?

Thanks & Regards, Barend
 

 

 By using the configuration option "Bottom Text Login = ..."

       icon2.gif   Re: Standard login Screen - bottom text, posted by Barend on Thu Oct 30 21:14:32 2008 

Stefan Ritt wrote:

 

Barend wrote:

Hi Stefan.

I have been "playing" around with this great tool and found an interesting "issue" ...

I use multiple logbooks and have both "Protect Selection page = 1" and "Expand Selection Page = 1".

When I open my elog, I get a Standard Login Screen with the Standard Bottom Text "ELOG V2.7.5-2130" which will link to your this website.

When I "Logout" and "Login" again from the Logbook page, I get another Login Screen with my own "Bottom text login" which will link to my own elog page.

How can I apply my own Bottom Text to the Standard Login Screen ?

Thanks & Regards, Barend
 

 

 By using the configuration option "Bottom Text Login = ..."

Stefan,

I have defined the "Bottom Text Login = ..." in each Logbook Configuration section. But when I use this option in the Global Section, ELOG fails to start.

Barend

 

          icon2.gif   Re: Standard login Screen - bottom text, posted by Stefan Ritt on Mon Nov 3 07:33:08 2008 Capture.jpg

Barend wrote:

Stefan,

I have defined the "Bottom Text Login = ..." in each Logbook Configuration section. But when I use this option in the Global Section, ELOG fails to start.

Barend

 

 That's strange. I just tried myself following configuration file:

[global]
port = 8080
Bottom text = <center>Hello</center>
Bottom text login = <center>Login Hello</center>
Password file = passwd

[demo1]
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Page Title = ELOG - $subject

[demo2]
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject

and everything works fine as can be seen from the login screen:

Capture.jpg

so can you check if above file works for you?

             icon2.gif   Re: Standard login Screen - bottom text, posted by Barend on Mon Dec 29 17:27:13 2008 

Stefan Ritt wrote:

Barend wrote:

Stefan,

I have defined the "Bottom Text Login = ..." in each Logbook Configuration section. But when I use this option in the Global Section, ELOG fails to start.

Barend

 

 That's strange. I just tried myself following configuration file:

[global]
port = 8080
Bottom text = 
Hello
Bottom text login =
Login Hello
Password file = passwd [demo1] Comment = General linux tips & tricks Attributes = Author, Type, Category, Subject Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other Page Title = ELOG - $subject [demo2] Comment = General linux tips & tricks Attributes = Author, Type, Category, Subject

and everything works fine as can be seen from the login screen:

Capture.jpg

so can you check if above file works for you?

 Hi Stefan,

Hope you have enjoyed the Christmas week.

Sorry for the delay.... I have tested your configuration and it worked for me as well. 

In order to determine, which of my settings is causing the problem, I had to activate each individual entry "one by one" and check if the error re-occured. I finally identified following entry "Protect Selection page = 1"

The error also occurs if I change your configuration into:

[global]
port = 8080
Bottom text = <center>Hello</center>
Bottom text login = <center>Login Hello</center>
Password file = passwd
Protect Selection page = 1

[demo1]
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Page Title = ELOG - $subject

[demo2]
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
 

Can you advise if I'm missing an entry in order for "Protect Selection page = 1" to work?

 

"Schönen Rutsch ins neue Jahr".

Regards, 

Barend

icon5.gif   Problems with execute delete, posted by Stefan Kanitz on Tue Dec 23 11:02:26 2008 

Hi all,

i have problems with execute delete (execute new works fine) in following config (the attribute 'Counter' will not evaluated). Can anybody help me?

 

Here is the config:

 

Attributes = Counter, Autor, Adressat, Start, Ende, Mitteilung, TextBeachten

Show Attributes = Counter, Autor, Adressat, Start, Ende, Mitteilung, TextBeachten
Show Attributes Edit = Counter, Autor, Adressat, Start, Ende, Mitteilung, TextBeachten


Type Start = date
Type Ende = date
Required Attributes =  Autor, Adressat, Start, Ende, Mitteilung
Extendable options = Adressat
Preset Autor = $long_name
Preset Counter = SoMi-#####



Locked Attributes = Autor, Counter
Required Attributes =  Adressat, Start, Ende, Mitteilung

Options Adressat = Alle, 1. Semester, 2. Semester, 3. Semester, 4. Semester, 5. Semester, 6. Semester, 7. Semester, 8. Semester
MOptions Textbeachten = Bitte Mitteilungs-Text anzeigen lassen



Execute new = C:\xampp\mysql\bin\mysql.exe -h localhost -u root -p123456 -D screen -e "insert into somi (counter,adressat,start,ende,kumi,mitlami,lami) values ('$Counter', '$Adressat', '$Start', '$Ende', '$Mitteilung',  '$TextBeachten', '$text')"


Execute delete = C:\xampp\mysql\bin\mysql.exe -h localhost -u root -p123456 -D screen -e "delete from somi where counter='$Counter'"

 

 

 

Thanks in advance and Merry Christmas!!

 

Steve

 

    icon2.gif   Re: Problems with execute delete, posted by Stefan Ritt on Tue Dec 23 11:34:25 2008 

 

Stefan Kanitz wrote:

i have problems with execute delete (execute new works fine) in following config (the attribute 'Counter' will not evaluated). Can anybody help me?

 

Attribute substitution on 'execute delete' was not implemented, since I thought that the ELOG message ID would be used as the primary key in an SQL database, so one would not need the attributes. I added howver this functrionality in SVN revision 2159, so the next release will contain this fix. 

       icon2.gif   Re: Problems with execute delete, posted by Stefan Kanitz on Tue Dec 23 12:17:06 2008 

Stefan Ritt wrote:

 

Stefan Kanitz wrote:

i have problems with execute delete (execute new works fine) in following config (the attribute 'Counter' will not evaluated). Can anybody help me?

 

Attribute substitution on 'execute delete' was not implemented, since I thought that the ELOG message ID would be used as the primary key in an SQL database, so one would not need the attributes. I added howver this functrionality in SVN revision 2159, so the next release will contain this fix. 

 This sounds very good! Thank you very much (Could you please add this functionality for execute edit too? Please :-))

Steve

 

          icon2.gif   Re: Problems with execute delete, posted by Stefan Ritt on Tue Dec 23 12:22:51 2008 

 

Stefan Kanitz wrote:

 

Stefan Ritt wrote:

 

Stefan Kanitz wrote:

i have problems with execute delete (execute new works fine) in following config (the attribute 'Counter' will not evaluated). Can anybody help me?

 

Attribute substitution on 'execute delete' was not implemented, since I thought that the ELOG message ID would be used as the primary key in an SQL database, so one would not need the attributes. I added howver this functrionality in SVN revision 2159, so the next release will contain this fix. 

 

This sounds very good! Thank you very much (Could you please add this functionality for execute edit too? Please :-))

 

For 'execute edit' this worked from the beginning. 

             icon2.gif   Re: Problems with execute delete, posted by Stefan Kanitz on Tue Dec 23 12:31:39 2008 

Stefan Ritt wrote:

 

Stefan Kanitz wrote:

 

Stefan Ritt wrote:

 

Stefan Kanitz wrote:

i have problems with execute delete (execute new works fine) in following config (the attribute 'Counter' will not evaluated). Can anybody help me?

 

Attribute substitution on 'execute delete' was not implemented, since I thought that the ELOG message ID would be used as the primary key in an SQL database, so one would not need the attributes. I added howver this functrionality in SVN revision 2159, so the next release will contain this fix. 

 

This sounds very good! Thank you very much (Could you please add this functionality for execute edit too? Please :-))

 

For 'execute edit' this worked from the beginning. 

 Thank you!

ELOG V3.1.5-3fb85fa6