kosmos/chef
kosmos/chef
8
3
Fork 0
Code Issues 30 Pull Requests 3 Projects 2 Activity

Keep our IPFS nodes connected to each other #44

New Issue
Closed
opened 2019-04-26 09:17:54 +00:00 by greg · 3 comments
greg commented 2019-04-26 09:17:54 +00:00
Owner
Copy Link

dev and andromeda keep disconnecting from each other, both after initial startup (they're in the list of bootstrap nodes for each other) and after manual connect

dev and andromeda keep disconnecting from each other, both after initial startup (they're in the list of bootstrap nodes for each other) and after manual connect
greg self-assigned this 2019-04-26 09:17:58 +00:00
greg changed title from Keep our IPFS connected to each other to Keep our IPFS nodes connected to each other 2019-04-26 09:18:56 +00:00
greg commented 2019-04-26 10:27:31 +00:00
Author
Owner
Copy Link

After seeing an error in the ipfs-cluster logs on dev (IPFS unsuccessful: 500: open /home/ipfs/.ipfs/datastore: too many open files), I have raised the maximum number of open files (manually for now) by adding ``LimitNOFILE=64000` to the systemd unit for dev and andromeda, this appears to have fixed the issue. dev and andromeda have been in each other's swarm peers for almost an hour now

After seeing an error in the ipfs-cluster logs on dev (`IPFS unsuccessful: 500: open /home/ipfs/.ipfs/datastore: too many open files`), I have raised the maximum number of open files (manually for now) by adding ``LimitNOFILE=64000` to the systemd unit for dev and andromeda, this appears to have fixed the issue. dev and andromeda have been in each other's swarm peers for almost an hour now
raucao commented 2019-04-26 10:55:53 +00:00
Owner
Copy Link

Hooray! Good catch.

Hooray! Good catch.
raucao commented 2019-04-26 14:40:35 +00:00
Owner
Copy Link

Confirmed to be solved by checking a new contribution on kredits-web just now.

Confirmed to be solved by checking a new contribution on kredits-web just now.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
service
accounts
Kosmos Accounts
service
discourse
Kosmos Community Forums
service
drone-ci
Kosmos Drone CI
service
email
mail.kosmos.org
service
garage
S3-compatible object storage
service
gitea
Kosmos Gitea
service
ipfs
Kosmos IPFS
service
mastodon
kosmos.social
service
postgres
Database cluster
service
remotestorage
Portable data storage for the Web
service
wiki
Kosmos Wiki
service
xmpp
Kosmos Chat
bug
Something is not working
design
Graphic/visual design
dev environment
Config, builds, CI, deployment, etc.
docs
Documentation
duplicate
This issue or pull request already exists
enhancement
Improving existing functionality
feature
New functionality
good first issue
Dive in, and start contributing
idea
Something to consider
invalid
Not a bug
kredits-1
Small contribution
kredits-2
Medium contribution
kredits-3
Large contribution
on hold
Currently not actionable
ops
Manual IT ops activities
question
Looking for an answer
release
major
release
minor
release
patch
security
All your base are belong to us
ui/ux
User interface, process design, etc.
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
bkero bumi fsmanuel galfert greg hueso raucao slvrbckt
No Assignees greg
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kosmos/chef#44
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?