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.

HELP: After Updating to rc8, Mover no longer works, even Manually

Featured Replies

Hi,

After updating to rc8 from r6 the mover stopped working, on rc 6 i had same errors in the log but mover worked.

 

More info: Virtualization and docker always disabled, I rebooted the PC bunch of times.

I have 2 cache pools, main cache is x4 1tb SSD RAID5 BTRFS and 500gb encrypted SSD for the single encrypted HDD that I have.

 

I always run the mover manually, this PC is either off or sleeps most of the time, so when im done copying i run mover and let it do its thing, saves me time.

 

This is from the log

4 04:30:57 12700 move: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 214: /usr/local/sbin/move: No such file or directory

 

Jun 14 04:41:11 12700 nginx: 2023/06/14 04:41:11 [error] 10027#10027: *2128 connect() to unix:/var/run/syslog.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.50.4, server: , request: "GET /webterminal/syslog/token HTTP/2.0", upstream: "http://unix:/var/run/syslog.sock:/token", host: "192.168.50.2", referrer: "https://192.168.50.2/webterminal/syslog/"
Jun 14 04:41:11 12700 nginx: 2023/06/14 04:41:11 [error] 10027#10027: *2575 connect() to unix:/var/run/syslog.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.50.4, server: , request: "GET /webterminal/syslog/ws HTTP/1.1", upstream: "http://unix:/var/run/syslog.sock:/ws", host: "192.168.50.2"
Jun 14 04:42:24 12700 nginx: 2023/06/14 04:42:24 [error] 10027#10027: *3118 connect() to unix:/var/run/syslog.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.50.4, server: , request: "GET /webterminal/syslog/token HTTP/2.0", upstream: "http://unix:/var/run/syslog.sock:/token", host: "192.168.50.2", referrer: "https://192.168.50.2/webterminal/syslog/"
Jun 14 04:42:24 12700 nginx: 2023/06/14 04:42:24 [error] 10027#10027: *3138 connect() to unix:/var/run/syslog.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.50.4, server: , request: "GET /webterminal/syslog/ws HTTP/1.1", upstream: "http://unix:/var/run/syslog.sock:/ws", host: "192.168.50.2"
Jun 14 04:42:27 12700 nginx: 2023/06/14 04:42:27 [error] 10027#10027: *3168 connect() to unix:/var/run/syslog.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.50.4, server: , request: "GET /webterminal/syslog/ws HTTP/1.1", upstream: "http://unix:/var/run/syslog.sock:/ws", host: "192.168.50.2"

 

These 2 lines pop up immediately when i press the MOVE button, on RC8 and back on RC6 too, but on RC6 it at least worked.

 

Jun 14 05:09:09 12700 nginx: 2023/06/14 05:09:09 [error] 10027#10027: *18525 connect() to unix:/var/run/syslog.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.50.4, server: , request: "GET /webterminal/syslog/token HTTP/2.0", upstream: "http://unix:/var/run/syslog.sock:/token", host: "192.168.50.2", referrer: "https://192.168.50.2/webterminal/syslog/"
Jun 14 05:09:09 12700 nginx: 2023/06/14 05:09:09 [error] 10027#10027: *18997 connect() to unix:/var/run/syslog.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.50.4, server: , request: "GET /webterminal/syslog/ws HTTP/1.1", upstream: "http://unix:/var/run/syslog.sock:/ws", host: "192.168.50.2"

 

 

EDIT3: I reverted back to RC6, mover works now, but i still get these 2 errors the moment i press the MOVE button

 

Jun 14 05:40:17 12700 emhttpd: shcmd (976): /usr/local/sbin/mover &> /dev/null &
Jun 14 05:40:55 12700 nginx: 2023/06/14 05:40:55 [error] 18366#18366: *2110 connect() to unix:/var/run/syslog.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.50.4, server: , request: "GET /webterminal/syslog/token HTTP/2.0", upstream: "http://unix:/var/run/syslog.sock:/token", host: "192.168.50.2", referrer: "https://192.168.50.2/webterminal/syslog/"
Jun 14 05:40:55 12700 nginx: 2023/06/14 05:40:55 [error] 18366#18366: *3832 connect() to unix:/var/run/syslog.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.50.4, server: , request: "GET /webterminal/syslog/ws HTTP/1.1", upstream: "http://unix:/var/run/syslog.sock:/ws", host: "192.168.50.2"

Diagnostics

 

Edited by Hexenhammer

Solved by JorgeB

  • Hexenhammer changed the title to HELP: After Updating to rc8, Mover no longer works, even Manually
  • Community Expert
  • Solution

Try uninstalling the mover tuning plugin, or rebooting in safe mode.

  • Author
6 hours ago, JorgeB said:

Try uninstalling the mover tuning plugin, or rebooting in safe mode.

 

Uninstall mover tuning, update back to rc8?

 

Do you know whats all the "unix:/var/run/syslog.sock failed" errors are?

 

Thanks

  • Community Expert
9 minutes ago, Hexenhammer said:

Do you know whats all the "unix:/var/run/syslog.sock failed" errors are?

Nope, post new diags after uninstalling the plugin or booting in safe mode.

  • Author
6 hours ago, JorgeB said:

Nope, post new diags after uninstalling the plugin or booting in safe mode.

So far after uninstalling the plugin and updating to rc8, mover works fine, and so far no such errors in the log, if they appear ill open a new post, for now this is solved and for other people that have such issues the solution is to uninstall the plugin or wait for update.

 

Thanks

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.