InternalServerException in InstallPlugin:

joeko

@chrishamm said in InternalServerException in InstallPlugin::

@joeko It looks like the root plugin service cannot reload the apparmor profile which is why you get that internalserverexception. Please follow exactly the steps from the upgrade notes to make sure apparmor is installed and enabled.

this does not install the plugin service
https://github.com/Duet3D/DuetSoftwareFramework/wiki/Changelog-DSF-3.x#version-330
apt-get install duetpluginservice install it but the root serice doesnt run

joeko

i have now install ubuntu minimal.
the service is now active but when i try to install a plugin over upload&install i get a new message

InternalServerException in InstallPlugin: UnauthorizedAccessException in InstallPlugin: Access to the path '/opt/dsf/sd/www/BtnCmd.b3e030d8.css' is denied.

joeko

ok, 2 days now for nothing
i have tried now to install the latest beta like in the guide.
after sudo apt update && sudo apt upgrade i can see the updates but they wont be install without an errormessage

Aktualisierung für 8 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, u                                                                             m sie anzuzeigen.
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
Die folgenden Pakete sind zurückgehalten worden:
  duetcontrolserver duetpluginservice duetruntime duettools duetwebcontrol
  duetwebserver reprapfirmware
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 7 nicht aktualisiert.
joern@Vcore:~$ apt list --upgradable
Listing... Done
duetcontrolserver/unstable 3.4-b5 arm64 [upgradable from: 3.3.0]
duetpluginservice/unstable 3.4-b5 arm64 [upgradable from: 3.3.0]
duetruntime/unstable 3.4-b5 arm64 [upgradable from: 3.3.0]
duetsoftwareframework/unstable 3.4-b5 arm64 [upgradable from: 3.3.0]
duettools/unstable 3.4-b5 arm64 [upgradable from: 3.3.0]
duetwebcontrol/unstable 3.4-b5 all [upgradable from: 3.3.0]
duetwebserver/unstable 3.4-b5 arm64 [upgradable from: 3.3.0]
reprapfirmware/unstable 3.4-b6-1 all [upgradable from: 3.3.0-1]

is there a secrete to install the beta ? i do exactly what the guide tell me...

Phaedrux

What version is currently installed when you try to upgrade?

joeko

@phaedrux said in InternalServerException in InstallPlugin::

What version is currently installed when you try to upgrade?

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TJ-6JKD8-3S46Q-1A8GS
Used output buffers: 1 of 40 (17 max)
=== RTOS ===
Static ram: 150904
Dynamic ram: 61684 of which 580 recycled
Never used RAM 141024, free system stack 200 words
Tasks: SBC(ready,5.1%,328) HEAT(delaying,0.0%,325) Move(notifyWait,0.0%,302) CanReceiv(notifyWait,0.0%,799) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.1%,93) MAIN(running,87.7%,922) IDLE(ready,0.1%,29), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:02:37 ago, cause: power up
Last software reset at 2021-11-17 19:01, reason: User, GCodes spinning, available RAM 141024, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 129
MCU temperature: min 12.0, current 24.8, max 24.9
Supply voltage: min 24.0, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.2, current 12.2, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, reads 28255, writes 18 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 28255, writes 18 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 28255, writes 18 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 28255, writes 18 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 28255, writes 18 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 28262, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2021-11-18 07:48:24
Slowest loop: 1.10ms; fastest: 0.03ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" in state(s) 0
Telnet* is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger* is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages queued 1349, received 1646, lost 0, longest wait 2ms for reply type 6049, peak Tx sync delay 179, free buffers 49 (min 48), ts 790/789/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
State: 4, failed transfers: 0, checksum errors: 0
Last transfer: 1ms ago
RX/TX seq numbers: 5478/5478
SPI underruns 0, overruns 0
Disconnects: 0, timeouts: 0, IAP RAM available 0x2c810
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.3.0
Code buffer space: 4096
Configured SPI speed: 8000000Hz
Full transfers per second: 0.18, max wait times: 11.9ms/0.0ms
Codes per second: 0.01
Maximum length of RX/TX data transfers: 2896/932

