"failed to hydrateHasOne" search errors

[MidnightKittenCat]

Getting 500 errors on torznab searches when paginating to higher offsets:

ERROR	gin	ginzap/ginzap.go:89	failed to search: failed to hydrateHasOne	{"status": 500, "method": "GET", "path": "/torznab/api", "query": "t=search&q=Bait&offset=2000&limit=100", "ip": "49.43.5.183", "user-agent": "Python/3.11 aiohttp/3.13.2", "latency": "57.578022ms", "time": "2025-11-28T03:49:44Z"}
github.com/bitmagnet-io/bitmagnet/internal/boilerplate/httpserver.New.func1.Ginzap.GinzapWithConfig.2
	/src/internal/boilerplate/httpserver/ginzap/ginzap.go:89
github.com/gin-gonic/gin.(*Context).Next
	/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185
github.com/gin-gonic/gin.(*Engine).handleHTTPRequest
	/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:633
github.com/gin-gonic/gin.(*Engine).ServeHTTP
	/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:589
net/http.serverHandler.ServeHTTP
	/usr/local/go/src/net/http/server.go:3210
net/http.(*conn).serve
	/usr/local/go/src/net/http/server.go:2092
ERROR	gin	ginzap/ginzap.go:89	failed to search: failed to hydrateHasOne	{"status": 500, "method": "GET", "path": "/torznab/api", "query": "t=search&q=The+Studio&offset=700&limit=100", "ip": "184.183.11.115", "user-agent": "Python/3.11 aiohttp/3.13.2", "latency": "1.183250299s", "time": "2025-11-28T03:50:10Z"}
github.com/bitmagnet-io/bitmagnet/internal/boilerplate/httpserver.New.func1.Ginzap.GinzapWithConfig.2
	/src/internal/boilerplate/httpserver/ginzap/ginzap.go:89
github.com/gin-gonic/gin.(*Context).Next
	/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185
github.com/gin-gonic/gin.(*Engine).handleHTTPRequest
	/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:633
github.com/gin-gonic/gin.(*Engine).ServeHTTP
	/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:589
net/http.serverHandler.ServeHTTP
	/usr/local/go/src/net/http/server.go:3210
net/http.(*conn).serve
	/usr/local/go/src/net/http/server.go:2092
ERROR	gin	ginzap/ginzap.go:89	failed to search: failed to hydrateHasOne	{"status": 500, "method": "GET", "path": "/torznab/api", "query": "t=search&q=Bottle+Rocket&offset=0&limit=100", "ip": "49.43.5.183", "user-agent": "Python/3.11 aiohttp/3.13.2", "latency": "31.491284ms", "time": "2025-11-28T03:52:01Z"}
github.com/bitmagnet-io/bitmagnet/internal/boilerplate/httpserver.New.func1.Ginzap.GinzapWithConfig.2
	/src/internal/boilerplate/httpserver/ginzap/ginzap.go:89
github.com/gin-gonic/gin.(*Context).Next
	/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185
github.com/gin-gonic/gin.(*Engine).handleHTTPRequest
	/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:633
github.com/gin-gonic/gin.(*Engine).ServeHTTP
	/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:589
net/http.serverHandler.ServeHTTP
	/usr/local/go/src/net/http/server.go:3210
net/http.(*conn).serve
	/usr/local/go/src/net/http/server.go:2092
ERROR	gin	ginzap/ginzap.go:89	failed to search: failed to hydrateHasOne	{"status": 500, "method": "GET", "path": "/torznab/api", "query": "t=search&q=Bottle+Rocket&offset=100&limit=100", "ip": "49.43.5.183", "user-agent": "Python/3.11 aiohttp/3.13.2", "latency": "59.61565ms", "time": "2025-11-28T03:52:01Z"}
github.com/bitmagnet-io/bitmagnet/internal/boilerplate/httpserver.New.func1.Ginzap.GinzapWithConfig.2
	/src/internal/boilerplate/httpserver/ginzap/ginzap.go:89
