Skip to content

Order of lines in the configuration file determines whether apache starts or not? #3

@SomeoneElseOSM

Description

@SomeoneElseOSM

This is on Ubuntu 22.04, and the apache there identifies itself as "Apache/2.4.52 (Ubuntu)"

mod_mbtiles was installed as per https://github.com/systemed/mod_mbtiles#installation ("sudo apt install apache2-dev libsqlite3-dev", then "sudo apxs -lsqlite3 -i -a -c mod_mbtiles.c"). It was happily serving tiles from one .mbtiles file until I tried to add a second. In the "<VirtualHost *:80>" in "000-default.conf" after " DocumentRoot /var/www/html" I have:

MbtilesEnabled true
MbtilesAdd sve01 /var/www/html/vector/sve01/tilemaker_sve01.mbtiles
MbtilesAdd omt_ny /var/www/html/vector/omt_ny/tilemaker_omt_ny.mbtiles

This fails, and "systemctl status apache2.service" says it failed with a fairly unhelpful "Segmentation fault (core dumped)".
However, if I swap the entries around:

MbtilesEnabled true
MbtilesAdd omt_ny /var/www/html/vector/omt_ny/tilemaker_omt_ny.mbtiles
MbtilesAdd sve01 /var/www/html/vector/sve01/tilemaker_sve01.mbtiles

Apache is a happy bunny! I have not changed https://github.com/systemed/mod_mbtiles/blob/master/mod_mbtiles.c , and it still has "#define MAX_TILESETS 20" in it. In addition to the various modules installed by default I also have "LoadModule tile_module /usr/lib/apache2/modules/mod_tile.so" for raster tiles.

The also error occurs (with the entries the other way around) if I use two "known good" mbtiles files (two differently named copies of the same working one).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions