ms4sman

Any news regarding the Affine template? I see it is still available in the Apps tab, but was reading this thread and seeing there were issues later last year. I just discovered Affine and was wondering about self hosting it.

Any chance you've had an opportunity to look at this issue? Still getting the error every day. Thanks!

A few days ago I started getting an error in my backup about not being able to back up the VM XMLs. I tried looking in the debug log as it said, but either I looked in the wrong file or just didn't know what I was looking at or something, but I didn't see anything meaningful. Here's my debug log ID. Hopefully you can help figure out what's going on! dc0c0c39-62e1-4b26-b37e-c610b363e470

OK this is a weirdly specific issue. Basically, under certain conditions (which I will outline in more detail below) I'm having issues with two of my containers crashing on startup. The two containers are Ghost (from cheesemarathon's repo) and Agent-DVR (from Froodle's repo, who does update the templates it seems, but is otherwise not active on the forums) Ghost seems to be a bit more inconsistent about when it has issues but Agent-DVR is pretty consistent. - Both of them start fine if I stop the container and start it again myself. - I use the current AppData Backup plugin, and depending on the order of apps being backed up, Agent-DVR has issues. It has no dependencies that I'm aware of. If it is FIRST on the list in the plugin, it will startup just fine. But from my testing so far, if it is anywhere else in the order, it will startup and then quickly crash. Sometimes if I try to start it again myself it will also crash the first time or two, but then eventually starts and works. - Ghost (seemingly) doesn't have problems with the backup plugin. At least not consistently. - If I disable the Docker system entirely in unRAID, and then re-enable it, all apps including these two seem to startup just fine and it's worth noting, don't take very long to startup all apps. - After a reboot of the entire server, all my dockers take significantly longer to start up, and I don't know why this is, but also, both Agent-DVR and Ghost seem to have issues starting up after a reboot. Again, they start up in the proper order, but then quickly crash. - I'm aware of Ghost's dependency on my MariaDB container, and I know that docker starts up and is running well before Ghost in the order. I don't think Agent-DVR relies on any other containers. I don't understand what's causing this. There are some errors in the logs of each container, but I'm not sure if they are related to the crashing or not. The only way I've been able to retrieve them is AFTER successfully starting the app back up manually, so I don't know if the errors are from before, or from the successful startup, and are unrelated. I'll include them below though. If anyone can help me troubleshoot this, I'd sure appreciate it! I don't understand why the containers work under some conditions and not under others. Here's the errors from Agent-DVR. They aren't very descriptive but seem like MAYBE they are related to the container stopping. text error warn system array login at Interop.Kernel32.SetEvent(SafeWaitHandle ) at System.Threading.EventWaitHandle.Set() at CoreLogic.Setup.<>c__DisplayClass2_0.<SetPermissions>b__2(Object sender, EventArgs e) at System.Diagnostics.Process.OnExited() at System.Diagnostics.Process.RaiseOnExited() at System.Diagnostics.Process.CompletionCallback(Object , Boolean ) at System.Threading._ThreadPoolWaitOrTimerCallback.WaitOrTimerCallback_Context(Object , Boolean ) at System.Threading._ThreadPoolWaitOrTimerCallback.WaitOrTimerCallback_Context_f(Object ) at System.Threading.ExecutionContext.RunInternal(ExecutionContext , ContextCallback , Object ) --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunInternal(ExecutionContext , ContextCallback , Object ) at System.Threading.ExecutionContext.Run(ExecutionContext , ContextCallback , Object ) at System.Threading._ThreadPoolWaitOrTimerCallback.PerformWaitOrTimerCallback(_ThreadPoolWaitOrTimerCallback , Boolean ) at System.Threading.RegisteredWaitHandle.PerformCallback(Boolean ) at System.Threading.PortableThreadPool.CompleteWait(RegisteredWaitHandle , Boolean ) at System.Threading.CompleteWaitThreadPoolWorkItem.CompleteWait() at System.Threading.CompleteWaitThreadPoolWorkItem.System.Threading.IThreadPoolWorkItem.Execute() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart() at System.Threading.Thread.StartCallback() TURN: Welcome user TURN: Welcome user TURN: Welcome user TURN: Welcome user TURN: Welcome user TURN: Welcome user TURN: Welcome user TURN: Welcome user TURN: Welcome user TURN: Welcome user TURN: Welcome user TURN: Welcome user TURN: Welcome user TURN: Welcome user TURN: Welcome user TURN: Welcome user TURN: Welcome user TURN: Welcome user TURN: Welcome user TURN: Welcome user TURN: Welcome user TURN: Welcome user Unhandled exception. System.ObjectDisposedException: Safe handle has been closed. Object name: 'SafeHandle'. at System.Runtime.InteropServices.SafeHandle.DangerousAddRef(Boolean& ) at System.StubHelpers.StubHelpers.SafeHandleAddRef(SafeHandle , Boolean& ) at Interop.Kernel32.SetEvent(SafeWaitHandle ) at System.Threading.EventWaitHandle.Set() at CoreLogic.Setup.<>c__DisplayClass2_0.<SetPermissions>b__2(Object sender, EventArgs e) at System.Diagnostics.Process.OnExited() at System.Diagnostics.Process.RaiseOnExited() at System.Diagnostics.Process.CompletionCallback(Object , Boolean ) at System.Threading._ThreadPoolWaitOrTimerCallback.WaitOrTimerCallback_Context(Object , Boolean ) at System.Threading._ThreadPoolWaitOrTimerCallback.WaitOrTimerCallback_Context_f(Object ) at System.Threading.ExecutionContext.RunInternal(ExecutionContext , ContextCallback , Object ) --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunInternal(ExecutionContext , ContextCallback , Object ) at System.Threading.ExecutionContext.Run(ExecutionContext , ContextCallback , Object ) at System.Threading._ThreadPoolWaitOrTimerCallback.PerformWaitOrTimerCallback(_ThreadPoolWaitOrTimerCallback , Boolean ) at System.Threading.RegisteredWaitHandle.PerformCallback(Boolean ) at System.Threading.PortableThreadPool.CompleteWait(RegisteredWaitHandle , Boolean ) at System.Threading.CompleteWaitThreadPoolWorkItem.CompleteWait() at System.Threading.CompleteWaitThreadPoolWorkItem.System.Threading.IThreadPoolWorkItem.Execute() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart() at System.Threading.Thread.StartCallback() Unhandled exception. System.ObjectDisposedException: Safe handle has been closed. Object name: 'SafeHandle'. at System.Runtime.InteropServices.SafeHandle.DangerousAddRef(Boolean& ) at System.StubHelpers.StubHelpers.SafeHandleAddRef(SafeHandle , Boolean& ) at Interop.Kernel32.SetEvent(SafeWaitHandle ) at System.Threading.EventWaitHandle.Set() at CoreLogic.Setup.<>c__DisplayClass2_0.<SetPermissions>b__2(Object sender, EventArgs e) at System.Diagnostics.Process.OnExited() at System.Diagnostics.Process.RaiseOnExited() at System.Diagnostics.Process.CompletionCallback(Object , Boolean ) at System.Threading._ThreadPoolWaitOrTimerCallback.WaitOrTimerCallback_Context(Object , Boolean ) at System.Threading._ThreadPoolWaitOrTimerCallback.WaitOrTimerCallback_Context_f(Object ) at System.Threading.ExecutionContext.RunInternal(ExecutionContext , ContextCallback , Object ) --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunInternal(ExecutionContext , ContextCallback , Object ) at System.Threading.ExecutionContext.Run(ExecutionContext , ContextCallback , Object ) at System.Threading._ThreadPoolWaitOrTimerCallback.PerformWaitOrTimerCallback(_ThreadPoolWaitOrTimerCallback , Boolean ) at System.Threading.RegisteredWaitHandle.PerformCallback(Boolean ) at System.Threading.PortableThreadPool.CompleteWait(RegisteredWaitHandle , Boolean ) at System.Threading.CompleteWaitThreadPoolWorkItem.CompleteWait() at System.Threading.CompleteWaitThreadPoolWorkItem.System.Threading.IThreadPoolWorkItem.Execute() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart() at System.Threading.Thread.StartCallback() And here's what I can capture from Ghost. It doesn't really seem related. Just seems like my template is likely out of date and using some deprecated stuff. text error warn system array login details: Usage of <code>{{@labs.members}}</code> is no longer supported and should be replaced with <code>{{@site.members_enabled}}</code><br>Find more information about the <code>@site</code> property <a href="https://ghost.org/docs/themes/helpers/site/" target=_blank>here</a>. regex: helper: {{@labs.members}} failures: - ref: default.hbs message: Please remove or replace {{@labs.members}} from this template - ref: partials/site-nav.hbs message: Please remove or replace {{@labs.members}} from this template - ref: post.hbs message: Please remove or replace {{@labs.members}} from this template code: GS001-DEPR-LABS-MEMBERS - fatal: false level: error rule: Replace <code>{{@site.lang}}</code> with <code>{{@site.locale}}</code> details: The usage of <code>{{@site.lang}}</code> is no longer supported and shoud be replaced with <code>{{@site.locale}}</code>.<br>Find more information about the <code>@site.locale</code> property <a href="https://ghost.org/docs/themes/helpers/site/" target=_blank>here</a>. regex: helper: {{@site.lang}} failures: - ref: default.hbs message: Please remove or replace {{@site.lang}} from this template code: GS001-DEPR-SITE-LANG - fatal: false level: error rule: Not all page features are being used details: <b>This error only applies to pages created with the Beta editor.</b> Some page features used by Ghost via the <code>{{@page}}</code> global are not implemented in this theme.&nbsp;Find more information about the <code>{{@page}}</code> global <a href="https://ghost.org/docs/themes/helpers/page/" target=_blank>here</a>. failures: - ref: page.hbs message: @page.show_title_and_feature_image is not used rule: GS110-NO-MISSING-PAGE-BUILDER-USAGE code: GS110-NO-MISSING-PAGE-BUILDER-USAGE warnings: (empty array) ---------------------------------------- ThemeValidationError: The currently active theme "casper-custom" has errors, but will still work. at Object.getThemeValidationError (/var/lib/ghost/versions/5.76.0/core/server/services/themes/validate.js:142:12) at module.exports.loadAndActivate (/var/lib/ghost/versions/5.76.0/core/server/services/themes/activate.js:30:35) at async initServicesForFrontend (/var/lib/ghost/versions/5.76.0/core/boot.js:192:5) at async bootGhost (/var/lib/ghost/versions/5.76.0/core/boot.js:513:31)

I will check on the timeout and try increasing it. Any suggestions regarding when it tries to restart the container and detects it is already started, but then in the morning it is clearly not started? Seems like for some reason it's being told the container is running when it isn't? I couldn't find anything about this in my searching online. Only things I saw about "already running" were in regards to the old version of the plugin and had to do with the auto-update.

Hi there. I used to use the old AppData Backup and Restore way back, and got rid of it a while ago, and then just recently started using this new AppData Backup plugin again. I'm trying to use it in combination with Duplicacy in the way I understand to be correct. Basically AppData Backup runs first, and backs up my AppData to another share called Backups. Then Duplicacy backs up that share later to Backblaze B2 storage. I have AppData Backup configured to stop and backup each container and start it again one at a time. I'm having some issues with the starting and stopping of containers that I never seemed to have with the old plugin. Looking in the logs, I see that many of the containers are having to be force stopped with 'docker stop' due to them not seeming to respond to the regular stop. I'm not sure if this just means they are taking too long to stop the normal way so the plugin gets tired of waiting or what. But I notice that it seems like many of the containers that have trouble stopping, then when its time to start, have trouble starting and end up with a message about already being started. This backup happens while I'm asleep so I dont know for sure if they are or not. All I know is that when I wake up in the morning, I usually have down notifications from UptimeKuma and sure enough, a handful of containers are stopped. But according to the logs, those containers were already started when it went to start them. I don't have AppData Backup configured to update any containers so that shouldn't be it. It's usually same few containers every time. Always Ghost and Agent DVR, and a couple others. This morning Glances was also a problem child though it hasn't been in the past. Oddly, not ALL the containers in the logs that had issues are not started Jellyfin for example had issues stopping AND starting. But it was running just fine this morning. But all the ones that are not started ARE ones that were logged as having issues. I'll include the logs below. If anyone can help out here, I'd sure appreciate it. I don't like having my containers down for hours until I wake up and then having to manually start them first thing in the morning. Debug log ID is 3ec2e7eb-9fab-42bc-8198-712b82790c04 Thanks in advance for any help! ab.log

Well my question may be answered...I switched to SATA to see if there was any performance difference and now I can't switch back to VirtIO. I'm not sure how I had it working before, but I definitely had virtio selected and it was definitely working...but now it doesn't recognize my SSD. I have the virtio driver installed on Windows too, because like I said, it worked before... Oh well, guess SATA is my answer...

I'm passing through an SSD from Unassigned Devices to my VM using the by-id technique using the ID starting with "ata-". Should I use SATA or VirtIO for this? I have the virtio drivers installed in Windows and I've been using VirtIO until now, but I'm not sure if that is correct or not. Does it matter? When I use VirtIO drivers, it shows up as an HDD in task manager, and as a "thin provisioned device" under the optimization window. If I use SATA it shows as an HDD in both places. I find lots of info about this for vdisks but I haven't been able to find a straight answer on this for passthrough disks. Thank you!

Hi all. I recently upgraded my unRAID server from a Ryzen 1700 to an 5900X. I kept my same motherboard for reference, a Gigabyte X370 board, but upgraded the BIOS to the latest to get support for the 5900X. I've had problems ever since upgrading with the CPU temp being crazy high with any load at all (say 10-20%). If all my dockers and VMs are stopped and CPU usage is a couple of percent, CPU temps are OK. 40-50s. About what I'd usually get on my old CPU with all my stuff running. But again, this is with everything stopped. But if everything is running and CPU usage is around 20-30%, my temps go wild and are in the 70's or 80's. Under a heavy load they barely go any higher which is strange too. I finally tracked this to the AMD Performance Boost setting in Tips and Tweaks. I've had this on for a long time, including with my old CPU and had no issues. But turning it off, my temps go back to where I'd expect. 40-50's, even with everything running. Turning it back on, temps shoot back up again. I'm not super familiar with this feature, is this how it's meant to work? I know this isn't really unRAID related, it's a CPU feature but maybe someone knowledgeable here can explain. Should this feature really cause a 30 degree delta whenever there's even a light 10-20% load on the CPU? This seems kind of reckless... Thanks in advance to anyone who can help!

Excellent, glad to hear that the issue is known and being worked on. I'll look forward to the 1.5.1 update and the following update to the container. In the meantime, I'm glad to have found the temporary solution of using no password, thanks to the others here with the same problem.

Hey @SpaceInvaderOne, I know this is a very old thread, but if you're still open to helping, I could use some! I downloaded your disk image for Win 98 and followed the instructions, but every time I try to boot it up, it just tells me that the disk isn't bootable. Any ideas? Does this still work for you on newer unRAID versions? Thanks!

Something seems to have corrupted the database on my Guacamole install. It was fine yesterday, but I think it may have been updated overnight by the Auto Update plugin, and this morning I just get the generic error page. Removing the AppData for it and letting it all be recreated gets me a working Guac install, but if I place the old database files back in place, it stops working again. There doesn't appear to be anything strange in the logs when I view them from right-clicking the container and choosing Logs. Any ideas what to do here? Can I at least back up my connection settings and transfer them to a new installation? I'd really rather not have to re-create ALL my connections. Thanks! EDIT: I was able to resolve this. I'm still not really sure what happened, but ultimately I did a sqldump to a file, deleted all the databases and started the container to remake them, then imported the dump back in and now things seem back to normal...

I think I may have figured it out. It seems that if when Ghost starts up, it can't reach it's SQL server, it just goes back down after a couple minutes of trying. So I have daily backups happening that shut down all dockers, then restart them after. I'm betting that MariaDB isn't coming back up quick enough sometimes, and Ghost just gives up trying and goes back down. All the crashes seem to be at 7 AM sharp, in the logs, which with the offset calculated, is 5 hours ahead, so 2 AM which is when my backup is scheduled. I'm going to try a few things to get around this.

It's certainly not impossible that auto-update is related, but I'm pretty sure it's gone down even when I turned Ghost off in the auto-updater. It also has definitely crashed lots of times when there was no update. It happened again today though, and looking at the log, there's loads of red errors about losing connection to the database, or other database related stuff. I'm using MariaDB but that container hasn't been going down, so I'm wondering why it's losing its connection to it off and on. I'll do some more digging...

Hey, so I've got Ghost installed and it is working well for me, but every few days or so, I notice the Docker has stopped (crashed I assume). I don't notice anything odd in the logs at the time of the shutdown last I looked, although I don't have one right now (I'll grab one as soon as it happens again). Initially I thought it was happening because I had a script in User Scripts that killed all Node processes, which was definitely nuking Ghost, but I have removed that so that's not it anymore, but I'm not sure what else would be causing it to seemingly crash randomly. It also seems to sometimes not come back online after an Auto-Update from the autoupdate community apps plugin, but other times it does. Is this anything familiar to anyone, or just me? I'll keep looking for processes that might be killing Node processes or something. Thanks!