No longer able to autoboot to ES after VPN/Transmission init script.

gdallas

Pi Model - Raspberry Pi 3 Model B Quad Core CPU 1.2 GHz 1 GB RAM
Power Supply used: powered from NAS USB
RetroPie Version Used - unsure how to check. sorry.
Error messages received: none. just cant boot into ES.

Guide used: https://www.htpcguides.com/remote-access-transmission-torrent-behind-vpn-linux/

Hello. I can no longer use ES since following this guide, which I followed to allow remote Transmission Daemon access to my PI when using my VPN. This guide worked a treat, however my PI no longer boots into ES. instead the last row of text i see on my screen is

'Initialization Sequence Completed'

pressumably talking about by VPN setup.

any ideas how i get it to carry on loading all ES etc?

Many thanks
G

mitu

@gdallas What happens if you log in and start Emulationstation manually, by typing emulationstation at the command prompt.
EDIT: You can try to use the RetroPie-Setup script and choose the autostart module to disable and then enable the autostart on boot, also choosing Emulationstation to be started on boot.

gdallas

@mitu said in No longer able to autoboot to ES after VPN/Transmission init script.:

RetroPie-Setup script

so from Putty I can SSH 'emulationstation' and it loads ok. but as soon as i close putty it goes back to the same screen with init seq completed etc.

I have this code for my VPN that runs from /etc/rc.local. I tried adding emulationstation in there too but didnt load.

sleep 10
cd /etc/openvpn
sudo openvpn --config /etc/openvpn/ipvanish-UK-Manchester-man-c06.ovpn --auth-user-pass /etc/openvpn/login.txt --script-security 2 --up /etc/openvpn/torrentvpn.sh --do$

sleep 3
emulationstation

exit 0

mitu

@gdallas You shouldn't load ES from the same script as the VPN. Use the RetroPie setup script as I mentioned and see if it auto-loads at start after you re-configure the boot/start options.

gdallas

ye I only just tried that there to check. was clutching at straws. Wasnt there when i posted. So i went into the RP setup script and done what you said. I got confirmation that ES would start at boot. but it didnt.

mitu

@gdallas Modify the contents of /etc/rc.local and put an & (ampersand) at the end of the line with the openvpn command:

sudo openvpn --config /etc/openvpn/whatever.ovpn --auth-user-pass /etc/openvpn/login.txt --script-security 2 --up /etc/openvpn/torrentvpn.sh --down /etc/openvpn/torrentvpnstop.sh

should be

openvpn --config /etc/openvpn/whatever.ovpn --auth-user-pass /etc/openvpn/login.txt --script-security 2 --up /etc/openvpn/torrentvpn.sh --down /etc/openvpn/torrentvpnstop.sh &

You don't need sudo, since the script is already started as root.

EDIT: replace the whatever.ovpn in the example command lines above with the actual filename you configured.

gdallas

Excellent, that seemed to work. Thanks mitu. I presume the issue was i just didnt copy the full code from that guide then?

mitu

@gdallas said in No longer able to autoboot to ES after VPN/Transmission init script.:

I presume the issue was i just didnt copy the full code from that guide then?

The original tutorial you linked didn't have the modification I mentioned, so the tutorial itself has the error. They should mention that the auto-start block added in /etc/rc.local blocks the boot sequence.

gdallas

Genius . Thank you very much. very happy now :-)