quinnmc
Members
-
Joined
-
Last visited
Everything posted by quinnmc
-
For me, the real issue was the 'data' folder somehow got owned by root rather than nobody:users. I suspect that's what happened to those who setting 18(puid) and 19(guid) to 0 - that's why it worked (IIRC, 0 is the root puid/guid) - went into the appdata/deluge folder and did "chown nobody:users data" and "chmod 777 data", and everything started up again without running deluge as root user.
-
Replaced a drive - it's rebuilding (at least, it's writing a lot to the disk) - but there's not status. Now, I do have the parity check tuning plugin to modify the timing of the rebuild, mostly because the disks get hot during the rebuild, so cooling them off is good, so it's possible that this is the culprit. I'll check that once the disk finished rebuilding. qbackup-diagnostics-20250508-2129.zip
-
I have notification set up to send to a specific email address from a gmail address, and use the gmail smtp server. When crontabs send email - they're sent to the "from" gmail address. In addition - they do not use the email subject prefix, so I can't tell which of my 3 email servers actually sent the email to me. qnas-diagnostics-20250311-1008.zip
-
Trying to set up my email address for notifications - domain is mail.xxxx.org, using 465 SSL (which works for Thunderbird), and have authentication (nslookup does work for the domain). Have all but "disable SSL: clicked. I get this: 2023-10-15 14:58:03.641 -07:00 [WRN] Exception when testing Email Notifications System.ArgumentException: The domain is invalid. (Parameter 'domain') at MimeKit.Utils.MimeUtils.GenerateMessageId(String domain) at Ombi.Notifications.GenericEmailProvider.SendAdHoc(NotificationMessage model, EmailNotificationSettings settings) in /home/runner/work/Ombi/Ombi/src/Ombi.Notifications/GenericEmailProvider.cs:line 47 at Ombi.Controllers.V1.External.TesterController.Email(EmailNotificationSettings settings) in /home/runner/work/Ombi/Ombi/src/Ombi/Controllers/V1/External/TesterController.cs:line 300 Not sure where to go from here..... (Update) I'm getting email notifications properly. However, when I do a test notification I still get this error.....
-
I would like to see the ability to run a "clone" parity disk to make it less vulnerable when upgrading a parity disk. Basically designate an unassigned drive as a duplicate parity of parity 1 or parity 2 - unraid would begin cloning the drive, and updating it live as necessary. Then it would be easy to swap the clone with the real parity disk and remove the old parity drive without ever leaving the array unprotected.