February 23, 20251 yr Hi All I seem to have problem with the mover again (I did remove the old plugin ad that solved the problem, but after upgrading to v7.0.0 I have problem again) prsssing the Mover button and nothing happens? If I do a mover.old start I can force it to run, just not running by itself, my cache runs full. Se Diagnostic below. And some memory problem? (I have the cache plugin installed and I have 128G of RAM with a load of 50-60%): nginx: 2025/02/23 18:03:13 [error] 32286#32286: MEMSTORE:01: can't create shared message for channel /disks And a new error in my e-mail from the Unraid server: Quote warning: Potentially dangerous mode on unraid-api: 0666 error: Ignoring unraid-api because it is writable by group or others. error: found error in file unraid-api, skipping warning: Potentially dangerous mode on unraid-api.patch: 0666 error: Ignoring unraid-api.patch because it is writable by group or others. error: found error in file unraid-api.patch, skipping Its allot of problems all at once, a reboot and its running for 3 days again. Attached my logs. Hope some one can help me? 🙂 Br Casperse diagnostics-20250223-1823.zip
February 23, 20251 yr Community Expert Remove the Mover Tuning plugin and try again. The version of the plugin you have installed is not compatible with Unraid 7.0.0
February 25, 20251 yr Author On 2/23/2025 at 6:54 PM, itimpi said: Remove the Mover Tuning plugin and try again. The version of the plugin you have installed is not compatible with Unraid 7.0.0 I removed the "CA Mover Tuning" and the mover works agaon now! Thanks Any input to fixing the error reported by e-mail from UNRAID? : warning: Potentially dangerous mode on unraid-api: 0666 error: Ignoring unraid-api because it is writable by group or others. error: found error in file unraid-api, skipping warning: Potentially dangerous mode on unraid-api.patch: 0666 error: Ignoring unraid-api.patch because it is writable by group or others. error: found error in file unraid-api.patch, skipping
February 25, 20251 yr Community Expert 32 minutes ago, casperse said: Any input to fixing the error reported by e-mail from UNRAID? : Update the Connect plugin to latest.
February 26, 20251 yr Author There wasn't any update so I just deleted the plugin and the mover works again. But the error below is back and the UI for the Docker section is unresponsive? I have included a new diagnostic file below (I haven't installed any new dockers! but maybe some update have broken something? or the mover running is generating these errors?) diagnostics-20250226-1020.zip
February 26, 20251 yr Community Expert Solution 1 hour ago, casperse said: so I just deleted the plugin and the mover works again. The update was for the Connect plugin, those errors are not from the mover plugin, though the mover not working is usually that. server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Feb 23 17:53:58 PLEXZONE nginx: 2025/02/23 17:53:58 [error] 32286#32286: MEMSTORE:01: can't create shared message for channel /disks Feb 23 17:53:59 PLEXZONE nginx: 2025/02/23 17:53:59 [crit] 32286#32286: ngx_slab_alloc() failed: no memory Feb 23 17:53:59 PLEXZONE nginx: 2025/02/23 17:53:59 [error] 32286#32286: shpool alloc failed Feb 23 17:53:59 PLEXZONE nginx: 2025/02/23 17:53:59 [error] 32286#32286: nchan: Out of shared memory while allocating message of size 22132. Increase nchan_max_reserved_memory. For these, try upgrading to 7.0.1, there's a change that may help.
February 27, 20251 yr Author Yes it seems that v7.0.1 helped, but after update I keep getting this: Any idea why the Flash backup stopped working everything else looks fine 🙂
February 28, 20251 yr Author Yes update buttom more than once just keep turning the "time" icon for a day Seems its working now. Maybe some connectivity problems to connect? Edited February 28, 20251 yr by casperse
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.