I have Postgres-XL 10 installed with geos-3.9.1 and postgis-3.1.1 on my Amazon Linux 2 machine. My cluster is running and working flawlessly but I am having troubles with getting postgis installed into the database. I've built and installed everything from source.
The error I'm getting when I run CREATE EXTENSION postgis; is:
ERROR: could not load library "/usr/local/pgsql/lib/postgis-3.so": libgeos_c.so.1: cannot open shared object file: No such file or directory
Using solutions from other posts online, I have tried:
Running sudo ldconfig
Using the --enable-shared option when installing geos and postgis
Ensured /usr/local/lib is in the LD_LIBRARY_PATH environment variable and I also added /usr/local/pgsql/lib to LD_LIBRARY_PATH
None of these solutions worked. I can't install PostGIS or Geos using yum because it will install postgresql 12 which conflicts with my version of postgresql which is a custom one for Postgres-XL.
Is there anything else I can try to solve this error? Any help is appreciated.
Thanks.
It looks like you might need to downgrade. Postgres-XL is only supporting 2.0.x versions of postgis right now. At least according to their docs.
https://www.postgres-xl.org/faq/
Q. Is PostGIS supported?
Yes, PostGIS can be added to Postgres-XL. It has been tested with PostGIS 2.0.
Related
I attempted to upgrade my tcms-api library from 5.0 to 5.3 using:
pip install tcms-api --upgrade
on a Windows 10 machine, I saw a lot of errors when trying to install the dependent package of kerberos. Even though this is old, I saw a similar set of errors. The package installation failed since the kerberos package isn't supported on Windows and I was left at tcms-api 5.0.
Please file a bug against https://github.com/kiwitcms/tcms-api.
We can do a quick fix by providing 2 package names:
tcms-api and tcms-api[kerberos]
The first one will not install the kerberos package.
The proposed workaround makes sense but changing the underlying kerberos implementation needs careful testing which isn't a quick job.
OTOH https://github.com/kiwitcms/python-social-auth-kerberos uses gssapi which seems to be the latest and most actively maintained implementation of Kerberos for Python. There is an open issue to migrate to that in tcms-api so you can contribute if you want.
As a workaround, I was able to do the following (caveat: I haven't extensively tested my installation yet):
Clone the tcms-api repo from GitHub
Edit setup.py to change the install_requires line to use 'kerberos-sspi' rather than 'kerberos'
Install the following pip packages: Setuptools, Wheel, Twine
CD to repo folder and run: python setup.py bdist_wheel
That creates a package under the dist folder
Run pip install dist\tcms_api-5.3-py3-none-any.whl
Celebrate successful package install
The steps were modified from this page.
Update:
I confirmed the things I need the API to do work with my custom package (create and update test runs). However, I'm in a situation where I don't need to specifically harden my Kiwi instance using kerberos authentication.
I'm a front-end developer and I need to do a Ckan Theme. To do so, I need a working source install of CKAN on my system. I'm using Mint 18.1 and installing Ckan 2.6.2.
Following the steps of the installation of ckan's docs I've got a warning and an error at step 6 as shown on the image.
As you can see the last line says SOLR schema version not supported: 2.7. Supported versions are [2.3] and I can't proceed with the installation. Searching on the Internet I found people having the same problem, but using Docker (have no idea what is this) and their solutions didn't work for me.
Because I have a really short time to build this theme I gave up CKAN 2.6.2 and installd 2.5.2 and everything worked fine.
The SOLR schema that comes with CKAN 2.6.2 is version 2.3, so somehow you have got 2.7, which is provided with later versions of CKAN. Maybe you installed CKAN master and the schema is lingering from then.
Here are some steps so that you can find out where the problem is:
You can check the version of the schema in the CKAN source repo on your disk:
grep 'name="ckan" version=' /usr/lib/ckan/default/src/ckan/ckan/config/solr/schema.xml
You would have then installed this file into Solr (in Step 5, using the 'ln' command). You can check the version in Solr:
grep 'name="ckan" version=' /etc/solr/conf/schema.xml
(When this file is changed, you need to restart SOLR (i.e. jetty) for it to take effect - see the docs again).
You can see what schema SOLR is actually using:
curl -s 'http://localhost:8983/solr/admin/file/?contentType=text/xml;charset=utf-8&file=schema.xml'|grep 'name="ckan" version='
Please do feed back on these.
It sounds like your Docker container for SOLR is a newer version than that is not compatible with CKAN 2.6.2.
When I am in my postgres db and tried to create an extension for my db, I get this error
ERROR: could not open extension control file "/usr/share/postgresql/9.5/extension/postgis.control": No such file or directory
I know there are so many posts out there with this error and solutions and I tried them all too. Found so much in stackoverflow but none of them worked.
I realized in my postgresql directory there are 9.2, 9.3, 9.4, 9.5, 9.6,
I went into the directory in the error and I realized there is really no postgis.control inside 9.5
I checked my psql version and showed 9.6.1
I went into 9.6 folder and I DO see a postgis.control in it.
I want to changed the installation directory so when i run
create extension postgis
it would go
"/usr/share/postgresql/9.6/extension/postgis.control"
instead of
"/usr/share/postgresql/9.5/extension/postgis.control"
Can someone please give me a hand?
Thanks in advance.
P.S. Using Ubuntu 14.04 and also have Ubuntu 16.04 as desktop which I haven't try to install postgis yet
You should use the following command:
sudo apt-get install postgresql-9.6-postgis-scripts
Use the following command to get the postgis.control in your 9.5 version directory:
sudo apt install postgis postgresql-9.5-postgis-2.3
I want to run a tiles server with OSM data
i want to install mod_tile so i followed the mod_tile setup
But when i do the
./configure
It says
checking for getloadavg... yes
checking for apxs... no
checking for apxs2... no
checking for /opt/local/apache2/bin/apxs... no
configure: error: Could not find apxs on the path.
any idea what went wrong?
According to the Internets you need to install apache2-dev (previously known as apache2-devel). The apx binary should then be located under /usr/bin/apxs2 or /usr/sbin/apxs2.
Note: For building a tile server you should follow the guide on switch2osm.
For Ubuntu
sudo apt-get install apache2-devel
For RedHat & CentOs
yum install httpd-devel
SUSE has removed the SDK ISO from the area where you download the server ISO.
Check out this page.
I consider their page as very complicated and not logical so play a bit around but you find it in the end.
When you are looking for a current version then it helps you check Last 6 months
I'm trying to install mod_perl on Centos 5.5 with Plesk. Does this already come with mod_perl? I'm not showing anything in the $ENV{MOD_PERL} variable.
I tried installing it via cpan (install mod_perl2) with this:
Please provide a full path to 'apxs' executable
which I don't know. So I skip it and then I am asked:
Please provide the location of the Apache directory:
Searched though I have, I can't seem to find it. No apache folder with ap_release.h.
Where would I find this or is there a better way to install it via plesk?
Thanks,
Jonathan
I was able to get mod_perl2 installed by:
>> yum install perl-devel
>> cpan
>> install YAML
>> install mod_perl2
Then, I configured it thanks to this: http://www.server-world.info/en/note?os=CentOS_6&p=httpd&f=9
I added a new <Directory> for my web site in case there would be a conflict with plesk.
/cgi-bin runs regular perl scripts
/mod-perl runs my scripts using mod_perl2... the $ENV{MOD_PERL} variable does exist here!
#oleg - thanks for your help, a2enmod perl does not work in CentOS
The Perl Support check box in Plesk doesn't seem to have any effect what-so-ever.
Does this already come with mod_perl?
Yes. Check any domain's hosting settings.
also you can check:
rpm -qa | grep perl
and I'm definitely recommend you use Plesk on Centos 6, because most things will be easier.