SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-06-11 18:02:48 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Journallog shows read/write error #196

New Issue
Closed
opened 2025-11-20 05:07:45 -05:00 by saavagebueno · 8 comments
saavagebueno commented 2025-11-20 05:07:45 -05:00
Owner
Copy Link

Originally created by @CommanderRedYT on GitHub (Oct 3, 2022).

journalctl -u netbird.service:

Oct 03 07:45:47 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:47 could not write packet: io: read/write on closed pipe
Oct 03 07:45:49 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:49 could not write packet: io: read/write on closed pipe
Oct 03 07:45:49 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:49 could not write packet: io: read/write on closed pipe
Oct 03 07:45:49 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:49 could not write packet: io: read/write on closed pipe
Oct 03 07:45:50 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:50 could not write packet: io: read/write on closed pipe
Oct 03 07:45:50 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:50 could not write packet: io: read/write on closed pipe
Oct 03 07:45:50 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:50 could not write packet: io: read/write on closed pipe
Oct 03 07:45:50 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:50 could not write packet: io: read/write on closed pipe
Oct 03 07:45:51 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:51 could not write packet: io: read/write on closed pipe
Oct 03 07:45:51 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:51 could not write packet: io: read/write on closed pipe
Oct 03 07:45:53 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:53 could not write packet: io: read/write on closed pipe
Oct 03 07:45:53 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:53 could not write packet: io: read/write on closed pipe
Oct 03 07:46:20 octopi netbird[605]: ice ERROR: 2022/10/03 07:46:20 could not write packet: io: read/write on closed pipe
Oct 03 07:46:20 octopi netbird[605]: ice ERROR: 2022/10/03 07:46:20 could not write packet: io: read/write on closed pipe
Oct 03 07:46:20 octopi netbird[605]: ice ERROR: 2022/10/03 07:46:20 could not write packet: io: read/write on closed pipe
Oct 03 07:46:20 octopi netbird[605]: ice ERROR: 2022/10/03 07:46:20 could not write packet: io: read/write on closed pipe
Oct 03 07:46:20 octopi netbird[605]: ice ERROR: 2022/10/03 07:46:20 could not write packet: io: read/write on closed pipe
Oct 03 07:46:20 octopi netbird[605]: ice ERROR: 2022/10/03 07:46:20 could not write packet: io: read/write on closed pipe

This is a fresh setup of netbird on a raspberry pi 4b. netbird status works and shows the IPs, but pinging the device or from the device to other netbird clients is not working. I already tried apt-purging it, deleting the config files and reinstalling, but that did not help.

Other clients have this output when pinging the raspberry:

From laptop (100.xx.xx.xx) icmp_seq=1 Destination Host Unreachable
ping: sendmsg: Required key not available
Originally created by @CommanderRedYT on GitHub (Oct 3, 2022). `journalctl -u netbird.service`: ``` Oct 03 07:45:47 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:47 could not write packet: io: read/write on closed pipe Oct 03 07:45:49 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:49 could not write packet: io: read/write on closed pipe Oct 03 07:45:49 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:49 could not write packet: io: read/write on closed pipe Oct 03 07:45:49 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:49 could not write packet: io: read/write on closed pipe Oct 03 07:45:50 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:50 could not write packet: io: read/write on closed pipe Oct 03 07:45:50 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:50 could not write packet: io: read/write on closed pipe Oct 03 07:45:50 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:50 could not write packet: io: read/write on closed pipe Oct 03 07:45:50 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:50 could not write packet: io: read/write on closed pipe Oct 03 07:45:51 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:51 could not write packet: io: read/write on closed pipe Oct 03 07:45:51 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:51 could not write packet: io: read/write on closed pipe Oct 03 07:45:53 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:53 could not write packet: io: read/write on closed pipe Oct 03 07:45:53 octopi netbird[605]: ice ERROR: 2022/10/03 07:45:53 could not write packet: io: read/write on closed pipe Oct 03 07:46:20 octopi netbird[605]: ice ERROR: 2022/10/03 07:46:20 could not write packet: io: read/write on closed pipe Oct 03 07:46:20 octopi netbird[605]: ice ERROR: 2022/10/03 07:46:20 could not write packet: io: read/write on closed pipe Oct 03 07:46:20 octopi netbird[605]: ice ERROR: 2022/10/03 07:46:20 could not write packet: io: read/write on closed pipe Oct 03 07:46:20 octopi netbird[605]: ice ERROR: 2022/10/03 07:46:20 could not write packet: io: read/write on closed pipe Oct 03 07:46:20 octopi netbird[605]: ice ERROR: 2022/10/03 07:46:20 could not write packet: io: read/write on closed pipe Oct 03 07:46:20 octopi netbird[605]: ice ERROR: 2022/10/03 07:46:20 could not write packet: io: read/write on closed pipe ``` This is a fresh setup of netbird on a raspberry pi 4b. `netbird status` works and shows the IPs, but pinging the device or from the device to other netbird clients is not working. I already tried apt-purging it, deleting the config files and reinstalling, but that did not help. Other clients have this output when pinging the raspberry: ``` From laptop (100.xx.xx.xx) icmp_seq=1 Destination Host Unreachable ping: sendmsg: Required key not available ```
saavagebueno commented 2025-11-20 05:07:46 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Oct 3, 2022):

