Jump to content

randall526

Members
  • Content Count

    75
  • Joined

  • Last visited

Community Reputation

0 Neutral

About randall526

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. This is my script to auto check if a docker is responding and restart it. The verification is http based which will catch both when the docker doesn't respond as well as when there is a http error code present. You have to run a sample curl on your own and potentially choose what http content validates the docker. The script comments are fairly self explanatory and the code function is pretty clean to make the script user friendly and easy to add variables and function lines to check other dockers. UnraidDockerCheck.sh
  2. I use the go script to populate my crontab. All my jobs stopped after the upgrade however the crontab looked normal when running crontab -l I had to add a killall crond and add /usr/sbin/crond to my go script to fix the issue. Seems odd why I would have to do this. I see crond in the process table with a -l command switch. Restarting crond fires off all my jobs no problem. I run 3 unraid VM's and the behavior was confirmed on all 3.
  3. I had to update broken slackware file locations again since it appears new versions are available for some of the downloads. Incase anyone wants the version I am using on unraid 6.4.1, here it is: openVMTools_auto62 (4).plg There is no GUI front end with unraid but I do show the process running and ESXi reporting tools is indeed running. Great plugin so far, i'm waiting for the next kernel release to see if it updates correctly. Good work putting this together.
  4. changing how the udp protocol was defined worked Didn't think to change it seeing as pfsence oepnVPN server generated it that way on behalf of the VPN client and worked fine outside the plugin. I can stop and start the VPN through the WebGUI now, the small things make one happy. Thanks again.
  5. I ended up scripting around this and starting the VPN in the go file the traditional openvpn command line way and using a cron job script to keep an eye on it. GUI plugin still fails to start the VPN by removing my "dev tun" line in my ovpn config file everytime.
  6. The .ovpn file was partially auto generate by pfsense and it defined the UDP protocol this way remote rand526.ddns.net 1198 udp <========= I normally add the udp line separately myself as you suggested however this way works too. I proved this configuration works by starting the VPN by the command line. This works and the .ovpn file is not butchered by the unraid plugin when started this way. The plugin however when starting the VPN via the GUI keeps editing my .ovpn file and removing the "dev tun" line incorrectly just before the VPN starts. The VPN log then bawks that it's missing the "dev tun". The plugin breaks my .ovpn file every time. This proves the plugin is incorrectly messing with my .ovpn file and the configuration works prior to the plugin deciding to update it. I can see updating .ovpn in the lower right corner flash ever so briefly when I use this .ovpn. What in the plugin decides my .ovpn must be updated and removes this line.... I have no idea. My other .ovpn file I use for another VPN, the plugin doesn't touch and thus I don't get my .ovpn butchered by the plugin lol. Summing up, I think someone understanding the plugin logic rather then openVPN would have to comment as to why the plugin is messing with my .ovpn file and removing "dev tun" every-time. I think this is a plugin issue not a openVPN configuration problem. Something about my setup however the plugin is deciding it must incorrectly update my .ovpn file.
  7. One more thing, confident the plugin was incorrectly editing the .ovpn file which was a valid config before the plugin touched it, I decided to fire the VPN up via the command line. The following command and config file connects to my openVPN server and shows up running in the GUI. However if I bounce it via the GUI plugin, it removes the "dev tun" line and mentioned it updated the file and fails to start due to no dev tun/tap adapter defined. Maddening I say. It only does it for this setup, my other VPN server and .ovpn config file the plugin doesn't touch or try to update. Working command openvpn --writepid /var/run/openvpn/openvpn.pid --script-security 3 --mute-replay-warnings --config /boot/openvpn/pfSense-udp-1198-Sister.ovpn Working config via command line dev tun persist-tun persist-key cipher AES-256-CBC auth SHA1 tls-client client resolv-retry infinite remote ######## 1198 udp lport 0 verify-x509-name "pfenseRand" name pkcs12 pfSense-udp-1198-Sister.p12 ns-cert-type server comp-lzo adaptive auth-user-pass /boot/config/plugins/openvpnclient/password.txt status /tmp/openvpn/openvpn-status.log
  8. Got a perplexing problem with the VPN client driving me up a wall. The plugin is dynamically updating my .ovpn config file every time I try to start the VPN Client and it some how removes the dev tun option in the file. The vpn fails to start with, no dev option defined in your .ovpn file. I'll add it back and the plugin updates the .ovpn and removes it every time and then the vpn log complains about the entry not being there. This is what my config file looks like before I start the VPN persist-tun dev tun persist-key cipher AES-256-CBC auth SHA1 tls-client client resolv-retry infinite remote ######### 1198 udp lport 0 verify-x509-name "pfenseRand" name pkcs12 pfSense-udp-1198-Sister.p12 ns-cert-type server comp-lzo adaptive auth-user-pass This is what it looks like after the VPN fails to start and it updates my .ovpn file. It fails to start and says the dev tun/tap option is missing cause the plugin took it out.... persist-tun persist-key cipher AES-256-CBC auth SHA1 tls-client client resolv-retry infinite remote ############## 1198 udp lport 0 verify-x509-name "pfenseRand" name pkcs12 pfSense-udp-1198-Sister.p12 ns-cert-type server comp-lzo adaptive auth-user-pass /boot/config/plugins/openvpnclient/password.txt status /tmp/openvpn/openvpn-status Interestingly, I have another remote VPNserver using different options without a password and the plugin never trys to change the .ovpn file and it works fine. Any bright ideas?
  9. hmmm I rebooted a few times to see how /dev/sda was getting assigned, seems the RDM assigned cache drive gets assigned as /dev/sda everytime. Since it's being passed through as a Raw device mapping, it seems to be seen first in the boot sequence before all my drives attached to the passed through I/O card does seance it has to load the I/O card driver little later in the boot sequence. I'll have to keep this in mind.
  10. So I thought about what Linix was doing here and the device-id's are nothing more then symbolic links to the /dev/sda file. the sda file is getting picked up every time as the cache drive is manually mountable this way. I looked at how ESXi was listing the disk at it's Linux device level, looked at the naming format in unRAID and created my own sym links via the go file. ln -s /dev/sda1 /dev/disk/by-id/ata-LITEONIT_LCS2D256M6S_2.5_7mm_256GB_TW0XFJWX5508534T1145-part1 ln -s /dev/sda /dev/disk/by-id/ata-LITEONIT_LCS2D256M6S_2.5_7mm_256GB_TW0XFJWX5508534T1145 After doing this, unRAID picked up my manually populated disk ID's and I was able to assign the cache drive. The drive is now being used as a cache and sharing the cache share properly with out having to manually mount it. Dirty work around but it works. I may try my original idea of assigning vmdk disks sourced from different VMware store SSD drives and see if this is feasible. I was going to create a cache pool this way. I don't know if anyone else out there is setup this way via ESXi however shall see how it goes.
  11. I run ESXi 6.0 with Plop boot manager as well. Will give this a go for sure, thanks for sharing it here, much obliged.
  12. I had this working before and don't know what happened. I decided to do a little experimenting with my Raw Device passthrough disk cache drive on my backup unRAID virtual machine first. The cache was directly attached to the VM at one point and I moved it off a SAS card attached to the VM and attached it to the motherboard to free up a SAS I/O card connection for a data drive. I RDM mapped it and all was well. I loose temp sensors and such this way but for a SSD cache disk, I was good with that. Then I thought about making that cache disk a VMware data store disk instead and pass a traditional vmdk disk as my caching disk just to see if it can be done. There was alot of wasted space on the disk the way I was using it that made this option attractive. I rsynced my RDM cache disk into the raid array and removed it. When assigning a typical vmdk, it failed to show up by disk-id and when assigning a device as a cache disk, unraid GUI just showed sda and the disk size with no other identifying characteristics. Assigning the cache disk wouldn't stick and the web page constantly showed the cache drive as unassigned after just assigning the disk. Hmmmm not desirable I say, so I back it all out. Removed the SSD drive from vmware's storage pool and setup a RDM disk again and the same thing happened again and it was just working before.... I manually formatted, mounted and restored my cache disk data which got my dockers up however unRAID does not see it as a cache disk via the GUI. See below, /dev/sda is there and mounted manually but with no identifiers. Any ideas? Is it possible to manually populate this data with a /proc file system hack? root@unRAIDbackup:/dev# ls -al /dev/disk/by-id | grep sda root@unRAIDbackup:/dev# ls -al /dev/disk/by-uuid | grep sda root@unRAIDbackup:/dev# cat /etc/mtab | grep sda /dev/sda1 /mnt/cache btrfs rw 0 0 root@unRAIDbackup:/dev# btrfs fi show /mnt/cache Label: none uuid: c3a77508-ff82-4fc5-a147-e0eb90812706 Total devices 1 FS bytes used 61.95GiB devid 1 size 238.47GiB used 88.04GiB path /dev/sda1 btrfs-progs v4.1.2 root@unRAIDbackup:/dev# fdisk -l /dev/sda WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sda: 256.1 GB, 256060514304 bytes 168 heads, 63 sectors/track, 47252 cylinders, total 500118192 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 2048 500118191 250058072 83 Linux root@unRAIDbackup:/dev# root@unRAIDbackup:/dev# ls -al /dev/disk/by-id | grep sda root@unRAIDbackup:/dev# ls -al /dev/disk/by-uuid | grep sda root@unRAIDbackup:/dev# cat /etc/mtab | grep sda /dev/sda1 /mnt/cache btrfs rw 0 0 root@unRAIDbackup:/dev# btrfs fi show /mnt/cache Label: none uuid: c3a77508-ff82-4fc5-a147-e0eb90812706 Total devices 1 FS bytes used 61.95GiB devid 1 size 238.47GiB used 88.04GiB path /dev/sda1 btrfs-progs v4.1.2 root@unRAIDbackup:/dev# fdisk -l /dev/sda WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sda: 256.1 GB, 256060514304 bytes 168 heads, 63 sectors/track, 47252 cylinders, total 500118192 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 2048 500118191 250058072 83 Linux root@unRAIDbackup:/dev# hdparm -I /dev/sda /dev/sda: SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 20 00 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ATA device, with non-removable media Serial Number: <@??? Standards: Likely used: 1 Configuration: Logical max current cylinders 0 0 heads 0 0 sectors/track 510 0 -- Logical/Physical Sector size: 512 bytes device size with M = 1024*1024: 0 MBytes device size with M = 1000*1000: 0 MBytes cache/buffer size = unknown Capabilities: IORDY not likely Cannot perform double-word IO R/W multiple sector transfer: not supported DMA: not supported PIO: pio0
  13. I got too many other VM's to go to bare unraid. I run unraid as 2 separate VM's to manage my primary and backup raid array. I'll be running 6.1.9 for a long time till this is resolved.