Single Setup for Duet 3

4lathe

@4lathe So I just setup my rpi4 in advance of receiving my duet 3 this week. No errors were thrown using the oem duzuki instructions. However when I http://127.0.0.1 on the pi I get
This page isn't working
127.0.0.1 is currently unable to handle this request.
Http error 500

When I run the journal I can see some errors but I have no idea what to do with any of it.
Any help much appreciated!

A Former User

Maybe post some of the errors?

4lathe

@4lathe error shown in journal was
Cannot assign requested address /var/run/duet.sock

4lathe

@4lathe that came right after
Request starting HTTP/1.1 GET http://127.0.0.1/

4lathe

@4lathe actually others are just a repetition of that error.

A Former User

@4lathe said in Single Setup for Duet 3:

Cannot assign requested address /var/run/duet.sock

i think that would suggest you either don't have permissions, or its already in use. did you use sudo to run as root?

4lathe

@bearer I was logged in as pi when I executed all the dozuki instructions. Many of those use sudo. I did have to add sudo in front of one of the commands though.

T3P3Tony

@4lathe DSF wont serve anything is the Duet is not connected.

4lathe

@T3P3Tony ahhhhh. What was that error? Any good way to test that the web server is running?

A Former User

@4lathe said in Single Setup for Duet 3:

So I just setup my rpi4 in advance of receiving my duet 3 this week

Ah, as tony says, thats not gonna work. everything depends on DuetControlServer, and it won't start without the Duet3 connected.

4lathe

@bearer ok so just leave it for now?

A Former User

@4lathe said in Single Setup for Duet 3:

so just leave it for now?

yeah, might as well, you won't be able to verify the software anyways.

Although I'm puzzled by the fact that you say you get a HTTP 500 error if the Duet3 isn't connected, which is why I glossed over that bit initially.

4lathe

@bearer no idea.

gtj0

@bearer said in Single Setup for Duet 3:

@4lathe said in Single Setup for Duet 3:

so just leave it for now?

yeah, might as well, you won't be able to verify the software anyways.

Although I'm puzzled by the fact that you say you get a HTTP 500 error if the Duet3 isn't connected, which is why I glossed over that bit initially.

The DuetWebServer will start but it communicates with the DuetControlServer via that /var/run/duet.sock socket which is created by the DuetControlServer and that won't even start if it doesn't get a response from the Duet3 via the SPI bus. So when you access the web server, it responds with a 500 because it can't connect to that socket.

A Former User

@gtj0 ah, must have changed the behavior at some point then, previously it would terminate right away if started manually without DuetControlServer; and the systemd service won't even start.

Anyways, moot point, gotta wait for the board in any case.

4lathe

@bearer thx much for the explanation.