[X] My Assistant

Not by any argument, but you could change the output flags in Out.java to do that.

However, debug logging is mostly about internal state, so I don't really think it will tell you a lot about quality/trust drops. 7000 is still quite good, though.

CODE

2014-01-03T07:54:52Z [ERROR] {org.hath.base.CacheHandler.flushRecentlyAccessed(CacheHandler.java:900)} CacheHandler: Failed to perform database operation
2014-01-03T07:54:52Z [ERR] {java.lang.Throwable$WrappedPrintStream.println(Unknown Source)} java.sql.SQLException: [SQLITE_IOERR]  Some kind of disk I/O error occurred (disk I/O error)
2014-01-03T07:54:52Z [ERR] {java.lang.Throwable$WrappedPrintStream.println(Unknown Source)}     at org.sqlite.DB.newSQLException(DB.java:383)
2014-01-03T07:54:52Z [ERR] {java.lang.Throwable$WrappedPrintStream.println(Unknown Source)}     at org.sqlite.DB.newSQLException(DB.java:387)
2014-01-03T07:54:52Z [ERR] {java.lang.Throwable$WrappedPrintStream.println(Unknown Source)}     at org.sqlite.DB.execute(DB.java:342)
2014-01-03T07:54:52Z [ERR] {java.lang.Throwable$WrappedPrintStream.println(Unknown Source)}     at org.sqlite.DB.executeUpdate(DB.java:363)
2014-01-03T07:54:52Z [ERR] {java.lang.Throwable$WrappedPrintStream.println(Unknown Source)}     at org.sqlite.PrepStmt.executeUpdate(PrepStmt.java:85)
2014-01-03T07:54:52Z [ERR] {java.lang.Throwable$WrappedPrintStream.println(Unknown Source)}     at org.hath.base.CacheHandler.flushRecentlyAccessed(CacheHandler.java:886)
2014-01-03T07:54:52Z [ERR] {java.lang.Throwable$WrappedPrintStream.println(Unknown Source)}     at org.hath.base.CacheHandler.flushRecentlyAccessed(CacheHandler.java:781)
2014-01-03T07:54:52Z [ERR] {java.lang.Throwable$WrappedPrintStream.println(Unknown Source)}     at org.hath.base.HentaiAtHomeClient.run(HentaiAtHomeClient.java:222)
2014-01-03T07:54:52Z [ERR] {java.lang.Throwable$WrappedPrintStream.println(Unknown Source)}     at java.lang.Thread.run(Unknown Source)
2014-01-03T07:54:52Z [ERROR] {org.hath.base.HentaiAtHomeClient.dieWithError(HentaiAtHomeClient.java:285)} Critical Error: java.sql.SQLException: [SQLITE_IOERR]  Some kind of disk I/O error occurred (disk I/O error)
2014-01-03T07:54:52Z [info] Shutting down...

it said an error occuried and shat down and told me to see logs, but I don't see anything usefull there =-\

it said an error occuried and shat down and told me to see logs, but I don't see anything usefull there =-\

Critical Error: java.sql.SQLException: [SQLITE_IOERR] Some kind of disk I/O error occurred (disk I/O error)

That's pretty useful. Do a chkdsk/fsck on the disk, and if possible, an extended SMART test.

That's pretty useful.

It said the same in the msgbox error along with suggestion to check logs for more info, and that's all what was there ;p

Something happened to my swap file, whole system got crappy and needed restart, now all works fine...

love the updates

CODE

