Argoneon script stuck

Argon Eon
Raspberry Pi 4 8GB
Raspberry Pi OS Lite 64 Bit
argoneon.sh

The only thing installed before running the argoneon script was open media vault
system packages up to date before running the script

Installation gets stuck at the message shown below. No errors; just an endless wait for something to finish

pi@foobox:~ $ curl https://download.argon40.com/argoneon.sh | bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0*************
Argon Setup


100 13198 100 13198 0 0 14946 0 --:–:-- --:–:-- --:–:-- 14946
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
python3-rpi.gpio is already the newest version (0.7.0-0.2+b2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following additional packages will be installed:
libi2c0
Recommended packages:
i2c-tools
The following NEW packages will be installed:
libi2c0 python3-smbus
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 23.8 kB of archives.
After this operation, 74.8 kB of additional disk space will be used.
Get:1 Index of /debian bullseye/main arm64 libi2c0 arm64 4.2-1+b1 [10.6 kB]
Get:2 Index of /debian bullseye/main arm64 python3-smbus arm64 4.2-1+b1 [13.2 kB]
Fetched 23.8 kB in 0s (98.6 kB/s)
Selecting previously unselected package libi2c0:arm64.
(Reading database … 44324 files and directories currently installed.)
Preparing to unpack …/libi2c0_4.2-1+b1_arm64.deb …
Unpacking libi2c0:arm64 (4.2-1+b1) …
Selecting previously unselected package python3-smbus:arm64.
Preparing to unpack …/python3-smbus_4.2-1+b1_arm64.deb …
Unpacking python3-smbus:arm64 (4.2-1+b1) …
Setting up libi2c0:arm64 (4.2-1+b1) …
Setting up python3-smbus:arm64 (4.2-1+b1) …
Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u2) …
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Suggested packages:
libi2c-dev python-smbus
Recommended packages:
read-edid
The following NEW packages will be installed:
i2c-tools
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 79.3 kB of archives.
After this operation, 297 kB of additional disk space will be used.
Get:1 Index of /debian bullseye/main arm64 i2c-tools arm64 4.2-1+b1 [79.3 kB]
Fetched 79.3 kB in 0s (828 kB/s)
Selecting previously unselected package i2c-tools.
(Reading database … 44337 files and directories currently installed.)
Preparing to unpack …/i2c-tools_4.2-1+b1_arm64.deb …
Unpacking i2c-tools (4.2-1+b1) …
Setting up i2c-tools (4.2-1+b1) …
Processing triggers for man-db (2.9.4-2) …
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following NEW packages will be installed:
hddtemp
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 56.8 kB of archives.
After this operation, 188 kB of additional disk space will be used.
Get:1 Index of /debian bullseye/main arm64 hddtemp arm64 0.3-beta15-54 [56.8 kB]
Fetched 56.8 kB in 0s (755 kB/s)
Preconfiguring packages …
Selecting previously unselected package hddtemp.
(Reading database … 44362 files and directories currently installed.)
Preparing to unpack …/hddtemp_0.3-beta15-54_arm64.deb …
Unpacking hddtemp (0.3-beta15-54) …
Setting up hddtemp (0.3-beta15-54) …
Processing triggers for man-db (2.9.4-2) …
Created symlink /etc/systemd/system/multi-user.target.wants/argononed.service → /lib/systemd/system/argononed.service.

Has anyone else seen this issue?

Edit: through walking through the script and trying different things it is clear that it is hanging on starting argononed.service and if I kill that it then it hangs on argoneond.service

Some other things worth noting:
the power button is working fine
the hdd backplane is working fine
the fan is working fine.

The oled screen only shows the power on screen then shuts off.

Same issue. Only commands I ran before were the usual sudo apt update ; sudo apt upgrade. Additionally, the script yields no output when ran directly:
/usr/bin/python3 /etc/argon/argoneond.py
nor
/usr/bin/python3 /etc/argon/argoneond.py SERVICE

If I’m not mistaken then rebooting the system with these services enabled freezes the entire indefinitely, at least that’s what happened to me. So after the second failed attempt at installing the Argon script, this time I’m trying

sudo systemctl disable argoneond.service
sudo systemctl disable argononed.service

before rebooting. :sweat:

1 Like

same problem Skript cannot run through and hangs indefintely - the process seems stuck in either i2c or gpio:

pi@altair:~ $ sudo lsof -p 28213
COMMAND   PID USER   FD      TYPE DEVICE SIZE/OFF  NODE NAME
python3 28213 root  cwd       DIR  179,2     4096   822 /home/pi
python3 28213 root  rtd       DIR  179,2     4096     2 /
python3 28213 root  txt       REG  179,2  5280744  1882 /usr/bin/python3.9
python3 28213 root  mem       REG  179,2    52304 12571 /usr/lib/python3/dist-packages/RPi/_GPIO.cpython-39-aarch64-linux-gnu.so
python3 28213 root  mem       REG  179,2    10064  2089 /usr/lib/aarch64-linux-gnu/libi2c.so.0.1.1
python3 28213 root  mem       REG  179,2    19640 18129 /usr/lib/python3/dist-packages/smbus.cpython-39-aarch64-linux-gnu.so
python3 28213 root  mem       REG  179,2   346132  9336 /usr/lib/locale/C.UTF-8/LC_CTYPE
python3 28213 root  mem       REG  179,2  3041504  9326 /usr/lib/locale/locale-archive
python3 28213 root  mem       REG  179,2  1458480  5116 /usr/lib/aarch64-linux-gnu/libc-2.31.so
python3 28213 root  mem       REG  179,2   104824  5407 /usr/lib/aarch64-linux-gnu/libz.so.1.2.11
python3 28213 root  mem       REG  179,2   161856  5161 /usr/lib/aarch64-linux-gnu/libexpat.so.1.6.12
python3 28213 root  mem       REG  179,2   633000  5253 /usr/lib/aarch64-linux-gnu/libm-2.31.so
python3 28213 root  mem       REG  179,2    14672  5385 /usr/lib/aarch64-linux-gnu/libutil-2.31.so
python3 28213 root  mem       REG  179,2    14560  5145 /usr/lib/aarch64-linux-gnu/libdl-2.31.so
python3 28213 root  mem       REG  179,2   160200  5334 /usr/lib/aarch64-linux-gnu/libpthread-2.31.so
python3 28213 root  mem       REG  179,2   145352  4986 /usr/lib/aarch64-linux-gnu/ld-2.31.so
python3 28213 root  mem       CHR  245,0             94 /dev/gpiomem
python3 28213 root  mem       REG  179,2    27004  5667 /usr/lib/aarch64-linux-gnu/gconv/gconv-modules.cache
python3 28213 root    0u      CHR  136,0      0t0     3 /dev/pts/0
python3 28213 root    1u      CHR  136,0      0t0     3 /dev/pts/0
python3 28213 root    2u      CHR  136,0      0t0     3 /dev/pts/0
python3 28213 root    3u      CHR   89,1      0t0   217 /dev/i2c-1
python3 28213 root    4u      CHR  245,0      0t0    94 /dev/gpiomem
python3 28213 root    6r      REG   0,18     4096 26996 /sys/devices/platform/soc/fe200000.gpio/gpiochip0/gpio/gpio4/value
python3 28213 root    7u  a_inode   0,13        0  7590 [eventpoll]

Ctrl-C on the process shows this:

root@altair:/home/pi# /usr/bin/python3 /usr/bin/argononed.py
^CException ignored in: <module 'threading' from '/usr/lib/python3.9/threading.py'>
Traceback (most recent call last):
  File "/usr/lib/python3.9/threading.py", line 1428, in _shutdown
    lock.acquire()
KeyboardInterrupt: 

They are systemd service modules if you look at the configuration in those modules whether they block bootup or not is dependent on the service type argument. I believe they are type simple which doesn’t block other scripts from running. Regardless I didn’t have any issues with restarting.

1 Like

[quote=“coro1404, post:3, topic:748”]the process seems stuck in either i2c or gpio:
[/quote]

I haven’t troubleshooted this any further TBH, but that is my suspicion as well. I have a hunch from reading the myriad of complaints about the oled screen(and some of the python code the service daemons run) that there is something wrong with the i2c connection which it seems is setup over gpio.

Curiously I sent a support email right after starting this thread and have received no response other then the canned automated one(so 2 weeks ago). Pretty annoying to me considering the main thing I’m currently using this thing for is just documenting how to set it up so I can write a howto thread for new users. Help me help you and all that.

[DarkElvenAngel / Argon One Daemon · GitLab](A replacement daemon for the Argon One Raspberry Pi cases, and the Argon Artik Fan Hat.)

this actually fixed this issue for me - maybe this is of help to you

regards

But you still have no OLED.

Might be worth mentioning that I had the script running perfectly fine on Ubuntu 20.04 LTS, although that was likely an earlier version of the script.

Inspecting the script it can be read:

# Check if Raspbian, otherwise Ubuntu
grep -q -F 'Raspbian' /etc/os-release &> /dev/null

but Pi OS identifies as

$ cat /etc/os-release                                 
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

the Ubuntu tweaks of the script is seemingly chosen instead the Raspbian/Pi OS ones.

Additionally the same grep command is used in /etc/argon/argoneon-rtcconfig.sh and in /etc/argon/argonone-ir which should concern @staff if the problem description is correct.

@yusf

Modify the script:

grep -q -F -e 'Raspbian' -e 'bullseye' /etc/os-release &> /dev/null 

This will allow Raspbian or bullseye to select RasperryPI OS.

2 Likes

Yes, this is what I looked into doing. Though both files mentioned; argoneon-rtcconfig.sh and argonone-ir are auxiliary in function and the Raspbian detection is at the point of installation only used for selecting which packages to install (and to create some desktop shortcut in /home/pi. So I don’t quite see how it would help as I’ve manually installed all required packages anyway. (Again, hesitant to reboot with services installed)

I can actually get the OLED and fan control to work by running /usr/bin/python3 /etc/argon/argononed.py SERVICE manually. However sudo systemctl start argononed.service freezes as usual.

Can we get this solved already :weary:

1 Like

Interesting… that worked for me to(fan is going bonkers, but that’s probably a config thing). Proves it’s a software issue not a hw one as far as I am concerned.

1 Like

If I run argononed.service in console one and let it hang, then check it’s status in console two it says “Active: inactive (dead)”.

But if I then “check ps -aux | grep argon” in a third console not only does it show the systemctl command still running, but it shows it running twice (once with sudo and once without and both running as root).

Journalctl logs don’t show anything

Either the script starts, fails silently, and systemctl locks up or
systemctl locks up and never even calls the command for some reason.

I also tried tweaking the systemd configuration in a variety of ways and reloading to no avail.