Hello @CommanderRedYT, sorry to hear that you are facing connectivity issues. In order for us to better understand the problem, could you please share the following information:

  • Are you using the cloud version or self-hosted?
  • when you run netbird status -d, do you see the status as connected between the two peers you are trying to connect?

Regarding the could not write packet this is a temporal error and the ice client should recover in max 1 minute, if the log persists after 1 minute, can you share a bit firewall configurations, blocking UDP and if you have other VPN clients installed that might be redirecting traffic?

@mlsmaycon commented on GitHub (Oct 3, 2022): Hello @CommanderRedYT, sorry to hear that you are facing connectivity issues. In order for us to better understand the problem, could you please share the following information: - Are you using the cloud version or self-hosted? - when you run `netbird status -d`, do you see the status as connected between the two peers you are trying to connect? Regarding the `could not write packet` this is a temporal error and the ice client should recover in max 1 minute, if the log persists after 1 minute, can you share a bit firewall configurations, blocking UDP and if you have other VPN clients installed that might be redirecting traffic?
saavagebueno commented 2025-11-20 05:07:46 -05:00
Author
Owner
Copy Link

@CommanderRedYT commented on GitHub (Oct 3, 2022):

Are you using the cloud version or self-hosted?

I am using the one hosted on app.netbird.io.

when you run netbird status -d, do you see the status as connected between the two peers you are trying to connect?

I have in total 4 devices in my network, and I only have connection issues to this pi. Other devices are 2nd pi and a VPS server.

Regarding the could not write packet this is a temporal error and the ice client should recover in max 1 minute, if the log persists after 1 minute, can you share a bit firewall configurations, blocking UDP and if you have other VPN clients installed that might be redirecting traffic?

I'm not entirely sure how to lookup the firewall configs, but this issue persists over every internet connection (home/office/mobile network hotspot,...) and only for this one device. Connecting to other devices works flawless, but I installed it everywhere the same way.

@CommanderRedYT commented on GitHub (Oct 3, 2022): > Are you using the cloud version or self-hosted? I am using the one hosted on app.netbird.io. > when you run `netbird status -d`, do you see the status as connected between the two peers you are trying to connect? I have in total 4 devices in my network, and I only have connection issues to this pi. Other devices are 2nd pi and a VPS server. > Regarding the `could not write packet` this is a temporal error and the ice client should recover in max 1 minute, if the log persists after 1 minute, can you share a bit firewall configurations, blocking UDP and if you have other VPN clients installed that might be redirecting traffic? I'm not entirely sure how to lookup the firewall configs, but this issue persists over every internet connection (home/office/mobile network hotspot,...) and only for this one device. Connecting to other devices works flawless, but I installed it everywhere the same way.
saavagebueno commented 2025-11-20 05:07:46 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Oct 3, 2022):