2557-01-15T07:35:27Z [info] Connecting to 95.211.199.137...
2557-01-15T07:35:28Z [info] /image.php?f=5b8b027d813816874f1b4433b1dd1d63a9241fd6-156478-568-800-jpg&t=386047-8d6853777962cc05e24fc0dd798cb0f03a79d08f: Retrieving 156478 bytes...
2557-01-15T07:35:30Z [info] The file 5b8b027d813816874f1b4433b1dd1d63a9241fd6-156478-568-800-jpg was successfully downloaded and inserted into the active cache.
2557-01-15T07:35:30Z [info] Connecting to 95.211.209.54...
2557-01-15T07:35:31Z [info] /image.php?f=be6776fe8471d8c665489711445315c5d549506f-160006-800-600-jpg&t=386047-8aac016703775fccffa036429e0fe76abe042992: Retrieving 160006 bytes...
2557-01-15T07:35:33Z [info] The file be6776fe8471d8c665489711445315c5d549506f-160006-800-600-jpg was successfully downloaded and inserted into the active cache.
2557-01-15T07:35:33Z [info] Connecting to 95.211.209.54...
2557-01-15T07:35:33Z [info] /image.php?f=ade3dc621750a9f321eacd44a030995bc29b0f1f-116300-800-600-jpg&t=386047-94d57198a8a94a0177f8f0f6d45bc8492b6cdba9: Retrieving 116300 bytes...
2557-01-15T07:35:34Z [info] The file ade3dc621750a9f321eacd44a030995bc29b0f1f-116300-800-600-jpg was successfully downloaded and inserted into the active cache.
2557-01-15T07:35:34Z [info] Connecting to 95.211.209.54...
2557-01-15T07:35:34Z [info] /image.php?f=d16a6afd9901924bdcc40deceb16134d622e77c8-40824-312-400-jpg&t=386047-fda40ce763f3e4a68c565079a7c077231b09fef3: Retrieving 40824 bytes...
2557-01-15T07:35:34Z [info] The file d16a6afd9901924bdcc40deceb16134d622e77c8-40824-312-400-jpg was successfully downloaded and inserted into the active cache.
2557-01-15T07:35:34Z [info] Connecting to 95.211.199.132...
2557-01-15T07:35:35Z [info] /image.php?f=bb67690259f04a0461b9b89ab5b89193b89b6d41-132208-550-766-jpg&t=386047-aa827a2defac5de364709212e5e6ee20c56b560b: Retrieving 132208 bytes...
2557-01-15T07:35:36Z [info] The file bb67690259f04a0461b9b89ab5b89193b89b6d41-132208-550-766-jpg was successfully downloaded and inserted into the active cache.
2557-01-15T07:35:36Z [info] Connecting to 95.211.209.54...
2557-01-15T07:35:36Z [info] /image.php?f=c7439f4113d2e03daf12521a539543fe227abbc5-181851-1000-1450-jpg&t=386047-f9d7e6675bbf55b85e2a82b8f90c97ad13d78bfa: Retrieving 181851 bytes...
2557-01-15T07:35:38Z [info] The file c7439f4113d2e03daf12521a539543fe227abbc5-181851-1000-1450-jpg was successfully downloaded and inserted into the active cache.
2557-01-15T07:35:38Z [info] Connecting to 95.211.199.130...
2557-01-15T07:35:38Z [info] /image.php?f=5cc8ba54c163449a9decf157017463e3854ab5b7-82753-640-480-jpg&t=386047-2b58577fb7415a605259b9238d13b4635c5311b4: Retrieving 82753 bytes...
2557-01-15T07:35:40Z [info] The file 5cc8ba54c163449a9decf157017463e3854ab5b7-82753-640-480-jpg was successfully downloaded and inserted into the active cache.
2557-01-15T07:35:40Z [info] Connecting to 95.211.199.137...
2557-01-15T07:35:40Z [info] /image.php?f=52b019b8786cef24c19fc938cb108fd21cab3019-70733-1024-680-jpg&t=386047-17b8dc4afba1e9e62dafe553335f285c7948403d: Retrieving 70733 bytes...
2557-01-15T07:35:42Z [info] The file 52b019b8786cef24c19fc938cb108fd21cab3019-70733-1024-680-jpg was successfully downloaded and inserted into the active cache.
2557-01-15T07:35:42Z [info] Connecting to 95.211.209.54...
2557-01-15T07:35:43Z [info] /image.php?f=efef22060c5e8c24c55a7e4fce54730e2bc72c88-75958-788-588-jpg&t=386047-627a53dc5e1795dfbdcd496b499fec60e9f7ae72: Retrieving 75958 bytes...
2557-01-15T07:35:44Z [info] The file efef22060c5e8c24c55a7e4fce54730e2bc72c88-75958-788-588-jpg was successfully downloaded and inserted into the active cache.
2557-01-15T07:35:44Z [info] Connecting to 95.211.199.130...

I not download any file yet.
WHy i connect to 95.211.199.what ever

WHy i connect to 95.211.199.what ever

Those are the E-Hentai images servers, from which your H@H client downloads images when it can't do it through another H@H client (or when it downloads an image from its static ranges).

I not download any file yet.

Your logs extract shows the opposite.

If your problem concerns the H@H downloader, make sure you follow the steps from the wiki. Also, take a look at the common H@H errors. If it doesn't solve your problem, detail it more accurately, because "I not download any file yet." is pretty vague ...

I not download any file yet.
WHy i connect to 95.211.199.what ever

That's your client connecting to nodes/servers to download files for your cache. You can increase your cache by downloading through the H@H image proxy, but what you posted is the way your client gets files by default.

OK I see
I don't know 95.211.199. IS image server

I don't know if it is done by some detection, but the speedsetting seems to have a mind of its own.
I have set the speed to 320 Kb and that shows in the settings yet the H@H overview says the max speed is 256 Kb and will not go higher no matter what I set it to.

The speed the site will utilize will never be more than 80% of the tested speed or set maximum burst speed, whichever is lower. 320 KB/s * 80% = 256 KB/s

Is it somehow possible to have traffic statistics? I mean I can see the byte size in my logs (Code=200 Bytes=527061), but it'd be nice to introduce some statistics coming from that info like total Giga/Megabytes transferred in January and such. Did you ever think about having such info? Would love to see this next to "Files Served".

Could imagine it like this:

Transferred (Dec/Jan)
1,2TiB / 400MiB

Any chance we can have this? (IMG:[invalid] style_emoticons/default/smile.gif)

Does anybody else notice increased disk usage? Sometimes H@H is using 100% disk I/O on the lower end servers.

On the older clients, disk I/O was never a problem.

It doesn't use more I/O, but depending on your setup, you could get more traffic than before. Of course, if you run it on a VM, everything depends on the total I/O on the host node. If that's overloaded, you'll get 100% I/O no matter what.

On Linux, you can symlink the data directory to /dev/shm to save some I/O, but if you forget to copy it to non-volatile storage before restarting or the system crashes, you have to re-enter your client key and wait for the database to rebuild.

Did the need for clients that have speed of 1Mb/s (upload) is inexistent now? My client is just on a 1Mb/s network and since a cople of days it receives a lot less requests, it also generates 0 hath. I don't really care about the hath (or GP), I have all perks I need. Yet, I suspect that's an incentive to stop the slow clients.

Therefore, is it sensible to say that h@h clients on 1Mb/s networks require more h@h server resources than they save? If that's true I'll probably just stop my H@H.

(PS: I tried restarting client, machine network and search logs; There's absolutelly nothing worng with H@H itself.)

thanks for the info

Did the need for clients that have speed of 1Mb/s (upload) is inexistent now? My client is just on a 1Mb/s network and since a cople of days it receives a lot less requests, it also generates 0 hath. I don't really care about the hath (or GP), I have all perks I need. Yet, I suspect that's an incentive to stop the slow clients.

Clients that get below 40 KB/s receive no hath. The absolute minimum limit was always 50 KB/s.

Fuck, I was suspecting my ISP started throttling my upload 6~7 months ago. Now I need to do some work and empirically check if it's true. Thank btw

Maybe it is time to update my client.

I have 2 problems with my clients

1) Since I updated to H@H 1.2 my clients max speed reach to 5-10 MB/s but with the previous it was reaching the max speed 28MB/s (80%*35MB/s). Maybe it is a problem with my clouds (hope not) or maybe i didnt do the update right (i only replaced the 3 files given in the update).

2) One of my clients has max disk cashe 75GB but it only uses 25GB for a long time now (I changed at some point OS and lost 10GB of cashe that had at that time ,I think another time too and after that when it reached 25GB cashe it stopped there)