I’m self-hosting on a VPS.
When I try to crawl any websites, Yacy gives:
504 Gateway Time-out
nginx
But it was working before?
Ports not blocked, and it has enough RAM.
this is solved via systemctl restart
but unclear why it happened
Did you examine the log? Usualy the cause can be found there.
I, personally, restart YaCy every day, via restartYACY.sh script called from cron. Some host do have a long long uptime, but not working in my case: after 2-3 days, my instance gets stucked. Everyday restart prevents that.
Are you talking about on a VPS or local home PC?
I want to be part of the freeworld network, but first crawl docs on my own first without being slowed down by so many DHT requests. How do I turn off DHT receive? where others give me docs to store?
I use dedicated hw server. But log is kept on all the instances.
In Administration > First Steps > Use Case & Account > Network Configuration : Uncheck Index Receive - Accept remote Index Transmissions.
Thanks for your reply.
For “Accept remote Index Transmissions.”
It has “Reject” already checked off for Index Receive
But the bulk of my index is from other people. And I see DHTReceive in the feed
How come sometimes my search has Peer-to-Peer and Stealth Mode,
And other times there’s no Stealth Mode button?
java.lang.OutOfMemoryError: Java heap space
UNCAUGHT-EXCEPTION Thread Connection evictor: Java heap space
java.lang.OutOfMemoryError: Java heap space
But it has enough memory, and set min to 100 mib, and max to the max it allows.
Nothing else on the system and 8G total, 6G to this
Oh, yes, that may be your searches in p2p mode. In fact, they are transfered as RWI/DHT. As you search, other hosts send you the results in form of RWI transfer. See manual, work in progress.
Looks like memory issue. Did you see the graph at /Performance_p.html? YaCy is memory hungry. Largely out of inefficiency of code, in my opinion.
1 Like
The same happens to me. Probably bug. You can report it at github issues.