bluepr0

There's some kind of bug that doesn't show your VM list, I've got one and it doesn't show up there.

Hello! thanks so much for putting this docker together. Looks like it's working like a charm... probably not renewing my Dropbox subscription next year. Anyway! I just wanted to ask if it could be possible that the nextcloud docker is avoiding my disk where the nextcloud share is to go to stand-by mode? Even if it's not syncing anything since yesterday, I'm still seeing my disk up. If yes, is there a way I can avoid this and let my disk to go to sleep? Thanks!

Shameless bump in case someone can throw some light

Updated successfully from rc5.

It seems to be working... yaaay! Thanks a lot!. Will do a check for sure, something weird happened for sure.

Alright removed it and added it back and now when I run the VMDelay it actually turns on the VMs (so it's triggering the other script). I will try restarting just to confirm it's finally working. Thanks!

Also If I do root@xserver:~# cd /boot/config/plugins/user.scripts/scripts/StartVMs -bash: cd: /boot/config/plugins/user.scripts/scripts/StartVMs: No such file or directory root@xserver:~# I can get into scripts folder root@xserver:~# cd /boot/config/plugins/user.scripts/scripts/ root@xserver:/boot/config/plugins/user.scripts/scripts# ls -la total 56 drwxrwxrwx 7 root root 8192 Mar 20 12:59 ./ drwxrwxrwx 3 root root 8192 Mar 19 21:19 ../ drwxrwxrwx 2 root root 8192 Mar 20 12:59 StartVMs/ drwxrwxrwx 2 root root 8192 Mar 20 12:59 VMDelay/ drwxrwxrwx 2 root root 8192 Mar 19 21:14 delete.ds_store/ drwxrwxrwx 2 root root 8192 Mar 19 21:14 delete_dangling_images/ drwxrwxrwx 2 root root 8192 Mar 19 21:14 viewDockerLogSize/ root@xserver:/boot/config/plugins/user.scripts/scripts# But then I can't O_O root@xserver:/boot/config/plugins/user.scripts/scripts# cd StartVMs -bash: cd: StartVMs: No such file or directory root@xserver:/boot/config/plugins/user.scripts/scripts# I can get inside VMDelay root@xserver:/boot/config/plugins/user.scripts/scripts# ls StartVMs/ VMDelay/ delete.ds_store/ delete_dangling_images/ viewDockerLogSize/ root@xserver:/boot/config/plugins/user.scripts/scripts# cd VMDelay/ root@xserver:/boot/config/plugins/user.scripts/scripts/VMDelay# ls -la total 32 drwxrwxrwx 2 root root 8192 Mar 20 12:59 ./ drwxrwxrwx 7 root root 8192 Mar 20 12:59 ../ -rwxrwxrwx 1 root root 7 Mar 20 12:59 name* -rwxrwxrwx 1 root root 85 Mar 20 12:59 script* root@xserver:/boot/config/plugins/user.scripts/scripts/VMDelay# I will try to delete and add the script again

This root@xserver:~# /boot/config/plugins/user.scripts/scripts/StartVMs/script -bash: /boot/config/plugins/user.scripts/scripts/StartVMs/script: No such file or directory root@xserver:~# VERY WEIRD O_O

Nope, I get this output but the VMs stay off root@xserver:~# echo "/boot/config/plugins/user.scripts/scripts/StartVMs/script" | at now warning: commands will be executed using /bin/sh job 8 at Wed Mar 20 15:43:00 2019 root@xserver:~#

Nope, if I run the VMDelay script it runs fine but it doesn't fire the other script it seems, at least the VMs are not getting started. If I run manually StartVMs they do get started so I would guess it's not a problem of the script itself. I did copy and paste the script on Atom to modify and then paste it on the script file on unRAID However here's the text as well #!/bin/bash printf "%s" "waiting for pfSense ..." # Change IP to match an address controlled by pfSense. # I recommend pfSense internal gateway or some address guaranteed to be up when pfSense is finished loading. # I don't use external IP's because I want my internal network and appliances to be fully available # whether the internet is actually connected or not. while ! ping -c 1 -n -w 1 10.0.1.1 &> /dev/null do printf "%c" "." done printf "\n%s\n" "pfSense is back online" virsh start Hassio # Insert optional delay to stagger VM starts sleep 1 virsh start Windows10 And the other one #!/bin/bash echo "/boot/config/plugins/user.scripts/scripts/StartVMs/script" | at now Thanks so much for your help ❤️

This should be it

Sorry, this should do it.

Seems like it's there indeed.

Just tried it but still not working. I'm making sure that from the server I can ping the pfSense machine and it works fine. So this command "ping -c 1 -n -w 1 10.0.1.1" is working. I'm also seeing the first script (I called it VMDelay) on the logs Mar 20 13:16:03 xserver root: Delaying execution of fix common problems scan for 10 minutes Mar 20 13:16:03 xserver emhttpd: /usr/local/emhttp/plugins/user.scripts/startBackground.php "/tmp/user.scripts/tmpScripts/VMDelay/script" > /dev/null 2>&1 Mar 20 13:16:03 xserver emhttpd: Starting services... Mar 20 13:16:03 xserver emhttpd: shcmd (55): /etc/rc.d/rc.samba restart But after pfSense is back online the other script is not triggering. However if I run it manually from the User Script panel by hitting the "Run Script" button then it turns on my other VMs. I'm probably doing something wrong but not sure how to debug the mistake 🤔