Persistence / unauthenticated? What am I doing wrong

[jimapl]

Hi all,

I've been running quirrel in my production app for a while now but I keep running into the same issue:
After a while, usually a week or so, quirrel.enqueue throws an unauthenticated error.
Usually I have to rerun my curl cmd and run another production build afterwards. I'm pretty fed up with this routine as it basicly breaks my production app.

I am running redis & Quirrel with docker-compose
I'm somewhat new to working with docker so I hope anyone could help me out with my setup.

Here is my yaml file:

version: "3.3"

services:
  redis:
    image: "bitnami/redis:latest"
    environment:
      - REDIS_PASSWORD=pass
    ports:
      - "6379:6379"
    volumes:
      - "redis_data:/bitnami/redis/data"
    networks:
      - redis-private
  quirrel:
    image: "ghcr.io/quirrel-dev/quirrel:sha-de34419"
    environment:
      - REDIS_URL=redis://:pass@redis:6379/0
      - QUIRREL_SERVER_URL=http://127.0.0.1:9181
      - NAME_OF_TOKEN=tokenName
      - PASSPHRASES=somepassprashes
    depends_on:
      - redis
    networks:
      - redis-private
      - quirrel-public
    ports:
      - "9181:9181"

networks:
  redis-private:
    external: false
  quirrel-public:
    external: true

volumes:
  redis_data:
    driver: local

#curlCmd=curl --user ignored:somepassprashes -X PUT http://localhost:9181/tokens/nameoftokenhere

How is this redis instance not persistent?

Hope someone can point my in the right direction.
& Thank you

[Skn0tt]

I very much feel that having to re-run the curl command is annoying. If there's something off with persistence, then not only your token is lost, but also all scheduled jobs that are stored within Redis.

I haven't encountered this problem when running the hosted Quirrel, so i'm assuming it's not something in the Quirrel codebase, but rather something with the Redis or Docker configuration.

Have you tried running Redis outside of Docker, to eliminate that potential source of errors?

[jimapl]

Hi,
I am still facing this issue!
Tried redis outside of docker. But it still happens that the quirrel instance just randomly stops, or throws an unauthenticated error!

I need some help!

[Skn0tt]

Please check if the Redis instance is configured to persist its data. You mention the instance "randomly stops", could you provide me with an excerpt of the logs when that happens?

[jimapl]

Swapped out Quirrel for bull. Thanks for the help anyways

[christopherpickering]

I had a similar (same?) issue whenever my server restarted or a pm2 process reloaded. I fixed it by moving the pm2 service for quirrel into my remix server.ts so that I get a new token whenever the app restarts: #1157

Bull looks nice, but the data persistance is the same there.