• Tags
  • Documentation
  • Order
  • Register
  • Login
Duet3D Logo Duet3D
  • Tags
  • Documentation
  • Order
  • Register
  • Login

3.2b1 Duet 3 (DCS is not started)

Scheduled Pinned Locked Moved
Firmware installation
10
38
1.4k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • undefined
    Dougal1957
    last edited by 15 Sept 2020, 19:06

    Fixed now thanks (one of the guys in a discord I am in suggested how I could edit it with NANO Thanks Luke

    1 Reply Last reply Reply Quote 0
    • undefined
      bcrazycramer
      last edited by 15 Sept 2020, 19:06

      Do you know why this isn't working?

      pi@duet3:~$ sudo /opt/dsf/bin/DuetWebServer
      crit: Microsoft.AspNetCore.Server.Kestrel[0]
      Unable to start Kestrel.
      System.IO.IOException: Failed to bind to address http://[::]:80: address already in use.
      ---> Microsoft.AspNetCore.Connections.AddressInUseException: Address already in use
      ---> System.Net.Sockets.SocketException (98): Address already in use
      at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName)
      at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
      at System.Net.Sockets.Socket.Bind(EndPoint localEP)
      at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind()
      --- End of inner exception stack trace ---
      at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind()
      at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketTransportFactory.BindAsync(EndPoint endpoint, CancellationToken cancellationToken)
      at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.<>c__DisplayClass21_01.<<StartAsync>g__OnBind|0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context) --- End of inner exception stack trace --- at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context) at Microsoft.AspNetCore.Server.Kestrel.Core.ListenOptions.BindAsync(AddressBindContext context) at Microsoft.AspNetCore.Server.Kestrel.Core.AnyIPListenOptions.BindAsync(AddressBindContext context) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.EndpointsStrategy.BindAsync(AddressBindContext context) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindAsync(IServerAddressesFeature addresses, KestrelServerOptions serverOptions, ILogger logger, Func2 createBinding)
      at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.StartAsync[TContext](IHttpApplication1 application, CancellationToken cancellationToken) Unhandled exception. System.IO.IOException: Failed to bind to address http://[::]:80: address already in use. ---> Microsoft.AspNetCore.Connections.AddressInUseException: Address already in use ---> System.Net.Sockets.SocketException (98): Address already in use at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName) at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Bind(EndPoint localEP) at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind() --- End of inner exception stack trace --- at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind() at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketTransportFactory.BindAsync(EndPoint endpoint, CancellationToken cancellationToken) at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.<>c__DisplayClass21_01.<<StartAsync>g__OnBind|0>d.MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
      at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context)
      --- End of inner exception stack trace ---
      at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context)
      at Microsoft.AspNetCore.Server.Kestrel.Core.ListenOptions.BindAsync(AddressBindContext context)
      at Microsoft.AspNetCore.Server.Kestrel.Core.AnyIPListenOptions.BindAsync(AddressBindContext context)
      at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.EndpointsStrategy.BindAsync(AddressBindContext context)
      at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindAsync(IServerAddressesFeature addresses, KestrelServerOptions serverOptions, ILogger logger, Func2 createBinding) at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.StartAsync[TContext](IHttpApplication1 application, CancellationToken cancellationToken)
      at Microsoft.AspNetCore.Hosting.GenericWebHostService.StartAsync(CancellationToken cancellationToken)
      at Microsoft.Extensions.Hosting.Internal.Host.StartAsync(CancellationToken cancellationToken)
      at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)
      at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)
      at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.Run(IHost host)
      at DuetWebServer.Program.Main(String[] args) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetWebServer/Program.cs:line 24
      Aborted
      pi@duet3:~$

      undefined 1 Reply Last reply 15 Sept 2020, 19:07 Reply Quote 0
      • undefined
        chrishamm administrators @bcrazycramer
        last edited by chrishamm 15 Sept 2020, 19:07

        @bcrazycramer It looks like there is another web server running on the same port (80). Do you have Apache or another HTTP server installed on your system? If not, try rebooting the Pi and check if that makes a difference.

        PS: DWS will usually run in the background as its own service, so there should be no need to start it manually. Follow my last reply describing the usage of journalctl to figure out why DCS/DWS isn't started.

        Duet software engineer

        1 Reply Last reply Reply Quote 0
        • undefined
          bcrazycramer
          last edited by 15 Sept 2020, 19:19

          I get the same after rebooting.

          I'm not using the Raspberry Pi for anything else except the Duet 3. I do have VNC enabled and SSH.

          undefined undefined 2 Replies Last reply 15 Sept 2020, 19:22 Reply Quote 0
          • undefined
            chrishamm administrators @bcrazycramer
            last edited by chrishamm 15 Sept 2020, 19:22

            @bcrazycramer Please see my earlier post where I mention journalctl.

            [edit]Sorry, linking posts doesn't seem to work too well[/edit]

            Duet software engineer

            undefined 1 Reply Last reply 15 Sept 2020, 19:24 Reply Quote 0
            • undefined
              Dougal1957 @bcrazycramer
              last edited by 15 Sept 2020, 19:22

              @bcrazycramer I get the same as well not that I have a clue what it means!

              1 Reply Last reply Reply Quote 0
              • undefined
                bcrazycramer
                last edited by 15 Sept 2020, 19:22

                fdd68c9f-5749-4f06-abd3-5f1bf7c3413b-image.png

                1 Reply Last reply Reply Quote 0
                • undefined
                  bcrazycramer @chrishamm
                  last edited by 15 Sept 2020, 19:24

                  @chrishamm said in 3.2b1 Duet 3 (DCS is not started):

                  @bcrazycramer Please see my earlier post.

                  Which part?

                  undefined 1 Reply Last reply 15 Sept 2020, 19:25 Reply Quote 0
                  • undefined
                    Dougal1957 @bcrazycramer
                    last edited by 15 Sept 2020, 19:25

                    @bcrazycramer it was to me asking me to run the journal cads to see what was happening!

                    1 Reply Last reply Reply Quote 0
                    • undefined
                      bcrazycramer
                      last edited by 15 Sept 2020, 19:28

                      2293ef33-61e6-4768-8fa0-50e60461f90e-image.png

                      undefined 1 Reply Last reply 16 Sept 2020, 11:47 Reply Quote 0
                      • undefined
                        chrishamm administrators @bcrazycramer
                        last edited by 16 Sept 2020, 11:47

                        @bcrazycramer That's looking good. You should be able to connect to your board over HTTP.

                        The GitHub releases and package feeds have been updated with the latest hotfixes as promised. If you're having problems, consider running another software update.

                        Duet software engineer

                        1 Reply Last reply Reply Quote 0
                        • ?
                          A Former User @chrishamm
                          last edited by A Former User 16 Sept 2020, 17:32

                          @chrishamm said in 3.2b1 Duet 3 (DCS is not started):

                          I suspect there may be a permission issue going on because we changed from root to a dedicate dsf user in the latest pre-release.

                          Can you explain the thinking behind changing from root to a dsf user?

                          As to be honest if it was working before, this seems to be a prime example of changes being made for the sake of it for diminishing returns.

                          As my old journeyman used to say : if it's working fuc*ing leave it alone.

                          undefined 1 Reply Last reply 16 Sept 2020, 19:55 Reply Quote 0
                          • undefined
                            Phaedrux Moderator @A Former User
                            last edited by 16 Sept 2020, 19:55

                            @CaLviNx Running things as root is generally frowned upon for security sake.

                            Z-Bot CoreXY Build | Thingiverse Profile

                            ? 1 Reply Last reply 16 Sept 2020, 20:07 Reply Quote 0
                            • ?
                              A Former User @Phaedrux
                              last edited by A Former User 16 Sept 2020, 20:07

                              @Phaedrux that I understand but in this instance it should be fine as people "should" have their home network secured.

                              My printers all connected via my own wireless "intranet" that is not connected to the outside world, so no one can get into that small network, house innternet itself is run through a Secure DDWRT equipped router which is well locked down, and I'm not the most IT tech savvy but I'm I am happy to run my printers in "Root" mode.

                              So to find yet another thing changed for the sake of change just trips things/people up as this instance proven

                              undefined 1 Reply Last reply 16 Sept 2020, 20:08 Reply Quote 0
                              • undefined
                                Phaedrux Moderator @A Former User
                                last edited by 16 Sept 2020, 20:08

                                @CaLviNx said in 3.2b1 Duet 3 (DCS is not started):

                                "should" have their home network secured.

                                Defence in depth would urge you to not assume any favorable circumstances exist.

                                Z-Bot CoreXY Build | Thingiverse Profile

                                ? 1 Reply Last reply 16 Sept 2020, 20:09 Reply Quote 1
                                • ?
                                  A Former User @Phaedrux
                                  last edited by 16 Sept 2020, 20:09

                                  @Phaedrux and to counter that why should people not be allowed to choose for themselves and a notification in the docs would suffice?

                                  undefined ? 2 Replies Last reply 16 Sept 2020, 20:16 Reply Quote 0
                                  • undefined
                                    dc42 administrators
                                    last edited by 16 Sept 2020, 20:12

                                    Given the huge number of hacking attempts made against everyone these days, we would rightly be castigated if we continued running DSF as root. This is even more important now that DSF supports plugins.

                                    Duet WiFi hardware designer and firmware engineer
                                    Please do not ask me for Duet support via PM or email, use the forum
                                    http://www.escher3d.com, https://miscsolutions.wordpress.com

                                    1 Reply Last reply Reply Quote 0
                                    • undefined
                                      dc42 administrators @A Former User
                                      last edited by dc42 16 Sept 2020, 20:16

                                      @CaLviNx said in 3.2b1 Duet 3 (DCS is not started):

                                      @Phaedrux and to counter that why should people not be allowed to choose for themselves and a notification in the docs would suffice?

                                      If you want to run DSF as root, you can modify DSF - it's open source. If you don't know how to, then IMO you shouldn't be trusted to run DSF as root. I don't want your RPi running DSF to be part of a botnet.

                                      Duet WiFi hardware designer and firmware engineer
                                      Please do not ask me for Duet support via PM or email, use the forum
                                      http://www.escher3d.com, https://miscsolutions.wordpress.com

                                      undefined 1 Reply Last reply 16 Sept 2020, 20:30 Reply Quote 0
                                      • ?
                                        A Former User @A Former User
                                        last edited by 16 Sept 2020, 20:23

                                        @CaLviNx said in 3.2b1 Duet 3 (DCS is not started):

                                        @Phaedrux and to counter that why should people not be allowed to choose for themselves and a notification in the docs would suffice?

                                        because secure by default solves more problems than it can create? (ref OpenBSD it won't stop you from pulling down your pants, even though it ships with belts and suspenders)

                                        1 Reply Last reply Reply Quote 1
                                        • undefined
                                          bot @dc42
                                          last edited by 16 Sept 2020, 20:30

                                          @dc42 said in 3.2b1 Duet 3 (DCS is not started):

                                          [...] I don't want your RPi running DSF to be part of a botnet.

                                          Wait... is that, like, discouraged or something? 😁 😁

                                          *not actually a robot

                                          1 Reply Last reply Reply Quote 0
                                          24 out of 38
                                          • First post
                                            24/38
                                            Last post
                                          Unless otherwise noted, all forum content is licensed under CC-BY-SA