Twinkie0101

Members
  • Posts

    49
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Twinkie0101's Achievements

Rookie

Rookie (2/14)

13

Reputation

  1. Since updating to 6.12.3, docker containers are randomly shutting down. Reviewing the docker logs, I see SIGTERM received. This is happening on a few containers. I've switched from macvlan to ipvlan as recommended, but not sure why this is happening or how to resolve. Attached diagnostics as well. Appreciate any insight to figure out the cause and fix. RADARR was the last container this happened to and here is the excerpt from the log for reference: 2023-08-02 06:48:40,774 WARN received SIGTERM indicating exit request 2023-08-02 06:48:40,774 DEBG killing radarr (pid 58) with signal SIGTERM 2023-08-02 06:48:40,775 INFO waiting for radarr to die 2023-08-02 06:48:40,809 DEBG 'radarr' stdout output: [Info] Microsoft.Hosting.Lifetime: Application is shutting down... brotower-diagnostics-20230802-1000.zip
  2. Nevermind, for those wondering, you can just click on the folder icon and click 'remove'.
  3. Is there a way to delete a folder?
  4. Did a little more research and the only correlating incident I could find that may have caused the issue is my internet had a break in service right before the spamming happened. Since reboot no spamming has occurred. Thanks @JorgeB for your help!
  5. I have it set up as an active backup: Looking at my router, there has been some traffic (278MB) but eth0 is primarily (26GB) being used over the past 6 days, both are 10GB NICs,
  6. Got this notification via Fix Common Problems so posting here hoping someone smarter than me may have insight to why this happened and potential ways to avoid: Either your server has an extremely long uptime, or your syslog could be potentially being spammed with error messages. A reboot of your server will at least temporarily solve this problem, but ideally you should seek assistance in the forums and post your I rebooted the server and will share additional information but looks like something with my NICs (specifically etho2). More info that may be helpful: Motherboard: ASRockRack X570D4U-2L2T American Megatrends Inc., Version P1.20 BIOS dated: Thu 27 Aug 2020 12:00:00 AM EDT RAM: 128GBs Unraid Version: 6.11.5 CPU: AMD Ryzen 9 3900X 12-Core @ 3800 MHz Attached diagnostics as well. brotower-diagnostics-20230507-0812.zip
  7. @ich777 @Spectral Force - Thanks for the help, reinstalled server and all is working as expected.
  8. Is anyone else have trouble with 7d2d? My game is currently using Alpha 20.7 but my 7d2d container won't upgrade past Alpha 20.6 so unable to play. I've restarted the container as I thought that would download the latest release but log says it's updated to the latest. I've tried adjusting the game_id to inculde the alpha 20.7 but that didn't fix the issue either. Setting for game: Any ideas on how to solve this?
  9. @ich777Send me your Steam ID, I'll hook you up with Sons of the Forest! It's the least I can do for all these game servers you churn out and I use!
  10. I ended up installing healthchecks.io (see apps, docker available) to monitor the backups. It's not full proof, meaining it doesn't check data integrity with the backup location so I recommend periodically testing a restore plan. That said, here's a summary of what I did: In healthchecks, you create the monitoring inc conjunction with dupicacy backup. When dupicacy backup executes (based on my schedule), I have the backup send a report to a healthchecks ip address when successfully completed. (Backup tab in duplicacy you can select the checkbox send report and paste the healthchecks generated ip) Based on my backup schedule, I set timing criteria (I think it's called a grace period) in healthchecks to say let me know if you don't get a report from duplicacy in this timeframe. For example, our photos are backed up daily, so if I report isn't sent every 24 hours, i'll get the notification) I used the Apprise integration to setup pushover notifications because I didn't want emails. If a backup fails I'll get a notification. This is a high level summary but wasn't too difficult to set up. Had a little trial and error but got it working. If you go this route, let me know if you have any questions, would be glad to help you!
  11. Makes at least 3 of us, getting unable to connect. @CorneliousJD any thoughts on how to get this working?
  12. Has anyone set up pushover notifications with Duplicacy? Looked on the duplicacy forum but what I found hasn't worked for me. What I've done: Created a message.json with the following: { "BackupResult": "{{.result}}", "BeginTime": "{{.start_time}}", "TotalFiles": "{{.total_files}}", "Storage": "{{.storage_url}}", "token": token ID", "user": "user ID", "message": "Backup {{.result}}. {{.total_files}} files in {{.directory}}", "title": "Duplicacy Backup Completed" } Put the message.json file in the duplicacy appdata foler For the backup plan I used the following site to send the message: https://api.pushover.net/1/messages.json Appreciate any help for others that have set this up successfully.
  13. To close the loop for others that might experience this. Ever since I removed the plugin, my server has been rock solid. Thanks @JorgeB
  14. I have two Unraid servers (1 rackmount (primary), 1 XL desktop (backup). I would like to use all trays for array drives in my primary server, but I've always kept one drive in unassigned devices (pre-cleared) to handle any drive failures. I have additional capacity available in the backup server, so here's my question: Can I pre-clear a disk in my backup server and add to the primary server to free up the last tray?
  15. Just uninstalled the plugin. The lockup has been happening during sleep hours so I'll report back after a couple of days to see how the server operates. Thanks for the quick reply @JorgeB