search

ZeroNetX / ZeroNet

ZeroNetX - Decentralized websites using Bitcoin crypto and BitTorrent network
https://zeronet.dev
Other
215 stars 32 forks source link

ERROR Site:* Save peer error: NOT NULL constraint failed: peer.time_response #109

Closed slrslr closed 2 years ago

slrslr commented 2 years ago

Step 1: Please describe your environment

Step 2: Describe the problem:

Steps to reproduce:

Hello, do You also see these errors? ERROR Site:1TaLkF..jipT Save peer error: NOT NULL constraint failed: peer.time_response

It seems to be triggered by some regular job when sites are checked or something. Show one entry per the zeronet site many entries per second. Causes tens of thousands lines in 48 hours of runtime when having hundreds of sites. Seen also in current ZeronetX enhanced branch.

slrslr commented 2 years ago

I no longer see these errors (in enhanced branch). I will inform if it re-appear.

slrslr commented 2 years ago

I am again seeing this issue. 30K ERROR lines for like 48 hours runtime zeronex and also in zeronetx zeronet-enhanced branch. Regarding ZNE, it is reported by "git status", but "git submodule status" no output

$ git pull -v
POST git-upload-pack (155 bytes)
From https://github.com/ZeroNetX/ZeroNet
 = [up to date]        zeronet-enhanced -> origin/zeronet-enhanced
 = [up to date]        canewsin-patch-1 -> origin/canewsin-patch-1
 = [up to date]        master           -> origin/master
 = [up to date]        py3              -> origin/py3
 = [up to date]        py3-internal     -> origin/py3-internal
 = [up to date]        py3-latest       -> origin/py3-latest
 = [up to date]        py3-patches      -> origin/py3-patches

So i am re-opening... Should i try something particular?

slrslr commented 2 years ago

180 000 of these warnings in just 4 days Before this bug is fixed, i have this in zeronet.conf

log_level = off
console_log_level = INFO
canewsin commented 2 years ago

didn't see this error till now on network. is this still happening ?

slrslr commented 2 years ago

Seems to no longer happen after like 16 hours of runtime. I will re-open in case it will happen again. Thanks.