Uploaded image for project: 'Bedrock Dedicated Server'
  1. Bedrock Dedicated Server
  2. BDS-1264

Unable to launch - Network port occupied, can't start server.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Incomplete
    • None
    • 1.9.0.15
    • Unconfirmed

      Upon trying to launched bedrock server, it appears that it is ignoring both options within server.properties:

       

      server-port=19132
      server-portv6=19133

       

      The following output is observed:

      # LD_LIBRARY_PATH=. ./bedrock_server
      NO LOG FILE! - setting up server logging...
      [2019-08-08 13:58:15 INFO] Starting Server
      [2019-08-08 13:58:15 INFO] Version 1.12.0.28
      [2019-08-08 13:58:15 INFO] Session ID e0d9fbf4-a584-4d6e-8df1-03e76330598f
      [2019-08-08 13:58:15 INFO] Level Name: Bedrock level
      [2019-08-08 13:58:15 INFO] Game mode: 0 Survival
      [2019-08-08 13:58:15 INFO] Difficulty: 1 EASY
      [2019-08-08 13:58:16 INFO] IPv4 supported, port: 0
      [2019-08-08 13:58:16 INFO] IPv6 supported, port: 0
      [2019-08-08 13:58:16 ERROR] Network port occupied, can't start server.
      Quit correctly

      It appears that BDS is trying to bind both IPv6 and IPv4 to port 0.

      Also, it is incorrectly identifying IPv6 as being supported, as this is disabled on the host via grub upon launch:

      default/grub:10:GRUB_CMDLINE_LINUX="ipv6.disable=1" 
      

      This is with a fresh copy of BDS, with default config values present:

      server-name=Dedicated Server
      gamemode=survival
      difficulty=easy
      allow-cheats=false
      max-players=10
      online-mode=true
      white-list=false
      server-port=19132
      server-portv6=19133
      view-distance=10
      tick-distance=4
      player-idle-timeout=30
      max-threads=8
      level-name=Bedrock level
      level-seed=
      default-player-permission-level=member
      texturepack-required=false
      content-log-file-enabled=false
      

      No other processes or services are running on the ports set within the configuration.

            Unassigned Unassigned
            ErTnEc Paul Bramhall
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: