Re: [freenet-support] Java cpu usage running amok, FMS crashed node

2010-10-16 Thread Matthew Toseland
On Thursday 08 July 2010 15:11:42 you wrote:
 Dennis Nezic schreef:
 
  I'm almost certain that error message has nothing to do with FMS :b.
  One of the good things about FMS is it run as a completely separate
  process (and more reliably :b). Usually when I used to get Internal
  error messages, it meant my node.db4o was corrupted or something, and
  I would lose all my download queues. Is this true in your case?
 
 It is one of the messages that keeps me off the street... yes, it is 
 often corrupted. About every time I get disconnected. Sometimes, only 
 sometimes it does not happen on a deliberate FN restart. Usually I shut 
 Frost off first to prevent that from happening.
 On a winz reboot, I can be almost sure of FN not working anymore.

So you get internal errors when you reboot? Something is severely wrong with 
your system, causing on-disk disk corruption and data loss on reboot. Likely 
not a Freenet issue.
 
 But if it helps to remove node.db4o.crypt is another issue.
 Now it is Frost that crashes my node, and it's hell once more to get 
 Freenet to connect to anything. Looks like I wind up yet again 
 reinstalling the lot of Freenet. Deleting that file does not help.

This has nothing to do with node.db4o. It is completely unrelated. And you 
haven't given enough information to understand the problem anyway. I.e. what 
happens, what does wrapper.log say etc.
 
 I take it was FMS not dealing with the mailserver already occupying the 
 webinterface, but seeing how many times I've tried to get FN working, I 
 won't try FMS again soon.
 Were I paid for efforts to get FN working, I had earned enough for a 
 weeks holiday.
 
 
 There was an error message I'd not seen before:
 ==
 The auto-updater may have been compromised! We have turned it off for 
 now, please click for more details.
 The auto-updater has been disabled. This might be because of a local 
 problem, such as running out of disk space, or the auto-updating system 
 may have been compromised. The reason is: Permanent error fetching 
 revocation (error inserting the revocation key?): 
 FetchException:Internal error:null:-1:null:false:null:null.
 
 Happened while only 1 stranger was connected.


signature.asc
Description: This is a digitally signed message part.
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe

Re: [freenet-support] Java cpu usage running amok, FMS crashed node

2010-07-28 Thread Matthew Toseland
On Thursday 08 July 2010 12:05:48 Jep wrote:
 As I'm used to by now, it took multiple efforts to get the new Freenet 
 version 1259 to connect to strangers; it seems to require a complete new 
 install from scratch and no less will do.
 No way of updating works for me, FN has been whirling all night in a 
 loop of restarting the old version and finding that it needs to be updated.
 
 But I got it working again, and decided to give FMS a try. Dl'd it over 
 FN, started it.
 It gave me a DOS window 'FMS is started'.
 On the config page http://localhost/8080 only a blank page came up.
 The node disconnected immediately; the 'browse FN' page gave:
 
 
 Internal error: please report
 
 java.lang.NoClassDefFoundError: Could not initialize class 
 freenet.support.HTMLEncoder
   at freenet.l10n.BaseL10n.addL10nSubstitution(BaseL10n.java:495)
   at 
 freenet.clients.http.WelcomeToadlet.handleMethodGET(WelcomeToadlet.java:459)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
   at java.lang.reflect.Method.invoke(Unknown Source)
   at 
 freenet.clients.http.ToadletContextImpl.handle(ToadletContextImpl.java:534)
   at 
 freenet.clients.http.SimpleToadletServer$SocketHandler.run(SimpleToadletServer.java:794)
   at 
 freenet.support.PooledExecutor$MyThread.realRun(PooledExecutor.java:228)
   at freenet.support.io.NativeThread.run(NativeThread.java:101)
 
 and my node restarted again.

That is definitely a low level, local problem: It happens when Java can't 
access the jar file any more.
 
 I guess FMS conflicted with my mail server, it has a web interface at 
 localhost/8080 that I forgot about.
 Switched it off but it will be a while before I try FMS again. Just 
 figured you want to know about the error.


signature.asc
Description: This is a digitally signed message part.
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe

Re: [freenet-support] Java cpu usage running amok, FMS crashed node

2010-07-08 Thread Jep
As I'm used to by now, it took multiple efforts to get the new Freenet 
version 1259 to connect to strangers; it seems to require a complete new 
install from scratch and no less will do.
No way of updating works for me, FN has been whirling all night in a 
loop of restarting the old version and finding that it needs to be updated.