github.com/gin-gonic/gin.(*Context).Next
	/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185
github.com/gin-gonic/gin.(*Engine).handleHTTPRequest
	/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:633
github.com/gin-gonic/gin.(*Engine).ServeHTTP
	/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:589
net/http.serverHandler.ServeHTTP
	/usr/local/go/src/net/http/server.go:3210
net/http.(*conn).serve
	/usr/local/go/src/net/http/server.go:2092
ERROR	gin	ginzap/ginzap.go:89	failed to search: failed to hydrateHasOne	{"status": 500, "method": "GET", "path": "/torznab/api", "query": "t=search&q=The+Studio&offset=700&limit=100", "ip": "184.183.11.115", "user-agent": "Python/3.11 aiohttp/3.13.2", "latency": "840.962398ms", "time": "2025-11-28T03:52:15Z"}
github.com/bitmagnet-io/bitmagnet/internal/boilerplate/httpserver.New.func1.Ginzap.GinzapWithConfig.2
	/src/internal/boilerplate/httpserver/ginzap/ginzap.go:89
github.com/gin-gonic/gin.(*Context).Next
	/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/context.go:185
github.com/gin-gonic/gin.(*Engine).handleHTTPRequest
	/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:633
github.com/gin-gonic/gin.(*Engine).ServeHTTP
	/go/pkg/mod/github.com/gin-gonic/gin@v1.10.0/gin.go:589
net/http.serverHandler.ServeHTTP
	/usr/local/go/src/net/http/server.go:3210
net/http.(*conn).serve
	/usr/local/go/src/net/http/server.go:2092

Any help would be appreciated.

[mgdigital]

Seems to be just timing out. Needs a beefier server/you're finding out why this wasn't designed to be publicly hosted.

There will likely be an OpenSearch integration in the not too distant future that might be more suitable to what you're trying to do - but if your instance is popular and open to everyone it will need significant investment in resources to maintain acceptable performance, whatever search engine is backing it.

[MidnightKittenCat]

Seems to be just timing out. Needs a beefier server/you're finding out why this wasn't designed to be publicly hosted.

There will likely be an OpenSearch integration in the not too distant future that might be more suitable to what you're trying to do - but if your instance is popular and open to everyone it will need significant investment in resources to maintain acceptable performance, whatever search engine is backing it.

This server is running a 9950x with 32 cores, on top of 100gb+ of ram; I'm not sure why it would be timing out. When abouts would OpenSearch be integrated in the near future do you know by any chance?

[MidnightKittenCat]

Here's my compose that I use for postgres; is there any issues you can see with it?

  bitmagnet_postgres:
    container_name: bitmagnet_postgres
    image: postgres:16-alpine
    restart: unless-stopped
    shm_size: 2g
    env_file:
      - .env
    volumes:
      - ${DOCKER_DATA_DIR}/bitmagnet/db:/var/lib/postgresql/data
    networks:
      bitmagnet:
        ipv4_address: 192.168.55.11
      aio_default: {}
    command:
      - "postgres"
      # Memory
      - "-c"
      - "shared_buffers=4GB"
      - "-c"
      - "effective_cache_size=12GB"
      - "-c"
      - "maintenance_work_mem=1GB"
      - "-c"
      - "work_mem=256MB"
      - "-c"
      - "wal_buffers=64MB"
      # I/O
      - "-c"
      - "random_page_cost=1.1"
      - "-c"
      - "effective_io_concurrency=200"
      # Parallelism
      - "-c"
      - "max_parallel_workers_per_gather=4"
      - "-c"
      - "max_parallel_workers=8"
      # Checkpoints & autovacuum
      - "-c"
      - "checkpoint_completion_target=0.9"
      - "-c"
      - "autovacuum_vacuum_scale_factor=0.02"
      - "-c"
      - "autovacuum_analyze_scale_factor=0.01"
    deploy:
      resources:
        limits:
          cpus: "8"
          memory: 16G
        reservations:
          cpus: "2"
          memory: 4G
    healthcheck:
      test: ["CMD", "pg_isready", "-U", "postgres", "-d", "bitmagnet"]
      interval: 10s
      timeout: 5s
      retries: 6
      start_period: 20s
    labels:
      - "deunhealth.restart.on.unhealthy=true"
    profiles: ["bitmagnet", "all"]

