Starting network unknown bind error 1 failed network failed to start terminating

I’m having difficulty getting monerod to start. I have seen the prior issue where this message occurs. The solution was to make sure that no other copies of monerod were running. I have ensured this, and am still have the problem. I know it is a config issue, but haven’t been able to spot it. Any help would be greatly appreciated.

Here is the startup log:

2022-02-14 20:32:31.077	I Monero 'Oxygen Orion' (v0.17.3.0-release)
2022-02-14 20:32:31.084	I Initializing cryptonote protocol...
2022-02-14 20:32:31.084	I Cryptonote protocol initialized OK
2022-02-14 20:32:31.088	I Initializing core...
2022-02-14 20:32:31.093	I Loading blockchain from folder /data/monero/lmdb ...
2022-02-14 20:32:36.837	I Loading checkpoints
2022-02-14 20:33:38.227	I Core initialized OK
2022-02-14 20:33:38.227	I Initializing p2p server...
2022-02-14 20:33:38.286	I p2p server initialized OK
2022-02-14 20:33:38.295	I Initializing core RPC server...
2022-02-14 20:33:38.301	I Binding on 127.0.0.1 (IPv4):18081
2022-02-14 20:33:39.237	F Error starting server: Failed to bind IPv4 (set to required)
2022-02-14 20:33:39.237	I Deinitializing p2p...
2022-02-14 20:33:39.237	I Deinitializing core...
2022-02-14 20:33:39.255	I Stopping cryptonote protocol...
2022-02-14 20:33:39.255	I Cryptonote protocol stopped successfully
2022-02-14 20:33:39.255	E Exception in main! Failed to initialize core RPC server.

I’m running on Linux Mint, latest release «una» based on Ubuntu 20.04:

dan@bullwinkle:~$ cat /etc/upstream-release/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu Focal Fossa"

Here is the bitmonero.conf file:

# /data/monero/bitmonero.conf

# Data directory
data-dir=/data/monero

# Log file
log-file=/data/monero/monero.log
log-level=0

# Tor: tell monerod your onion address so it can be advertised on P2P network
anonymous-inbound=mvfnom6ngqpdup6hol7rtk4txkbqja4ad3s2nu7nnjtwshdqlsyx53yd.onion:18083,127.0.0.1:18083,25

# Tor: be forgiving to connecting wallets; suggested by http://xmrguide42y34onq.onion/remote_nodes
disable-rpc-ban=1

# P2P full node
p2p-bind-ip=127.0.0.1 # Bind to TOR
p2p-bind-port=9050   # Bind to default port

# RPC TLS
rpc-ssl=autodetect             # Use TLS if client wallet supports it (the default behavior); the certificate will be generated on the fly on every restart

# RPC open node
public-node=0                  # Don't Advertise to other users they can use this node as a remote one for connecting their wallets
# confirm-external-bind=1        # Open Node (confirm)
rpc-bind-ip=127.0.0.1          # Bind to TOR
rpc-bind-port=18081            # Bind to default port (the Open Node)
# restricted-rpc=1               # Obligatory for Open Node interface
# rpc-restricted-bind-ip=0.0.0.0     #
# rpc-restricted-bind-port=18083
no-igd=1                       # Disable UPnP port mapping
no-zmq=1                       # Disable ZMQ RPC server to decrease attack surface (it's not used)

# Tor: broadcast transactions originating from connected wallets over Tor (does not concern relayed transactions)
tx-proxy=tor,127.0.0.1:9050,16
pad-transactions=1

# Tor: add P2P seed nodes for the Tor network
# For an up-to-date list of working nodes see https://www.ditatompel.com/monero/node-peers
add-peer=z3denj4xaipjcljghwl4r76b5adj4qmmq7lwf4asoodqydka3wdr4myd.onion:18083
add-peer=pguw4kurjlkldao3s2x73x4iigx5rehjrdfvu4hplp6alyw3zvrq5nad.onion:18083
add-peer=kxobl5btvt4tqjizxr5czoxgpsvgcdapygiwuimp3fpa77r7v7appyqd.onion:18083
add-peer=hzq4ilpxw4e6woti2u5qofwvmvgxgse5c4at4jy6u3yxnuts25vrq4qd.onion:18083
add-peer=vaetyrrkyycaa33uyjfcxjrz736s5pkq2cpmpvyiki2y7hpxa5xivoyd.onion:18083
add-peer=55f5lsughwodhqtuf62mb67mggljsjd5iggwjhe6ssymyafrdl6ei2yd.onion:18083
add-peer=zrncccrzltp47e5qbb65c22o66qof3i5ke6om5ppf7466kogytjp6uad.onion:18083

