Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 101 of 808  Not logged in ELOG logo
ID Date Icondown Author Author Email Category OS ELOG Version Subject
  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...
  950   Wed Feb 16 09:02:09 2005 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.5.6Re: images attached shown as inline
As I wrote you by mail, I implemented your idea in the following way. As you
say, it's only working on Gecko based systems. I did not implement additional
configuration parameters, but made it through the CSS file:

- adding a new CSS style "attachmentframe" around all attachments
- adding class "attachmentframe" to the 'default.css' like:

.attachmentframe {
  border:1px solid grey;
  border-top:1px solid lightgrey;
  border-left:1px solid lightgrey;
  background-color:white;
  padding:5px;
}

.attachmentframe img {
    max-width:100%;
}

The latter restricts the image size to 100%, which is the width of the 
browser window. I like it that, but of course you can write 200px or 
anything else. Please find the modified elogd.c and default.css under CVS.
  952   Fri Feb 18 08:47:20 2005 Reply Stefan Rittstefan.ritt@psi.ch Linux Re: How to import previous emails to elog ?
Have a look at http://midas.psi.ch/elogs/Contributions/10
  954   Sun Feb 20 15:30:04 2005 Reply Stefan Rittstefan.ritt@psi.chBug fixLinux2.5.7Re: Problem with 'Show Attributes' option
> There is a problem with the 'Show Attributes' option
> causing the 'Format ...' options to be ignored.
> 
> See attachment for patch.

Thanks a lot. I applied your patch and committed the changes to CVS.
  956   Tue Feb 22 10:35:17 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.5.7Re: Space in logbook name with password list results in "List" menu acting strange
> If you have a space in a logbook name and you enable password list, then 
> the "List" menu option forces you to the login page each time.
> The URL says "aaa+bbb", but when you do not have passwords enabled, the 
> URL is "aaa bbb"

Thanks for reporting this. I fixed it in the current CVS version.
  960   Thu Feb 24 11:23:44 2005 Reply Emiliano GabrielliAlberT@SuperAlberT.itBug reportAll2.5.6Re: HTML 4.1 transitional validation fails
> > as this url shows http://www.htmlhelp.com/tools/validator/problems.html#amp
> 
> > it should be used an HTML entity instead of the ampersand sign.<p> > > Can you please be a bit more specific? In which URL should the ampersand be > replaced? uhmm... http://midas.psi.ch/elogs/Forum/page2?mode=threaded&expand=0&last=7 the bug is also a "documentation bug", infact similar tricks are also in FAQs (FAQ 5 for example) I tried to substitute avery occurrence of hard coded "&" with "&amp;" but it does not do the job at all ... infact the first time the HTML code is ok, but following a link let the browser to automatically decode html entities .. and everything turns wrong again ... maybe the encoding should be done in printing-to-the-browser-time ..
ELOG V3.1.5-3fb85fa6