alanshaw changed the topic of #ipfs to: Heads Up: To talk, you need to register your nick! Announcements: go-ipfs 0.4.22 and js-ipfs 0.40 are out! Get them from dist.ipfs.io and npm respectively! | Also: #libp2p #ipfs-cluster #filecoin #ipfs-dev | IPFS, the InterPlanetary FileSystem: https://github.com/ipfs/ipfs | Logs: https://view.matrix.org/room/!yhqiEdqNjyPbxtUjzm:matrix.org/ | Forums: https://discuss.ipfs.io | Code of
mathemancer has joined #ipfs
MrSparkle has quit []
infinity-elf has joined #ipfs
a18t[m] has joined #ipfs
alozxy[m] has joined #ipfs
RamRanRa has quit [Read error: Connection reset by peer]
gimzmoe has quit [Quit: WeeChat 1.9.1]
appa has joined #ipfs
appa has quit [Client Quit]
appa has joined #ipfs
appa has quit [Client Quit]
elfatherbrown has joined #ipfs
appa has joined #ipfs
appa has quit [Client Quit]
gimzmoe has joined #ipfs
gimzmoe has left #ipfs [#ipfs]
Belkaar_ has quit [Ping timeout: 260 seconds]
Belkaar has joined #ipfs
Belkaar has joined #ipfs
DavidPH has joined #ipfs
elfatherbrown has quit [Ping timeout: 246 seconds]
user_51 has quit [Ping timeout: 268 seconds]
user_51 has joined #ipfs
hurikhan77 has joined #ipfs
kakra has quit [Ping timeout: 265 seconds]
KempfCreative has joined #ipfs
elfatherbrown has joined #ipfs
verin0x3 has joined #ipfs
KempfCreative1 has joined #ipfs
KempfCreative has quit [Ping timeout: 260 seconds]
KempfCreative1 is now known as KempfCreative
verin0x has quit [Ping timeout: 260 seconds]
verin0x3 is now known as verin0x
elfatherbrown has quit [Ping timeout: 252 seconds]
ipfs-stackbot2 has quit [Remote host closed the connection]
q-u-a-n2 has quit [Ping timeout: 268 seconds]
ipfs-stackbot1 has joined #ipfs
rardiol has quit [Ping timeout: 260 seconds]
MrSparkle has joined #ipfs
KempfCreative has quit [Ping timeout: 240 seconds]
xcm has quit [Remote host closed the connection]
xcm has joined #ipfs
jamiew has quit [Remote host closed the connection]
jamiew has joined #ipfs
is_null has quit [Ping timeout: 268 seconds]
b12b5 has joined #ipfs
b12b has quit [Ping timeout: 258 seconds]
b12b5 is now known as b12b
hqdruxn08 has joined #ipfs
hqdruxn08_ has quit [Ping timeout: 256 seconds]
hqdruxn08 has quit [Ping timeout: 256 seconds]
hqdruxn08 has joined #ipfs
DavidPH has quit [Ping timeout: 260 seconds]
Jybz has joined #ipfs
xcm has quit [Ping timeout: 258 seconds]
Adbray has quit [Quit: Ah! By Brain!]
aldente has joined #ipfs
aldente has quit [Quit: aldente]
xcm has joined #ipfs
rendar has joined #ipfs
i9zO5AP has joined #ipfs
Ai9zO5AP has quit [Ping timeout: 260 seconds]
<eleitlDiscord[m]>
Using the WebUI seems to cause a crash sooner or later. Probably API-related. No crashes on a node I'm operating by CLI only.
<jonbvDiscord[m]>
i am in ubuntu host and thank you.
<jonbvDiscord[m]>
anyone experienced building from source?
is_null has joined #ipfs
<jonbvDiscord[m]>
i assume it is up to date building from source.
<eleitlDiscord[m]>
No need, unless you want to pick a different branch. I would abstain for time being if you're a first time user.
<jonbvDiscord[m]>
cool
<eleitlDiscord[m]>
Next release (v0.5.0) will be likely landing in January, so you don't have to wait long for the latest and greatest.
<jonbvDiscord[m]>
nice to hear it.
<eleitlDiscord[m]>
I'm seeing up to 60% RAM use on CX11 instances of https://www.hetzner.com/cloud which don't do anything other than being public servers, so it seems the recommendation should be more like 4 GB RAM rather than 2 GB. CPU load is 20%-50%, so adequate with one vCPU.
<eleitlDiscord[m]>
I'll rescale to CX21 in order to test gateways + publishing.
<eleitlDiscord[m]>
I think an embedded footprint node like e.g. Raspberry Pi 4 with 4 GB RAM should do for a domestic LAN IPFS node. Once the API-related crashes are fixed. And the setup for anything other than localhost needs streamlining.
<cyberwolf[m]>
2 cpu and 2GB for ipfs will not be enough?
<eleitlDiscord[m]>
With swap it should work. Notice these are public nodes configured as server, but not doing anything else.
<eleitlDiscord[m]>
If you're publishing files you will need to factor in extra resource use. If you're publishing a lot it might make sense to run an IPFS cluster rather than have all nodes public.
<eleitlDiscord[m]>
Haven't done that yet, so this is from what other people say.
<cyberwolf[m]>
ok, thx
<swedneck>
my ipfs node isn't using more than a gig of ram
<eleitlDiscord[m]>
Is it a public facing node and how much are you publishing? Did you tune the config?
aLeSD_ has quit [Ping timeout: 260 seconds]
<swedneck>
yeah it's public, 5GB of files, and i think i've tuned the config
RamRanRa has joined #ipfs
<eleitlDiscord[m]>
You don't happen to recall what exactly you changed from the defaults?
<JorropoDiscord[m>
eleitl maybe just do `make build`
<JorropoDiscord[m>
mb
teleton has joined #ipfs
teleton has quit [Remote host closed the connection]
<eleitlDiscord[m]>
It works now. Seems my go install has some residual brain damage still.
<eleitlDiscord[m]>
It doesn't seem to grow the peer number so aggressively as stable. This is behind NAT, on home LAN.
soldier has left #ipfs [#ipfs]
zeden has joined #ipfs
soldier has joined #ipfs
<eleitlDiscord[m]>
Seems a bit behind with IPNS name resolution. Might be cause it's too new, and not many peers yet. Also, my second WAN changes IP once in 24 h, so that's not going to improve address location stability.
mowcat has quit [Remote host closed the connection]
rardiol has joined #ipfs
mathemancer has quit [Quit: Lost terminal]
mowcat has joined #ipfs
<eleitlDiscord[m]>
"ERROR pubsub-val: PubsubPeerJoin: error interacting with new peer%!(EXTRA *errors.errorString=protocol not supported) pubsub.go:4" in the logs.
mattgu74[m] has joined #ipfs
<aschmahmann[m]>
@eleitl that error is from IPNS over PubSub. You're using master which includes an updated IPNS over PubSub protocol. However, not all of the nodes using IPNS over PubSub for that topic are running master, so the logs are letting you know that.
soldier has left #ipfs [#ipfs]
maxzor has joined #ipfs
ipfs-stackbot1 has quit [Remote host closed the connection]
mowcat has quit [Remote host closed the connection]
ipfs-stackbot has joined #ipfs
_whitelogger has joined #ipfs
jcea has joined #ipfs
jcea has quit [Excess Flood]
jcea has joined #ipfs
dellie__ has joined #ipfs
delli3_ has quit [Ping timeout: 260 seconds]
maxzor has quit [Remote host closed the connection]
tec__ has quit [Read error: Connection reset by peer]
MrAureliusR has quit [Ping timeout: 268 seconds]
Clarth has joined #ipfs
snk07523 has joined #ipfs
xcm has quit [Remote host closed the connection]
xcm has joined #ipfs
tec__ has joined #ipfs
DavidPH has quit [Quit: Leaving]
elfatherbrown has joined #ipfs
MrAureliusR has joined #ipfs
Clarth has quit [Remote host closed the connection]
jadedctrl has quit [Quit: WeeChat 2.2]
snk07523 has quit [Ping timeout: 268 seconds]
jadedctrl has joined #ipfs
delli3_ has joined #ipfs
snk07523 has joined #ipfs
dellie__ has quit [Ping timeout: 260 seconds]
xcm has quit [Remote host closed the connection]
maxzor has joined #ipfs
xcm has joined #ipfs
<eleitlDiscord[m]>
Thanks!
snk07523 has quit [Ping timeout: 258 seconds]
stoopkid has joined #ipfs
elfatherbrown has quit [Remote host closed the connection]
maxzor has quit [Ping timeout: 265 seconds]
snk07523 has joined #ipfs
jadedctrl has quit [Quit: WeeChat 2.2]
Ai9zO5AP has joined #ipfs
MrSparkle has quit []
jadedctrl has joined #ipfs
rendar has quit []
elfatherbrown has joined #ipfs
elfatherbrown_ has joined #ipfs
<eleitlDiscord[m]>
For a homelab I've scrounged up 3x 2 GB RAM and 2x 4 GB RAM older Atoms, so 5 nodes in total, each with a small SSD and 2 or 3-4 Tb HDD. Dual-port Intel NICs, so I can use a dedicated data network (on a 5-port switch). I'm planning to run the 2 larger Atoms with full IPFS nodes and the 3 small ones as IPFS cluster. Any hints to how set that up? Jumbo frames on the data network, check. Anything else config-wise that make
<eleitlDiscord[m]>
sense? Thanks.
<bonedaddyDiscord>
You shouldn't need jumbo frames unless you have a SAN
<bonedaddyDiscord>
You might be overcomplicating things setting up a data network on a 5 port switch
<bonedaddyDiscord>
The odds of you being able to get your IPFS nodes to communicate solely on that switching fabric is very slim
<bonedaddyDiscord>
You could use that for ipfs cluster but for go-ipfs not worth the trouble
<eleitlDiscord[m]>
Thanks! Roger about ipfs cluster.
<eleitlDiscord[m]>
Btw, I notice I'm getting 59% memory for ipfs-0.5.0-dev on a 16 Gb RAM machine, so there seems to be a giant memory leak.
basilgohar has quit [Quit: leaving]
basilgohar has joined #ipfs
<JorropoDiscord[m>
eleitl wich commit ?
<eleitlDiscord[m]>
As of earlier today. I don't recall.
<eleitlDiscord[m]>
.CurrentCommit=3c95f65b2" ?
<eleitlDiscord[m]>
It's at 3% right now, but with only 49 peers so far.
maxzor has joined #ipfs
jadedctrl has quit [Quit: WeeChat 2.2]
mowcat has joined #ipfs
Royaljello has joined #ipfs
Taoki has quit [Remote host closed the connection]
Taoki has joined #ipfs
b12b3 has joined #ipfs
b12b has quit [Ping timeout: 260 seconds]
b12b3 is now known as b12b
MrSparkle has joined #ipfs
Acacia has joined #ipfs
matthis has joined #ipfs
joocain2 has quit [Ping timeout: 240 seconds]
joocain2 has joined #ipfs
cybercat[m] has joined #ipfs
fiws- has quit [Quit: i quit]
fiws has joined #ipfs
stoopkid has quit [Quit: Connection closed for inactivity]
einyx[m] has joined #ipfs
lnostdal has quit [Remote host closed the connection]
mowcat has quit [Remote host closed the connection]