Trixie Appliance Installation Fails

AllStarLink
1

Setup Information

Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl exist?)
********** AllStarLink [ASL] Version Info **********

OS : Debian GNU/Linux 13 (trixie)
OS Kernel : 6.12.74+deb13+1-amd64

Asterisk : 22.8.2+asl3-3.8.3-1.deb13
ASL [app_rpt] :

Package Version
============================== ==============================
allmon3 1.8.1-1.deb13
asl3 3.17-1.deb13
asl3-asterisk 2:22.8.2+asl3-3.8.3-1.deb13
asl3-asterisk-config 2:22.8.2+asl3-3.8.3-1.deb13
asl3-asterisk-modules 2:22.8.2+asl3-3.8.3-1.deb13
asl3-menu 1.18-1.deb13
asl3-tts 1.0.1-1.deb13
asl3-update-nodelist 2.0.0-1.deb13
asl-apt-repos 2.0-1.deb13
cockpit 337-1
cockpit-bridge 337-1
cockpit-networkmanager 337-1
cockpit-packagekit 337-1
cockpit-sosreport 337-1
cockpit-storaged 337-1
cockpit-system 337-1
cockpit-wifimanager 1.2.0-1.deb13
cockpit-ws 337-1
dahdi 1:3.1.0-2.1
dahdi-linux 1:3.4.0-11.asl.deb13

Installation of Trixie version current as of today on intel silicon went smoothly. Moved on to install ASL3 PC Appliance using “sudo apt install asl3-appliance-pc” and I see the following:

asl3-appliance-pc is already the newest version (2.1.0-2.deb13).

[I inadvertantly erased the full installation screen print; so ran the install again. This is the same error shown here. Until this point all was normal.]

Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
2 not fully installed or removed.
Space needed: 0 B / 87.3 GB available

Continue? [Y/n] Y
Setting up asl3-appliance (2.1.0-2.deb13) ...
apache2_invoke ssl: already enabled
apache2_invoke default-ssl: already enabled
apache2_invoke headers: already enabled
apache2_invoke nocache: already enabled
Synchronizing state of apache2.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install enable apache2
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.

Possible reasons for having these kinds of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/, .requires/, or .upholds/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 148.
dpkg: error processing package asl3-appliance (--configure):
installed asl3-appliance package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of asl3-appliance-pc:
asl3-appliance-pc depends on asl3-appliance; however:
Package asl3-appliance is not configured yet.

dpkg: error processing package asl3-appliance-pc (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
asl3-appliance
asl3-appliance-pc
Error: Sub-process /usr/bin/dpkg returned an error code (1)

I have no idea how to fix this error. I have tried:

sudo apt remove asl3-appliance-pc
sudo reboot
and then after reboot, reinstall; the same error recurs.

73 de K3FZT / Steve

2

Try doing the following:

sudo apt remove asl3-appliance-pc
sudo apt install --reinstall asl3-appliance

See if that results in a working system. If it does, then add:

sudo apt install --reinstall asl3-appliance-pc

Hard to tell without the missing logging if something hiccuped during package install or there's something odd with your setup.

3

Thank you. No, remove fails with the same error as does reinstall.

Time to reinstall Trixie using Net Install.

I will do so, retry installing the PC appliance and then report back here.

Thank you. 73 de K3FZT / Steve

4

there is one level of software removal stronger than remove, and that's purge

small chance that might help

5

New trixie installation w/drive format and swap partition format. No problems. Installation ran to the end. sudo apt update and sudo apt upgrade yielded 0 change. Did the "asl-appliance" installation and again failed same error. I'm reluctant to paste the full installation log printed to the screen, but I will if you tell me to do so.

73 de K3FZT / Steve

6

I just spun up a clean Trixie install and did exactly the following:

root@clients-212:~# history
    1  wget https://repo.allstarlink.org/public/asl-apt-repos.deb13_all.deb
    2  dpkg -i asl-apt-repos.deb13_all.deb
    3  apt update
    4  apt install asl3-appliance

Took about 4 minutes to download and install everything. I working ASL3 install right up with no errors. That's right from initial boot and su - to root.

You'll have to provide some logging or note what might be nonstandard with what you're doing. You installed the Trixie ASL repo and not Bookworm right?

7

I left the Windows 11 installation on the 512G SSD that the device came with. I used Trixie netinst w/manual partitioning to create a 124G Ext4 w/journaling partition for instattation and a 1G swap partition. I installed trixie to the Ext4 partition adding only an xfce desktop to the Allstarlink detailed recipe. Installation completed with no complaints. Then I did exactly what you're showing above and got the error I'm reporting. I suppose there could be an interaction with the desktop that's causing the issue, but I'd like to use this machine to further develop my linux knowledge and use of basic desktop tools.

Out of frustration, a few hours ago I thought to try ssh into the install and was connected. ASL-menu ran just fine and I configured my node number. I have connected to and listened/transmitted on several nodes. I have not yet been able to get Allmon3 to show my node though I edited manager.conf and "systemctl reload allmon3" and have set a user name and password and logged in. I've been in this movie with Allmon3 before but I don't recall the fix. As soon as I send this message I'll go look through/search this forum.
73 de K3FZT / Steve