Jump to content

Recommended Posts

Posted

My TOS version is 4.2.44, I updated Emby Server to 4.8.8.0 from TOS applications. After the isntallation, I clicked the 'Start' button, and it shows 'Configurating' for a while and the shows 'Start'. However the Emby server is not start, after reopen the Emby Server page in Applications, it shows 'Stopped'

I tried to uninstall it, restart NAS, and remove the emby and emby-server folder from the application folder by SSH. But the Emby Server still can not start.

Could it cause by this version of Emby Server? Is there any way to get an older version of Emby Server?

I have attached the log file.

 

TNAS-1661_CST_20250117_142256.zip

sa2000
Posted

I am not familiar with TerraMaster. Noticed a lot of repeated disc disc errors in the messages log file. Example:

Jan 17 14:20:51 TNAS-1661 kernel: EXT4-fs error (device dm-0): __ext4_find_entry:1449: inode #116129845: comm EmbyServer: reading directory lblock 0
Jan 17 14:20:55 TNAS-1661 kernel:          res 41/40:08:20:8a:e9/00:00:dd:00:00/00 Emask 0x409 (media error) <F>
Jan 17 14:20:55 TNAS-1661 kernel: ata2.00: error: { UNC }
Jan 17 14:20:55 TNAS-1661 kernel: sd 2:0:0:0: [sdc] tag#20 Sense Key : Medium Error [current] 
Jan 17 14:20:55 TNAS-1661 kernel: sd 2:0:0:0: [sdc] tag#20 Add. Sense: Unrecovered read error - auto reallocate failed
Jan 17 14:20:55 TNAS-1661 kernel: print_req_error: I/O error, dev sdc, sector 3723069984
Jan 17 14:20:55 TNAS-1661 kernel: EXT4-fs error (device dm-0): __ext4_find_entry:1449: inode #116129845: comm EmbyServer: reading directory lblock 0

I presume these are relevant to the problem ?

Posted
2 hours ago, sa2000 said:

I am not familiar with TerraMaster. Noticed a lot of repeated disc disc errors in the messages log file. Example:

Jan 17 14:20:51 TNAS-1661 kernel: EXT4-fs error (device dm-0): __ext4_find_entry:1449: inode #116129845: comm EmbyServer: reading directory lblock 0
Jan 17 14:20:55 TNAS-1661 kernel:          res 41/40:08:20:8a:e9/00:00:dd:00:00/00 Emask 0x409 (media error) <F>
Jan 17 14:20:55 TNAS-1661 kernel: ata2.00: error: { UNC }
Jan 17 14:20:55 TNAS-1661 kernel: sd 2:0:0:0: [sdc] tag#20 Sense Key : Medium Error [current] 
Jan 17 14:20:55 TNAS-1661 kernel: sd 2:0:0:0: [sdc] tag#20 Add. Sense: Unrecovered read error - auto reallocate failed
Jan 17 14:20:55 TNAS-1661 kernel: print_req_error: I/O error, dev sdc, sector 3723069984
Jan 17 14:20:55 TNAS-1661 kernel: EXT4-fs error (device dm-0): __ext4_find_entry:1449: inode #116129845: comm EmbyServer: reading directory lblock 0

I presume these are relevant to the problem ?

Thanks for checking, I have changed the application folder to another disc, but the Emby Server still can not start, the other apps are OK.

sa2000
Posted

Could you see if there are any Emby Server log files being created. I believe they would be in this folder

/home/emby/logs

Other suggestion is to try the current build available here https://emby.media/terramaster-server.html

Posted
6 minutes ago, sa2000 said:

Could you see if there are any Emby Server log files being created. I believe they would be in this folder

/home/emby/logs

Other suggestion is to try the current build available here https://emby.media/terramaster-server.html

I have installed this version, 4.8.10.0 still same issue.

 

The  logs are like this

 

