PADD not starting

[mikebetz42]

PADD not starting, and yes I have edited "~/.bashrc". it use to work, but it's no longer displaying on the Pi. I can run it in an SSH session without a problem.

Pi-hole® v4.2.2, Web v4.2, FTL v4.2.2, PADD v2.2.1

Linux 4.14.98-v7+ armv7l
Raspbian GNU/Linux 9.8 (stretch)

Thank you,

Mike

[maserowik]

sudo chmod +x padd.sh I had to redo this command in order for it to work for me. Mike From: mikebetz42 [mailto:notifications@github.com] Sent: Tuesday, February 19, 2019 3:04 PM To: jpmck/PADD <PADD@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: [jpmck/PADD] PADD not starting (#47) PADD not starting, and yes I have edited "~/.bashrc". it use to work, but it's no longer displaying on the Pi. I can run it in an SSH session without a problem. Pi-hole® v4.2.2, Web v4.2, FTL v4.2.2, PADD v2.2.1 Linux 4.14.98-v7+ armv7l Raspbian GNU/Linux 9.8 (stretch) <https://user-images.githubusercontent.com/25675511/53043566-99d47d80-343d-11e9-8459-0081ced83250.jpg> Thank you, Mike — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#47> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AYhcdr3dXWTsMb2HlfQp21NUv5Og7TeFks5vPFi2gaJpZM4bDwjK> . <https://github.com/notifications/beacon/AYhcdtDRZwinZmszGtq1bVvelC4_nik4ks5vPFi2gaJpZM4bDwjK.gif>

…

--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

[mikebetz42]

I fixed my problem.... edited "~/.bashrc" and

if [ "$TERM" == "linux" ] ; then

changed to

if [ "$TERM" == "xterm" ] ; then

Did the trick.

[tspotz]

I fixed my problem.... edited "~/.bashrc" and

if [ "$TERM" == "linux" ] ; then

changed to

if [ "$TERM" == "xterm" ] ; then

Did the trick.

since a SSH connection is also "xterm" this leads to PADD starting even on ssh'd terminal.
i changed this last night (after upgrading the pi) and encounter this problem to

if [ "$SSH_TTY" == "" ] ; then

locally loged in the SSH_TTY is empty.

[stephenjmcmahon]

Sorry to re-open this but I've also run into the same issue using the latest PADD (v3.0.2) only after updating the kernel from

pi@PiHole-02:~ $ uname -a
Linux PiHole-02 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l GNU/Linux

to

pi@pihole-01:~ $ uname -a
Linux pihole-01 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT 2019 armv7l GNU/Linux

I had to sudo raspi-config to re-enable auto-login to console and verified ~/.bashrc still had the included code to auto-run but still nothing.

as @tspotz mentioned above that was the trick to fixing this.

changing
if [ "$TERM" == "linux" ] ; then
to
if [ "$SSH_TTY" == "" ] ; then
in ~/.bashrc

[R3clu23]

I fixed my problem.... edited "~/.bashrc" and
if [ "$TERM" == "linux" ] ; then
changed to
if [ "$TERM" == "xterm" ] ; then
Did the trick.

since a SSH connection is also "xterm" this leads to PADD starting even on ssh'd terminal.
i changed this last night (after upgrading the pi) and encounter this problem to

if [ "$SSH_TTY" == "" ] ; then

locally loged in the SSH_TTY is empty.

I have the same problem, how did you edit the .bashrc file if you can't stop the script from running?

[stephenjmcmahon]

Ctrl+C should stop PADD from running and drop you back into CLI

[R3clu23]

Ctrl+C should stop PADD from running and drop you back into CLI

It doesn't it just restarts the script over again.

I edited my .bashrc with:

if [ "$TERM" == "xterm" ] ; then

[tspotz]

press Ctrl-C several times since the .bashrc itself is a bash-script which should be exited too (seen the while loop which restarts the padd.sh after waiting a second ?)
I connected directly with an USB Keyboard to RPi

[R3clu23]

press Ctrl-C several times since the .bashrc itself is a bash-script which should be exited too (seen the while loop which restarts the padd.sh after waiting a second ?)
I connected directly with an USB Keyboard to RPi

Okay, pressing ctrl-c while the script loaded did in fact cancel the script from loading and I'm back at the pi@pihole~$ CLI line. Thanks for the help.

[timkingman]

When raspi-config turns on auto-login, it writes your current $TERM to /etc/systemd/system/getty@tty1.service.d/autologin.conf. Edit that file and change the last parameter to linux, and then the test in .bashrc should start padd.sh on only the console auto-login.

Edit: or change the last arg to literal $TERM, per this raspi-config issue