| Stefan Ritt wrote: |
|
| Gillian Sabberton wrote: |
|
We have been running elog for a couple of years now and this morning it stopped working.
We have tried to rstart it and it says successful start but still does not run, when doing a restart it says stop failed start success.
Does anyone have any ideas.
thanks
|
You shoudl start elogd interactively in a DOS box to see if there is any error. Maybe disk full or a network problem...
|
It is running on a linux box, we have started in it in a telnet session, and no errors appear, as I am new to e-log is there an error log anywhere. |
| Gillian Sabberton wrote: |
|
| Stefan Ritt wrote: |
|
| Gillian Sabberton wrote: |
|
We have been running elog for a couple of years now and this morning it stopped working.
We have tried to rstart it and it says successful start but still does not run, when doing a restart it says stop failed start success.
Does anyone have any ideas.
thanks
|
You shoudl start elogd interactively in a DOS box to see if there is any error. Maybe disk full or a network problem...
|
It is running on a linux box, we have started in it in a telnet session, and no errors appear, as I am new to e-log is there an error log anywhere.
|
Have fixed this by removing the last added user from the Passwd file. |
| Gillian Sabberton wrote: |
|
| Stefan Ritt wrote: |
|
| Gillian Sabberton wrote: |
|
We have been running elog for a couple of years now and this morning it stopped working.
We have tried to rstart it and it says successful start but still does not run, when doing a restart it says stop failed start success.
Does anyone have any ideas.
thanks
|
You shoudl start elogd interactively in a DOS box to see if there is any error. Maybe disk full or a network problem...
|
It is running on a linux box, we have started in it in a telnet session, and no errors appear, as I am new to e-log is there an error log anywhere.
|
Have fixed this by removing the last added user from the Passwd file. |
Hi,
my ELOG sometimes dies with "deadc0de", do I have too large ELOG config or logbook? Or is it simply a bug?
What can I do to solve this problem? "ulimit"? Or some trace output from elog?
BR, Niklas |
Hi all,
I'm trying to use the command-line client from linux, but I can't make it
work and that's driving me nuts...
What I want is to reply to a selected message in the logbook, but I
stumble onto two problems:
- There is a read password ("Read Password=..." entry in elogd.cfg)on
the logbook which I cannot bypass from the client. Specifying the switch
-u "" password on the command line has no effect, and neither does
-w password. The error message I get is included at the bottom of this message. If I disable the
read password, I get past the authentication.
- There is a required attribute called "Publiek", and it's defined as
MOptions. Whenever I try to upload, I keep getting the message that it misses this attribute. I
tried the switch -a Publiek=Anders, -a "Publiek=Anders", -a
Publiek_0=Anders, -a "Publiek_0=Anders" -a "Publiek_1=Onbekend,
-a Publiek=1 on the beginning, end, and middle of the command, but
the results are the same. Both "Anders" and "Onbekend" are in the MOptions
list (including capitals).
For completeness, here's (one variety) of my command line:
elog -a "Publiek=1" -h localhost -p 8181 -l Artikelen -v -r 80
The obvious question is if anybody knows what I'm doing wrong. Any help
is greatly appreciated.
Pieter
Authentication error:
Successfully connected to host localhost,
port 8181
Request sent to host:
GET /Artikelen/80?cmd=download HTTP/1.0
Host: pde.dyndns.org
User-Agent: ELOG
Cookie: upwd=bWFOZGFyaWpO;
Response received:
HTTP/1.1 401 Authorization Required
Server: ELOG HTTP 2.5.7-1
WWW-Authenticate: Basic realm="Artikelen"
Connection: close
Content-Type: text/html
<HTML><HEAD>
<TITLE>401 Authorization Required</TITLE>
</HEAD><BODY>
<H1>Authorization Required</H1>
This server could not verify that you
are authorized to access the document
requested. Either you supplied the wrong
credentials (e.g., bad password), or your
browser doesn't understand how to supply
the credentials required.
</BODY></HTML>
Error transmitting message
Missing attribute error
Successfully connected to host localhost, port 8181
Request sent to host:
POST /Artikelen/ HTTP/1.0
Content-Type: multipart/form-data; boundary=---------------------------75ABFDB1E
CB47273B853CE0
Host: pde.dyndns.org
User-Agent: ELOG
Content-Length: 3651
Content sent to host.
Response received:
HTTP/1.1 200 Document follows
Server: ELOG HTTP 2.5.7-1
Content-Type: text/html;charset=ISO-8859-1
Connection: Keep-Alive
Keep-Alive: timeout=60, max=10
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head><title>ELOG error</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">
</head>
<body><center>
<table class="dlgframe" width="50%" cellpadding=1 cellspacing=0<tr><td
class="er
rormsg"><i>Error: Attribute <b>Publiek</b> not
supplied.</i><p>
Please go back and enter the <b>Publiek</b> field.
</td></tr>
<tr><td class="errormsg">Please use your browser's back button to go back
</td></tr>
</table>
</center></body></html>
Error: Missing required attribute "Publiek"
|
This solved the problems, thanks for the fast response!
On a side note, one would expect that when "Fixed Attributes Edit" or "Fixed Attributes
Reply" is set, the attributes in this list shouldn't be supplied with the command line client.
Anyway, my problem is solved. Thanks for the great product.
Pieter. |