How can i fix a GeoDjango OSError: undefined Symbol?
How can i fix a GeoDjango OSError: undefined Symbol?
几天前执行 yum 升级后，我的 Django 项目出现以下错误
Traceback (most recent call last):
File "manage.py", line 21, in <module>
main()
File "manage.py", line 17, in main
execute_from_command_line(sys.argv)
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
utility.execute()
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/core/management/__init__.py", line 357, in execute
django.setup()
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/__init__.py", line 24, in setup
apps.populate(settings.INSTALLED_APPS)
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/apps/registry.py", line 114, in populate
app_config.import_models()
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/apps/config.py", line 211, in import_models
self.models_module = import_module(models_module_name)
File "/home/joincic/GeoRouting/GeoRouting_2/lib64/python3.6/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 994, in _gcd_import
File "<frozen importlib._bootstrap>", line 971, in _find_and_load
File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 678, in exec_module
File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/auth/models.py", line 2, in <module>
from django.contrib.auth.base_user import AbstractBaseUser, BaseUserManager
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/auth/base_user.py", line 47, in <module>
class AbstractBaseUser(models.Model):
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/db/models/base.py", line 117, in __new__
new_class.add_to_class('_meta', Options(meta, app_label))
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/db/models/base.py", line 321, in add_to_class
value.contribute_to_class(cls, name)
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/db/models/options.py", line 204, in contribute_to_class
self.db_table = truncate_name(self.db_table, connection.ops.max_name_length())
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/db/__init__.py", line 28, in __getattr__
return getattr(connections[DEFAULT_DB_ALIAS], item)
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/db/utils.py", line 201, in __getitem__
backend = load_backend(db['ENGINE'])
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/db/utils.py", line 110, in load_backend
return import_module('%s.base' % backend_name)
File "/home/joincic/GeoRouting/GeoRouting_2/lib64/python3.6/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/db/backends/postgis/base.py", line 6, in <module>
from .features import DatabaseFeatures
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/db/backends/postgis/features.py", line 1, in <module>
from django.contrib.gis.db.backends.base.features import BaseSpatialFeatures
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/db/backends/base/features.py", line 3, in <module>
from django.contrib.gis.db.models import aggregates
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/db/models/__init__.py", line 3, in <module>
import django.contrib.gis.db.models.functions # NOQA
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/db/models/functions.py", line 4, in <module>
from django.contrib.gis.db.models.fields import BaseSpatialField, GeometryField
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/db/models/fields.py", line 3, in <module>
from django.contrib.gis import forms, gdal
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/forms/__init__.py", line 3, in <module>
from .fields import ( # NOQA
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/forms/fields.py", line 2, in <module>
from django.contrib.gis.gdal import GDALException
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/gdal/__init__.py", line 28, in <module>
from django.contrib.gis.gdal.datasource import DataSource
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/gdal/datasource.py", line 39, in <module>
from django.contrib.gis.gdal.driver import Driver
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/gdal/driver.py", line 5, in <module>
from django.contrib.gis.gdal.prototypes import ds as vcapi, raster as rcapi
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/gdal/prototypes/ds.py", line 9, in <module>
from django.contrib.gis.gdal.libgdal import GDAL_VERSION, lgdal
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/gdal/libgdal.py", line 47, in <module>
lgdal = CDLL(lib_path)
File "/usr/lib64/python3.6/ctypes/__init__.py", line 343, in __init__
self._handle = _dlopen(self._name, mode)
OSError: /usr/gdal30/lib/libgdal.so.26: undefined symbol: GEOSMakeValid_r
升级前项目运行正常，尝试修复错误我安装了gdal 3.0.2但是没有运行
我不知道您是否需要有关该项目或虚拟机的更多信息，如果需要，您可以问我，我很乐意为您提供任何信息
有什么想法吗？
在我的例子中，yum 有几个启用的 pgdg 存储库，gdal lib 是从与 Postgis 不同的 pg 版本安装的。将启用的 pgdg 存储库减少到一个（感兴趣的版本）并重新安装（或更好地擦除并安装）受影响的包后，我能够再次将 pg 与 Postgis 一起使用。
如何禁用存储库请参阅 How to enable or disable repositories in CentOS。相关文件在我的案例中 /etc/yum.repos.d/pgdg-redhat-all.repo
混合存储库的情况在升级前已经存在，Postgis 运行没有问题
[test@mytest ~]$ yum list installed | grep -i geos
geos37.x86_64 3.7.2-2.rhel7 @pgdg10
[test@mytest ~]$ yum list installed | grep -i gdal
gdal-libs.x86_64 1.11.4-12.rhel7 @pgdg96
gdal30-libs.x86_64 3.0.1-4.rhel7 @pgdg10
[test@mytest ~]$ yum list installed | grep -i postgis
postgis24_96.x86_64 2.4.8-5.rhel7 @pgdg96
postgis24_96-client.x86_64 2.4.8-5.rhel7 @pgdg96
[test@mytest ~]$ yum repolist enabled | grep -i Postgre
pgdg10/7/x86_64 PostgreSQL 10 for RHEL/CentOS 7 - x86_64 1,306
pgdg11/7/x86_64 PostgreSQL 11 for RHEL/CentOS 7 - x86_64 1,162
pgdg12/7/x86_64 PostgreSQL 12 for RHEL/CentOS 7 - x86_64 596
pgdg96/7/x86_64 PostgreSQL 9.6 for RHEL/CentOS 7 - x86_64 1,354
[test@mytest ~]$ psql
psql (9.6.15)
postgres=# CREATE DATABASE test;
CREATE DATABASE
postgres=# \connect test
You are now connected to database "test" as user "test".
test=# CREATE EXTENSION postgis;
CREATE EXTENSION
test=# \connect postgres
You are now connected to database "postgres" as user "test".
postgres=# DROP DATABASE test;
DROP DATABASE
在yum update之后，混合存储库的情况得到了扩展，postgis 造成了麻烦。 （grep 搜索 pgdg 以检测所有受影响的包）
[test@mytest ~]$ yum list installed | grep -i pgdg
CGAL.x86_64 4.7-1.rhel7.1 @pgdg11
SFCGAL.x86_64 1.3.1-2.rhel7 @pgdg12
SFCGAL-libs.x86_64 1.3.1-2.rhel7 @pgdg12
gdal-libs.x86_64 1.11.4-12.rhel7 @pgdg96
gdal30-libs.x86_64 3.0.1-4.rhel7 @pgdg10
geos37.x86_64 3.7.2-2.rhel7 @pgdg10
libgeotiff.x86_64 1.4.0-1.rhel7.1 @pgdg11
libgeotiff15.x86_64 1.5.1-2.rhel7 @pgdg12
ogdi.x86_64 3.2.0-4.rhel7.1 @pgdg11
ogdi41.x86_64 4.1.0-2.rhel7 @pgdg10
pgdg-redhat-repo.noarch 42.0-5 @pgdg10
postgis24_96.x86_64 2.4.8-5.rhel7 @pgdg96
...
proj62.x86_64 6.2.0-1.rhel7 @pgdg10
[test@mytest ~]$ psql
...
test=# CREATE EXTENSION postgis;
ERROR: could not load library "/usr/pgsql-9.6/lib/rtpostgis-2.4.so": /usr/gdal30/lib/libgdal.so.26: undefined symbol: GEOSMakeValid_r
test=#
我尝试在仅启用一个 pgpdg 存储库的情况下重新安装 Postgis。这不是重新安装依赖的 geos、gdal、proj 包。所以我删除了所有受影响的包并重新安装它们。
[test@mytest ~]$ sudo yum erase CGAL geos37 proj62 proj49 ogdi41
[test@mytest ~]$ sudo yum install postgis24_96
[test@mytest ~]$ yum list installed | grep -i pgdg
CGAL.x86_64 4.7-1.rhel7 @pgdg96
SFCGAL.x86_64 1.3.1-1.rhel7 @pgdg96
SFCGAL-libs.x86_64 1.3.1-1.rhel7 @pgdg96
gdal30-libs.x86_64 3.0.4-2.rhel7 @pgdg96
geos38.x86_64 3.8.0-1.rhel7 @pgdg96
...
postgis24_96.x86_64 2.4.8-8.rhel7 @pgdg96
这是一项硬性系统更改，请确保有一个备份（例如 VM 快照）。还要检查依赖的其他安装（例如 python shapely）是否仍然适用于更改后的库或需要重新安装。
我遇到了与客户完全相同的问题并研究了原因。因此，尽管 Iczub 的回答很好，但我认为还是值得解释一下问题的原因。
在我的例子中，错误表现为：
test=> SELECT PostGIS_Full_Version();
ERROR: could not load library "/usr/pgsql-10/lib/rtpostgis-2.4.so": /usr/gdal30/lib/libgdal.so.26: undefined symbol: GEOSMakeValid_r
CONTEXT: SQL statement "SELECT public.postgis_gdal_version()"
PL/pgSQL function postgis_full_version() line 33 at SQL statement
解决方法很简单：
# yum remove geos37
对事件的解释：
这是从 postgis24_10-2.4.6-3.rhel7.x86_64 到 postgis24_10-2.4.8-9.rhel7.x86_64（存储库 pgdg10）（次要）升级的结果，它安装了 gdal30-libs-3.0.4 和 geos38-3.8.1-1 作为依赖项。
问题的最终原因是之前安装的GEOS版本没有卸载：
# rpm -qa | grep geos
geos38-3.8.1-1.rhel7.x86_64
geos37-3.7.0-1.rhel7.x86_64
现在这两个软件包都有一个库 libgeos_c.so.1，安装在不同的目录中：
/usr/geos38/lib64/libgeos_c.so.1
/usr/geos37/lib64/libgeos_c.so.1
两个包都通过向 /etc/ld.so.conf.d 添加配置文件将它们的目录放在共享库路径中，所以我们最终在路径上有两个同名的库。
不幸的是，来自 GEOS 3.7 的库恰好是搜索路径上的第一个库，因此 libgdal.so.26 错误地加载了那个库，这导致了观察到的错误。
谁对谁错？
我认为有两个错误：
GEOS 库 libgeos_c 在版本 3.7 和 3.8 之间存在 ABI 中断，但无法更改库的主要版本。
PGDG RPM 包无法实现这两个 GEOS 包之间的不兼容性。它们绝不能同时安装。
几天前执行 yum 升级后，我的 Django 项目出现以下错误
Traceback (most recent call last):
File "manage.py", line 21, in <module>
main()
File "manage.py", line 17, in main
execute_from_command_line(sys.argv)
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
utility.execute()
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/core/management/__init__.py", line 357, in execute
django.setup()
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/__init__.py", line 24, in setup
apps.populate(settings.INSTALLED_APPS)
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/apps/registry.py", line 114, in populate
app_config.import_models()
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/apps/config.py", line 211, in import_models
self.models_module = import_module(models_module_name)
File "/home/joincic/GeoRouting/GeoRouting_2/lib64/python3.6/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 994, in _gcd_import
File "<frozen importlib._bootstrap>", line 971, in _find_and_load
File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 678, in exec_module
File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/auth/models.py", line 2, in <module>
from django.contrib.auth.base_user import AbstractBaseUser, BaseUserManager
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/auth/base_user.py", line 47, in <module>
class AbstractBaseUser(models.Model):
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/db/models/base.py", line 117, in __new__
new_class.add_to_class('_meta', Options(meta, app_label))
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/db/models/base.py", line 321, in add_to_class
value.contribute_to_class(cls, name)
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/db/models/options.py", line 204, in contribute_to_class
self.db_table = truncate_name(self.db_table, connection.ops.max_name_length())
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/db/__init__.py", line 28, in __getattr__
return getattr(connections[DEFAULT_DB_ALIAS], item)
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/db/utils.py", line 201, in __getitem__
backend = load_backend(db['ENGINE'])
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/db/utils.py", line 110, in load_backend
return import_module('%s.base' % backend_name)
File "/home/joincic/GeoRouting/GeoRouting_2/lib64/python3.6/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/db/backends/postgis/base.py", line 6, in <module>
from .features import DatabaseFeatures
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/db/backends/postgis/features.py", line 1, in <module>
from django.contrib.gis.db.backends.base.features import BaseSpatialFeatures
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/db/backends/base/features.py", line 3, in <module>
from django.contrib.gis.db.models import aggregates
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/db/models/__init__.py", line 3, in <module>
import django.contrib.gis.db.models.functions # NOQA
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/db/models/functions.py", line 4, in <module>
from django.contrib.gis.db.models.fields import BaseSpatialField, GeometryField
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/db/models/fields.py", line 3, in <module>
from django.contrib.gis import forms, gdal
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/forms/__init__.py", line 3, in <module>
from .fields import ( # NOQA
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/forms/fields.py", line 2, in <module>
from django.contrib.gis.gdal import GDALException
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/gdal/__init__.py", line 28, in <module>
from django.contrib.gis.gdal.datasource import DataSource
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/gdal/datasource.py", line 39, in <module>
from django.contrib.gis.gdal.driver import Driver
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/gdal/driver.py", line 5, in <module>
from django.contrib.gis.gdal.prototypes import ds as vcapi, raster as rcapi
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/gdal/prototypes/ds.py", line 9, in <module>
from django.contrib.gis.gdal.libgdal import GDAL_VERSION, lgdal
File "/home/joincic/GeoRouting/GeoRouting_2/lib/python3.6/site-packages/django/contrib/gis/gdal/libgdal.py", line 47, in <module>
lgdal = CDLL(lib_path)
File "/usr/lib64/python3.6/ctypes/__init__.py", line 343, in __init__
self._handle = _dlopen(self._name, mode)
OSError: /usr/gdal30/lib/libgdal.so.26: undefined symbol: GEOSMakeValid_r
升级前项目运行正常，尝试修复错误我安装了gdal 3.0.2但是没有运行
我不知道您是否需要有关该项目或虚拟机的更多信息，如果需要，您可以问我，我很乐意为您提供任何信息
有什么想法吗？
在我的例子中，yum 有几个启用的 pgdg 存储库，gdal lib 是从与 Postgis 不同的 pg 版本安装的。将启用的 pgdg 存储库减少到一个（感兴趣的版本）并重新安装（或更好地擦除并安装）受影响的包后，我能够再次将 pg 与 Postgis 一起使用。
如何禁用存储库请参阅 How to enable or disable repositories in CentOS。相关文件在我的案例中 /etc/yum.repos.d/pgdg-redhat-all.repo
混合存储库的情况在升级前已经存在，Postgis 运行没有问题
[test@mytest ~]$ yum list installed | grep -i geos
geos37.x86_64 3.7.2-2.rhel7 @pgdg10
[test@mytest ~]$ yum list installed | grep -i gdal
gdal-libs.x86_64 1.11.4-12.rhel7 @pgdg96
gdal30-libs.x86_64 3.0.1-4.rhel7 @pgdg10
[test@mytest ~]$ yum list installed | grep -i postgis
postgis24_96.x86_64 2.4.8-5.rhel7 @pgdg96
postgis24_96-client.x86_64 2.4.8-5.rhel7 @pgdg96
[test@mytest ~]$ yum repolist enabled | grep -i Postgre
pgdg10/7/x86_64 PostgreSQL 10 for RHEL/CentOS 7 - x86_64 1,306
pgdg11/7/x86_64 PostgreSQL 11 for RHEL/CentOS 7 - x86_64 1,162
pgdg12/7/x86_64 PostgreSQL 12 for RHEL/CentOS 7 - x86_64 596
pgdg96/7/x86_64 PostgreSQL 9.6 for RHEL/CentOS 7 - x86_64 1,354
[test@mytest ~]$ psql
psql (9.6.15)
postgres=# CREATE DATABASE test;
CREATE DATABASE
postgres=# \connect test
You are now connected to database "test" as user "test".
test=# CREATE EXTENSION postgis;
CREATE EXTENSION
test=# \connect postgres
You are now connected to database "postgres" as user "test".
postgres=# DROP DATABASE test;
DROP DATABASE
在yum update之后，混合存储库的情况得到了扩展，postgis 造成了麻烦。 （grep 搜索 pgdg 以检测所有受影响的包）
[test@mytest ~]$ yum list installed | grep -i pgdg
CGAL.x86_64 4.7-1.rhel7.1 @pgdg11
SFCGAL.x86_64 1.3.1-2.rhel7 @pgdg12
SFCGAL-libs.x86_64 1.3.1-2.rhel7 @pgdg12
gdal-libs.x86_64 1.11.4-12.rhel7 @pgdg96
gdal30-libs.x86_64 3.0.1-4.rhel7 @pgdg10
geos37.x86_64 3.7.2-2.rhel7 @pgdg10
libgeotiff.x86_64 1.4.0-1.rhel7.1 @pgdg11
libgeotiff15.x86_64 1.5.1-2.rhel7 @pgdg12
ogdi.x86_64 3.2.0-4.rhel7.1 @pgdg11
ogdi41.x86_64 4.1.0-2.rhel7 @pgdg10
pgdg-redhat-repo.noarch 42.0-5 @pgdg10
postgis24_96.x86_64 2.4.8-5.rhel7 @pgdg96
...
proj62.x86_64 6.2.0-1.rhel7 @pgdg10
[test@mytest ~]$ psql
...
test=# CREATE EXTENSION postgis;
ERROR: could not load library "/usr/pgsql-9.6/lib/rtpostgis-2.4.so": /usr/gdal30/lib/libgdal.so.26: undefined symbol: GEOSMakeValid_r
test=#
我尝试在仅启用一个 pgpdg 存储库的情况下重新安装 Postgis。这不是重新安装依赖的 geos、gdal、proj 包。所以我删除了所有受影响的包并重新安装它们。
[test@mytest ~]$ sudo yum erase CGAL geos37 proj62 proj49 ogdi41
[test@mytest ~]$ sudo yum install postgis24_96
[test@mytest ~]$ yum list installed | grep -i pgdg
CGAL.x86_64 4.7-1.rhel7 @pgdg96
SFCGAL.x86_64 1.3.1-1.rhel7 @pgdg96
SFCGAL-libs.x86_64 1.3.1-1.rhel7 @pgdg96
gdal30-libs.x86_64 3.0.4-2.rhel7 @pgdg96
geos38.x86_64 3.8.0-1.rhel7 @pgdg96
...
postgis24_96.x86_64 2.4.8-8.rhel7 @pgdg96
这是一项硬性系统更改，请确保有一个备份（例如 VM 快照）。还要检查依赖的其他安装（例如 python shapely）是否仍然适用于更改后的库或需要重新安装。
我遇到了与客户完全相同的问题并研究了原因。因此，尽管 Iczub 的回答很好，但我认为还是值得解释一下问题的原因。
在我的例子中，错误表现为：
test=> SELECT PostGIS_Full_Version();
ERROR: could not load library "/usr/pgsql-10/lib/rtpostgis-2.4.so": /usr/gdal30/lib/libgdal.so.26: undefined symbol: GEOSMakeValid_r
CONTEXT: SQL statement "SELECT public.postgis_gdal_version()"
PL/pgSQL function postgis_full_version() line 33 at SQL statement
解决方法很简单：
# yum remove geos37
对事件的解释：
这是从 postgis24_10-2.4.6-3.rhel7.x86_64 到 postgis24_10-2.4.8-9.rhel7.x86_64（存储库 pgdg10）（次要）升级的结果，它安装了 gdal30-libs-3.0.4 和 geos38-3.8.1-1 作为依赖项。
问题的最终原因是之前安装的GEOS版本没有卸载：
# rpm -qa | grep geos
geos38-3.8.1-1.rhel7.x86_64
geos37-3.7.0-1.rhel7.x86_64
现在这两个软件包都有一个库 libgeos_c.so.1，安装在不同的目录中：
/usr/geos38/lib64/libgeos_c.so.1
/usr/geos37/lib64/libgeos_c.so.1
两个包都通过向 /etc/ld.so.conf.d 添加配置文件将它们的目录放在共享库路径中，所以我们最终在路径上有两个同名的库。
不幸的是，来自 GEOS 3.7 的库恰好是搜索路径上的第一个库，因此 libgdal.so.26 错误地加载了那个库，这导致了观察到的错误。
谁对谁错？
我认为有两个错误：
GEOS 库
libgeos_c在版本 3.7 和 3.8 之间存在 ABI 中断，但无法更改库的主要版本。PGDG RPM 包无法实现这两个 GEOS 包之间的不兼容性。它们绝不能同时安装。