And my bitmagnet .env;

# Auto-tuned PostgreSQL perf
PG_SHARED_BUFFERS=2GB
PG_WORK_MEM=64MB
PG_MAINTENANCE_WORK_MEM=512MB
PG_EFFECTIVE_CACHE_SIZE=6GB
PG_MAX_CONNECTIONS=100
PG_SYNCHRONOUS_COMMIT=off
PG_WAL_COMPRESSION=on
PG_CHECKPOINT_TIMEOUT=15min

# ========== PERFORMANCE ==========
DHT_CRAWLER_SAVE_PIECES=false
DHT_CRAWLER_SAVE_FILES_THRESHOLD=20
DHT_CRAWLER_SCALING_FACTOR=8
PROCESSOR_CONCURRENCY=8
HTTP_SERVER_CONCURRENCY=8
IMPORT_BATCH_SIZE=2000
BATCH_COMMIT_INTERVAL=3s
DISK_FLUSH_INTERVAL=5s
DHT_TOKEN_CACHE_TTL=120s
MAX_PEER_CONNECTIONS=200
TORRENT_DOWNLOAD_TIMEOUT=300
ENABLE_STATS_COLLECTION=false
LOG_LEVEL=info
CLASSIFIER_WORKFLOW=keep_movies_tv_music

[MidnightKittenCat]

@mgdigital Does everything look right here to you or am I missing anything?

[mgdigital]

Paginating to higher offsets is not efficient in Postgres. It needs to query all results up to the pagination point to achieve this. You could put in a WAF to prevent users paginating too high based on query parameters as this will kill performance for other users.

This server is running a 9950x with 32 cores, on top of 100gb+ of ram; I'm not sure why it would be timing out.

Supporting hundreds of users searching at once is a problem that needs to be parallelized. This isn't natively supported in Postgres, but putting in several read replicas behind a load balancer might mitigate.

When abouts would OpenSearch be integrated in the near future do you know by any chance?

Hopefully sometime in the next year.

[mgdigital]

Also you need to increase your memory limits (shm_size and resources sections). You are only giving a fraction of your resources to Postgres.

[MidnightKittenCat]

I see thanks for your input, I've raised the resources as well as the memory limits- and added an nginx proxy to force the offset to 1000 if it goes above it.

[MidnightKittenCat]

Paginating to higher offsets is not efficient in Postgres. It needs to query all results up to the pagination point to achieve this. You could put in a WAF to prevent users paginating too high based on query parameters as this will kill performance for other users.

This server is running a 9950x with 32 cores, on top of 100gb+ of ram; I'm not sure why it would be timing out.

Supporting hundreds of users searching at once is a problem that needs to be parallelized. This isn't natively supported in Postgres, but putting in several read replicas behind a load balancer might mitigate.

When abouts would OpenSearch be integrated in the near future do you know by any chance?

Hopefully sometime in the next year.

Also, I'm in contact with the dev behind the search engine connected to bitmagnet; what would be the proper way of paginating instead of using offsets?

[MidnightKittenCat]

@mgdigital Just a reminder incase you didn't get the notification; what would be the proper way of paginating efficiently?

[mgdigital]

what would be the proper way of paginating efficiently?

I'm not sure if I understand your question but there's no trick you're missing that will make pagination a lot faster - Bitmagnet simply wasn't designed to support many users searching at once. The many trade offs that have been made all lean towards optimising for small scale usage on modest hardware. A future update may allow for an OpenSearch integration that might be better suited to your use case.

For now you could improve things a little by reducing the size of your database, by not writing to the same DB you're trying to search from (i.e. use read replicas), limit pagination and rate limit individual users.