[X] My Assistant

Hi. Why my H@H was die before restart?

2025-02-08T02:40:52Z [WARN] Failed stillAlive test: (KEY_EXPIRED) - will retry later
2025-02-08T02:42:42Z [WARN] Failed stillAlive test: (KEY_EXPIRED) - will retry later
2025-02-08T02:44:32Z [WARN] Failed stillAlive test: (KEY_EXPIRED) - will retry later
2025-02-08T02:46:22Z [WARN] Failed stillAlive test: (KEY_EXPIRED) - will retry later
2025-02-08T02:48:12Z [WARN] Failed stillAlive test: (KEY_EXPIRED) - will retry later
2025-02-08T02:50:02Z [WARN] Failed stillAlive test: (KEY_EXPIRED) - will retry later
2025-02-08T02:51:52Z [WARN] Failed stillAlive test: (KEY_EXPIRED) - will retry later
2025-02-08T02:53:42Z [WARN] Failed stillAlive test: (KEY_EXPIRED) - will retry later
2025-02-08T02:55:32Z [WARN] Failed stillAlive test: (KEY_EXPIRED) - will retry later
2025-02-08T02:57:22Z [WARN] Failed stillAlive test: (KEY_EXPIRED) - will retry later
2025-02-08T02:59:12Z [WARN] Failed stillAlive test: (KEY_EXPIRED) - will retry later
^[[A ^C2025-02-08T02:59:23Z [info] Shutting down...
2025-02-08T02:59:23Z [WARN] Server reported expired key; attempting to refresh time from server and retrying
^C^C^C2025-02-08T02:59:24Z [info] Shutdown in progress - please wait up to 30 seconds
^C2025-02-08T02:59:29Z [info] ServerSocket was closed and will no longer accept new connections.
2025-02-08T02:59:29Z [info] Your business is appreciated
hath@VPS:~$ java -jar HentaiAtHome.jar
2025-02-08T03:00:38Z [info] Hentai@Home 1.6.4 (Build 176) starting up
2025-02-08T03:00:38Z [info] Copyright © 2008-2024, E-Hentai.org - all rights reserved.
2025-02-08T03:00:38Z [info] This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL v3 license.
2025-02-08T03:00:38Z [info] Loaded login settings from client_login
2025-02-08T03:00:38Z [info] Connecting to the Hentai@Home Server to register client with ID *****...
2025-02-08T03:00:39Z [info] Reading Hentai@Home client settings from server...
2025-02-08T03:00:39Z [info] Applying settings...
2025-02-08T03:00:39Z [info] Logging ended.
2025-02-08T03:00:39Z [info] Finished applying settings
2025-02-08T03:00:39Z [info] CacheHandler: Attempting to load persistent cache data...
2025-02-08T03:00:39Z [info] CacheHandler: All persistent fields found, loading remaining objects
2025-02-08T03:00:39Z [info] CacheHandler: Loaded static range ages
2025-02-08T03:00:39Z [info] CacheHandler: Loaded LRU cache
2025-02-08T03:00:39Z [info] CacheHandler: Successfully loaded persistent cache data
2025-02-08T03:00:39Z [info] Requesting certificate from server...
2025-02-08T03:00:40Z [info] Starting up the internal HTTP Server...
2025-02-08T03:00:40Z [info] Internal HTTP Server was successfully started, and is listening on port 8443
2025-02-08T03:00:40Z [info] Notifying the server that we have finished starting up the client...
2025-02-08T03:00:42Z [info] {1/37.48.81.219} Code=200 Bytes=36 GET /servercmd/still_alive//1739031634/a98a66d9bedbc8624b3d2ee694994671785af33d HTTP/1.1
2025-02-08T03:00:42Z [info] {1/37.48.81.219} Code=200 Bytes=36 Finished processing request in 0.00 seconds
2025-02-08T03:00:42Z [info] {2/37.48.81.219} Code=200 Bytes=2500002 GET /servercmd/speed_test/testsize=2500002/1739031635/c60ab8621494319eecde0baed21e3f941474a256 HTTP/1.1
2025-02-08T03:00:42Z [info] {3/37.48.81.219} Code=200 Bytes=2500001 GET /servercmd/speed_test/testsize=2500001/1739031635/ca2e0a293b14c26ea047ac63dd354ff204f8de3d HTTP/1.1
2025-02-08T03:00:43Z [info] {3/37.48.81.219} Code=200 Bytes=2500001 Finished processing request in 0.61 seconds (4105.09 KB/s)
2025-02-08T03:00:43Z [info] {2/37.48.81.219} Code=200 Bytes=2500002 Finished processing request in 0.62 seconds (4006.41 KB/s)
2025-02-08T03:00:44Z [info] {4/37.48.81.219} Code=200 Bytes=5000003 GET /servercmd/speed_test/testsize=5000003/1739031636/838b77b4df63cf5e817d2dbe25d7e28ea446ae50 HTTP/1.1
2025-02-08T03:00:44Z [info] {6/37.48.81.219} Code=200 Bytes=5000001 GET /servercmd/speed_test/testsize=5000001/1739031636/b430b679db1de94bbbbebad4b07289cbfb8cfbdd HTTP/1.1
2025-02-08T03:00:44Z [info] {5/37.48.81.219} Code=200 Bytes=5000002 GET /servercmd/speed_test/testsize=5000002/1739031636/13945570fc0135345a187efbd1334518cd8e2173 HTTP/1.1
2025-02-08T03:00:44Z [info] {4/37.48.81.219} Code=200 Bytes=5000003 Finished processing request in 0.52 seconds (9560.24 KB/s)
2025-02-08T03:00:44Z [info] {6/37.48.81.219} Code=200 Bytes=5000001 Finished processing request in 0.55 seconds (9124.09 KB/s)
2025-02-08T03:00:44Z [info] {5/37.48.81.219} Code=200 Bytes=5000002 Finished processing request in 0.56 seconds (8849.56 KB/s)
2025-02-08T03:00:46Z [info] {8/37.48.81.219} Code=200 Bytes=5000001 GET /servercmd/speed_test/testsize=5000001/1739031638/5c91f4b4378ed0183e2de21a864224bd48b38f28 HTTP/1.1
2025-02-08T03:00:46Z [info] {11/37.48.81.219} Code=200 Bytes=5000002 GET /servercmd/speed_test/testsize=5000002/1739031638/9ef26308d6bb86626d6998c4f803282065626fea HTTP/1.1
2025-02-08T03:00:46Z [info] {7/37.48.81.219} Code=200 Bytes=5000003 GET /servercmd/speed_test/testsize=5000003/1739031638/a3dd606899e5412e720b04fcc9513379df9bd8cd HTTP/1.1
2025-02-08T03:00:46Z [info] {9/37.48.81.219} Code=200 Bytes=5000004 GET /servercmd/speed_test/testsize=5000004/1739031638/b14a7e7b0fcaf7c7e86679cf364c1481f8f139e5 HTTP/1.1
2025-02-08T03:00:46Z [info] {10/37.48.81.219} Code=200 Bytes=5000005 GET /servercmd/speed_test/testsize=5000005/1739031638/f33c0ae1116d2d2445a3e9d83eeb4b53d2a222e0 HTTP/1.1

Hi. Why my H@H was die before restart?

Unless you waited 13 hours before posting that, your computer's clock is off by 13 hours and change, or the time zone is wrong. H@H will compensate to some extent, but you could run into issues if it changes abruptly or drifts a lot.

deleted

This post has been edited by sdgwetgs: Feb 8 2025, 20:41

So fix your clock then? NTP obviously isn't working, it's off by 13 hours.

So fix your clock then? NTP obviously isn't working, it's off by 13 hours.

Yes. I installing ntp on all H@H servers now

Is there a rough guideline for an optimal "storage to data transfer limit" ratio for a H@H node?

Like between a node with large disk space (1-2 TB) but lower data transfer limit (<5 TB), and lower storage (100-200 GB) but lots of data transfer (10-20 TB), would one be more beneficial (or generate more Hath)? Obviously unlimited data transfer is ideal but not always possible.

Is there a rough guideline for an optimal "storage to data transfer limit" ratio for a H@H node?

Like between a node with large disk space (1-2 TB) but lower data transfer limit (<5 TB), and lower storage (100-200 GB) but lots of data transfer (10-20 TB), would one be more beneficial (or generate more Hath)? Obviously unlimited data transfer is ideal but not always possible.

Hard to give a concise answer, since it varies a lot by region and how old the client is. Traffic per range varies by a factor of 100 between the lowest-traffic region and the highest-traffic one. For the low-traffic regions like Oceania and South America, you won't get much traffic unless you have a lot of ranges, which means you need a lot of disk space.

These numbers are a bit higher than the real ones, but I can give some rough numbers for the main regions based on the bandwidth limiter estimates. For Asia, clients average around 8.5 KB/s per assigned P1 range, each of which requires 500 MB of assigned space. Followed by North America with around 2.4 KB/s per P1 range, and Europe with around 1.4 KB/s per P1 range. But there won't generally be enough assignable P1 ranges to make full use of a large cache, so a fast connection with a smaller SSD will probably perform better than a slow connection with a larger HDD.

thanks for the hard work like always