TheGleaner

They no longer have a supported app for android is my understanding when I looked into them and the community response of the various forks to replace the app have been...tepid at best.

For close to a decade I have been using Resilio Sync and its many other names as basically a live backup utility(dumping everything on the UnRaid server). It appears it is dead and I have tried for months to get it reliably working again. What do any of you recommend for a similar program, that works on both Android and Windows systems? Something I can just set it as "backup the entire drive to this folder on this server, and backup all changes as they are made to all files and never delete anything". It really is a shame it appears to be dead as I really liked the ability to, say, take a picture on my phone and within a minute or so it would be on the unraid server as a backup, regardless of where I was, as long as I had internet it just worked. NOTE: NOT LIMITED TO PHOTOS.

This may help someone in the future: https://stackoverflow.com/questions/55279515/elasticsearchexception-failed-to-bind-service-error You need to make sure that the directory on the host machine is owned by 1000:1000. Run the following command. sudo chown 1000:1000 <directory you wish to mount>

I will try it if it happens again, I guess. What is "nchan" and the shared memory it is referencing?

As of right now, it appears to be yes, but the entire server just had an issue, as seen here. I don't know if they are related.

For what it is worth, The VM freezing issue is still an issue, as I reported here, in case it is related.

This is from immediately after the restart, via the gui.

I did copy the boot/logs folder after it restarted, but I assume those are not for posting to the public.

Apr 4 22:14:27 Server1 nginx: 2025/04/04 22:14:27 [alert] 12745#12745: worker process 4033852 exited on signal 6 Apr 4 22:14:29 Server1 nginx: 2025/04/04 22:14:29 [alert] 12745#12745: worker process 4033853 exited on signal 6 Apr 4 22:14:29 Server1 nginx: 2025/04/04 22:14:29 [alert] 12745#12745: worker process 4033860 exited on signal 6 Apr 4 22:14:31 Server1 nginx: 2025/04/04 22:14:31 [alert] 12745#12745: worker process 4033861 exited on signal 6 Apr 4 22:14:31 Server1 nginx: 2025/04/04 22:14:31 [alert] 12745#12745: worker process 4033898 exited on signal 6 Apr 4 22:14:33 Server1 nginx: 2025/04/04 22:14:33 [alert] 12745#12745: worker process 4033905 exited on signal 6 Apr 4 22:14:33 Server1 nginx: 2025/04/04 22:14:33 [alert] 12745#12745: worker process 4034122 exited on signal 6 Apr 4 22:14:35 Server1 nginx: 2025/04/04 22:14:35 [alert] 12745#12745: worker process 4034123 exited on signal 6 Apr 4 22:14:35 Server1 nginx: 2025/04/04 22:14:35 [alert] 12745#12745: worker process 4034131 exited on signal 6 Apr 4 22:14:36 Server1 nginx: 2025/04/04 22:14:36 [crit] 4034132#4034132: ngx_slab_alloc() failed: no memory Apr 4 22:14:36 Server1 nginx: 2025/04/04 22:14:36 [error] 4034132#4034132: shpool alloc failed Apr 4 22:14:36 Server1 nginx: 2025/04/04 22:14:36 [error] 4034132#4034132: nchan: Out of shared memory while allocating message of size 19959. Increase nchan_max_reserved_memory. Apr 4 22:14:36 Server1 nginx: 2025/04/04 22:14:36 [error] 4034132#4034132: *1264941 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Apr 4 22:14:36 Server1 nginx: 2025/04/04 22:14:36 [error] 4034132#4034132: MEMSTORE:01: can't create shared message for channel /disks Apr 4 22:14:37 Server1 nginx: 2025/04/04 22:14:37 [crit] 4034132#4034132: ngx_slab_alloc() failed: no memory Apr 4 22:14:37 Server1 nginx: 2025/04/04 22:14:37 [error] 4034132#4034132: shpool alloc failedI wasn't having a problem, until suddenly it became unresponsive. There are pages of the signal 6 error, then pages of the memory error. I can not get diagnostics as that results in nothing happening and but the log complaining about no memory for diagnostics. The web UI will not fully load either. Currently I am waiting here:

Currently TBD You're going to have to elaborate on that, the first part anyways. For the second, the latest that is supported by the OS usually. The third, I found that out the hard way about a year ago, everything from dockers to VMs are excluded from using the first core/thread pair to my knowledge anyways.

More frequent, but shorter, freezes occur. It does appear to be related to disk usage, as when the VM starts using its disks, that greatly increases the frequency and chances of the freezing.

After the update to 7.0.0 a few VMs that had worked fine since 6.9.2 began to randomly freeze, then unfreeze after minutes and continue to function like nothing had ever happened. This appears to happen with windows 7, 8.1, and 10 VMs. There doesn't appear to be any reason or cause, as it will happen in VMs running software or freshly started and idling. At first I thought it may be just the viewing system being unresponsive, until I relaunched it a few times and that did not change anything, then I got sidetracked and it became functional/unfroze. Then when one VM froze, one that is functioning as a backup system for my security cameras, I tried accessing the webpage for the security software (Blue Iris) and I could, but it ran very slowly and lagged badly, along with the video streams becoming a slideshow with up to minutes between frames, until the VM unfroze again. The only thing that appears to happen in two threads max out on the dashboard screen when it happens. It does not seem to matter if the VMs are on the cache drive or on the array, or if the parity check is running or not.

No apparent problem from 6.12.14 to 6.12.15 then to 7. 4-3-2025: VMs are freezing, updating to 701 doesn't help either.

# 1 Background long Failed in segment --> 7

I went on a trip and as Murphy's law dictates, one drive failed. I sent a few TBs of video back while away and I came back to the same failed and disabled drive, along with an enabled but has errors, secondary parity drive. A thing to note is the erroring parity drive only errors when parity checking and gets the same number every time: 502. I have two, larger, replacement drives preclearing and being tested now, but my question is what do I replace and in what order? There was a power flicker recently, so I don't know how helpful the diagnostics will be, but they are attached anyways.