renderd "socket bind failed" after reboot

Question

I have followed the instructions of https://switch2osm.org/serving-tiles/manually-building-a-tile-server-20-04-lts/ and it worked initially, but after rebooting I get the following error message:

el@openstreetmap:~$ renderd -f -c /usr/local/etc/renderd.conf
renderd[1591]: Rendering daemon started
renderd[1591]: Initiating request_queue
renderd[1591]: Parsing section renderd
renderd[1591]: Parsing render section 0
renderd[1591]: Parsing section mapnik
renderd[1591]: Parsing section ajt
renderd[1591]: config renderd: unix socketname=/var/run/renderd/renderd.sock
renderd[1591]: config renderd: num_threads=4
renderd[1591]: config renderd: num_slaves=0
renderd[1591]: config renderd: tile_dir=/var/lib/mod_tile
renderd[1591]: config renderd: stats_file=/var/run/renderd/renderd.stats
renderd[1591]: config mapnik:  plugins_dir=/usr/lib/mapnik/3.0/input
renderd[1591]: config mapnik:  font_dir=/usr/share/fonts/truetype
renderd[1591]: config mapnik:  font_dir_recurse=1
renderd[1591]: config renderd(0): Active
renderd[1591]: config renderd(0): unix socketname=/var/run/renderd/renderd.sock
renderd[1591]: config renderd(0): num_threads=4
renderd[1591]: config renderd(0): tile_dir=/var/lib/mod_tile
renderd[1591]: config renderd(0): stats_file=/var/run/renderd/renderd.stats
renderd[1591]: config map 0:   name(ajt) file(/home/renderaccount/src/openstreetmap-carto/mapnik.xml) uri(/hot/) htcp() host(localhost)
renderd[1591]: Initialising unix server socket on /var/run/renderd/renderd.sock
socket bind failed for: /var/run/renderd/renderd.sock
el@openstreetmap:~$

Answer 1

0

Are you sure that the UNIX user you are running this under ("el") actually has write permissions on /var/run/renderd? Try the command touch /var/run/renderd/testfile to check. If that gives you an error messsage, you need to "su" into a different account or change the permissions or ownership of /var/run/renderd.

permanent link

answered 24 Sep '21, 10:31

Frederik Ramm ♦
82.5k●92●720●1273
accept rate: 23%

Answer 2

The "Running renderd in the background" part of https://switch2osm.org/serving-tiles/manually-building-a-tile-server-20-04-lts/ ensures that access to /var/run is maintained. After a reboot, if you want to run

renderd -f -c /usr/local/etc/renderd.conf

again you'll need to do

sudo mkdir /var/run/renderd
sudo chown renderaccount /var/run/renderd

again first. https://switch2osm.org/serving-tiles/manually-building-a-tile-server-20-04-lts/ doesn't mention this because it doesn't expect you to want to run "Running renderd for the first time" more than once.

renderd "socket bind failed" after reboot

Follow this question

Related questions