# Make the seed nodes permanent to fix monerod issue of not maintaining enough connections,
# based on this reddit comment:
# https://www.reddit.com/r/monerosupport/comments/k3m3x2/comment/ge5ehcy/?utm_source=share&utm_medium=web2x&context=3
add-priority-node=z3denj4xaipjcljghwl4r76b5adj4qmmq7lwf4asoodqydka3wdr4myd.onion:18083
add-priority-node=pguw4kurjlkldao3s2x73x4iigx5rehjrdfvu4hplp6alyw3zvrq5nad.onion:18083
add-priority-node=kxobl5btvt4tqjizxr5czoxgpsvgcdapygiwuimp3fpa77r7v7appyqd.onion:18083
add-priority-node=hzq4ilpxw4e6woti2u5qofwvmvgxgse5c4at4jy6u3yxnuts25vrq4qd.onion:18083
add-priority-node=vaetyrrkyycaa33uyjfcxjrz736s5pkq2cpmpvyiki2y7hpxa5xivoyd.onion:18083
add-priority-node=55f5lsughwodhqtuf62mb67mggljsjd5iggwjhe6ssymyafrdl6ei2yd.onion:18083
add-priority-node=zrncccrzltp47e5qbb65c22o66qof3i5ke6om5ppf7466kogytjp6uad.onion:18083

# Mempool size
max-txpool-weight=268435456    # Maximum unconfirmed transactions pool size in bytes (here 256MB, default ~618MB)

# Slow but reliable db writes
db-sync-mode=safe:sync

# Limits on peer connections
out-peers=50
in-peers=50

# Limit bandwidth
limit-rate-down=500
limit-rate-up=50

# Prevent malicious forks
enforce-dns-checkpointing=1


# Performance parameters
max-concurrency=4           # Number of threads to use for parallel jobs. 
prep-blocks-threads=3       # Number of threads for syncing blockchain

Here is the torrc file:

## Configuration file for a typical Tor user
## Last updated 9 October 2013 for Tor 0.2.5.2-alpha.
## (may or may not work for much older or much newer versions of Tor.)
##
## Lines that begin with "## " try to explain what's going on. Lines
## that begin with just "#" are disabled commands: you can enable them
## by removing the "#" symbol.
##
## See 'man tor', or https://www.torproject.org/docs/tor-manual.html,
## for more options you can use in this file.
##
## Tor will look for this file in various places based on your platform:
## https://www.torproject.org/docs/faq#torrc

## Tor opens a socks proxy on port 9050 by default -- even if you don't
## configure one below. Set "SocksPort 0" if you plan to run Tor only
## as a relay, and not make any local application connections yourself.
#SocksPort 9050 # Default: Bind to localhost:9050 for local connections.
#SocksPort 192.168.0.1:9100 # Bind to this address:port too.

## Entry policies to allow/deny SOCKS requests based on IP address.
## First entry that matches wins. If no SocksPolicy is set, we accept
## all (and only) requests that reach a SocksPort. Untrusted users who
## can access your SocksPort may be able to learn about the connections
## you make.
SocksPolicy accept 192.168.0.0/16
SocksPolicy accept 127.0.0.1/32
SocksPolicy reject *

## Select countries for exit nodes
ExitNodes {us}
## Use only the selected nodes. Do not make excptions.
StrictNodes 1

## Logs go to stdout at level "notice" unless redirected by something
## else, like one of the below lines. You can have as many Log lines as
## you want.
##
## We advise using "notice" in most cases, since anything more verbose
## may provide sensitive information to an attacker who obtains the logs.
##
## Send all messages of level 'notice' or higher to /var/log/tor/notices.log
Log notice file /var/log/tor/notices.log
## Send every possible message to /var/log/tor/debug.log
#Log debug file /var/log/tor/debug.log
## Use the system log instead of Tor's logfiles
#Log notice syslog
## To send all messages to stderr:
#Log debug stderr

## Uncomment this to start the process in the background... or use
## --runasdaemon 1 on the command line. This is ignored on Windows;
## see the FAQ entry if you want Tor to run as an NT service.
#RunAsDaemon 1

## The directory for keeping all the keys/etc. By default, we store
## things in $HOME/.tor on Unix, and in Application Datator on Windows.
#DataDirectory /var/lib/tor

## The port on which Tor will listen for local connections from Tor
## controller applications, as documented in control-spec.txt.
ControlPort 9051
## If you enable the controlport, be sure to enable one of these
## authentication methods, to prevent attackers from accessing it.
HashedControlPassword 16:3691B28D305703B160CE8F6F8F7739D084343718F39604DA8E43AD6FEA
#CookieAuthentication 1

############### This section is just for location-hidden services ###

## Once you have configured a hidden service, you can look at the
## contents of the file ".../hidden_service/hostname" for the address
## to tell people.
##
## HiddenServicePort x y:z says to redirect requests on port x to the
## address y:z.

HiddenServiceDir /var/lib/tor/hidden_service/
HiddenServicePort 8333 127.0.0.1:8333
HiddenServicePort 18081 127.0.0.1:18081
HiddenServicePort 18083 127.0.0.1:18083

################ This section is just for relays #####################
#
## See https://www.torproject.org/docs/tor-doc-relay for details.

## Required: what port to advertise for incoming Tor connections.
## This is the configuration the use when behind NAT
## Public port
#ORPort 9010 NoListen
## Internal port
#ORPort 9001 NoAdvertise

