[X] My Assistant

The new changes are great, but here's something I spotted twice while running the program which I don't recall seeing before with prev versions. After the error it just goes back to normal, so it's not a problem, but still.
(IMG:[i.imgur.com] http://i.imgur.com/iA1LttM.jpg)

The new changes are great, but here's something I spotted twice while running the program which I don't recall seeing before with prev versions. After the error it just goes back to normal, so it's not a problem, but still.

Looks like a DNS issue. Try changing your DNS server to 8.8.8.8 (Google DNS) instead of whatever your ISP offers.

The new changes are great, but here's something I spotted twice while running the program which I don't recall seeing before with prev versions. After the error it just goes back to normal, so it's not a problem, but still.
(IMG:[i.imgur.com] http://i.imgur.com/iA1LttM.jpg)

You can also try OpenDNS (208.67.222.222, 208.67.220.220) if you'd rather avoid Google.

THANK YOU

Thanks for the update.No more argee

On a whim I recently decided to start H@H with --verify_cache, and it ended up finding 3 or so files that were corrupt. I was wondering, what happens if one of those files was part of one of the static ranges assigned to my client? Would it get replaced automatically, or fail to be served (reducing trust)?

On a whim I recently decided to start H@H with --verify_cache, and it ended up finding 3 or so files that were corrupt. I was wondering, what happens if one of those files was part of one of the static ranges assigned to my client? Would it get replaced automatically, or fail to be served (reducing trust)?

It gets replaced automatically if anyone requests it.

So freaking good.

The speed never bothered me anyway.

It gets replaced automatically if anyone requests it.

Thanks (IMG:[invalid] style_emoticons/default/smile.gif)

Having some issues with 1.2.5.
Updated from 1.2.0 which was working.

After loading it gets stuck on "Building and sending cache list to server..."
Nothing in the log of interest. Passes the speed tests, sends the cache file, finishes sending then nothing.
Heaps of warnings about rejecting connection request during startup after that.

It does say it may take awhile, but i left it for over an hour and still nothing. The cache is fairly small, 1.42gb.

CODE

2015-03-12T04:06:05Z [debug] Response Written:
2015-03-12T04:06:05Z [debug] I feel FANTASTIC and I'm still alive
2015-03-12T04:06:05Z [info] {1/94.100.22.210}   Code=200 Bytes=36       GET /servercmd/still_alive//1426133160/bc58a76f34b1bf698de439a94618e5979e18bed8 HTTP/1.1
2015-03-12T04:06:05Z [info] {1/94.100.22.210}   Code=200 Bytes=36       Finished processing request in 0.00 seconds (36.00 KB/s)
2015-03-12T04:06:06Z [info] {2/94.100.22.210}   Code=200 Bytes=10000001 GET /servercmd/speed_test/testsize=10000001/1426133161/79690232bd883a27c76d36c7f4cb2781061e5a08 HTTP/1.1
2015-03-12T04:06:06Z [WARN] Rejecting connection request during startup.
2015-03-12T04:06:07Z [WARN] Rejecting connection request during startup.
2015-03-12T04:06:07Z [WARN] Rejecting connection request during startup.
2015-03-12T04:06:08Z [WARN] Rejecting connection request during startup.
2015-03-12T04:06:09Z [WARN] Rejecting connection request during startup.
2015-03-12T04:06:09Z [WARN] Rejecting connection request during startup.
2015-03-12T04:06:09Z [WARN] Rejecting connection request during startup.
2015-03-12T04:06:10Z [WARN] Rejecting connection request during startup.
2015-03-12T04:06:46Z [info] {2/94.100.22.210}   Code=200 Bytes=10000001 Finished processing request in 40.28 seconds (248.27 KB/s)
2015-03-12T04:06:49Z [info] {3/94.100.22.210}   Code=200 Bytes=3333334  GET /servercmd/speed_test/testsize=3333334/1426133204/f7de09b1a8a434bd785c2aa6938d71e3688ed8db HTTP/1.1
2015-03-12T04:06:49Z [info] {5/94.100.22.210}   Code=200 Bytes=3333336  GET /servercmd/speed_test/testsize=3333336/1426133204/c0ecc2b077fde55e7ed000162837792361172dfd HTTP/1.1
2015-03-12T04:06:49Z [info] {4/94.100.22.210}   Code=200 Bytes=3333335  GET /servercmd/speed_test/testsize=3333335/1426133204/545b758f3877a6365d9fc648eb373033a8e5536b HTTP/1.1
2015-03-12T04:07:04Z [info] {3/94.100.22.210}   Code=200 Bytes=3333334  Finished processing request in 14.91 seconds (223.61 KB/s)
2015-03-12T04:07:06Z [info] {5/94.100.22.210}   Code=200 Bytes=3333336  Finished processing request in 17.74 seconds (187.86 KB/s)
2015-03-12T04:07:16Z [info] {4/94.100.22.210}   Code=200 Bytes=3333335  Finished processing request in 27.22 seconds (122.48 KB/s)
2015-03-12T04:07:19Z [info] {6/94.100.22.210}   Code=200 Bytes=2000002  GET /servercmd/speed_test/testsize=2000002/1426133234/d7aeb43f6fc64fca9b16a4c9e66b2bb8e7707c66 HTTP/1.1
2015-03-12T04:07:19Z [info] {7/94.100.22.210}   Code=200 Bytes=2000005  GET /servercmd/speed_test/testsize=2000005/1426133234/13349be7742754eafe5e30f49b07ef42909df974 HTTP/1.1
2015-03-12T04:07:19Z [info] {9/94.100.22.210}   Code=200 Bytes=2000003  GET /servercmd/speed_test/testsize=2000003/1426133234/e2f258820ec7aea4a8dca15fe508abb869250893 HTTP/1.1
2015-03-12T04:07:19Z [info] {10/94.100.22.210}   Code=200 Bytes=2000001  GET /servercmd/speed_test/testsize=2000001/1426133234/ef9db927de5a56c4f68c50fbb6828abba2efffa8 HTTP/1.1
2015-03-12T04:07:19Z [info] {8/94.100.22.210}   Code=200 Bytes=2000004  GET /servercmd/speed_test/testsize=2000004/1426133234/c0f27873164568dde16612583b496d1047c90c13 HTTP/1.1
2015-03-12T04:07:27Z [info] {6/94.100.22.210}   Code=200 Bytes=2000002  Finished processing request in 8.77 seconds (228.10 KB/s)
2015-03-12T04:07:33Z [info] {9/94.100.22.210}   Code=200 Bytes=2000003  Finished processing request in 13.82 seconds (144.69 KB/s)
2015-03-12T04:07:34Z [info] {7/94.100.22.210}   Code=200 Bytes=2000005  Finished processing request in 15.61 seconds (128.12 KB/s)
2015-03-12T04:07:37Z [info] {10/94.100.22.210}   Code=200 Bytes=2000001  Finished processing request in 18.69 seconds (107.02 KB/s)
2015-03-12T04:07:38Z [info] {8/94.100.22.210}   Code=200 Bytes=2000004  Finished processing request in 19.68 seconds (101.64 KB/s)
2015-03-12T04:07:41Z [info] Sending cache list, and waiting for the server to register the cached files.. (this could take a while)
2015-03-12T04:07:41Z [info] {11/94.100.22.210}   Code=200 Bytes=530905   GET /servercmd/cache_list/max_filesize=0;max_filecount=99999999/1426133257/3521f092c851c409568a2b10eacca3c45b0884fb HTTP/1.1
2015-03-12T04:07:41Z [info] Retrieving segment 0 of 16
2015-03-12T04:07:41Z [info] Retrieving segment 1 of 16
2015-03-12T04:07:41Z [info] Retrieving segment 2 of 16
2015-03-12T04:07:41Z [info] Retrieving segment 3 of 16
2015-03-12T04:07:42Z [info] Retrieving segment 4 of 16
2015-03-12T04:07:43Z [info] Retrieving segment 5 of 16
2015-03-12T04:07:43Z [info] Retrieving segment 6 of 16
2015-03-12T04:07:44Z [info] Retrieving segment 7 of 16
2015-03-12T04:07:44Z [info] Retrieving segment 8 of 16
2015-03-12T04:07:44Z [info] Retrieving segment 9 of 16
2015-03-12T04:07:45Z [info] Retrieving segment 10 of 16
2015-03-12T04:07:46Z [info] Retrieving segment 11 of 16
2015-03-12T04:07:46Z [info] Retrieving segment 12 of 16
2015-03-12T04:07:47Z [info] Retrieving segment 13 of 16
2015-03-12T04:07:48Z [info] Retrieving segment 14 of 16
2015-03-12T04:07:48Z [info] Retrieving segment 15 of 16
2015-03-12T04:07:49Z [info] {11/94.100.22.210}   Code=200 Bytes=530905   Finished processing request in 7.47 seconds (71.07 KB/s)
2015-03-12T04:07:57Z [WARN] Rejecting connection request during startup.
2015-03-12T04:08:18Z [WARN] Rejecting connection request during startup.
2015-03-12T04:08:19Z [WARN] Rejecting connection request during startup.
2015-03-12T04:08:22Z [WARN] Rejecting connection request during startup.
2015-03-12T04:08:26Z [WARN] Rejecting connection request during startup.
2015-03-12T04:08:26Z [WARN] Rejecting connection request during startup.
2015-03-12T04:08:30Z [WARN] Rejecting connection request during startup.

I tried a fresh instance without the caches file (0byte cache) but it still gets stuck at the same point.
H@H active clients on the website reports the host has timed out.
Any ideas?

Having some issues with 1.2.5.
Updated from 1.2.0 which was working.

As far as I can tell, your client is online and working as it should?

On a whim I recently decided to start H@H with --verify_cache, and it ended up finding 3 or so files that were corrupt. I was wondering, what happens if one of those files was part of one of the static ranges assigned to my client? Would it get replaced automatically, or fail to be served (reducing trust)?

Hmm... silent data corruption of 3 files?

It gets replaced automatically if anyone requests it.

So, since I run zfs, I shouldn't ever need --verify_cache right? Or, what would happen if it attempted to read, and zfs returned an error due to having detected data corruption? Would the h@h client replace it automatically, or do I need to recover from backups, or run --verify_cache?

So, since I run zfs, I shouldn't ever need --verify_cache right? Or, what would happen if it attempted to read, and zfs returned an error due to having detected data corruption? Would the h@h client replace it automatically, or do I need to recover from backups, or run --verify_cache?

It's relatively unlikely that a client will ever experience random data corruption. Unless there was some kind of crash or power loss while the data was written, it usually indicates that something is wrong on the hardware level, like a faulty storage device, a bad disk controller, or bad RAM. In the latter case, ZFS wouldn't help you since data could be corrupted before it was checksummed and written to disk, but it should catch most of the other cases.

If there is a file system or hardware failure when H@H reads a file, it should report the failure prominently, but it would leave it to the user to do any repairs.

(IMG:[invalid] style_emoticons/default/cool.gif) cruisin' now with this new update (IMG:[invalid] style_emoticons/default/laugh.gif)

As far as I can tell, your client is online and working as it should?

Yep,

Took about 25 restarts last night before it just started working by itself.
Afraid to reload it now.

Hello, I've been using the client fine but as of 3-11-15 16:42 I am suddenly not able to connect to the servers. Am I missing something?

The client status is stuck on "Sending startup notification."

This post has been edited by CordellXXX: Mar 22 2015, 13:05

http://ehwiki.org/wiki/Technical_Issues#Startup_Errors

http://ehwiki.org/wiki/Technical_Issues#Startup_Errors

Ignore this post.. I think I need to forward port 80 again.
That was definitely the problem, thanks.



-
-
-

This post has been edited by CordellXXX: Mar 24 2015, 11:11

Try launching H@H with java -Djava.net.preferIPv4Stack=true -jar HentaiAtHome.jar.

How do I do this exactly?

You type "java -Djava.net.preferIPv4Stack=true -jar HentaiAtHome.jar" where H@H is?