Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 216 of 796  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectup
  944   Mon Feb 14 19:03:31 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionOther2.5.7-1Re: Configuration problems
> I am trying to run eLog under Apache 2 on my FreeBSD 5.3 server.  I started
> the daemon with "elogd -n <my hostname> -p 8080" and when I connect to my
> server on that port, I get a 500 server configuration error.  The Apache log
> contains this:
> 
> malformed header from script. Bad header=Please specify hostname.: elog

- make sure your proxy definition in httpd.conf is correct and it uses port 8080
- start elogd with the "-v" flag to see the communication between Apache and elogd
- maybe you might need an "URL = http://<my hostname>/<elog dir>/" in the config
file
  945   Mon Feb 14 20:39:30 2005 Reply Erich Beyrenterich.beyrent@beyrent.netQuestionOther2.5.7-1Re: Configuration problems
> > I am trying to run eLog under Apache 2 on my FreeBSD 5.3 server.  I started
> > the daemon with "elogd -n <my hostname> -p 8080" and when I connect to my
> > server on that port, I get a 500 server configuration error.  The Apache log
> > contains this:
> > 
> > malformed header from script. Bad header=Please specify hostname.: elog
> 
> - make sure your proxy definition in httpd.conf is correct and it uses port 8080
> - start elogd with the "-v" flag to see the communication between Apache and elogd
> - maybe you might need an "URL = http://<my hostname>/<elog dir>/" in the config
> file

No luck.  I have the proxy definition in my httpd.conf file.  I have the URL parameter
in my elogd.cfg file.

Here is the command line I am using to start the daemon:

elogd -v -D -n <myhost> -p 8080 -l <myhost>/cgi-bin/elog/logbooks -c
/usr/local/server/apache/cgi-bin/elog/elogd.cfg

With the -v argument, here are the messages I get in /var/log/messages:

elogd 2.5.7-1 built Feb 14 2005, 09:55:19 
Feb 14 14:38:28 onion elogd[34579]: revision 1.558
Feb 14 14:38:28 onion elogd[34579]: Config file  :
/usr/local/server/apache/cgi-bin/elog/elogd.cfg
Feb 14 14:38:28 onion elogd[34579]: Resource dir : /usr/local/server/apache/cgi-bin/elog/
Feb 14 14:38:28 onion elogd[34579]: Logbook dir  :
/usr/local/server/apache/cgi-bin/elog/logbooks/
Feb 14 14:38:28 onion elogd[34579]: Falling back to default group "elog"
Feb 14 14:38:28 onion elogd[34579]: Group "elog" not found
Feb 14 14:38:28 onion elogd[34579]: Falling back to default group "nogroup"
Feb 14 14:38:28 onion elogd[34579]: Falling back to default user "elog"
Feb 14 14:38:28 onion elogd[34579]: User "elog" not found
Feb 14 14:38:28 onion elogd[34579]: Falling back to default user "nobody"
Feb 14 14:38:28 onion elogd[34579]: Indexing logbook "demo" ... 
Feb 14 14:38:28 onion elogd[34579]: 
Feb 14 14:38:28 onion elogd[34579]:   ID   1, 011108a.log, ofs     0, thead, MD5=
Feb 14 14:38:28 onion elogd[34579]: E4
Feb 14 14:38:28 onion elogd[34579]: 25
Feb 14 14:38:28 onion elogd[34579]: 4C
Feb 14 14:38:28 onion elogd[34579]: B8
Feb 14 14:38:28 onion elogd[34579]: AD
Feb 14 14:38:28 onion elogd[34579]: 4E
Feb 14 14:38:28 onion elogd[34579]: 88
Feb 14 14:38:28 onion elogd[34579]: 68
Feb 14 14:38:28 onion elogd[34579]: 08
Feb 14 14:38:28 onion elogd[34579]: 91
Feb 14 14:38:28 onion elogd[34579]: C9
Feb 14 14:38:28 onion elogd[34579]: 4D
Feb 14 14:38:28 onion elogd[34579]: 1E
Feb 14 14:38:28 onion elogd[34579]: B7
Feb 14 14:38:28 onion elogd[34579]: CB
Feb 14 14:38:28 onion elogd[34579]: C3
Feb 14 14:38:28 onion elogd[34579]: 
Feb 14 14:38:28 onion elogd[34579]: After sort:
Feb 14 14:38:28 onion elogd[34579]:   ID   1, 011108a.log, ofs     0
Feb 14 14:38:28 onion elogd[34579]: ok
Feb 14 14:38:28 onion elogd[34579]: Server listening on port 8080 ...

I am still getting the exact same error in my Apache log.

Any more ideas?

-Erich-
  946   Mon Feb 14 20:43:48 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionOther2.5.7-1Re: Configuration problems
> No luck.  I have the proxy definition in my httpd.conf file.  I have the URL parameter
> in my elogd.cfg file.