## If you want to listen on a port other than the one advertised in
## ORPort (e.g. to advertise 443 but bind to 9090), you can do it as
## follows.  You'll need to do ipchains or other port forwarding
## yourself to make this work.
#ORPort 443 NoListen
#ORPort 127.0.0.1:9090 NoAdvertise

## The IP address or full DNS name for incoming connections to your
## relay. Leave commented out and Tor will guess.
#Address noname.example.com

## If you have multiple network interfaces, you can specify one for
## outgoing traffic to use.
# OutboundBindAddress 10.0.0.5

## A handle for your relay, so people don't have to refer to it by key.
#Nickname danandgeno

## Define these to limit how much relayed traffic you will allow. Your
## own traffic is still unthrottled. Note that RelayBandwidthRate must
## be at least 20 KB.
## Note that units for these config options are bytes per second, not bits
## per second, and that prefixes are binary prefixes, i.e. 2^10, 2^20, etc.
#RelayBandwidthRate 100 KB  # Throttle traffic to 100KB/s (800Kbps)
#RelayBandwidthBurst 200 KB # But allow bursts up to 200KB/s (1600Kbps)

## Use these to restrict the maximum traffic per day, week, or month.
## Note that this threshold applies separately to sent and received bytes,
## not to their sum: setting "4 GB" may allow up to 8 GB total before
## hibernating.
##
## Set a maximum of 4 gigabytes each way per period.
#AccountingMax 4 GB
## Each period starts daily at midnight (AccountingMax is per day)
#AccountingStart day 00:00
## Each period starts on the 3rd of the month at 15:00 (AccountingMax
## is per month)
#AccountingStart month 3 15:00

## Administrative contact information for this relay or bridge. This line
## can be used to contact you if your relay or bridge is misconfigured or
## something else goes wrong. Note that we archive and publish all
## descriptors containing these lines and that Google indexes them, so
## spammers might also collect them. You may want to obscure the fact that
## it's an email address and/or generate a new address for this purpose.
#ContactInfo Dan <danvondra AT protonmail dot com>
## You might also include your PGP or GPG fingerprint if you have one:
#ContactInfo 0xFFFFFFFF Random Person <nobody AT example dot com>

## Uncomment this to mirror directory information for others. Please do
## if you have enough bandwidth.
# DirPort 9030 # what port to advertise for directory connections
## If you want to listen on a port other than the one advertised in
## DirPort (e.g. to advertise 80 but bind to 9091), you can do it as
## follows.  below too. You'll need to do ipchains or other port
## forwarding yourself to make this work.
#DirPort 80 NoListen
#DirPort 127.0.0.1:9091 NoAdvertise
## Uncomment to return an arbitrary blob of html on your DirPort. Now you
## can explain what Tor is if anybody wonders why your IP address is
## contacting them. See contrib/tor-exit-notice.html in Tor's source
## distribution for a sample.
#DirPortFrontPage /etc/tor/tor-exit-notice.html

## Uncomment this if you run more than one Tor relay, and add the identity
## key fingerprint of each Tor relay you control, even if they're on
## different networks. You declare it here so Tor clients can avoid
## using more than one of your relays in a single circuit. See
## https://www.torproject.org/docs/faq#MultipleRelays
## However, you should never include a bridge's fingerprint here, as it would
## break its concealability and potentionally reveal its IP/TCP address.
#MyFamily $keyid,$keyid,...

## A comma-separated list of exit policies. They're considered first
## to last, and the first match wins. If you want to _replace_
## the default exit policy, end this with either a reject *:* or an
## accept *:*. Otherwise, you're _augmenting_ (prepending to) the
## default exit policy. Leave commented to just use the default, which is
## described in the man page or at
## https://www.torproject.org/documentation.html
##
## Look at https://www.torproject.org/faq-abuse.html#TypicalAbuses
## for issues you might encounter if you use the default exit policy.
##
## If certain IPs and ports are blocked externally, e.g. by your firewall,
## you should update your exit policy to reflect this -- otherwise Tor
## users will be told that those destinations are down.
##
## For security, by default Tor rejects connections to private (local)
## networks, including to your public IP address. See the man page entry
## for ExitPolicyRejectPrivate if you want to allow "exit enclaving".
##
#ExitPolicy accept *:6660-6667,reject *:* # allow irc ports but no more
#ExitPolicy accept *:119 # accept nntp as well as default exit policy
ExitPolicy reject *:* # no exits allowed

## Bridge relays (or "bridges") are Tor relays that aren't listed in the
## main directory. Since there is no complete public list of them, even an
## ISP that filters connections to all the known Tor relays probably
## won't be able to block all the bridges. Also, websites won't treat you
## differently because they won't know you're running Tor. If you can
## be a real relay, please do; but if not, be a bridge!
#BridgeRelay 1
## By default, Tor will advertise your bridge to users through various
## mechanisms like https://bridges.torproject.org/. If you want to run
## a private bridge, for example because you'll give out your bridge
## address manually to your friends, uncomment this line:
#PublishServerDescriptor 0