Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Get this nginix error on the server log. And the plex transs is buggy with green lag

Featured Replies

Get this in my log: Feb 22 15:43:03 Elsa nginx: 2020/02/22 15:43:03 [alert] 6714#6714: worker process 30118 exited on signal 6

 

and transoc on plex is buggy. ( green legg)

 

Feb 22 15:42:15 Elsa login[29970]: ROOT LOGIN on '/dev/pts/1'
Feb 22 15:42:17 Elsa nginx: 2020/02/22 15:42:17 [alert] 6714#6714: worker process 29969 exited on signal 6
Feb 22 15:42:17 Elsa login[29978]: ROOT LOGIN on '/dev/pts/1'
Feb 22 15:42:19 Elsa nginx: 2020/02/22 15:42:19 [alert] 6714#6714: worker process 29977 exited on signal 6
Feb 22 15:42:19 Elsa login[29987]: ROOT LOGIN on '/dev/pts/1'
Feb 22 15:42:21 Elsa nginx: 2020/02/22 15:42:21 [alert] 6714#6714: worker process 29986 exited on signal 6
Feb 22 15:42:21 Elsa login[29997]: ROOT LOGIN on '/dev/pts/1'
Feb 22 15:42:23 Elsa nginx: 2020/02/22 15:42:23 [alert] 6714#6714: worker process 29996 exited on signal 6
Feb 22 15:42:23 Elsa login[30005]: ROOT LOGIN on '/dev/pts/1'
Feb 22 15:42:25 Elsa nginx: 2020/02/22 15:42:25 [alert] 6714#6714: worker process 30004 exited on signal 6
Feb 22 15:42:25 Elsa login[30017]: ROOT LOGIN on '/dev/pts/1'
Feb 22 15:42:27 Elsa nginx: 2020/02/22 15:42:27 [alert] 6714#6714: worker process 30016 exited on signal 6
Feb 22 15:42:27 Elsa login[30027]: ROOT LOGIN on '/dev/pts/1'
Feb 22 15:42:29 Elsa nginx: 2020/02/22 15:42:29 [alert] 6714#6714: worker process 30026 exited on signal 6
Feb 22 15:42:30 Elsa login[30036]: ROOT LOGIN on '/dev/pts/1'
Feb 22 15:42:31 Elsa nginx: 2020/02/22 15:42:31 [alert] 6714#6714: worker process 30035 exited on signal 6
Feb 22 15:42:31 Elsa login[30044]: ROOT LOGIN on '/dev/pts/1'
Feb 22 15:42:33 Elsa nginx: 2020/02/22 15:42:33 [alert] 6714#6714: worker process 30043 exited on signal 6
Feb 22 15:42:33 Elsa login[30054]: ROOT LOGIN on '/dev/pts/1'
Feb 22 15:42:35 Elsa nginx: 2020/02/22 15:42:35 [alert] 6714#6714: worker process 30053 exited on signal 6
Feb 22 15:42:35 Elsa login[30069]: ROOT LOGIN on '/dev/pts/1'
Feb 22 15:42:37 Elsa nginx: 2020/02/22 15:42:37 [alert] 6714#6714: worker process 30068 exited on signal 6
Feb 22 15:42:39 Elsa nginx: 2020/02/22 15:42:39 [alert] 6714#6714: worker process 30078 exited on signal 6
Feb 22 15:42:41 Elsa nginx: 2020/02/22 15:42:41 [alert] 6714#6714: worker process 30089 exited on signal 6
Feb 22 15:42:43 Elsa nginx: 2020/02/22 15:42:43 [alert] 6714#6714: worker process 30090 exited on signal 6
Feb 22 15:42:45 Elsa nginx: 2020/02/22 15:42:45 [alert] 6714#6714: worker process 30091 exited on signal 6
Feb 22 15:42:47 Elsa nginx: 2020/02/22 15:42:47 [alert] 6714#6714: worker process 30098 exited on signal 6
Feb 22 15:42:49 Elsa nginx: 2020/02/22 15:42:49 [alert] 6714#6714: worker process 30101 exited on signal 6
Feb 22 15:42:51 Elsa nginx: 2020/02/22 15:42:51 [alert] 6714#6714: worker process 30102 exited on signal 6
Feb 22 15:42:53 Elsa nginx: 2020/02/22 15:42:53 [alert] 6714#6714: worker process 30106 exited on signal 6
Feb 22 15:42:55 Elsa nginx: 2020/02/22 15:42:55 [alert] 6714#6714: worker process 30107 exited on signal 6
Feb 22 15:42:57 Elsa nginx: 2020/02/22 15:42:57 [alert] 6714#6714: worker process 30112 exited on signal 6
Feb 22 15:42:59 Elsa nginx: 2020/02/22 15:42:59 [alert] 6714#6714: worker process 30115 exited on signal 6
Feb 22 15:43:01 Elsa nginx: 2020/02/22 15:43:01 [alert] 6714#6714: worker process 30116 exited on signal 6
Feb 22 15:43:03 Elsa nginx: 2020/02/22 15:43:03 [alert] 6714#6714: worker process 30118 exited on signal 6

 

