[X] My Assistant

For some reason, my H@H client doesn't seem to want to stay "Online." The actual client shows nothing interesting at all happening, except for the keepalive every 5 minutes.

For about 15 seconds after the keepalive packet, the client status is recorded as "Online", but quickly switches to "Timeout" afterward. The client works fine as an image proxy, so I'm not quite sure what's going on.

Trust is not going up, as obviously the system believes the client is timed out. This is a headless server, so there is no GUI.

Excerpt from logs:

CODE

2012-10-03T00:19:07Z [info] Checking for old files to prune...
2012-10-03T00:19:07Z [info] Pruned 0 files.
2012-10-03T00:21:37Z [info] Connecting to rpc.hentaiathome.net...
2012-10-03T00:21:37Z [info] /clientapi.php?clientbuild=69&act=still_alive[...]: Retrieving 46 bytes...
2012-10-03T00:24:07Z [info] Checking for old files to prune...
2012-10-03T00:24:07Z [info] Pruned 0 files.
2012-10-03T00:26:37Z [info] Connecting to rpc.hentaiathome.net...
2012-10-03T00:26:37Z [info] /clientapi.php?clientbuild=69&act=still_alive[...]: Retrieving 41 bytes...
2012-10-03T00:29:07Z [info] Checking for old files to prune...
2012-10-03T00:29:07Z [info] Pruned 0 files.
2012-10-03T00:31:37Z [info] Connecting to rpc.hentaiathome.net...
2012-10-03T00:31:38Z [info] /clientapi.php?clientbuild=69&act=still_alive[...]: Retrieving 41 bytes...
2012-10-03T00:34:07Z [info] Checking for old files to prune...
2012-10-03T00:34:07Z [info] Pruned 0 files.
2012-10-03T00:36:37Z [info] Connecting to rpc.hentaiathome.net...
2012-10-03T00:36:37Z [info] /clientapi.php?clientbuild=69&act=still_alive[...]: Retrieving 39 bytes...

(On an unrelated note, it's a bit annoying that the stdout logfile isn't flushed on a regular basis. Given the verbosity of the logging done to file, I can see why, but perhaps if the file were flushed to disk at least every 5 minutes or so, instead of when the buffer fills, it might be a bit more useful.) (Although perhaps the only reason not enough log activity is being generated is because the client is some state of broken at the moment.)

Have you tried restarting the client? You could try and see if it might be an issue with your ports. It could also be an issue with your client and you have to re-install it. Just copy over the new client to where the old client was and replace it. It should work then. I had an issue similar to this and that's what worked for me.

For some reason, my H@H client doesn't seem to want to stay "Online." The actual client shows nothing interesting at all happening, except for the keepalive every 5 minutes.

For about 15 seconds after the keepalive packet, the client status is recorded as "Online", but quickly switches to "Timeout" afterward. The client works fine as an image proxy, so I'm not quite sure what's going on.

Trust is not going up, as obviously the system believes the client is timed out. This is a headless server, so there is no GUI.

Excerpt from logs:

CODE

2012-10-03T00:19:07Z [info] Checking for old files to prune...
2012-10-03T00:19:07Z [info] Pruned 0 files.
2012-10-03T00:21:37Z [info] Connecting to rpc.hentaiathome.net...
2012-10-03T00:21:37Z [info] /clientapi.php?clientbuild=69&act=still_alive[...]: Retrieving 46 bytes...
2012-10-03T00:24:07Z [info] Checking for old files to prune...
2012-10-03T00:24:07Z [info] Pruned 0 files.
2012-10-03T00:26:37Z [info] Connecting to rpc.hentaiathome.net...
2012-10-03T00:26:37Z [info] /clientapi.php?clientbuild=69&act=still_alive[...]: Retrieving 41 bytes...
2012-10-03T00:29:07Z [info] Checking for old files to prune...
2012-10-03T00:29:07Z [info] Pruned 0 files.
2012-10-03T00:31:37Z [info] Connecting to rpc.hentaiathome.net...
2012-10-03T00:31:38Z [info] /clientapi.php?clientbuild=69&act=still_alive[...]: Retrieving 41 bytes...
2012-10-03T00:34:07Z [info] Checking for old files to prune...
2012-10-03T00:34:07Z [info] Pruned 0 files.
2012-10-03T00:36:37Z [info] Connecting to rpc.hentaiathome.net...
2012-10-03T00:36:37Z [info] /clientapi.php?clientbuild=69&act=still_alive[...]: Retrieving 39 bytes...

(On an unrelated note, it's a bit annoying that the stdout logfile isn't flushed on a regular basis. Given the verbosity of the logging done to file, I can see why, but perhaps if the file were flushed to disk at least every 5 minutes or so, instead of when the buffer fills, it might be a bit more useful.) (Although perhaps the only reason not enough log activity is being generated is because the client is some state of broken at the moment.)

This is similar to what i had happen. Close and restart your client. If that doesn't help, you may need to delete everything and start it from scratch to make it work again.

Just ran into this issue on an Ubuntu and again Centos client. I'm running 1.0.10.

This post has been edited by G Just G: Nov 7 2012, 17:43

If you're getting the NOT_LOGGED_ON error, that's related to a desync caused by a cluster node restart yesterday. Read ze twitter.

I've got this issue again. Client 7531 is showing timeout on my end but it's currently sending at about 13Mb/s... Sometimes it shows timeout and sometimes it shows a status of online.

The entire time its been doing this hath has stayed at 20/day and +1000 trust. Just seems to randomly show timeout when it's online and sending files.