as i setup up the sbc it looks like rrf 3.3.0.1 will install but now is 3.3. also i got the message that user dsf doesnt exist but now user dsf is present.

joeko

@chrishamm

i got for testing an raspberry 3 from a friend.
on a raspberry i can install or setup the sbc like in the guide (i did the new setup and not the duetpi image)

on the raspberry i dont have to modify the /opt/dsf/conf/config.json file because the conf.json is preset while the setup. while the setup i can see that the firmwar is installing. with an other sbc i get the error that the sbc is not found until i modify the config.json and i dont see firmware installing.

it is possible, while the sbc setup or installation, to modify the config.json or use the standard config.json ? this should be easy to do or not ?

this would make it much easier to setup an non raspbery sbc.

beside this, it was possible to install and start the managment plugin but not install others without the errormessage and both duetplugin services was running

chrishamm

@joeko You can delete /opt/dsf/conf/config.json and then restart DCS or the Pi to revert to the defaults. DCS creates the config file automatically if it does not exist.

joeko

@chrishamm said in InternalServerException in InstallPlugin::

@joeko You can delete /opt/dsf/conf/config.json and then restart DCS or the Pi to revert to the defaults. DCS creates the config file automatically if it does not exist.

hmm, you have misunderstood me.
i am talking about a new setup for the sbc like written in the guide
after

wget -q https://pkg.duet3d.com/duet3d.gpg
wget -q https://pkg.duet3d.com/duet3d.list
sudo mv duet3d.gpg /etc/apt/trusted.gpg.d/
sudo mv duet3d.list /etc/apt/sources.list.d/duet3d.list
sudo chown root:root /etc/apt/trusted.gpg.d/duet3d.gpg
sudo chown root:root /etc/apt/sources.list.d/duet3d.list

i have to

sudo apt-get install apt-transport-https
sudo apt-get update
sudo apt-get install duetsoftwareframework

the /opt/dsf/conf/config.json will create with

sudo apt-get install duetsoftwareframework

this config.json has to modify with an other sbc than raspberry and the result is an error because the sbc is not found. if it would be possible to modify the config.json in this step

sudo apt-get install duetsoftwareframework

it would be possible to make it easy to setup the sbc and should be easy to make it enable.
also, is there a way to install the beta firmware ?

sudo apt-get update
sudo apt-get upgrade

doesnt do it

Phaedrux

@joeko said in InternalServerException in InstallPlugin::

is there a way to install the beta firmware ?

First you must add the unstable branch repository

https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Software_Installation

joeko

@phaedrux said in InternalServerException in InstallPlugin::

@joeko said in InternalServerException in InstallPlugin::

is there a way to install the beta firmware ?

First you must add the unstable branch repository

https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Software_Installation

yes i know and i did but after apt-get update and upgrade i get the message that updates hold back without any reason. (i wrote it in post 259113 from 17.11
without sbc i can use M997 for update but in sbc mode ?

Phaedrux

I'd be interested to see if you run into the same issues if you tried starting with the latest DuetPi image.

joeko

@phaedrux said in InternalServerException in InstallPlugin::

I'd be interested to see if you run into the same issues if you tried starting with the latest DuetPi image.

that mean ready duetpi image ?
hmm, i have to install it because i use the raspberry only for testing and than the odroid. the test tell me that i have to modify the config.jason as soon as possible the odroid runs very fine. cool, fast and stable but updates are a problem and plugins doesnt work

joeko

i talk the most time with me but it is also for other user
now i got the install without errormessage and install the stable firmware is possible. plugin i dont try further until a new stable firmware will arrive.
after

sudo apt-get install duetsoftwareframework

i modifeyed the config.json to the correct gpio pins. than i deinstalled it again, reboot and installed it again and now....all fine also with installing the stable firmware. plugins i dont have tried because also with the raspberry and manuel installing like in the guide it was not possible (and all needed services was running also appamor) in standalone it tried it with the latest beta and all was fine