| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
945
|
Mon Feb 14 20:39:30 2005 |
 | Erich Beyrent | erich.beyrent@beyrent.net | Question | Other | 2.5.7-1 | Re: 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 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Other | 2.5.7-1 | Re: 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... |
|
959
|
Thu Feb 24 11:23:03 2005 |
 | Jaap van Vliet | jake.info@hccnet.nl | Question | Other | Any | Re: Is any one using elog on Solaris 9? |
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. |
|
1077
|
Tue Apr 12 01:05:20 2005 |
| G | levineg@med.govt.nz | Bug report | Other | 2.5.8-3 | XML password files, replication & FreeBSD |
Ok this really is 2 questions.
1)
I have been running ELOG on FreeBSD no problem for a year now,
but this new version 2.5.8-x doesn't seem to wanna work, it compiles fine
with a few warnings (see attached logs).
But has issues with password files, now it shows message "Can't open
passwords.pwd" for all my logbooks. It did convert the password files to
xml format. I had a good hard look at file permissions and config file with
no luck. So I went back a version and compiled 2.5.7-1 which works just
fine with old password files. So something with XML & FreeBSD?...
2)
Version 2.5.7-1 (maybe this has been fixed in 2.5.8?)
When I run a ./elogd -C http://elog.blah.here:88 it clones the config file
just fine, also seems to copy over all logbook entries.
But once I look through them there's a fault with one of the fields it
copies over, so entries never show up.
It should be:
========================================
Date: Tue Mar 01 19:41:29 2005
In reply to: 24
Work done by: someuser
Work done at (dd/mm/yy hh:mm): 1/03/05 3:30pm
Downtime duration: 0 min
Planned: Yes
Reason: Normal work
Attachment:
Encoding: plain
But once cloned it looks like this:
========================================
Date: Tue Mar 01 19:41:29 2005
In reply to: 24
Work done by: someuser
Work done at (dd/mm/yy hh: m): 1/03/05 3:30pm
Downtime duration: 0 min
Planned: Yes
Reason: Normal work
Attachment:
Encoding: plain
For some reason it looses the "m" so line 4 instead of having
"hh:mm" has "hh: m"
Cheers,
GL. |
| Attachment 1: compiling_ELOG_Errors_2.5.7-1.txt
|
===[root] /usr/local/elog #gmake
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -o elog src/elog.c
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -c -o regex.o src/regex.c
src/regex.c: In function `regex_compile':
src/regex.c:1193: warning: comparison between signed and unsigned
src/regex.c:1208: warning: comparison between signed and unsigned
src/regex.c:1301: warning: comparison between signed and unsigned
src/regex.c:1326: warning: comparison between signed and unsigned
src/regex.c:1340: warning: comparison between signed and unsigned
src/regex.c:1350: warning: comparison between signed and unsigned
src/regex.c:1362: warning: comparison between signed and unsigned
src/regex.c:1368: warning: comparison between signed and unsigned
src/regex.c:1376: warning: comparison between signed and unsigned
src/regex.c:1612: warning: comparison between signed and unsigned
src/regex.c:1630: warning: suggest explicit braces to avoid ambiguous `else'
src/regex.c:1642: warning: comparison between signed and unsigned
src/regex.c:1650: warning: suggest explicit braces to avoid ambiguous `else'
src/regex.c:1686: warning: comparison between signed and unsigned
src/regex.c:1702: warning: comparison between signed and unsigned
src/regex.c:1730: warning: comparison between signed and unsigned
src/regex.c:1817: warning: comparison between signed and unsigned
src/regex.c:1930: warning: comparison between signed and unsigned
src/regex.c:1936: warning: comparison between signed and unsigned
src/regex.c:1941: warning: comparison between signed and unsigned
src/regex.c:1945: warning: comparison between signed and unsigned
src/regex.c:1949: warning: comparison between signed and unsigned
src/regex.c:1953: warning: comparison between signed and unsigned
src/regex.c:1957: warning: comparison between signed and unsigned
src/regex.c:1961: warning: comparison between signed and unsigned
src/regex.c:1979: warning: comparison between signed and unsigned
src/regex.c:2027: warning: comparison between signed and unsigned
src/regex.c:2031: warning: comparison between signed and unsigned
src/regex.c: In function `compile_range':
src/regex.c:2240: warning: comparison between signed and unsigned
src/regex.c:2242: warning: signed and unsigned type in conditional expression
src/regex.c:2242: warning: signed and unsigned type in conditional expression
src/regex.c: In function `re_match_2':
src/regex.c:3317: warning: comparison between signed and unsigned
src/regex.c:3407: warning: comparison between signed and unsigned
src/regex.c:3431: warning: comparison between signed and unsigned
src/regex.c:3470: warning: empty body in an else-statement
src/regex.c:3484: warning: comparison between signed and unsigned
src/regex.c:3500: warning: comparison between signed and unsigned
src/regex.c:3775: warning: comparison between signed and unsigned
src/regex.c:3775: warning: unused variable `destination'
src/regex.c:3922: warning: comparison between signed and unsigned
src/regex.c:3922: warning: unused variable `destination'
src/regex.c:3975: warning: comparison between signed and unsigned
src/regex.c:3975: warning: unused variable `destination'
src/regex.c:4081: warning: comparison between signed and unsigned
src/regex.c:4114: warning: comparison between signed and unsigned
src/regex.c:4114: warning: unused variable `destination'
src/regex.c:4127: warning: comparison between signed and unsigned
src/regex.c:4127: warning: unused variable `destination'
src/regex.c:4295: warning: comparison between signed and unsigned
src/regex.c: In function `regcomp':
src/regex.c:4770: warning: signed and unsigned type in conditional expression
src/regex.c: In function `regerror':
src/regex.c:4890: warning: comparison between signed and unsigned
src/regex.c: At top level:
src/regex.c:4882: warning: unused parameter 'preg'
In file included from src/regex.c:3838:
src/regex.c: In function `re_match_2':
src/regex.c:4599: warning: passing arg 1 of `bcmp_translate' discards qualifiers from pointer target type
src/regex.c:4599: warning: passing arg 2 of `bcmp_translate' discards qualifiers from pointer target type
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -o elogd src/elogd.c regex.o
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -o elconv src/elconv.c
|
| Attachment 2: compiling_ELOG_Errors_2.5.8.txt
|
===[root] /usr/local/elog-2.5.8 #gmake
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -o elog src/elog.c
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -c -o regex.o src/regex.c
src/regex.c: In function `regex_compile':
src/regex.c:1193: warning: comparison between signed and unsigned
src/regex.c:1208: warning: comparison between signed and unsigned
src/regex.c:1301: warning: comparison between signed and unsigned
src/regex.c:1326: warning: comparison between signed and unsigned
src/regex.c:1340: warning: comparison between signed and unsigned
src/regex.c:1350: warning: comparison between signed and unsigned
src/regex.c:1362: warning: comparison between signed and unsigned
src/regex.c:1368: warning: comparison between signed and unsigned
src/regex.c:1376: warning: comparison between signed and unsigned
src/regex.c:1612: warning: comparison between signed and unsigned
src/regex.c:1630: warning: suggest explicit braces to avoid ambiguous `else'
src/regex.c:1642: warning: comparison between signed and unsigned
src/regex.c:1650: warning: suggest explicit braces to avoid ambiguous `else'
src/regex.c:1686: warning: comparison between signed and unsigned
src/regex.c:1702: warning: comparison between signed and unsigned
src/regex.c:1730: warning: comparison between signed and unsigned
src/regex.c:1817: warning: comparison between signed and unsigned
src/regex.c:1930: warning: comparison between signed and unsigned
src/regex.c:1936: warning: comparison between signed and unsigned
src/regex.c:1941: warning: comparison between signed and unsigned
src/regex.c:1945: warning: comparison between signed and unsigned
src/regex.c:1949: warning: comparison between signed and unsigned
src/regex.c:1953: warning: comparison between signed and unsigned
src/regex.c:1957: warning: comparison between signed and unsigned
src/regex.c:1961: warning: comparison between signed and unsigned
src/regex.c:1979: warning: comparison between signed and unsigned
src/regex.c:2027: warning: comparison between signed and unsigned
src/regex.c:2031: warning: comparison between signed and unsigned
src/regex.c: In function `compile_range':
src/regex.c:2240: warning: comparison between signed and unsigned
src/regex.c:2242: warning: signed and unsigned type in conditional expression
src/regex.c:2242: warning: signed and unsigned type in conditional expression
src/regex.c: In function `re_match_2':
src/regex.c:3317: warning: comparison between signed and unsigned
src/regex.c:3407: warning: comparison between signed and unsigned
src/regex.c:3431: warning: comparison between signed and unsigned
src/regex.c:3470: warning: empty body in an else-statement
src/regex.c:3484: warning: comparison between signed and unsigned
src/regex.c:3500: warning: comparison between signed and unsigned
src/regex.c:3775: warning: comparison between signed and unsigned
src/regex.c:3775: warning: unused variable `destination'
src/regex.c:3922: warning: comparison between signed and unsigned
src/regex.c:3922: warning: unused variable `destination'
src/regex.c:3975: warning: comparison between signed and unsigned
src/regex.c:3975: warning: unused variable `destination'
src/regex.c:4081: warning: comparison between signed and unsigned
src/regex.c:4114: warning: comparison between signed and unsigned
src/regex.c:4114: warning: unused variable `destination'
src/regex.c:4127: warning: comparison between signed and unsigned
src/regex.c:4127: warning: unused variable `destination'
src/regex.c:4295: warning: comparison between signed and unsigned
src/regex.c: In function `regcomp':
src/regex.c:4770: warning: signed and unsigned type in conditional expression
src/regex.c: In function `regerror':
src/regex.c:4890: warning: comparison between signed and unsigned
src/regex.c: At top level:
src/regex.c:4882: warning: unused parameter 'preg'
In file included from src/regex.c:3838:
src/regex.c: In function `re_match_2':
src/regex.c:4599: warning: passing arg 1 of `bcmp_translate' discards qualifiers from pointer target type
src/regex.c:4599: warning: passing arg 2 of `bcmp_translate' discards qualifiers from pointer target type
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -DHAVE_STRLCPY -c -o mxml.o ../mxml/mxml.c
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -I../mxml -o elogd src/elogd.c regex.o mxml.o
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -o elconv src/elconv.c
|
|
1079
|
Tue Apr 12 09:30:51 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Other | 2.5.8-3 | Re: XML password files, replication & FreeBSD |
> I have been running ELOG on FreeBSD no problem for a year now,
> but this new version 2.5.8-x doesn't seem to wanna work, it compiles fine
> with a few warnings (see attached logs).
> But has issues with password files, now it shows message "Can't open
> passwords.pwd" for all my logbooks. It did convert the password files to
> xml format. I had a good hard look at file permissions and config file with
> no luck. So I went back a version and compiled 2.5.7-1 which works just
> fine with old password files. So something with XML & FreeBSD?...
Hard to say. The simplest would be if I could debug this.
> Version 2.5.7-1 (maybe this has been fixed in 2.5.8?)
> When I run a ./elogd -C http://elog.blah.here:88 it clones the config file
> just fine, also seems to copy over all logbook entries.
> But once I look through them there's a fault with one of the fields it
> copies over, so entries never show up.
>
> It should be:
> ========================================
> Date: Tue Mar 01 19:41:29 2005
> In reply to: 24
> Work done by: someuser
> Work done at (dd/mm/yy hh:mm): 1/03/05 3:30pm
> Downtime duration: 0 min
> Planned: Yes
> Reason: Normal work
> Attachment:
> Encoding: plain
>
> But once cloned it looks like this:
> ========================================
> Date: Tue Mar 01 19:41:29 2005
> In reply to: 24
> Work done by: someuser
> Work done at (dd/mm/yy hh: m): 1/03/05 3:30pm
> Downtime duration: 0 min
> Planned: Yes
> Reason: Normal work
> Attachment:
> Encoding: plain
>
>
> For some reason it looses the "m" so line 4 instead of having
> "hh:mm" has "hh: m"
Your problem is that the attribute "Work done at (dd/mm/yy hh:mm)" which
contains a ":". This character is not allowed in attributes. Unfortunately I did
not document this (and even didn't know this until now... (;-) ). So you should
use the new option
Type Work done at = datetime
this gives you at the entry mask fields for day/month/year/hour/minute to fill
out, so you don't have to write it directly into the attribute. Another option
would be to use
Comment Work done at = Please enter as (dd/mm/yy hh:mm)
which just displays a comment below the attribute in the entry mask.
- Stefan |
|
1081
|
Wed Apr 13 00:40:55 2005 |
| G | levineg@med.govt.nz | Bug report | Other | 2.5.8-3 | Re: XML password files, replication & FreeBSD |
> > I have been running ELOG on FreeBSD no problem for a year now,
> > but this new version 2.5.8-x doesn't seem to wanna work, it compiles fine
> > with a few warnings (see attached logs).
> > But has issues with password files, now it shows message "Can't open
> > passwords.pwd" for all my logbooks. It did convert the password files to
> > xml format. I had a good hard look at file permissions and config file with
> > no luck. So I went back a version and compiled 2.5.7-1 which works just
> > fine with old password files. So something with XML & FreeBSD?...
>
> Hard to say. The simplest would be if I could debug this.
Anything I could send you to help debug this?
>
> > Version 2.5.7-1 (maybe this has been fixed in 2.5.8?)
> > When I run a ./elogd -C http://elog.blah.here:88 it clones the config file
> > just fine, also seems to copy over all logbook entries.
> > But once I look through them there's a fault with one of the fields it
> > copies over, so entries never show up.
> >
> > It should be:
> > ========================================
> > Date: Tue Mar 01 19:41:29 2005
> > In reply to: 24
> > Work done by: someuser
> > Work done at (dd/mm/yy hh:mm): 1/03/05 3:30pm
> > Downtime duration: 0 min
> > Planned: Yes
> > Reason: Normal work
> > Attachment:
> > Encoding: plain
> >
> > But once cloned it looks like this:
> > ========================================
> > Date: Tue Mar 01 19:41:29 2005
> > In reply to: 24
> > Work done by: someuser
> > Work done at (dd/mm/yy hh: m): 1/03/05 3:30pm
> > Downtime duration: 0 min
> > Planned: Yes
> > Reason: Normal work
> > Attachment:
> > Encoding: plain
> >
> >
> > For some reason it looses the "m" so line 4 instead of having
> > "hh:mm" has "hh: m"
>
> Your problem is that the attribute "Work done at (dd/mm/yy hh:mm)" which
> contains a ":". This character is not allowed in attributes. Unfortunately I did
> not document this (and even didn't know this until now... (;-) ). So you should
> use the new option
>
> Type Work done at = datetime
>
> this gives you at the entry mask fields for day/month/year/hour/minute to fill
> out, so you don't have to write it directly into the attribute. Another option
> would be to use
>
> Comment Work done at = Please enter as (dd/mm/yy hh:mm)
>
> which just displays a comment below the attribute in the entry mask.
>
> - Stefan
Ok, i see, the problem for me now is that this attribute name has been in use for
half a year or so by me. So now I have 100's of logbook entries with the old name
in them, if I change it's name then all old logbook entries will show up with that
field blank. I'm not sure if there's an easy way to change that attribute's name in
100's of entries in 10's of logbooks, because I wouldn't want to try doing that by
hand.. Any ideas? (i'm no good at scripting something like that 4 sure)
Thanks,
G. |
|
1082
|
Wed Apr 13 09:06:46 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Other | 2.5.8-3 | Re: XML password files, replication & FreeBSD |
> Ok, i see, the problem for me now is that this attribute name has been in use for
> half a year or so by me. So now I have 100's of logbook entries with the old name
> in them, if I change it's name then all old logbook entries will show up with that
> field blank. I'm not sure if there's an easy way to change that attribute's name in
> 100's of entries in 10's of logbooks, because I wouldn't want to try doing that by
> hand.. Any ideas? (i'm no good at scripting something like that 4 sure)
find . -name "*a.log" -exec perl -pi -e 's|Work done at (dd/mm/yy hh:mm):|Work done at:|g' {} \;
Looks a bit cryptic, but searches for all *a.log files, and starts perl to replace
all occurences of "Work done at (dd/mm/yy hh:mm)" with "Word done at:". Better try
this first with a copy of your logbook. After you successfully changed that, you
have to modify the attribute list in elogd.cfg accordingly, like
Attirbutes = ..., Work done at, ...
Please note that after each manual modification of the logbook files, you have to
restart elogd. |
|
1422
|
Mon Sep 26 11:03:52 2005 |
 | Guenter Nowak | Guenter.Nowqak@t-systems.at | Bug fix | Other | V2.5.9-2 | error when searching for POST |
is this an elog bug?
calling
http://midas.psi.ch/elogs/Linux%20Demo/?cmd=Find
(ELOG V2.6.0-beta4)
and typing
POST
in uppercase-letters
I get the error
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /elogs/Linux Demo/.
Reason: Error reading from remote server
--------------------------------------------------------------------------------
Apache/2.0.46 (Red Hat) Server at midas.psi.ch Port 80
doing the same thing on my elog installation (ELOG V2.5.9-2) gives the error
Die Seite kann nicht angezeigt werden.
Die gewünschte Seite ist zurzeit nicht verfügbar. Möglicherweise sind technische Schwierigkeiten aufgetreten oder Sie sollten die Browsereinstellungen überprüfen.
--------------------------------------------------------------------------------
Versuchen Sie Folgendes:
... (some text skipped, guenter)
Fehler: Server oder DNS kann nicht gefunden werden
Internet Explorer
if if dont type all letters in uppercase no problem occurs
thanks
guneter |