Textile Client healthcheck... Not initialized yet.
rngadam opened this issue · 3 comments
rngadam commented
Space Daemon v0.0.23 on Mac OS X 10.15.6
What configuration do I need to get rid of the Textile Client healthcheck warning?
INFO[0028] gRPC-web proxy server started on Port 9998
INFO[0028] gRPC server started on Port 9999
INFO[0028] Daemon ready
[...]
DEBU[0589] Textile Client healthcheck... Start.
DEBU[0589] Textile Client healthcheck... Not initialized yet.
DEBU[0592] Textile Client healthcheck... Start.
DEBU[0592] Textile Client healthcheck... Not initialized yet.
dmerrill6 commented
Hi @rngadam, this probably means you haven't generated a public/private key pair (a key pair is needed to initialize the Textile Client). You can do that by calling the GenerateKeyPair gRPC endpoint.
Let me know if that works.
FredyVia commented
space daemon 0.1.3 on Ubuntu 20.04
I just download the binary file from the release page and run it, the problem arised.
sorry to bother you! I have the same problem, where shoud I call GenerateKeyPair gRPC, I'm not very familiar with grpc.
here is the full debug info:
./space_Linux_x86_64
DEBU[0000] Running mode DevMode=false
DEBU[0000] Running daemon with profiler. Visit http://localhost:6060/debug/pprof
2021/04/10 11:58:42 Error loading .env file. Using defaults
DEBU[0000] Got Rlimit: Cur: 1024, Max: 1048576
DEBU[0000] Set Rlimit: Cur: 10240, Max: 1048576
INFO[0000] using path /home/fredyvia/.fleek-space for store
badger 2021/04/10 11:58:42 INFO: All 1 tables opened in 0s
badger 2021/04/10 11:58:42 INFO: Replaying file id: 0 at offset: 933
badger 2021/04/10 11:58:42 INFO: Replay took: 15.156µs
badger 2021/04/10 11:58:42 DEBUG: Value log discard stats empty
DEBU[0000] Starting Component name=Store
DEBU[0000] Starting Component name=FolderWatcher
DEBU[0000] Starting Async Component name=IpfsNode
INFO[0000] Starting the ipfs node
INFO[0000] Running the ipfs node
DEBU[0000] Starting Async Component name=BucketDaemon
API server listening on /ip4/127.0.0.1/tcp/5123
DEBU[0000] No Buckd Path provided. Using default. path=/home/fredyvia/.buckd
INFO[0000] using path /home/fredyvia/.buckd/collections for store
badger 2021/04/10 11:58:43 INFO: All 0 tables opened in 0s
badger 2021/04/10 11:58:43 INFO: Replaying file id: 0 at offset: 0
badger 2021/04/10 11:58:43 INFO: Replay took: 8.241µs
badger 2021/04/10 11:58:43 DEBUG: Value log discard stats empty
INFO[0006] Welcome to bucket peerID=12D3KooWS3GJtYKPKzug8stp52vPaUXp5Sy1VyAui98MHMqWd3Ax
INFO[0006] Sleeping for 5s to wait for buckd grpc ports to listen ...
DEBU[0011] Starting Component name=FilesSearchEngine
DEBU[0011] Starting Async Component name=TextileClient
DEBU[0011] Creating buckets client in 127.0.0.1:3006
DEBU[0011] Creating threads client in 127.0.0.1:3006
DEBU[0011] Textile Client healthcheck... Start.
DEBU[0011] Textile sync [buckets]: Sync start
DEBU[0011] Textile sync [buckets]: Total: 0, Queued: 0, Pending: 0, Failed: 0
DEBU[0011] Textile sync [buckets]: Sync end
DEBU[0011] Textile sync [file pinning]: Sync start
DEBU[0011] Textile sync [file pinning]: Total: 0, Queued: 0, Pending: 0, Failed: 0
DEBU[0011] Textile sync [file pinning]: Sync end
DEBU[0011] Textile Client healthcheck... Not initialized yet.
DEBU[0011] No persisted mountFuseDrive state found
DEBU[0011] Starting Component name=FuseController
DEBU[0011] Starting Async Component name=gRPCServer
INFO[0011] listening on address [::]:9999
INFO[0011] REST server is starting port=9997
INFO[0011] gRPC-web proxy server started on Port 9998
INFO[0011] gRPC server started on Port 9999
DEBU[0011] Starting Async Component name=BucketSync
DEBU[0011] start watching open files ...
DEBU[0011] Starting watcher in bucketsync
INFO[0011] Daemon ready
DEBU[0011] Starting watcher filePath="[]"
DEBU[0014] Textile Client healthcheck... Start.
DEBU[0014] Textile Client healthcheck... Not initialized yet.
...repeat...
DEBU[0038] Textile Client healthcheck... Start.
DEBU[0038] Textile Client healthcheck... Not initialized yet.
DEBU[0041] Textile sync [buckets]: Sync start
DEBU[0041] Textile sync [buckets]: Total: 0, Queued: 0, Pending: 0, Failed: 0
DEBU[0041] Textile sync [buckets]: Sync end
DEBU[0041] Textile sync [file pinning]: Sync start
DEBU[0041] Textile sync [file pinning]: Total: 0, Queued: 0, Pending: 0, Failed: 0
DEBU[0041] Textile sync [file pinning]: Sync end
DEBU[0041] Textile Client healthcheck... Start.
DEBU[0041] Textile Client healthcheck... Not initialized yet.
DEBU[0044] Textile Client healthcheck... Start.
DEBU[0044] Textile Client healthcheck... Not initialized yet.
DEBU[0047] Textile Client healthcheck... Start.
DEBU[0047] Incoming REST Proxy Request method=GET path=/
DEBU[0047] Textile Client healthcheck... Not initialized yet.
DEBU[0047] Incoming REST Proxy Request method=GET path=/favicon.ico
DEBU[0050] Textile Client healthcheck... Start.
DEBU[0050] Textile Client healthcheck... Not initialized yet.
DEBU[0053] Textile Client healthcheck... Start.
DEBU[0053] Textile Client healthcheck... Not initialized yet.
DEBU[0056] Textile Client healthcheck... Start.
DEBU[0056] Textile Client healthcheck... Not initialized yet.
^CINFO[0058] Daemon shutdown started
DEBU[0058] Shutting down Component name=BucketSync
DEBU[0058] shutting down folder watcher in bucketsync
DEBU[0059] shutting down textile thread listener in bucketsync
DEBU[0059] Shutting down Component name=gRPCServer
DEBU[0059] Watcher graceful shutdown triggered
DEBU[0059] Textile Client healthcheck... Start.
DEBU[0059] Textile Client healthcheck... Not initialized yet.
...repeat...
DEBU[0068] Textile Client healthcheck... Start.
DEBU[0068] Textile Client healthcheck... Not initialized yet.
DEBU[0071] Textile sync [file pinning]: Sync start
DEBU[0071] Textile sync [file pinning]: Total: 0, Queued: 0, Pending: 0, Failed: 0
DEBU[0071] Textile sync [file pinning]: Sync end
DEBU[0071] Textile sync [buckets]: Sync start
DEBU[0071] Textile sync [buckets]: Total: 0, Queued: 0, Pending: 0, Failed: 0
......
klaatucarpenter commented
Hi guys,
I have the same issue. I am trying to call GenerateKeyPair gRPC endpoint but I receive response:
{
"code": 2,
"message": "Http response at 400 or 500 level",
"metadata": {}
}