I have observed this. It seems to be an unrelated issue, but I haven't found the root cause yet. But as far as I can tell, it only lasts until the next time the client reports in.

If it persists long term, i've been able to clear timeout issues by cycling the client (close, restart)

Tenboro I turned on full logging for H@H and manged to match up a "Timeout" with the following form H@H


2012-12-24T01:06:57Z [info] Connecting to 95.211.199.137...
2012-12-24T01:07:02Z [WARN] Read timed out, retrying.. (2 tries left)
2012-12-24T01:07:02Z [info] Connecting to 95.211.199.137...
2012-12-24T01:07:06Z [WARN] Read timed out, retrying.. (1 tries left)
2012-12-24T01:07:06Z [info] Connecting to 95.211.199.130...
2012-12-24T01:07:06Z [WARN] Read timed out, retrying.. (2 tries left)
2012-12-24T01:07:06Z [info] Connecting to 95.211.209.54...
2012-12-24T01:07:07Z [WARN] Read timed out, retrying.. (2 tries left)
2012-12-24T01:07:07Z [info] Connecting to 95.211.199.137...
2012-12-24T01:07:12Z [WARN] Read timed out, retrying.. (1 tries left)
2012-12-24T01:07:12Z [info] Connecting to 95.211.199.137...
2012-12-24T01:07:15Z [info] /image.php?f=5c9578f3ff06602930b3a9207c33d8072e79962f-331168-1133-1600-jpg&t=376752-19457f4750c3983b1caf53762049099039d1920f: Retrieving 331168 bytes...
2012-12-24T01:07:15Z [info] /image.php?f=25613ffcec0b2abfdbb26f7969927d4b61998eaf-452828-1110-1600-jpg&t=376753-ce6bbf4690dd23f408d887f03efd4eb4e32406dd: Retrieving 452828 bytes...
2012-12-24T01:07:16Z [WARN] Read timed out, retrying.. (0 tries left)
2012-12-24T01:07:16Z [WARN] Read timed out, retrying.. (1 tries left)
2012-12-24T01:07:16Z [info] Connecting to 95.211.209.54...
2012-12-24T01:07:16Z [WARN] Exhaused retries or aborted getting [95.211.199.130] http://95.211.199.130:80/image.php?f=1ef0d...ab40d40430a4e2d

The client continued to send files during this time but the website showed timeout.


Also does fast.box.net sound familiar to you? I keep getting pounded by that domain when I timeout.

This post has been edited by G Just G: Dec 24 2012, 03:14

Tenboro I turned on full logging for H@H and manged to match up a "Timeout" with the following form H@H
2012-12-24T01:06:57Z [info] Connecting to 95.211.199.137...
2012-12-24T01:07:02Z [WARN] Read timed out, retrying.. (2 tries left)
2012-12-24T01:07:02Z [info] Connecting to 95.211.199.137...
2012-12-24T01:07:06Z [WARN] Read timed out, retrying.. (1 tries left)
2012-12-24T01:07:06Z [info] Connecting to 95.211.199.130...
2012-12-24T01:07:06Z [WARN] Read timed out, retrying.. (2 tries left)
2012-12-24T01:07:06Z [info] Connecting to 95.211.209.54...
2012-12-24T01:07:07Z [WARN] Read timed out, retrying.. (2 tries left)
2012-12-24T01:07:07Z [info] Connecting to 95.211.199.137...
2012-12-24T01:07:12Z [WARN] Read timed out, retrying.. (1 tries left)
2012-12-24T01:07:12Z [info] Connecting to 95.211.199.137...
2012-12-24T01:07:15Z [info] /image.php?f=5c9578f3ff06602930b3a9207c33d8072e79962f-331168-1133-1600-jpg&t=376752-19457f4750c3983b1caf53762049099039d1920f: Retrieving 331168 bytes...
2012-12-24T01:07:15Z [info] /image.php?f=25613ffcec0b2abfdbb26f7969927d4b61998eaf-452828-1110-1600-jpg&t=376753-ce6bbf4690dd23f408d887f03efd4eb4e32406dd: Retrieving 452828 bytes...
2012-12-24T01:07:16Z [WARN] Read timed out, retrying.. (0 tries left)
2012-12-24T01:07:16Z [WARN] Read timed out, retrying.. (1 tries left)
2012-12-24T01:07:16Z [info] Connecting to 95.211.209.54...
2012-12-24T01:07:16Z [WARN] Exhaused retries or aborted getting [95.211.199.130] http://95.211.199.130:80/image.php?f=1ef0d...ab40d40430a4e2d

The client continued to send files during this time but the website showed timeout.
Also does fast.box.net sound familiar to you? I keep getting pounded by that domain when I timeout.

And now you know why i've got a thousand plus domain names blacklisted at my H@H servers' iptables firewalls (IMG:[invalid] style_emoticons/default/tongue.gif)

Likely you're the target of a DDoS or something at that time from that domain, box.net's a file sharing site, so not sure whether your system's being targetted by them or someone on your system is using box.net... *shrugs*

The H@H server usage has never spiked above 80Mb/s and it's on a line capable of much more than that. Incoming traffic has never exceeded 5.08Mb/s and average 3.35Mb/s and outgoing sits at 67.75Mb/s and a max of 185.8Mb/s so it's not a DDoS. Also I've sent an email off to my hosting provider because I think box.net may be who they're subleasing through. Also the other services hosted on that server experienced no problems. H@H didn't even disconnect and that entire blip lasted 19 seconds. After that it just started working again with no issues.

Also by "pounded" by fast.box.net I mean it was pulling around 20mb/s of outbound traffic.

This post has been edited by G Just G: Dec 24 2012, 19:10