troubleshuting start serviio

Hello, I'm trying to install serviio, but something went wrong. I downloaded it from the off-site, unpacked it along the way /opt/serviio,created a script to run /etc/systemd/system/serviio.service, but after restarting the service does not start, as a result, the management console is unavailable, here is the terminal output to the sudo systemctl status serviio.service command

  Code:

[jeka@localhost serviio]$ sudo systemctl status serviio.service
× serviio.service - Serviio media Server
     Loaded: loaded (/etc/systemd/system/serviio.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: exit-code) since Sat 2024-11-09 11:51:21 MSK; 9s ago
   Duration: 397ms
    Process: 3543 ExecStart=/opt/serviio/bin/serviio.sh (code=exited, status=203/EXEC)
   Main PID: 3543 (code=exited, status=203/EXEC)
        CPU: 6ms

ноя 09 11:51:20 localhost.localdomain systemd[1]: Started serviio.service - Serviio media Server.
ноя 09 11:51:20 localhost.localdomain systemd[1]: serviio.service: Main process exited, code=exited, status=203/EXEC
ноя 09 11:51:21 localhost.localdomain systemd[1]: serviio.service: Failed with result 'exit-code'.
[jeka@localhost serviio]$

tell me pls how i can fix it problem?

[atc98092]

Please upload your Serviio log here. It will be located under your Serviio install in the Logs folder. We don't need the Derby log, just the Serviio log.

pls see file info Logs derby

[atc98092]

Sorry, you misunderstood. Not the Derby.log file. We need the Serviio.log file.

here

[atc98092]

Well, that certainly didn't help, there's almost nothing there. I am assuming you did not grab the log until after Serviio had tried failed to load. If you do a process check (ps -ef if I remember my Linux commands) there is no remanent of Serviio running, right?

I compared it to one of my Serviio logs, and while I'm running on Windows the log starts with the identical lines (other than file locations listed), everything is the same until it finishes loading the console. After those first four loading signs, mine continues with these:

2022-10-23T16:40:16,323 INFO [RestletServer] Starting HTTP/1.1 Restlet server (/cds) exposed on port 23424
2022-10-23T16:40:16,323 INFO [RestletServer] Starting HTTP/1.1 Restlet server (/mediabrowser) exposed on port 23424
2022-10-23T16:40:16,324 INFO [RestletServer] Starting HTTPS/1.1 Restlet server (/cds) exposed on port 23524
2022-10-23T16:40:16,324 INFO [RestletServer] Starting HTTPS/1.1 Restlet server (/mediabrowser) exposed on port 23524

So, just guessing on my part, there's something that is either killing your Serviio process once it's finished the first four lines, or something in the fifth line (the first line I pasted from mine) is blocking Serviio from starting. Normally Serviio would write an error message here, which is why I think something is killing the process before it can proceed. I can't say if you already have something running using port 23424 or if it's something else. Perhaps you could run a port scanner when you aren't trying to run Serviio and see if something comes up on ports 23423/23523/23424/23524. Beyond that, we've exceeded my knowledge in the area and only the developer (Zip) can delve further into this.