kartoza / docker-qgis-server

A dockerfile that contains a running QGIS server
68 stars 31 forks source link

The requested URL /cgi-bin/qgis_mapserv.fcgi was not found on this server. #8

Closed rduivenvoorde closed 7 years ago

rduivenvoorde commented 8 years ago

Hi, here with @tudorbarascu trying to run the image, but running:

http://localhost:8081/cgi-bin/qgis_mapserv.fcgi?

Shows: the requested URL /cgi-bin/qgis_mapserv.fcgi was not found on this server.

We found the qgis_mapserv.fcgi in /usr/bin cannot find configs pointing to that.

Any hints

timlinux commented 8 years ago

Thanks @rduivenvoorde I am having issues with the build service - can you try build it locally and see if you get the same issue? Actually the issue with the build service is for the QGIS Desktop images which the server now inherits - so to test you need to first build the desktop image then the server one. I will try to trigger a rebuild here and see if the hub is behaving again...

timlinux commented 8 years ago

Desktop builds triggered - results will show here: https://hub.docker.com/r/kartoza/qgis-desktop/builds/

tudorbarascu commented 8 years ago

Hi Tim, I followed your advice and I built the desktop and the server images and the issue persists.

timlinux commented 8 years ago

Thanks @tudorbarascu

docker run --rm kartoza/qgis-desktop:2.12 ls /usr/bin | grep gis

might do it...

tudorbarascu commented 8 years ago

I've build for the latest tag, and yes, the binary exists, as seen in output:

dh_suidregister
fcgistarter
qgis
qgis_bench
qgis_mapserv.fcgi
tudorbarascu commented 8 years ago

@timlinux Do you think I may have a newbie problem or it's due to the configs? Thanks a lot! forgot to mention that's really nice to have a qgis server docker container :).

rduivenvoorde commented 8 years ago

@timlinux the current setup became better (because orchastrated with postgis and qgis-application), but I think there is also a 'market' for a straight forward dummy qgis-server container. Happy to dig up the older version of docker-file and add an image to the qgis-repo. Then Kartoza can keep the 'orchastrated' ones. And QGIS has the 'my first qgis-server docker'? Ok with that?

timlinux commented 8 years ago

Hi @rduivenvoorde A straight forward QGIS Server container is exactly what I am building. The only thing I am trying to do is have a version for each release of QGIS. Because we often can't get debs for old version of QGIS in apt I hand compile everything. It would be great if you wanted to help to contribute to rather get eh apache configs working rather than digging out the old one.

The QGIS server image inherits from the QGIS Desktop (which is compiled in the container in the build process rather than installed from packages). QGIS Desktop image installs all compile deps, builds QGIS into /usr and then cleans out all the downloaded packages and uninstalls the dev libs to make the resulting package as small as possible. Currently it gets to be around 600mb which is not too bad.

QGIS Server adds a very thin layer over gis-desktop container. The usage pattern is supposed to be a very simple:

docker run -d -p 8080:8080 -v <some path>:/web/ kartoza/qgis-server:2.12

I am just a bit overloaded at the moment but I will get back to making the images work soon I promise. In the mean time if you just want to play, and don't mind using gis 2.8.3 on the server this should still be working:

docker run -d -p 8080:8080 -v <some path>:/web/ kartoza/qgis-server:2.12

As far as I know it is only the tagged versions which are having problems - and I haven't tried to promote them as being available yet. If 2.8.3 is also not working, let me know and I will look.

So docker-compose has nothing to do with the egis-server image - it sits a conceptual layer above and you use it when you want to do orchestration which is not (really) needed when running a single container only.

Hope that makes sense?

timlinux commented 8 years ago

@rduivenvoorde btw I am more than happy that we publish everything under official QGIS docker organisation - can you add me to the QGIS group and I will publish there as these come on line? My plan is to publish an official docker based release each time a QGIS release is made - and add some notes to the download page about it.

Gustry commented 8 years ago

Just for information, it still failing. There is not qgis server in the container :

[etienne:/home/etienne] $ docker exec -it qgis-server /bin/bash
root@0b0ae40fba69:/tmp# ls /usr/lib/cgi-bin/
root@0b0ae40fba69:/tmp# 

I'm going to try with another version, or to build it from scratch.

Gustry commented 8 years ago

I confirm that kartoza/qgis-server:latest doesn't work, but kartoza/qgis-server:2.6 works, even if it's very old.

othke commented 7 years ago

I Tim, Like Gustry, I confirm that 2.6 works, but not the latest (2.14.6)

othke commented 7 years ago

Hi again Tim. I compared the 000-default.conf from the TAG 2.6 and 2.14.6. In the TAG 2.14.6, there is no specific conf while in the 2.6, there is a QGIS server conf `<VirtualHost *:80> ServerAdmin webmaster@localhost ServerName qgis-server.qgis.org

    DocumentRoot /web
    <Directory />
            Options FollowSymLinks
            AllowOverride None
    </Directory>
    <Directory /web>
            Options Indexes FollowSymLinks MultiViews
            AllowOverride None
            Order allow,deny
            allow from all
            Require all granted
    </Directory>

    ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
    <Directory "/usr/lib/cgi-bin">
            AllowOverride None
            Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
            Order allow,deny
            Allow from all
            Require all granted
    </Directory>
    ErrorLog ${APACHE_LOG_DIR}/error.log

    # Possible values include: debug, info, notice, warn, error, crit,
    # alert, emerg.
    LogLevel warn

    CustomLog ${APACHE_LOG_DIR}/access.log combined

    #Uncomment the next line to enable logging to a file
    SetEnv QGIS_LOG_FILE /tmp/qgislog.txt
    SetEnv QGIS_DEBUG 3

`

othke commented 7 years ago

I use the 000-default.conf from the TAG 2.6 with the 2.14.6 Now I get this error

`

Githubissues.
  • Githubissues is a development platform for aggregating issues.