elsa-diagnostics-20200222-1546.zip

  • Author

Now its gone. and the plex work norm again :o

  • Community Expert

Why is your system share on disk1?

  • Author
3 minutes ago, trurl said:

Why is your system share on disk1?

Dont now xD I am new on this XD

 

Shuld I ??

  • Community Expert

appdata, domains, and system are normally kept on cache so your docker and VM performance won't be impacted by the slower parity writes on the array, and so your dockers and VMs won't keep array disks spinning.

 

Of these 3 shares, I would say system is the most important to keep on cache, because it is always in use if you have Docker and/or VM Services enabled.

 

You will have to disable Docker and VM Services since Mover can't move open files, then set system share to cache-prefer and run Mover to get it moved to cache where it belongs.

 

You can check how much of which disks each of your Shares are using by using the Compute All button on the Shares page.

  • Author
2 minutes ago, trurl said:

appdata, domains, and system are normally kept on cache so your docker and VM performance won't be impacted by the slower parity writes on the array, and so your dockers and VMs won't keep array disks spinning.

 

Of these 3 shares, I would say system is the most important to keep on cache, because it is always in use if you have Docker and/or VM Services enabled.

 

You will have to disable Docker and VM Services since Mover can't move open files, then set system share to cache-prefer and run Mover to get it moved to cache where it belongs.

 

You can check how much of which disks each of your Shares are using by using the Compute All button on the Shares page.

Hooo thx! :D 

  • Author
16 minutes ago, trurl said:

appdata, domains, and system are normally kept on cache so your docker and VM performance won't be impacted by the slower parity writes on the array, and so your dockers and VMs won't keep array disks spinning.

 

Of these 3 shares, I would say system is the most important to keep on cache, because it is always in use if you have Docker and/or VM Services enabled.

 

You will have to disable Docker and VM Services since Mover can't move open files, then set system share to cache-prefer and run Mover to get it moved to cache where it belongs.

 

You can check how much of which disks each of your Shares are using by using the Compute All button on the Shares page.

Get this:

 

Feb 22 17:27:48 Elsa root: mover: started
Feb 22 17:27:48 Elsa move: move: skip /mnt/disk1/system/docker/docker.img
Feb 22 17:27:48 Elsa shfs: set_nocow path: /mnt/cache/system
Feb 22 17:27:48 Elsa move: move: skip /mnt/disk1/system/libvirt/libvirt.img
Feb 22 17:27:48 Elsa root: find: 'system': No such file or directory
Feb 22 17:27:48 Elsa root: mover: finished

 

  • Community Expert

Did you disable the Docker and VM Services? Not the individual dockers and VMs but the services in Settings - Docker and Settings - VM Manager

  • Author
13 hours ago, trurl said:

Did you disable the Docker and VM Services? Not the individual dockers and VMs but the services in Settings - Docker and Settings - VM Manager

hoo no :)

  • 3 years later...

This is why: 

It's an issue with Unraid still present in the latest version which the team hasn't commented or acknowledged it seems.

 

 

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.