building error

[autobrr]

building error

[GregTroar]

by the way you can close this issue :)

[ludviglundgren]

Hi.

If you look in the Dockerfile how things are built, it first needs to build the frontend in web.

1. Make sure you have node/npm/yarn installed
2. navigate into web
3. Install packages with npm install or yarn
4. Build npm run build or yarn build
5. Then you can go back up into the root and build the binary

Again, more official instructions ARE coming.

[GregTroar]

Awesome let me try
By the way with the binaries here is the issue I have:

https://imgur.com/lC1L1Ml

And i am running:

Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye

after this error if I refresh I am redirected to login screen

[ludviglundgren]

Here's how Swizzin (seedbox installer/distro/package manager) sets everything up. swizzin autobrr install

It uses a few helpers etc for nginx, but most is in there. Downloads binary, unpacks, moves, creates a systemd service file, creates config in the expected place in users home, then creates the initial user with autobrrctl.

[GregTroar]

I achieved to build the binaries, unfortunately on my seedbox it still does not work with same error, I will run my tests on a local VM.

Nothing in the logs, also something strange, I added 3 definitions thus 18 indexers but it counts only 17 in the trace log

2021-12-21T16:24:48+01:00 DBG Starting autobrr
2021-12-21T16:24:48+01:00 DBG Log-level: TRACE
2021-12-21T16:24:48+01:00 INF Starting server. Listening on 0.0.0.0:8989
2021-12-21T16:24:48+01:00 TRC parsing: definitions/alpharatio.yaml
2021-12-21T16:24:48+01:00 TRC parsing: definitions/beyondhd.yaml
2021-12-21T16:24:48+01:00 TRC parsing: definitions/btn.yaml
2021-12-21T16:24:48+01:00 TRC parsing: definitions/emp.yaml
2021-12-21T16:24:48+01:00 TRC parsing: definitions/filelist.yaml
2021-12-21T16:24:48+01:00 TRC parsing: definitions/gazellegames.yaml
2021-12-21T16:24:48+01:00 TRC parsing: definitions/hd-torrents.yaml
2021-12-21T16:24:48+01:00 TRC parsing: definitions/iptorrents.yaml
2021-12-21T16:24:48+01:00 TRC parsing: definitions/milkie.yaml
2021-12-21T16:24:48+01:00 TRC parsing: definitions/nebulance.yaml
2021-12-21T16:24:48+01:00 TRC parsing: definitions/orpheus.yaml
2021-12-21T16:24:48+01:00 TRC parsing: definitions/ptp.yaml
2021-12-21T16:24:48+01:00 TRC parsing: definitions/red.yaml
2021-12-21T16:24:48+01:00 TRC parsing: definitions/superbits.yaml
2021-12-21T16:24:48+01:00 TRC parsing: definitions/torrentDay.yaml
2021-12-21T16:24:48+01:00 TRC parsing: definitions/torrentSeeds.yaml
2021-12-21T16:24:48+01:00 TRC parsing: definitions/torrentleech.yaml
2021-12-21T16:24:48+01:00 TRC parsing: definitions/uhdbits.yaml
2021-12-21T16:24:48+01:00 INF Loaded 17 indexer definitions

[GregTroar]

Anyway this issue is resolved, I will try to further investigate why it works well on Debian 11 on my VM and not on my seedbox which also runs Debian 11.

[ludviglundgren]

That's indeed weird the numbers don't match. There's plenty of logging for the parsing so that should catch any errors. I see your fork with milkie and TD, could you push TS so I could check for any errors? You're more than welcome to make a PR with the additions as well. But please change to some non obvious release names before doing so, like the current definitions have. :)

Could it be a browser cache issue on the web? Try and clear/remove the database as well if you have started it with different results. It should run the migrations when you set up the user with autobrrctl.

And could you please maybe continue on this issue for further discussion if needed? I'll close the others but keep this open for a couple days.

[GregTroar]

Hi Ludvig,

I am still scratching my head on this issue.
I have deleted the database and config file, recreated user with autobrrctl --config /path/ create-user test
I have cleared all the chrome cache, changed the binaries to directory /tmp and chmoded 777 for testing purpose.
It does not work.

Version of linux on my seedbox is Linux 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux and is exactly the same on my virtual machine...

Problem is I have no log to look out to find out the issue :(

I have done 3 indexers and have updated the the releases names to something non obvious. I will test them and need to read how to do a PR cause I have never done any :)