[admin@TNAS logs]$ ls -l
total 33136
-rw-r--r-- 1 emby emby 9523743 Jan 14 23:57 embyserver-63872496043.txt
-rw-r--r-- 1 emby emby 9916230 Jan 15 23:58 embyserver-63872582445.txt
-rw-r--r-- 1 emby emby 9882314 Jan 16 23:59 embyserver-63872668846.txt
-rw-r--r-- 1 emby emby 4471577 Jan 17 13:11 embyserver-63872716304.txt
-rw-r--r-- 1 emby emby     154 Jan 17 13:17 embyserver-63872716644.txt
-rw-r--r-- 1 emby emby     154 Jan 17 13:19 embyserver-63872716785.txt
-rw-r--r-- 1 emby emby     154 Jan 17 13:20 embyserver-63872716821.txt
-rw-r--r-- 1 emby emby     154 Jan 17 13:25 embyserver-63872717133.txt
-rw-r--r-- 1 emby emby     154 Jan 17 14:11 embyserver-63872719877.txt
-rw-r--r-- 1 emby emby     154 Jan 17 14:11 embyserver-63872719906.txt
-rw-r--r-- 1 emby emby     154 Jan 17 14:14 embyserver-63872720080.txt
-rw-r--r-- 1 emby emby     101 Jan 17 14:16 embyserver-63872720239.txt
-rw-r--r-- 1 emby emby     154 Jan 17 14:17 embyserver-63872720250.txt
-rw-r--r-- 1 emby emby     154 Jan 17 14:20 embyserver-63872720455.txt
-rw-r--r-- 1 emby emby     154 Jan 17 14:36 embyserver-63872721402.txt
-rw-r--r-- 1 emby emby     154 Jan 17 16:38 embyserver-63872728731.txt
-rw-r--r-- 1 emby emby     154 Jan 17 16:39 embyserver-63872728771.txt
-rw-r--r-- 1 emby emby     154 Jan 17 16:44 embyserver-63872729083.txt
-rw-r--r-- 1 emby emby     154 Jan 17 16:45 embyserver-63872729115.txt
-rw-r--r-- 1 emby emby     154 Jan 17 17:12 embyserver-63872730732.txt
-rw-r--r-- 1 emby emby     154 Jan 17 17:13 embyserver-63872730781.txt
-rw-r--r-- 1 emby emby     154 Jan 17 17:23 embyserver-63872731438.txt
-rw-r--r-- 1 emby emby     154 Jan 17 17:25 embyserver-63872731547.txt
-rw-r--r-- 1 emby emby     154 Jan 17 17:48 embyserver-63872732910.txt
-rw-r--r-- 1 emby emby     154 Jan 17 20:40 embyserver-63872743243.txt
-rw-r--r-- 1 emby emby     154 Jan 17 20:41 embyserver-63872743281.txt
-rw-r--r-- 1 emby emby     154 Jan 17 20:42 embyserver-63872743320.txt
-rw-r--r-- 1 emby emby     154 Jan 17 20:42 embyserver-63872743363.txt
-rw-r--r-- 1 emby emby     154 Jan 17 21:09 embyserver-63872744968.txt
-rw-r--r-- 1 emby emby     154 Jan 17 21:14 embyserver-63872745283.txt
-rw-r--r-- 1 emby emby     154 Jan 17 21:18 embyserver-63872745505.txt
-rw-r--r-- 1 emby emby     454 Jan 17 21:18 readme.txt
[admin@TNAS logs]$ cat embyserver-63872745505.txt
2025-01-17 21:18:12.815 Info Main: Application path: /mnt/md2/application/emby/system/EmbyServer.dll
2025-01-17 21:18:25.717 Info Main: Shutdown complete
[admin@TNAS logs]$ cat embyserver-63872745283.txt
2025-01-17 21:14:34.604 Info Main: Application path: /mnt/md2/application/emby/system/EmbyServer.dll
2025-01-17 21:14:43.622 Info Main: Shutdown complete
 

sa2000
Posted (edited)

Could you look for this file 

"/home/emby/config/system.xml" and edit it and add or change this line if set to false

 

  <EnableDebugLevelLogging>true</EnableDebugLevelLogging>

and then see if the server launch logs some extra info

Edited by sa2000
Posted
1 hour ago, sa2000 said:

Could you look for this file 

"/home/emby/config/system.xml" and edit it and add or change this line if set to false

 

  <EnableDebugLevelLogging>true</EnableDebugLevelLogging>

and then see if the server launch logs some extra info

If no log is currently being created, then changing this will not help. This will only add more information the log that is already there.

Posted
4 hours ago, fuluel said:

My TOS version is 4.2.44, I updated Emby Server to 4.8.8.0 from TOS applications. After the isntallation, I clicked the 'Start' button, and it shows 'Configurating' for a while and the shows 'Start'. However the Emby server is not start, after reopen the Emby Server page in Applications, it shows 'Stopped'

I tried to uninstall it, restart NAS, and remove the emby and emby-server folder from the application folder by SSH. But the Emby Server still can not start.

Could it cause by this version of Emby Server? Is there any way to get an older version of Emby Server?

I have attached the log file.

 

TNAS-1661_CST_20250117_142256.zip 7.62 MB · 1 download

Are you able to update TOS or is this device stuck on 4?

sa2000
Posted
4 minutes ago, Luke said:

If no log is currently being created, then changing this will not help. This will only add more information the log that is already there.

There appears to be logs created but they just show immediate shutdown

admin@TNAS logs]$ cat embyserver-63872745283.txt
2025-01-17 21:14:34.604 Info Main: Application path: /mnt/md2/application/emby/system/EmbyServer.dll
2025-01-17 21:14:43.622 Info Main: Shutdown complete

See above post here

sa2000
Posted

This is what gets run by the emby script in \etc\init.d after calling service_prepare

start-stop-daemon -S -q -b -c emby:emby -x /usr/local/emby/bin/emby-server -p /var/run/emby-server.pid -m

Could try to run it manually 

It is part of this sequence 

