Arch Linux User Repository

@mikep @PatoPan I pushed a fix. Please let me know if it works as expected.

@FabioAreia Please post your arm64 build logs via a paste service.

I don't know if this is related to the problem below, but on a new install /var/lib/jellyseerr/logs and /var/lib/jellyseerr/cache don't get created.

I'll take a look at this today. I have to set up a chroot for installation testing.

installation logs https://privatebin.net/?4f18dae3faede1a0#4SY2nGKcivv3FSYRBbCan55mdRuSKvFDSvZU66xQrk8R

The var lib folder is not getting created, so the config folder is a broken symlink

ls -l /usr/lib/jellyseerr
total 204
lrwxrwxrwx 1 root       root      19 Dec  5 18:00 config -> /var/lib/jellyseerr
drwxr-xr-x 1 jellyseerr media    326 Dec  5 17:59 dist
-rw-r--r-- 1 jellyseerr media    581 Nov 20 21:42 next.config.js
drwxr-xr-x 1 jellyseerr media   1954 Dec  5 17:59 node_modules
-rw-r--r-- 1 jellyseerr media 188991 Nov 20 21:42 overseerr-api.yml
-rw-r--r-- 1 jellyseerr media   7982 Nov 20 21:42 package.json
drwxr-xr-x 1 jellyseerr media   2560 Dec  5 17:59 public
ls -l /var/lib/jellyseerr
ls: cannot access '/var/lib/jellyseerr': No such file or directory
ls -l /var/lib/ | grep "jelly"
drwxr-x--- 1 jellyfin jellyfin  86 Dec  4 06:07 jellyfin

Also, maybe it's odd the symlink is created as a root user. Changing the owner and group doesn't fix it, I had to create the folder to fix it

@txtsd I had the same issue happen again when I was forced to reinstall, after having to reinstall Jellyfin. What kind of logs do you wish to see? The logs I have aren't useful and don't fit the aur

Dec 05 18:01:56 mediasupreme systemd[1]: Started Jellyseerr Service.
░░ Subject: A start job for unit jellyseerr.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit jellyseerr.service has finished successfully.
░░ 
░░ The job identifier is 36594.
Dec 05 18:01:56 mediasupreme node[79893]: /usr/lib/jellyseerr/node_modules/.pnpm/file-stream-rotator@0.6.1/node_modules/file-stream-rotator/FileStreamRotator.js:672
Dec 05 18:01:56 mediasupreme node[79893]:                         throw e;
Dec 05 18:01:56 mediasupreme node[79893]:                         ^
Dec 05 18:01:56 mediasupreme node[79893]: Error: ENOENT: no such file or directory, mkdir '/usr/lib/jellyseerr/config/logs/'
Dec 05 18:01:56 mediasupreme node[79893]:     at Object.mkdirSync (node:fs:1371:26)
Dec 05 18:01:56 mediasupreme node[79893]:     at /usr/lib/jellyseerr/node_modules/.pnpm/file-stream-rotator@0.6.1/node_modules/file-stream-rotator/FileStreamRotator.js:669:24
Dec 05 18:01:56 mediasupreme node[79893]:     at Array.reduce (<anonymous>)
Dec 05 18:01:56 mediasupreme node[79893]:     at mkDirForFile (/usr/lib/jellyseerr/node_modules/.pnpm/file-stream-rotator@0.6.1/node_modules/file-stream-rotator/FileStreamRotator.js:656:27)
Dec 05 18:01:56 mediasupreme node[79893]:     at FileStreamRotator.getStream (/usr/lib/jellyseerr/node_modules/.pnpm/file-stream-rotator@0.6.1/node_modules/file-stream-rotator/FileStreamRotator.js:532:5)
Dec 05 18:01:56 mediasupreme node[79893]:     at new DailyRotateFile (/usr/lib/jellyseerr/node_modules/.pnpm/winston-daily-rotate-file@4.7.1_winston@3.8.2/node_modules/winston-daily-rotate-file/daily-rotate-file.js:80:57)
Dec 05 18:01:56 mediasupreme node[79893]:     at Object.<anonymous> (/usr/lib/jellyseerr/dist/logger.js:55:9)
Dec 05 18:01:56 mediasupreme node[79893]:     at Module._compile (node:internal/modules/cjs/loader:1469:14)
Dec 05 18:01:56 mediasupreme node[79893]:     at Module._extensions..js (node:internal/modules/cjs/loader:1548:10)
Dec 05 18:01:56 mediasupreme node[79893]:     at Module.load (node:internal/modules/cjs/loader:1288:32) {
Dec 05 18:01:56 mediasupreme node[79893]:   errno: -2,
Dec 05 18:01:56 mediasupreme node[79893]:   code: 'ENOENT',
Dec 05 18:01:56 mediasupreme node[79893]:   syscall: 'mkdir',
Dec 05 18:01:56 mediasupreme node[79893]:   path: '/usr/lib/jellyseerr/config/logs/'
Dec 05 18:01:56 mediasupreme node[79893]: }
Dec 05 18:01:56 mediasupreme node[79893]: Node.js v20.18.0
Dec 05 18:01:56 mediasupreme systemd[1]: jellyseerr.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ An ExecStart= process belonging to unit jellyseerr.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
Dec 05 18:01:56 mediasupreme systemd[1]: jellyseerr.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit jellyseerr.service has entered the 'failed' state with result 'exit-code'.
Dec 05 18:02:01 mediasupreme systemd[1]: jellyseerr.service: Scheduled restart job, restart counter is at 8.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ Automatic restarting of the unit jellyseerr.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.

I cant build the new version in arm64

@PatoPan Thanks for reporting. Logs would have been much more helpful.

A weird bug. On a complete fresh arch install, that only has radarr, sonarr, jellyfin, prowlarr, qbittorrent, and moonlight-qt installed, the jellyseer service was failing to start. I noticed that there was a config *file* inside /usr/lib/jellyseer. I fixed it by deleting the file, because it's supposed to be a directory.

Everything including Arch was installed yesterday

While the current versions of the package have the symlink problem fixed. They might still exist on your system. You will have to back up your data and delete them manually.

Detected unsafe path transition /var/lib/jellyseerr (owned by jellyseerr) → /var/lib/jellyseerr/cache (owned by root) during canonicalization of usr/lib/jellyseerr/config/cache/images.
Detected unsafe path transition /var/lib/jellyseerr (owned by jellyseerr) → /var/lib/jellyseerr/cache (owned by root) during canonicalization of usr/lib/jellyseerr/config/cache/images.
error: command failed to execute correctly

Yep, I also see these warnings currently. That's a packaging bug, not an issue with your system.