Re: [freenet-support] ugly bug

2003-01-23 Thread Dave Hooper
Ian Clarke wrote:
 A better way might be to track the log-file itself and look for
 particular log messages.  This could be used to both deterimine when
 : is available, and also to spot common problems.

I disagree - I think we had this discussion before.  A user can review the
log-file if he/she wishes, but programmatically parsing the log-file is
not really sensible, unless we are able to guarantee the text, content and
meaning of messages will not change beyond a rigid specification.
One way to tackle this might be to add ftp-style codes to error messages,
but it still doesn't solve the issue of needing to identify when something
has *stopped* working  (if it's stopped working unexpectedly it won't be
able to log a message saying I've stopped working unexpectedly ...)

Probing FNP and fproxy ports is the obvious solution.

d

___
support mailing list
[EMAIL PROTECTED]
http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support



[freenet-support] ugly bug

2003-01-22 Thread 5tucatz elPunishar
hi there,

i just found a bug that fucked me up the ass for the last two days.
if you enter a non-existent hostname in the allowedHosts field, the 
freenetnode crashes with a BadHostName exception, but does not indicate this 
on the system tray (windows).

___
support mailing list
[EMAIL PROTECTED]
http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support



Re: [freenet-support] ugly bug

2003-01-22 Thread 5tucatz elPunishar
yeah the BadHostName exception is in the logfile (thats how i found out of 
course..).
the web interface does not start up.

On Wednesday 22 January 2003 11:58, Dave Hooper wrote:
  hi there,
 
  i just found a bug that fucked me up the ass for the last two days.
  if you enter a non-existent hostname in the allowedHosts field, the
  freenetnode crashes with a BadHostName exception, but does not indicate
  this
  on the system tray (windows).

 See my earlier email.  I'm currently modifying the windows tray app to
 probe the FNP (FreeNet Protocol) and web interface ports to see if the
 freenet node is actually running.  This will visually indicate precisely
 this sort of problem.
 As general advice, if you're having problems with freenet and it seems
 like it isn't working as it should, you can right click the tray and pick
 View Logfile to see the most recent logs which should include errors and
 exceptions.  Alternatively use the 'most recent exceptions' (I forget its
 name) in the web interface.

 Can you describe the 'crash' ?  Does the web interface actually stop
 working?  Does the BadHostName exception actually not appear in
 freenet.log (as shown by View Logfile) ?

 d

 ___
 support mailing list
 [EMAIL PROTECTED]
 http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support


___
support mailing list
[EMAIL PROTECTED]
http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support



Re: [freenet-support] ugly bug

2003-01-22 Thread Ian Clarke
A better way might be to track the log-file itself and look for 
particular log messages.  This could be used to both deterimine when 
: is available, and also to spot common problems.

Ian.

On Wed, Jan 22, 2003 at 11:58:18AM -, Dave Hooper wrote:
  hi there,
 
  i just found a bug that fucked me up the ass for the last two days.
  if you enter a non-existent hostname in the allowedHosts field, the
  freenetnode crashes with a BadHostName exception, but does not indicate
  this
  on the system tray (windows).
 
 See my earlier email.  I'm currently modifying the windows tray app to
 probe the FNP (FreeNet Protocol) and web interface ports to see if the
 freenet node is actually running.  This will visually indicate precisely
 this sort of problem.
 As general advice, if you're having problems with freenet and it seems
 like it isn't working as it should, you can right click the tray and pick
 View Logfile to see the most recent logs which should include errors and
 exceptions.  Alternatively use the 'most recent exceptions' (I forget its
 name) in the web interface.
 
 Can you describe the 'crash' ?  Does the web interface actually stop
 working?  Does the BadHostName exception actually not appear in
 freenet.log (as shown by View Logfile) ?
 
 d
 
 ___
 support mailing list
 [EMAIL PROTECTED]
 http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support

-- 
Ian Clarkeian@[freenetproject.org|locut.us|cematics.com]
Latest Project  http://locut.us/
Personal Homepage   http://locut.us/ian/

___
support mailing list
[EMAIL PROTECTED]
http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support