service_start() {
  service_prepare
  start-stop-daemon -S -q -b -c emby:emby -x $APP_DIR/bin/emby-server -p $PID_FILE -m
  if [ ! -e "$EMBY_CONF" ]; then
    echo -e "location ~ ^/emby {\n\tproxy_pass http://127.0.0.1:8096;\n}" >$EMBY_CONF
    service nginx reload
  fi
  sleep 1
}

We do have two install packages for each of intel and arm - Is it TOS 5 onwards and TOS 4?

Posted
12 hours ago, sa2000 said:

Could you look for this file 

"/home/emby/config/system.xml" and edit it and add or change this line if set to false

 

  <EnableDebugLevelLogging>true</EnableDebugLevelLogging>

and then see if the server launch logs some extra info

This folder is empty

Posted
11 hours ago, Luke said:

Are you able to update TOS or is this device stuck on 4?

I heard to update to TOS 5.x will required to Reset to Factory Default, I don't want to do that unless there is really no other choice.

Posted
11 hours ago, sa2000 said:

This is what gets run by the emby script in \etc\init.d after calling service_prepare

start-stop-daemon -S -q -b -c emby:emby -x /usr/local/emby/bin/emby-server -p /var/run/emby-server.pid -m

Could try to run it manually 

It is part of this sequence 

service_start() {
  service_prepare
  start-stop-daemon -S -q -b -c emby:emby -x $APP_DIR/bin/emby-server -p $PID_FILE -m
  if [ ! -e "$EMBY_CONF" ]; then
    echo -e "location ~ ^/emby {\n\tproxy_pass http://127.0.0.1:8096;\n}" >$EMBY_CONF
    service nginx reload
  fi
  sleep 1
}

We do have two install packages for each of intel and arm - Is it TOS 5 onwards and TOS 4?

I downloaded from the link '64-bit' not '64-bit (TOS5)' I belive it should be the one for TOS 4 right?

 

Could you let me know how to run it manually? By SSH to the NAS?

sa2000
Posted
7 hours ago, fuluel said:

This folder is empty

I don't have a TerraMaster to check this - I expect there to be a system.xml file within /home/emby if it is similar to other platforms

 

7 hours ago, fuluel said:

I downloaded from the link '64-bit' not '64-bit (TOS5)' I belive it should be the one for TOS 4 right?

That is what I think 

 

7 hours ago, fuluel said:

Could you let me know how to run it manually? By SSH to the NAS?

I would presume you would ssh to the NAS and you can 

cd /etc/init.d

In here you will see the emby script 

I thought it might be possible to try this 

start-stop-daemon -S -q -b -c emby:emby -x /usr/local/emby/bin/emby-server -p /var/run/emby-server.pid -m

But I am not a linux expert - and would need help from others to go further - no harm in trying it

 

Posted
On 1/18/2025 at 5:35 PM, sa2000 said:

I don't have a TerraMaster to check this - I expect there to be a system.xml file within /home/emby if it is similar to other platforms

 

That is what I think 

 

I would presume you would ssh to the NAS and you can 

cd /etc/init.d

In here you will see the emby script 

I thought it might be possible to try this 

start-stop-daemon -S -q -b -c emby:emby -x /usr/local/emby/bin/emby-server -p /var/run/emby-server.pid -m

But I am not a linux expert - and would need help from others to go further - no harm in trying it

 

I tried this 

start-stop-daemon -S -q -b -c emby:emby -x /usr/local/emby/bin/emby-server -p /var/run/emby-server.pid -m

 

But the Emby server still not running.

sa2000
Posted (edited)

 

45 minutes ago, fuluel said:

I tried this 

start-stop-daemon -S -q -b -c emby:emby -x /usr/local/emby/bin/emby-server -p /var/run/emby-server.pid -m

 

But the Emby server still not running.

Thanks for trying

@alucrydCould you help with this - I looked at the emby script in /etc/init.d and suggested the user runs the start manually. We could do with adding logging to the emby script to help troubleshoot. The emby server logs show the server shuts down immediately - see my earlier responses and the zip provided. Thanks

 

Edited by sa2000
  • 2 weeks later...
sa2000
Posted

@fuluelIs your problem resolved ? I was trying to see if others can help

Posted
On 1/17/2025 at 9:20 PM, fuluel said:

I downloaded from the link '64-bit' not '64-bit (TOS5)' I belive it should be the one for TOS 4 right?

 

Could you let me know how to run it manually? By SSH to the NAS?

Yes there is a separate package for TOS 4. How did you install? Just from TOS package center? Did you manually install a package?

alucryd
Posted

@fuluelPlease try `sudo -u emby /usr/local/emby/bin/emby-server`, that should run the server in the foreground and hopefully give us some pointers as to why it doesn't launch normally.

  • 3 weeks later...
Posted
On 2/1/2025 at 6:08 AM, alucryd said:

@fuluelPlease try `sudo -u emby /usr/local/emby/bin/emby-server`, that should run the server in the foreground and hopefully give us some pointers as to why it doesn't launch normally.

I will try that later. Thanks

Posted
10 hours ago, fuluel said:

I will try that later. Thanks

Let us know how you get on. Thanks.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...