Please help! UDM / UDMPro Boot Script

[nickmac88]

I consider myself a pretty smart guy and i have been researching this for some time with no success so hoping someone will be bale to point me in the right direction. First, I'm starting to get a little frustrated with all of the things this "PRO" router does not come with OOTB but that aside, i am bought in at this point.

I followed all of the directions for the setup of this Boot Utilities, but no matter what i do my script does not start on boot. I am able to start my script manually and it works just fine, i have the correct #!/bin/sh , I have the file in the correct directory, i have made my script executable. My script is similar to the following. My ultimate goal is to auto connect one of my VLANs to a VPN. Any help would be fantastic.

I don't think my issue is with the script below, i was able to follow the install instructions for the boot service fairly easily. Honestly no idea where i need to look to find the issue.

#!/bin/sh
cd /mnt/data/split-vpn/openvpn/pia
source ./vpn.conf
/mnt/data/split-vpn/vpn/updown.sh ${DEV} pre-up &> pre-up.log
nohup openvpn --config filename.ovpn
--route-noexec
--up /mnt/data/split-vpn/vpn/updown.sh
--down /mnt/data/split-vpn/vpn/updown.sh
--auth-user-pass username_password.txt
--dev-type tun --dev ${DEV}
--script-security 2
--ping-restart 15
--mute-replay-warnings &> openvpn.log &

[boostchicken]

Well the first thing you can do to see if the startup hook is running is get into unifios shell and look at the status of the udm-boot.service. If that is running it should be fine. Does this file end .sh? It should otherwise it will get filtered

[VeniceNerd]

ok i figured out the right command. that's where the problem is. there is no udm-boot.service. Should that not install automagically when i run the following?

unifi-os shell curl -L https://udm-boot.boostchicken.dev -o udm-boot_1.0.5_all.deb dpkg -i udm-boot_1.0.5_all.deb

Would you be so kind to let me know the command you ran? I'm having issued myself and would love to see if everything is even running. Thank you!

[nickmac88]

Would be nice if I could get some help on this, as this is still not working for me... @boostchicken ? Any ideas what may be going on here? I followed all of the steps exactly and rinsed repeated and still no joy... The service never starts.

That aside, below are the commands you will need to run to check the service.

1. You need to SSH to the UDM Pro
2. run - "unifi-os shell"
3. run - "systemctl"
4. Then you can look for the "udm-boot.service" and see what its status it.

[VeniceNerd]

1. You need to SSH to the UDM Pro
2. run - "unifi-os shell"
3. run - "systemctl"
4. Then you can look for the "udm-boot.service" and see what its status it.

Thank you so much! Mine shows the following:

Would that be good news, even though it says "exited"?

I really hope someone will respond to your issue soon. The community seems really small so it's very hard to come by any answers.

[nickmac88]

LOL, yes... Very small community indeed. Honestly, I'm at the point where I will try a factory reset. Kind of frustrating, but may be all I can do at this point. I've been a Systems Admin for 15 years now so I'm not an idiot, but I'm no linux/networking wiz, so i'm pretty much at the extent of my knowledge on this stuff ¯_(ツ)_/¯

You are in a better position than me given that your service is in a good state. I would think that you would want it to be started. You can use the same "systemctl" to start said service

1. run - "systemctl start udm-boot.service"
2. then check to see if the service is a running state. using "systemctl"
3. Then try a reboot and your.sh file should kick in and your VPN automatically connected.

Side note - I've mentioned this before, but I cant believe that this is not an OOTB service! This is a "Pro" router after all, lol.

[VeniceNerd]

No dice. Ran the command:

Same result:

Are we sure, though, that it needs to show as "loaded / active/ running " or is it maybe normal that it says "loaded / active / exited"? Maybe @boostchicken will have some time to chime in at some point. Would be great to know.

[drmugzy]

Troubleshooting udm-boot.service in systemd

@nickmac88, I know this is a bit late, but I came upon your post while troubleshooting this same issue on my UDM-Pro. @VeniceNerd was on the right track, troubleshooting the systemd unit file. While both of you have probably already resolved the issue, I wanted to post in case it helps others and to offer an answer, closing this thread (hopefully).

Without going on too much about systemd, I'd like to highlight a few commands that would've helped ya'll zero in on the culprit. In this specific scenario, after @boostchicken pointed to the "udm-boot.service" unit file, my troubleshooting process proceeded as follows:

1. Enter the UniFi-OS shell.

   unifi-os shell

2. Check the status of the udm-boot.service unit file.

   systemctl status udm-boot (The ".service" file extension is assumed by systemd)

   In my case, this service was "disabled", which is why my boot scripts weren't running at startup.

3. Ensure the udm-boot.service unit file is "enabled" (in systemd "enabled" means that it runs at startup).

   systemctl enable udm-boot

   After verifying the unit file was actually enabled, all startup scripts executed as expected. To verify:

   systemctl status udm-boot

4. To continue troubleshooting, examine the udm-boot.service unit file.

   systemctl cat udm-boot

Here we start to understand how the service functions, within the UniFi-OS container. @VeniceNerd , to answer your last question, "loaded, active, exited" is the appropriate status. The type "oneshot" indicates that the service will run once and exit. Digital Ocean has a pretty good systemd overview with practical explanations.

5. If the desired behavior isn't achieved after rebooting, check the systemd journal for errors.

   journalctl -xeu udm-boot (x=expanded output, useful messages when available | e=end of log | u=unit to look for)

   @nickmac88, your journal indicated an issue with 99-run-vpn.sh on line 1, specifically that it's missing.

Nov 16 22:44:58 ubnt ssh-proxy[9119]: /mnt/data/on_boot.d/99-run-vpn.sh: line 1: /mnt/data/on_boot.d/99-run-vpn.sh: not found

@nickmac88, your issue seems be an invalid directory structure. The udm-boot.service will only traverse the target directory to a depth of 1, as observed in the "ExecStart=" directive of the unit file. If you ran the setup script within the UniFi-OS container, the appropriate directory structure would be missing. The persistence of /mnt/data/ is only achieved on the linux host, not inside of any of the application containers, thus the udm-boot.service pulls the startup scripts from the linux host and into the UniFi-OS application container.

@nickmac88 , your installation command indicates you ran the setup from within the UniFi-OS application container.

unifi-os shell
curl -L https://udm-boot.boostchicken.dev/ -o udm-boot_1.0.5_all.deb
dpkg -i udm-boot_1.0.5_all.deb

@nickmac88 , pay close attention to the terminal prompt you're working in.

 " # " indicates that your operating on the linux host

 " root@ubnt:/# "  indicates that your operating within the UniFi-OS application container