Everything posted by TexasUnraid
-
[Support] binhex - qBittorrentVPN
It would be cool if openvpn could rotate through the ovpn files until it finds a working server in situations like this. I am having to keep the files in another folders and move them into qbittorrent 1 at a time till I find one that works right now. I had to find a new server this morning and ended up getting france to work, if it gives me trouble I will try spain.
-
Securely auto-start 6.8+ Encrypted array using SFTP from your phone OR quick and dirty auto-start
lol, no worries
-
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
If your drive is called "Backup", Then replace "mountpoint" with "Backup" in the command or it will not work.
-
btrfs incremental snapshots
I am sure this exists but no idea where and it is way over my head. I know I found some details on how to make scripts use the unraid notification system purely by chance at some point and it is actually quite simple to do. Got to think there is a thread about the plugin system floating around as well. It could be from a decade ago though.
-
[Support] Data-Monkey - netdata
The DBengine is working good now, saving data as expected. Although I am now getting a new issue, my docker stats stopped showing up? I used to be able to see all the stats for my dockers but now they are simply missing? I have restarted netdata a few times but they are still gone. Any ideas?
-
btrfs incremental snapshots
Yep, to be honest I am shocked that a server OS is lacking such basic features as snapshots as a built in feature. Really surprised a plugin does not exists for it either.
-
Securely auto-start 6.8+ Encrypted array using SFTP from your phone OR quick and dirty auto-start
Yep that is it^ It is listed above in the OP as well
-
[Support] Data-Monkey - netdata
Ok, after it ran for awhile the dbengine compression level suddenly jumped up to 77%. So looks like it is working as expected!
-
[Support] Data-Monkey - netdata
Ok, I just wiped the entire netdata docker and did a clean install and now it seems to be using the dbengine by default? I can't explain it, I had not messed with anything on the old container prior to this. I then made the same changes I did before, mapping the config and dbengine folder to appdata and bingo, seems to be working. Will have to wait and see if it holds onto the data for longer this time but database files are showing up in the folder. Although I did notice that under dbengine compression savings ratio, it shows 0? Seems from reading that it should be at least 50% or higher? Any idea why it is not being compressed? according to the calculator without compression it is going to eat a LOT of space.
-
[Support] Data-Monkey - netdata
Yes, although in my case the netdata file was empty by default and asked me to wget it. I did that and it was then filled but the default memory mode was save and it did not include the page cache or disk space options in the file. I manually added then though but still got the same error.
-
[Support] Data-Monkey - netdata
That is the container I am using. This is the error I get after changing the netdata.conf file to enable dbengine: 2020-09-12 16:46:41: netdata FATAL : MAIN : RRD_MEMORY_MODE_DBENGINE is not supported in this platform. # : Invalid argument 2020-09-12 16:46:41: netdata INFO : MAIN : EXIT: netdata prepares to exit with code 1... 2020-09-12 16:46:41: netdata INFO : MAIN : EXIT: cleaning up the database... 2020-09-12 16:46:41: netdata INFO : MAIN : Cleaning up database [0 hosts(s)]... I mapped the dbengine to appdata along with the etc/netdata folder (after coping it to appdata first) to make updating the netdata.conf easier, never have been able to figure out the text editor in alpine.
-
[Support] Data-Monkey - netdata
Did more research and it seems that the docker is setup to use ram for the logs and for some reason the dbengine option is disabled? I tried to enable it but it just errors and says it is not supported on this platform? Anyway to enable it? I would like to keep a few days of logs if possible.
-
[Support] binhex - qBittorrentVPN
Cool, thanks for the heads up, switched to France as well and it is working again.
-
[Support] binhex - qBittorrentVPN
I started getting the same error today as well, at one point I saw an error saying that the port forward API was down so I disabled port forwarding and that got it working again but naturally no real connections now but at least the GUI starts up.
-
[Support] binhex - qBittorrentVPN
Yeah, I found it strange as well, best guess is that increased load on the Montreal server has causes it to either run out of ports or crash the port forwarding.
-
[Support] binhex - qBittorrentVPN
After messing with it, it seems that the Montreal server is down or something. I tried Vancouver and it worked but in the past I saw significantly worse performance with it but should work for now. Will try Montreal again at some point. It is still really strange how binhex sabnzb worked with Montreal but qbittorrent did not. I guess that sab does not use port forwarding and that was causing the issue? Could be so many people have moved to Montreal there are no ports left?
-
[Support] binhex - qBittorrentVPN
Changing to nextgen servers and disabling port forwarding got it working for now but as we know port forwarding is much better. Might try some different servers tomorrow to see if any of them have port forwarding working. Did I read something earlier about someone getting port forwarding working on next gen servers?
-
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
Have you restarted the server? Try that first if not. "samba restart" from the terminal might also do it.
-
[Support] binhex - qBittorrentVPN
The issue is limited to qbittorrent. I have 2 other dockers using the exact same PIA connection files and they are both working fine, including binhex-sabnzbdvpn which I would think uses the same connection setup
-
[Support] binhex - qBittorrentVPN
I made the mistake of updating all dockers and am seeing a similar issue today as well. It was working fine before the update but after updating and restarting I an now seeing this 2020-09-05 16:18:18,585 DEBG 'start-script' stdout output: Sat Sep 5 16:18:18 2020 Initialization Sequence Completed 2020-09-05 16:18:18,710 DEBG 'start-script' stdout output: [info] Port forwarding is enabled [info] Checking endpoint 'ca-montreal.privateinternetaccess.com' is port forward enabled... 2020-09-05 16:18:19,641 DEBG 'start-script' stdout output: [info] PIA endpoint 'ca-montreal.privateinternetaccess.com' is in the list of endpoints that support port forwarding 2020-09-05 16:18:19,641 DEBG 'start-script' stdout output: [info] List of PIA endpoints that support port forwarding:- [info] ca-toronto.privateinternetaccess.com [info] ca-montreal.privateinternetaccess.com [info] ca-vancouver.privateinternetaccess.com [info] de-berlin.privateinternetaccess.com [info] de-frankfurt.privateinternetaccess.com [info] swiss.privateinternetaccess.com [info] france.privateinternetaccess.com [info] czech.privateinternetaccess.com 2020-09-05 16:18:19,641 DEBG 'start-script' stdout output: [info] spain.privateinternetaccess.com [info] ro.privateinternetaccess.com [info] israel.privateinternetaccess.com [info] Attempting to get dynamically assigned port... 2020-09-05 16:18:19,641 DEBG 'start-script' stdout output: [info] PIA endpoint 'ca-montreal.privateinternetaccess.com' is in the list of endpoints that support port forwarding 2020-09-05 16:18:19,641 DEBG 'start-script' stdout output: [info] List of PIA endpoints that support port forwarding:- [info] ca-toronto.privateinternetaccess.com [info] ca-montreal.privateinternetaccess.com [info] ca-vancouver.privateinternetaccess.com [info] de-berlin.privateinternetaccess.com [info] de-frankfurt.privateinternetaccess.com [info] swiss.privateinternetaccess.com [info] france.privateinternetaccess.com [info] czech.privateinternetaccess.com 2020-09-05 16:18:19,641 DEBG 'start-script' stdout output: [info] spain.privateinternetaccess.com [info] ro.privateinternetaccess.com [info] israel.privateinternetaccess.com [info] Attempting to get dynamically assigned port... 2020-09-05 16:18:19,898 DEBG 'start-script' stdout output: [warn] Exit code '56' from curl != 0 or no response body received [info] 12 retries left [info] Retrying in 10 secs... 2020-09-05 16:18:30,019 DEBG 'start-script' stdout output: [warn] Exit code '56' from curl != 0 or no response body received [info] 11 retries left [info] Retrying in 10 secs... 2020-09-05 16:18:30,019 DEBG 'start-script' stdout output: [warn] Exit code '56' from curl != 0 or no response body received [info] 11 retries left [info] Retrying in 10 secs... 2020-09-05 16:18:40,143 DEBG 'start-script' stdout output: [warn] Exit code '56' from curl != 0 or no response body received [info] 10 retries left [info] Retrying in 10 secs... It just keeps repeating this and qbittorrent never starts. Is there a way to revert the update?
-
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
If you disconnect the drive from the system and then move the slider from "simple" to "complete" on the UD section it should show you a list of saved drives. Click the X on the right side and it will delete the saved settings and should let you rename it.
-
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
Sorry to keep posting but figured I would toss what information I had here while I was thinking about it. After unmounting, disconnecting and reconnecting the drive (properly mounted and unmounted prior to this) I now get this error when trying to mount it again: Sep 2 12:04:21 NAS unassigned.devices: Adding disk '/dev/mapper/Personal_Data_Backup'... Sep 2 12:04:24 NAS unassigned.devices: Mount drive command: /sbin/mount -o rw,noatime,nodiratime '/dev/mapper/Personal_Data_Backup' '/mnt/disks/Personal_Data_Backup' Sep 2 12:04:24 NAS kernel: /dev/mapper/Personal_Data_Backup: Can't open blockdev Sep 2 12:04:24 NAS unassigned.devices: Mount of '/dev/mapper/Personal_Data_Backup' failed. Error message: mount: /mnt/disks/Personal_Data_Backup: special device /dev/mapper/Personal_Data_Backup does not exist. Sep 2 12:04:24 NAS unassigned.devices: Partition 'Personal_Data_Backup' could not be mounted. Sep 2 12:04:24 NAS unassigned.devices: Issue spin down timer for device '/dev/sdq' Once again the only fix is to reboot yet again. This happens during backups when I need to connect a few different drives during the process although I have seen many different errors, which is why I didn't report it before, was hoping to find a pattern. So far noting solid I can figure out.
-
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
I tried putting the echo in the script to test it out but nothing shows up in the log file? Tested a few other commands and without explicitly telling it to echo into the log file nothing ends up in the log. I would really need to see the output if I made snapshots automatic, is this intended behavior or am I doing something wrong? I assumed it would work more or less like user scripts?
-
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
I tried stopping array and mounting the drive after adding the password to the UD settings but the luks error went away but it would still not mount and the partition is missing from the drop down menu for the drive Sep 2 11:15:15 NAS unassigned.devices: Adding disk '/dev/sdq1'... Sep 2 11:15:15 NAS unassigned.devices: No filesystem detected on '/dev/sdq1'. Sep 2 11:15:15 NAS unassigned.devices: Partition '' could not be mounted. Sep 2 11:15:15 NAS unassigned.devices: Issue spin down timer for device '/dev/sdq'. Going to reboot now and see if it starts working again. this normally works, at least if you do it enough lol. Is there a way to "clear all traces" of UD and/or "restart" UD without stopping the array/rebooting? Many times I think the issue is because something was dangling during the unmount process as the real issues seem to present themselves when I have mounted and unmounted a drive and try to mount it again. Edit: sure enough, reboot and it mounts up just fine first try.
-
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
I have noticed that whenever I use UD, the system in general tends to get unstable and I have to reboot it shortly after. Been this way since I first started using unraid. Starting to get annoyed as I can't figure out the issue so was going to see if anyone else has noticed general issues when/after using UD? Today for example, I was doing a backup and I unmounted the drive at one point to test the scripting function when mounted, just wanted to do a simple echo to start. But when I tried to remount the drive it fails. The error today is this but it has varied a lot and is generally along the lines of can't mount or unmount for reasons. Sep 2 10:53:00 NAS unassigned.devices: Adding disk '/dev/mapper/Personal_Data_Backup'... Sep 2 10:53:00 NAS emhttpd: shcmd (729): /usr/sbin/cryptsetup luksOpen /dev/sdq1 Personal_Data_Backup Sep 2 10:53:00 NAS emhttpd: emhttpd: HTTP/1.1 500 Internal Server Error#015 Sep 2 10:53:00 NAS unassigned.devices: luksOpen error: 500 Internal Server Error Sep 2 10:53:04 NAS unassigned.devices: Partition 'Personal_Data_Backup' could not be mounted. Sep 2 10:53:04 NAS unassigned.devices: Issue spin down timer for device '/dev/sdq'. Sep 2 10:53:04 NAS unassigned.devices: Running device script: 'Personal_Data_Backup.sh' with action 'ERROR_MOUNT'. Sep 2 10:53:57 NAS emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/disk_log sdq This would seem to say that the encryption password or something is wrong but it uses the same password as the array and was working fine before I unmounted. Unmounting in particular seems to have issues. The only option I have found to fix issues is to reboot the whole server, generally if I am lucky I can mount a drive and unmount it once before needing to reboot. Yesterday I had to reboot 4 times just to get 3 UD drives to mount and work properly and it would not unmount on 2 of those occasions causing a forced shutdown. Nothing particularly special about my setup, USB 3.0 dock but have also tried a sata dock my case has built in. BTRFS formatted drives but had even worse issues with NTFS formatted drives. Encryption is enabled but uses the same password as the array. I don't expect anything be done since I know I am not giving any actionable logs but just figured I would see if anyone else has noticed similar issues. Really makes backups more involved then they need to be.