Long search string queries from specific IP address - RAM exhausted

This has been going on for months. Example query from today’s log:

I 2026/05/14 15:49:12 SolrSelect * client=167.235.1.187 q=(“kalshi” AND “incentive” AND “program” AND “liquidity” AND “volume” AND “reward” AND “payout” AND “2026” AND “active”)

The search:

kalshi incentive program liquidity volume reward payout 2026 active

Nine keywords…. that is too many for my server to handle, especially with similar searches being repeated, and this could be why the RAM on my server is reported to be exhausted.

The IP address 167.235.1.187 in a browser, reports as: searchlab2.

Add the port number: 167.235.1.187:8090 and we see agent-refamep-ufe-0.

I do not know why this peer sends long search queries over many months, if it is an especially inquisitive human or an automated script, but I have decided to block it again.

sudo iptables -I INPUT 1 -s 167.235.1.187 -j DROP

If you are the peer administrator, I ask you to look into why your machine sends out, what looks like to me, automated long search queries.

And for others, if you see your server being taxed too much, you might want to also block this IP address.

That one Yacy peer was busy in just the past day…. so many searches and in multiple languages.

kalshi incentive program liquidity volume reward payout 2026 active
dj
https www biglobalization.ca
sydney property market
webview2 runtime
joseph jagger monte carlo roulette 1881 bias
difference between rest and graphql apis
docker compose tutorial for beginners
宁德分类信息网
股权 对赌协议 回购
best practices for kubernetes cluster management
health check
巨人网络 竞争优势 核心壁垒 护城河
kalshi market maker rebate payment order flow cftc regulated prediction 2026
test
陈妍希
do need an antivirus
background music for relaxation and focus while working
how to install and configure nginx on linux server
公司担保 越权 代表 案例 判决
bank account opening bonus churn detection patterns 2025 multiple accounts same household
伊朗 美国 和平协议 战争 最新进展 2026年5月
并购重组 法律 监管
股权转让 纠纷 判决书 案例 判决
三个刚成年的精神小妹 不好好学习在家也玩起了自拍
2018整理最新微信微拍20部极品女神精华合集 超多美女各种自拍总有一部是你喜欢的
eja.it
prepperintel
void linux
screenshot of modern user interface design examples
convergence trading merger arbitrage statistical 1990s 2000s hedge fund
mexc maker fee spot trading 2025 2026 verified
股权转让 纠纷 判决书 案例 判决
keep3r network v4 migration 2024 new contract features
wikipedia pageview trading strategy near miss alternative data signal failed
insider trading desk wall street documented 2000s legal edge
uk iva proof of debt creditor claim transfer assignment secondary market platform
操纵市场 处罚 案例 判决
九江银行 资金存管 现货交易 第三方存管
景德镇陶瓷 版权登记 2023 1.42万件作品
best minimalist logo design inspiration 2024
explain the fundamentals of quantum computing for beginners
смотреть онлайн порно milf cheating
matchbook zero commission free betting exchange comparison betfair smarkets
polymarket lp reward program market maker 2025 2026
how to debug and troubleshoot docker container issues
上市公司 担保 纠纷 最高法 判决 案例
royalty free ambient music for video editing
background music for relaxation and focus while working
pumpswap fee structure 2025 2026 dex trading costs
zig generate headers
nextcloud include google calendar
japan fsa asset management center policy 2025 foreign fund
risk appetite index
google traduction
重庆宗申航空发动机制造股份有限公司处罚
上市公司信息披露合规
disа bled symbol
posix for nt

It does not look like what one human would search for in a single day, right? It appears to be automated. Or is it multiple people using the same Yacy peer for search?

The shell command used to find the query activity of a single IP address, which you could also try:

grep -E ‘167.235.1.187’ ~/yacy/DATA/LOG/yacy*.log