Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Title
w
white-garden-41931
03/14/2023, 12:29 AMI haven't seen this reported before...running k3s 1.25.4+k3s1 on Fedora 36
I get an error:
2023/03/03 00:09:28 Starting NATS Server Reloader v0.7.4
Error: too many open files
Stream closed EOF for testkube/testkube-nats-0 (reloader)c
creamy-pencil-82913
03/14/2023, 12:33 AMI would probably check the ulimit settings on your node. You might need to raise the maximum number of open file descriptors (
ulimit -nThe systemd unit that the k3s installer generates already has a pretty high limit though, so if you’re hitting that, something else might be going on…
https://github.com/k3s-io/k3s/blob/master/install.sh#L792