But I got it working again, and decided to give FMS a try. Dl'd it over 
FN, started it.

It gave me a DOS window 'FMS is started'.
On the config page http://localhost/8080 only a blank page came up.
The node disconnected immediately; the 'browse FN' page gave:


Internal error: please report

java.lang.NoClassDefFoundError: Could not initialize class 
freenet.support.HTMLEncoder

at freenet.l10n.BaseL10n.addL10nSubstitution(BaseL10n.java:495)
	at 
freenet.clients.http.WelcomeToadlet.handleMethodGET(WelcomeToadlet.java:459)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
	at 
freenet.clients.http.ToadletContextImpl.handle(ToadletContextImpl.java:534)
	at 
freenet.clients.http.SimpleToadletServer$SocketHandler.run(SimpleToadletServer.java:794)

at 
freenet.support.PooledExecutor$MyThread.realRun(PooledExecutor.java:228)
at freenet.support.io.NativeThread.run(NativeThread.java:101)

and my node restarted again.

I guess FMS conflicted with my mail server, it has a web interface at 
localhost/8080 that I forgot about.
Switched it off but it will be a while before I try FMS again. Just 
figured you want to know about the error.


___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe


Re: [freenet-support] Java cpu usage running amok, FMS crashed node, and now Frost as well

2010-07-08 Thread Jep

Jep schreef:
[FMS crashed FN, probably due to mail server interface]


A yet new way of the node disconnecting. I was used to Frost remembering 
what I was downloading, but now also starting Frost crashes it.

sigh... I'll try it again with all downz/uploads removed.

___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe


Re: [freenet-support] Java cpu usage running amok, FMS crashed node

2010-07-08 Thread Dennis Nezic
On Thu, 08 Jul 2010 13:05:48 +0200, Jep wrote:
 As I'm used to by now, it took multiple efforts to get the new
 Freenet version 1259 to connect to strangers; it seems to require a
 complete new install from scratch and no less will do.
 No way of updating works for me, FN has been whirling all night in a 
 loop of restarting the old version and finding that it needs to be
 updated.
 
 But I got it working again, and decided to give FMS a try. Dl'd it
 over FN, started it.
 It gave me a DOS window 'FMS is started'.
 On the config page http://localhost/8080 only a blank page came up.
 The node disconnected immediately; the 'browse FN' page gave:
 
 
 Internal error: please report
 
 java.lang.NoClassDefFoundError: Could not initialize class 
 freenet.support.HTMLEncoder
   at freenet.l10n.BaseL10n.addL10nSubstitution
 (BaseL10n.java:495) at 
 freenet.clients.http.WelcomeToadlet.handleMethodGET
 (WelcomeToadlet.java:459) at
 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
 sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at
 java.lang.reflect.Method.invoke(Unknown Source) at 
 freenet.clients.http.ToadletContextImpl.handle
 (ToadletContextImpl.java:534) at 
 freenet.clients.http.SimpleToadletServer$SocketHandler.run
 (SimpleToadletServer.java:794) at freenet.support.PooledExecutor
 $MyThread.realRun(PooledExecutor.java:228) at
 freenet.support.io.NativeThread.run(NativeThread.java:101)
 
 and my node restarted again.
 
 I guess FMS conflicted with my mail server, it has a web interface at 
 localhost/8080 that I forgot about.
 Switched it off but it will be a while before I try FMS again. Just 
 figured you want to know about the error.

I'm almost certain that error message has nothing to do with FMS :b.
One of the good things about FMS is it run as a completely separate
process (and more reliably :b). Usually when I used to get Internal
error messages, it meant my node.db4o was corrupted or something, and
I would lose all my download queues. Is this true in your case?
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe


Re: [freenet-support] Java cpu usage running amok, FMS crashed node

2010-07-08 Thread Jan
Spam detection software, running on the system freenetproject.org, has
identified this incoming email as possible spam.  The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email.  If you have any questions, see
the administrator of that system for details.

Content preview:  Dennis Nezic schreef:  I'm almost certain that error message
   has nothing to do with FMS :b.  One of the good things about FMS is it run
   as a completely separate  process (and more reliably :b). Usually when I
   used to get Internal  error messages, it meant my node.db4o was corrupted
   or something, and  I would lose all my download queues. Is this true in
  your case? [...] 