Can you show me the proxy definition? I hope you don't treat elogd as a CGI script...
  67753   Fri Jan 16 14:29:58 2015 Reply Stefan Rittstefan.ritt@psi.chRequestAll-Re: Configure default time range in 'Find'

Have you tried in the "Find" page to set a start date, or select "Show last: Month". This shoudl speed up searching quit a bit.

Eoin Butler wrote:

Hello,

We have a very large elog database, and executing a 'Find' on the whole range takes several minutes, locking other users out of the elog for that time. It would be very nice if there could be an option to set the default value of the 'search last ...' option on the find page. Thanks in advance!

 

  67754   Mon Jan 19 11:09:31 2015 Reply Eoin Butlereoin.butler@cern.chRequestAll-Re: Configure default time range in 'Find'

Yes, this works, but users inevitably forget to select "last week" or whatever, and just leave it blank, which means their search unintentionally takes a long time. It would be much better if one could configure it to default to something "fast".

Stefan Ritt wrote:

Have you tried in the "Find" page to set a start date, or select "Show last: Month". This shoudl speed up searching quit a bit.

  67755   Mon Jan 19 17:17:32 2015 Idea David PilgramDavid.Pilgram@epost.org.ukRequestAll-Re: Configure default time range in 'Find'

Hi there, In the "Find" page, I changed the default of the "Show last" drop down box in the Entry Date section from the (unstated) "All time" to "Day", and added back in an "All Time" option at the very bottom.  This gives a default of searching the last day, and one has to think and select the period of time to search back on.

I did this on my 2.9.2-2475 version, recompiled and it works.  Two lines of code changed and even my cr*ppy coding was up to the task.  I don't know if Stefan would want to put this into the Master copy (I'll forward the changes if you want Stefan, but it's pretty easy if I can do it), but if you can edit and recompile (Eoin) I can tell you which to lines for immediate functionality.  Back up everything first, though!

Eoin Butler wrote:

Yes, this works, but users inevitably forget to select "last week" or whatever, and just leave it blank, which means their search unintentionally takes a long time. It would be much better if one could configure it to default to something "fast".

Stefan Ritt wrote:

Have you tried in the "Find" page to set a start date, or select "Show last: Month". This shoudl speed up searching quit a bit.

 

  67756   Tue Jan 20 00:58:58 2015 Warning David PilgramDavid.Pilgram@epost.org.ukRequestAll-Re: Configure default time range in 'Find'

It has just occurred to me that you may also have to check the non-English files, (./resorces/eloglang_xxxx) as this change introduces a new term "All time" that would need translation into the other lexicons.

 

By the way, in further testing, the "Show last" selection over-rides whatever two dates are selected, so if you ask for any entry in Dec 2014, but the "Show last" selects "week", nothing is found - very quickly.  I trust that is what you're after, Eoin.  I'll keep my change to the coding, but that's personal choice.

David.

David Pilgram wrote:

Hi there, In the "Find" page, I changed the default of the "Show last" drop down box in the Entry Date section from the (unstated) "All time" to "Day", and added back in an "All Time" option at the very bottom.  This gives a default of searching the last day, and one has to think and select the period of time to search back on.

I did this on my 2.9.2-2475 version, recompiled and it works.  Two lines of code changed and even my cr*ppy coding was up to the task.  I don't know if Stefan would want to put this into the Master copy (I'll forward the changes if you want Stefan, but it's pretty easy if I can do it), but if you can edit and recompile (Eoin) I can tell you which to lines for immediate functionality.  Back up everything first, though!

Eoin Butler wrote:

Yes, this works, but users inevitably forget to select "last week" or whatever, and just leave it blank, which means their search unintentionally takes a long time. It would be much better if one could configure it to default to something "fast".

Stefan Ritt wrote:

Have you tried in the "Find" page to set a start date, or select "Show last: Month". This shoudl speed up searching quit a bit.

 

 

  67759   Thu Jan 22 16:30:07 2015 Reply Stefan Rittstefan.ritt@psi.chRequestAll-Re: Configure default time range in 'Find'

I added a new optoin "Show last default = <days>", where one can pre-set the "Show last" drop-down box. I think this is a good idea, so now people can configure their elog to a certain default in this parameter. Of course all settings in the Find page are AND'ed together, so if one restricts the search to tha last week, but then looks for a date more in the past, the result will be zero by definition. The change is in the GIT repository. If you cannot recompile the code yourself, you have to wait for the next release.

David Pilgram wrote:

By the way, in further testing, the "Show last" selection over-rides whatever two dates are selected, so if you ask for any entry in Dec 2014, but the "Show last" selects "week", nothing is found - very quickly.  I trust that is what you're after, Eoin.  I'll keep my change to the coding, but that's personal choice.

ELOG V3.1.5-2eba886