Closed X015 closed 2 years ago
The migrations are supposed to create the extension but uhh obviously don't.
$ docker-compose exec postgres psql wowthing -U wowthing
wowthing=# create extension pg_trgm with schema pg_catalog;
Thank you got it working! I took it down with docker compose down and reinstalled it, I changed the redirect URL too point to my home server and not to localhost.
But i have a other Problem now
I can login via the BattleNET API and when trying to access the site i get this:
KABOOM! Something has gone horribly wrong, try reloading the page?
LOG:
[09:40:21.614 WRN Worker 2H] 129677501 UserUpload - Invalid realm: EU/Defias Brotherhood
[09:40:21.614 WRN Worker 2H] 129677501 UserUpload - Invalid realm: EU/Kilrogg
[09:40:21.614 WRN Worker 2H] 129677501 UserUpload - Invalid realm: EU/Ravencrest
and this
[11:26:54.440 ERR Scheduler ] Kaboom!
StackExchange.Redis.RedisConnectionException: No connection is active/available to service this operation: SET lock:scheduler, mc: 1/1/0, mgr: 10 of 10 available, clientName: Wowthing.Lib, IOCP: (Busy=0,Free=1000,Min=4,Max=1000), WORKER: (Busy=2,Free=32765,Min=4,Max=32767), v: 2.2.88.56325
at StackExchange.Redis.ConnectionMultiplexer.ThrowFailed[T](TaskCompletionSource`1 source, Exception unthrownException) in /_/src/StackExchange.Redis/ConnectionMultiplexer.cs:line 2829
--- End of stack trace from previous location ---
at Wowthing.Lib.Repositories.JobRepository.AcquireLockAsync(String key, String value, TimeSpan expiry) in /app/src/Wowthing.Lib/Repositories/JobRepository.cs:line 88
The scheduler one seems weird, it should be able to contact Redis if it's running. The other one is most likely that scheduled jobs are terrible and don't handle errors properly, can check the JS console (F11 usually) but easiest fix:
docker-compose exec redis redis-cli
127.0.0.1:6379> del scheduled_job:ImportDumps_v11
backend
container logs127.0.0.1:6379> del scheduled_job:CacheStatic_v41
Fresh install on Debian based system