Content analysis details:   (7.9 points, 5.0 required)

 pts rule name  description
 -- --
 3.3 TVD_RCVD_IP4   TVD_RCVD_IP4
 1.6 TVD_RCVD_IPTVD_RCVD_IP
 2.9 RCVD_IN_XBLRBL: Received via a relay in Spamhaus XBL
[83.160.55.145 listed in zen.spamhaus.org]


---BeginMessage---

Dennis Nezic schreef:


I'm almost certain that error message has nothing to do with FMS :b.
One of the good things about FMS is it run as a completely separate
process (and more reliably :b). Usually when I used to get Internal
error messages, it meant my node.db4o was corrupted or something, and
I would lose all my download queues. Is this true in your case?


It is one of the messages that keeps me off the street... yes, it is 
often corrupted. About every time I get disconnected. Sometimes, only 
sometimes it does not happen on a deliberate FN restart. Usually I shut 
Frost off first to prevent that from happening.

On a winz reboot, I can be almost sure of FN not working anymore.

But if it helps to remove node.db4o.crypt is another issue.
Now it is Frost that crashes my node, and it's hell once more to get 
Freenet to connect to anything. Looks like I wind up yet again 
reinstalling the lot of Freenet. Deleting that file does not help.


I take it was FMS not dealing with the mailserver already occupying the 
webinterface, but seeing how many times I've tried to get FN working, I 
won't try FMS again soon.
Were I paid for efforts to get FN working, I had earned enough for a 
weeks holiday.



There was an error message I'd not seen before:
==
The auto-updater may have been compromised! We have turned it off for 
now, please click for more details.
The auto-updater has been disabled. This might be because of a local 
problem, such as running out of disk space, or the auto-updating system 
may have been compromised. The reason is: Permanent error fetching 
revocation (error inserting the revocation key?): 
FetchException:Internal error:null:-1:null:false:null:null.


Happened while only 1 stranger was connected.

---End Message---
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe

Re: [freenet-support] Java cpu usage running amok, FMS crashed node

2010-07-08 Thread Jep
Spam detection software, running on the system freenetproject.org, has
identified this incoming email as possible spam.  The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email.  If you have any questions, see
the administrator of that system for details.

Content preview:  Dennis Nezic schreef:  I'm almost certain that error message
   has nothing to do with FMS :b.  One of the good things about FMS is it run
   as a completely separate  process (and more reliably :b). Usually when I
   used to get Internal  error messages, it meant my node.db4o was corrupted
   or something, and  I would lose all my download queues. Is this true in
  your case? [...] 

Content analysis details:   (7.9 points, 5.0 required)

 pts rule name  description
 -- --
 3.3 TVD_RCVD_IP4   TVD_RCVD_IP4
 1.6 TVD_RCVD_IPTVD_RCVD_IP
 2.9 RCVD_IN_XBLRBL: Received via a relay in Spamhaus XBL
[83.160.55.145 listed in zen.spamhaus.org]


---BeginMessage---

Dennis Nezic schreef:


I'm almost certain that error message has nothing to do with FMS :b.
One of the good things about FMS is it run as a completely separate
process (and more reliably :b). Usually when I used to get Internal
error messages, it meant my node.db4o was corrupted or something, and
I would lose all my download queues. Is this true in your case?


It is one of the messages that keeps me off the street... yes, it is
often corrupted. About every time I get disconnected. Sometimes, only
sometimes it does not happen on a deliberate FN restart. Usually I shut
Frost off first to prevent that from happening.
On a winz reboot, I can be almost sure of FN not working anymore.

But if it helps to remove node.db4o.crypt is another issue.
Now it is Frost that crashes my node, and it's hell once more to get
Freenet to connect to anything. Looks like I wind up yet again
reinstalling the lot of Freenet. Deleting that file does not help.

I take it was FMS not dealing with the mailserver already occupying the
webinterface, but seeing how many times I've tried to get FN working, I
won't try FMS again soon.
Were I paid for efforts to get FN working, I had earned enough for a
weeks holiday.


There was an error message I'd not seen before:
==
The auto-updater may have been compromised! We have turned it off for
now, please click for more details.
The auto-updater has been disabled. This might be because of a local
problem, such as running out of disk space, or the auto-updating system
may have been compromised. The reason is: Permanent error fetching
revocation (error inserting the revocation key?):
FetchException:Internal error:null:-1:null:false:null:null.

Happened while only 1 stranger was connected.


---End Message---
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe