Re: Configuration problems, posted by Erich Beyrent on Mon Feb 14 20:39:30 2005
|
> > 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- |
|
Re: Configuration problems, posted by Stefan Ritt on Mon Feb 14 20:43:48 2005
|
> 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... |
length of fields, posted by Paul Harrington on Wed Feb 23 13:02:59 2005
|
When creating/updating entries in elog, excluding the main text field are
there any limits on the size of the other fields?
many thanks
Paul |
|
Re: Is any one using elog on Solaris 9?, posted by Jaap van Vliet on Thu Feb 24 11:23:03 2005
|
I've got it running for two years now on a Sun Netra box running Solaris 9
> I searched and found some problems people were having compiling it on Solaris.
> However I didn't see anything else.
I just used the compile instructions as shown in the elog admin manual
Here the Makefile I used
#
# Simple makefile for elogd
#
# S. Ritt, May 12th 2000
# install/clean section by Th. Bullinger, Apr. 26th, 2002
#
# add "-DHAVE_CRYPT" and "-lcrypt" to use crypt() function
#
CC = gcc
LIBS =
CFLAGS = -L/usr/lib/ -ldl -lresolv -lm -ldl -lnsl -lsocket
#CFLAGS = -g -O
EXECS = elog elogd elconv
DESTDIR = /usr/local/bin
SDESTDIR = /usr/local/sbin
MANDIR = /usr/local/man
INSTALL = /usr/bin/install
RM = /bin/rm
ifeq ($(OSTYPE),solaris)
CC = gcc
#LIBS = -lsocket -lnsl
#CFLAGS =
INSTALL = /usr/ucb/install
RM = /usr/bin/rm
endif
ifeq ($(OSTYPE),darwin)
CC = cc
endif
all: $(EXECS)
%: src/%.c
$(CC) $(CFLAGS) -o $@ $< $(LIBS)
install: $(EXECS)
$(INSTALL) -m 0755 -o bin -g bin elog elconv $(DESTDIR)
$(INSTALL) -m 0755 -o bin -g bin elogd $(SDESTDIR)
$(INSTALL) -m 0644 man/elog.1 man/elconv.1 $(MANDIR)/man1/
$(INSTALL) -m 0644 man/elogd.8 $(MANDIR)/man8/
clean:
-$(RM) *~ $(EXECS)
> If your using it, was it hard to get it installed and working?
Not at all.
Just read the manual and it just works.
If you are having problems just read this "forum" the get the answers. |
Including the text in the CSV export, posted by Gary Mercier on Mon Feb 28 21:35:57 2005
|
Is there any way to include the text of a log message in the CSV export?
Anyway to include a pointer to the attachment? |
|
Re: Including the text in the CSV export, posted by Stefan Ritt on Tue Mar 1 13:39:09 2005
|
> Is there any way to include the text of a log message in the CSV export?
> Anyway to include a pointer to the attachment?
The text of a log message is usually several lines long. To my knowledge, CSV
only allows single line values, that's why I excluded the text field from the
CSV export. This is different in the XML export, which supports multi-line
values. If you teach me however how multi-line values can be represented in
CSV format, I could easily add that.
As for the attachment, do you just need a name, or a URL back to the logbook?
Should the pointer be in the form "http://elog.server/logbook/attachment.jpg"
or in HTML form like <a href="http:/...">attachment</a> ? |
|
Re: Including the text in the CSV export, posted by Gary Mercier on Tue Mar 1 17:29:47 2005
|
> > Is there any way to include the text of a log message in the CSV export?
> > Anyway to include a pointer to the attachment?
>
> The text of a log message is usually several lines long. To my knowledge, CSV
> only allows single line values, that's why I excluded the text field from the
> CSV export. This is different in the XML export, which supports multi-line
> values. If you teach me however how multi-line values can be represented in
> CSV format, I could easily add that.
>
> As for the attachment, do you just need a name, or a URL back to the logbook?
> Should the pointer be in the form "http://elog.server/logbook/attachment.jpg"
> or in HTML form like <a href="http:/...">attachment</a> ?
I will attempt to use an active x script in a DTS package on SQL Server to parse
the xml and load it into the database. I can see where CSV has it's limitations. |
|
Re: length of fields, posted by Stefan Ritt on Wed Mar 2 15:00:04 2005
|
> When creating/updating entries in elog, excluding the main text field are
> there any limits on the size of the other fields?
Yes, this is controlled by the variable NAME_LENGTH in elogd.c, which is
currently set to 1500 characters. You can try to increase this and recompile,
but at some point you will produce a stack overflow and elogd will crash. So
the current length is a compromise.
- Stefan |