@CommanderRedYT thanks for the fast response. Can you share some logs from your raspberry pi with the issue? You can follow the steps below for that.

On the pi that you can connect, can you run netbird status -d, in the block with IP from you laptop, you can copy and save its public key, we will use that for checking logs.

Next, can you run the following commands to enable debug log and to get logs from connection attempts to your laptop:

enable debug logs

sudo netbird service stop
sudo netbird service uninstall
sudo netbird service install --log-level debug
sudo netbird service start

grep all logs for laptop connection

sudo grep LAPTOP_PUBLIC_KEY /var/log/netbird/client.log
@mlsmaycon commented on GitHub (Oct 3, 2022): @CommanderRedYT thanks for the fast response. Can you share some logs from your raspberry pi with the issue? You can follow the steps below for that. On the pi that you can connect, can you run `netbird status -d`, in the block with IP from you laptop, you can copy and save its public key, we will use that for checking logs. Next, can you run the following commands to enable debug log and to get logs from connection attempts to your laptop: enable debug logs ```shell sudo netbird service stop sudo netbird service uninstall sudo netbird service install --log-level debug sudo netbird service start ``` grep all logs for laptop connection ```shell sudo grep LAPTOP_PUBLIC_KEY /var/log/netbird/client.log ```
saavagebueno commented 2025-11-20 05:07:46 -05:00
Author
Owner
Copy Link

@CommanderRedYT commented on GitHub (Oct 3, 2022):

time="2022-10-03T10:26:19+02:00" level=error msg="failed signaling candidate to the remote peer <peer_id> rpc error: code = Unknown desc = peer <peer_id> is not registered" file="conn.go:455"

I got this a couple of times in the log, but nothing else other than this message. Weirdly enough, after enabling debug logs, it started to work again. (When I set it up last week, it too worked for ~24hrs and stopped the next day..)

@CommanderRedYT commented on GitHub (Oct 3, 2022): ``` time="2022-10-03T10:26:19+02:00" level=error msg="failed signaling candidate to the remote peer <peer_id> rpc error: code = Unknown desc = peer <peer_id> is not registered" file="conn.go:455" ``` I got this a couple of times in the log, but nothing else other than this message. Weirdly enough, after enabling debug logs, it started to work again. (When I set it up last week, it too worked for ~24hrs and stopped the next day..)
saavagebueno commented 2025-11-20 05:07:46 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Oct 8, 2022):

Hello @CommanderRedYT did you face the issue again after 24 hours?

@mlsmaycon commented on GitHub (Oct 8, 2022): Hello @CommanderRedYT did you face the issue again after 24 hours?
saavagebueno commented 2025-11-20 05:07:46 -05:00
Author
Owner
Copy Link

@CommanderRedYT commented on GitHub (Oct 8, 2022):

Hello @CommanderRedYT did you face the issue again after 24 hours?

No, now everything works as expected

@CommanderRedYT commented on GitHub (Oct 8, 2022): > Hello @CommanderRedYT did you face the issue again after 24 hours? No, now everything works as expected
saavagebueno commented 2025-11-20 05:07:47 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Oct 8, 2022):

Thanks, I will close this issue as it seems to have been a temporary issue and we can reopen if the issue happens again.

@mlsmaycon commented on GitHub (Oct 8, 2022): Thanks, I will close this issue as it seems to have been a temporary issue and we can reopen if the issue happens again.
saavagebueno commented 2025-11-20 05:07:47 -05:00
Author
Owner
Copy Link

@CommanderRedYT commented on GitHub (Oct 12, 2022):

@mlsmaycon So its happening again...
Only this one single raspberry has a problem, but 3 others don't.
The webinterface even says last seen "just now"

@CommanderRedYT commented on GitHub (Oct 12, 2022): @mlsmaycon So its happening again... Only this one single raspberry has a problem, but 3 others don't. The webinterface even says last seen "just now"
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#196
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?