Jump to content

SWN

Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by SWN

  1. 2022-01-17T04:27:26.232Z ERROR contact:service ping satellite failed {"Satellite ID": "xxxx removed for security.....", "attempts": 7, "error": "ping satellite: check-in ratelimit: node rate limited by id", "errorVerbose": "ping satellite: check-in ratelimit: node rate limited by id\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:138\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}

     

    any thoughts on this error?

    Not sure how to start troubleshooting this one.

    thanks.

  2. 1 hour ago, SWN said:

    Here are more log files.  these are the first lines after a boot of docker:

    2022-01-17T03:10:55.851Z INFO Configuration loaded {"Location": "/app/config/config.yaml"}
    2022-01-17T03:10:55.852Z INFO Operator email {"Address": "xxxxxx"}
    2022-01-17T03:10:55.853Z INFO Operator wallet {"Address": "xxxxxxx"}
    2022-01-17T03:10:56.084Z INFO Telemetry enabled {"instance ID": "xxxxxx"}
    2022-01-17T03:10:56.150Z INFO db.migration Database Version {"version": 53}

    2022-01-17T03:10:56.717Z INFO preflight:localtime start checking local system clock with trusted satellites' system clock.
    2022-01-17T03:10:57.240Z INFO preflight:localtime local system clock is in sync with trusted satellites' system clock.
    2022-01-17T03:10:57.240Z INFO bandwidth Performing bandwidth usage rollups
    2022-01-17T03:10:57.240Z INFO trust Scheduling next refresh {"after": "4h58m9.068406927s"}
    2022-01-17T03:10:57.240Z INFO Node xxxxxx started
    2022-01-17T03:10:57.240Z INFO Public server started on [::]:28967
    2022-01-17T03:10:57.240Z INFO Private server started on 127.0.0.1:7778
    2022-01-17T03:10:57.241Z ERROR services unexpected shutdown of a runner {"name": "piecestore:monitor", "error": "piecestore monitor: error verifying location and/or readability of storage directory: open config/storage/storage-dir-verification: no such file or directory", "errorVerbose": "piecestore monitor: error verifying location and/or readability of storage directory: open config/storage/storage-dir-verification: no such file or directory\n\tstorj.io/storj/storagenode/monitor.(*Service).Run.func1.1:133\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/storj/storagenode/monitor.(*Service).Run.func1:130\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}

     

    piecestore monitor: error verifying location and/or readability of storage directory: open config/storage/storage-dir-verification: no such file or directory

     

    Why is it looking for this file or directory called 'storage-dir-verification'?  it doesn't exist in my storage folder.

     

    i mounted the folder for storage, deleted the docker, re installed it.  i am not getting this error anymore.

    used this tutorial to mount the folder.

    https://docs.storj.io/node/resources/faq/linux-static-mount

     

    I am having another problem now.  I will post another thread.

  3. Here are more log files.  these are the first lines after a boot of docker:

    2022-01-17T03:10:55.851Z INFO Configuration loaded {"Location": "/app/config/config.yaml"}
    2022-01-17T03:10:55.852Z INFO Operator email {"Address": "xxxxxx"}
    2022-01-17T03:10:55.853Z INFO Operator wallet {"Address": "xxxxxxx"}
    2022-01-17T03:10:56.084Z INFO Telemetry enabled {"instance ID": "xxxxxx"}
    2022-01-17T03:10:56.150Z INFO db.migration Database Version {"version": 53}

    2022-01-17T03:10:56.717Z INFO preflight:localtime start checking local system clock with trusted satellites' system clock.
    2022-01-17T03:10:57.240Z INFO preflight:localtime local system clock is in sync with trusted satellites' system clock.
    2022-01-17T03:10:57.240Z INFO bandwidth Performing bandwidth usage rollups
    2022-01-17T03:10:57.240Z INFO trust Scheduling next refresh {"after": "4h58m9.068406927s"}
    2022-01-17T03:10:57.240Z INFO Node xxxxxx started
    2022-01-17T03:10:57.240Z INFO Public server started on [::]:28967
    2022-01-17T03:10:57.240Z INFO Private server started on 127.0.0.1:7778
    2022-01-17T03:10:57.241Z ERROR services unexpected shutdown of a runner {"name": "piecestore:monitor", "error": "piecestore monitor: error verifying location and/or readability of storage directory: open config/storage/storage-dir-verification: no such file or directory", "errorVerbose": "piecestore monitor: error verifying location and/or readability of storage directory: open config/storage/storage-dir-verification: no such file or directory\n\tstorj.io/storj/storagenode/monitor.(*Service).Run.func1.1:133\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/storj/storagenode/monitor.(*Service).Run.func1:130\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}

     

    piecestore monitor: error verifying location and/or readability of storage directory: open config/storage/storage-dir-verification: no such file or directory

     

    Why is it looking for this file or directory called 'storage-dir-verification'?  it doesn't exist in my storage folder.

     

  4. 10 hours ago, MrChunky said:

     

    Suggest there is an issue with the storage path. Have a look at your config and setup instructions.

    here are my settings in the docker on Unraid 6.9.2:

    --mount type=bind,source="/mnt/user/appdata/storj/identity/storagenode/",destination=/app/identity  --mount type=bind,source="/mnt/disks/d3pjf/storj/",destination=/app/config

     

    Error:

    Error: piecestore monitor: error verifying location and/or readability of storage directory: open config/storage/storage-dir-verification: no such file or directory

     

    I am pointing the storage device to unassigned disks that are mounted and formatted to XFS.

    I created a folder on the disk (dev 3, sde, d3pjf) called storj per the instructions from Storj CLI tutorial.  Here is my directory listing at storage destination.

    root@CALRISSIAN:/mnt/disks/d3pjf/storj# ls -l
    total 44
    -rw------- 1 root root  9355 Jan 16 00:29 config.yaml
    drwx------ 4 root root    47 Jan 16 09:02 orders/
    -rw------- 1 root root 32768 Jan 16 19:48 revocations.db
    drwx------ 6 root root  4096 Jan 16 19:48 storage/
    -rw------- 1 root root  1374 Jan 16 19:48 trust-cache.json
     

    I can see all the files that Storj created during the install.  I am confused as to why it is not able to point here now that docker is installed.

     

  5. 4 minutes ago, Squid said:

    That's the log window, and since it was opened, you installed an update (or removed and reinstalled) the container and the original reference no longer exists.  Perfectly normal.  Reopen it

    Thanks.  I see the log files now.  the docker has shutdown itself.  here are the log files showing what looks like 2 errors: storage directory and satellite failed.

     

    2022-01-16T16:02:25.460Z INFO Public server started on [::]:28967
    2022-01-16T16:02:25.460Z INFO Private server started on 127.0.0.1:7778


    2022-01-16T16:02:25.460Z ERROR services unexpected shutdown of a runner {"name": "piecestore:monitor", "error": "piecestore monitor: error verifying location and/or readability of storage directory: open config/storage/storage-dir-verification: no such file or directory", "errorVerbose": "piecestore monitor: error verifying location and/or readability of storage directory: open config/storage/storage-dir-verification: no such file or directory\n\tstorj.io/storj/storagenode/monitor.(*Service).Run.func1.1:133\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/storj/storagenode/monitor.(*Service).Run.func1:130\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}


    2022-01-16T16:02:25.461Z ERROR nodestats:cache Get pricing-model/join date failed {"error": "context canceled"}


    2022-01-16T16:02:25.461Z ERROR contact:service ping satellite failed {"Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "attempts": 1, "error": "ping satellite: rpc: dial tcp: operation was canceled", "errorVerbose": "ping satellite: rpc: dial tcp: operation was canceled\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:114\n\tstorj.io/common/rpc.TCPConnector.DialContext:78\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:220\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:110\n\tstorj.io/common/rpc/rpcpool.(*Pool).get:105\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:128\n\tstorj.io/common/rpc.Dialer.dialPool:186\n\tstorj.io/common/rpc.Dialer.DialNodeURL:109\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:124\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}


    2022-01-16T16:02:25.461Z INFO contact:service context cancelled {"Satellite ID": "121RTSxxxx.xxxx.....xxxxx1tuvgk3vzoA6"}
    2022-01-16T16:02:25.461Z ERROR piecestore:cache error during init space usage db: {"error": "piece space used: context canceled", "errorVerbose": "piece space used: context canceled\n\tstorj.io/storj/storagenode/storagenodedb.(*pieceSpaceUsedDB).Init:73\n\tstorj.io/storj/storagenode/pieces.(*CacheService).Run:75\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2.1:87\n\truntime/pprof.Do:40\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2:86\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}

  6. I got the docker setup, and running. but i am getting an error after docker starts.  any suggestions on how to resolve this?

     

    e":"No such container: 0889798417f7"}
    e":"No such container: 0889798417f7"}
    e":"No such container: 0889798417f7"}
    e":"No such container: 0889798417f7"}
    and so on....  it just repeats over and over.

×
×
  • Create New...