notifyrefreshmentsent error

Abierto
  • ¿Algo no está bien?
#5,402 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 3 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
go
Área
backend

Línea de trabajo

Start by following the README in the linked swarm-mobile repository and reproduce with go run main.go, then transfer a large file while collecting Bee logs. The report points to peer disconnections and payment/refresh errors but does not identify a Bee file or test to investigate. Done means explaining and resolving the instability so large uploads or downloads complete without the node crashing or peers dropping unexpectedly.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

on hold
Context

Actively working on to run a Bee node on mobile.
To achieve this, there is a repository which hardly relies on Bee, it is bee-lite. The purpose of this repo is to expose the original Bee API to callable functions instead of using HTTP requests to the locally running Bee node.
In other words, the Android app is implemented in Native Go (using Fyne framework).
swarm-mobile
Achieved running the node in Ultra-light or Light mode.

Tried with the following RPCs it doesn't make any difference:
https://gnosis.publicnode.com
https://xdai.fairdatasociety.org

I have tried with an upgraded node with a funded Chequebook, but that also doesn't make any difference.

Problem

When running 5Mb+ uploads or downloads the log is full of errors like this:
"msg"="notifyrefreshmentsent failed to refresh" "error"="settlement allowance timestamps from peer differed from our measurement by more than 2 seconds"
"msg"="notifyrefreshmentsent failed to refresh" "error"="peer not found"
"msg"="payment failure" "error"="call issue function: connection closed (local): code: 0x0: transport error: sent go away, code: 0"
"msg"="payment failure" "error"="call issue function: stream reset: stream reset: connection closed: EOF"

On some days when the above happens to fast, all the peers get disconnected, and the Bee node crashes during transfer. On other days, the connected peers drop off around 50-60, and the download/upload succeeds.
This is the biggest problem because the node is unstable.

Expected behavior

Node should work normally like on a standard PC.

Actual behavior

Peers are disconnecting, Log is full of errors, and the download/upload sometime works sometime not.

Image [2026-03-17-success-but-nodes-drop-off.log](https://github.com/user-attachments/files/26057304/2026-03-17-success-but-nodes-drop-off.log) [2026-02-27-failure.log](https://github.com/user-attachments/files/26057305/2026-02-27-failure.log) Image
Steps to reproduce

Checkout swarm-mobile follow the Readme to startup the node with the easiest command go run main.go - I'm happy to help anytime with this! - and start a download with a Hash that belongs to a large file

Lenguaje dominante
Go
Estrellas
1.5k
Forks
390
Merge medio
3 d 2 h
PR fusionados (30 d)
17

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ethersphere/bee

Todos los issues de ethersphere/bee

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.