Hi Henning,

 

Some update on my upgrade to kamailio 5.0.7.

 

First of all, I posted other question related to the mod_perl requirement, etc... and I got some interesting answers.

 

I succeeded to get rid of the dependencies and now my server is upgraded to 5.0.7. Unfortunately, Kamailio doesn't start and is in a kind of loop.

 

The kamailio.log contains entries I've never seen before with 5.0.1. Extract of the log :

 

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/cfg.y:1623]: yyparse(): loading module app_perl.so

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/sr_module.c:575]: load_module(): trying to load </usr/lib64/kamailio/modules/app_perl.so>

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/sr_module.c:624]: load_module(): attempt to lookup exports structure failed - dlerror: /usr/lib64/kamailio/modules/app_perl.so: undefined symbol: exports

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/sr_module.c:636]: load_module(): looking up exports with name: _app_perl_exports

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/sr_module.c:652]: load_module(): /usr/lib64/kamailio/modules/app_perl.so: exports dlflags interface is deprecated and it will not be supported in newer versions; consider using mod_register() instead

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/sr_module.c:624]: load_module(): attempt to lookup exports structure failed - dlerror: /usr/lib64/kamailio/modules/app_perl.so: undefined symbol: exports

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/sr_module.c:636]: load_module(): looking up exports with name: _app_perl_exports

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/cfg.lex:1713]: pp_define(): defining id: MOD_app_perl

….

….

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/cfg.lex:1713]: pp_define(): defining id: NODETYPE_MGCF

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/cfg.lex:1803]: pp_define_set(): ### setting define ID [NODETYPE_MGCF] value [1]

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/cfg.lex:1713]: pp_define(): defining id: NODETYPE_MMM

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/cfg.lex:1803]: pp_define_set(): ### setting define ID [NODETYPE_MMM] value [2]

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/cfg.lex:1713]: pp_define(): defining id: MGCF_NODESTRING

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/cfg.lex:1803]: pp_define_set(): ### setting define ID [MGCF_NODESTRING] value ["MGCF"]

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/modparam.c:83]: set_mod_param_regex(): 'app_perl' matches module 'app_perl'

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/sr_module.c:794]: find_param_export(): found <modpath> in module app_perl [/usr/lib64/kamailio/modules/app_perl.so]

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/modparam.c:99]: set_mod_param_regex(): found <modpath> in module app_perl [/usr/lib64/kamailio/modules/app_perl.so]

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/modparam.c:83]: set_mod_param_regex(): 'app_perl' matches module 'app_perl'

Aug  7 10:02:09 vm-siprouter74 kamailio: WARNING: <core> [core/cfg.y:3388]: warn_at(): warning in config file /etc/kamailio/kamailio.cfg, line 978, column 6-13: constant value in if(...)

 

Then lot of [core/route_struct.c:nnnn] entries, I have never seen before with kamailio 5.0.1 :

 

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:467]: print_action(): f_ptr<0x7f65e4973bd0>

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:493]: print_action(): , 2

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:524]: print_action(): , "L_WARN"

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:546]: print_action(): );

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:545]: print_action(): };

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:519]: print_action(): } else {

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:545]: print_action(): };

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:442]: print_action(): assign(

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:483]: print_action(): type<21>

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:517]: print_action(): , type<22>

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:546]: print_action(): );

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:401]: print_action(): if (

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:483]: print_action(): type<22>

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:485]: print_action(): ) {

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:442]: print_action(): assign(

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:483]: print_action(): type<21>

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:517]: print_action(): , type<22>

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:546]: print_action(): );

 

This sequence of [core/route_struct.c:nnnn] entries ends with :

 

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:467]: print_action(): f_ptr<0x7f65e4973bd0>

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:493]: print_action(): , 2

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:524]: print_action(): , "L_DBG"

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:546]: print_action(): );

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route.c:2134]: print_rl():

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/route.c:129]: route_add(): mapping routing block (0xaff280)[core:receive-parse-error] to 5

Aug  7 10:02:09 vm-siprouter74 kamailio: INFO: <core> [core/sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module

Aug  7 10:02:09 vm-siprouter74 kamailio: WARNING: <core> [core/socket_info.c:1314]: fix_hostname(): could not rev. resolve 129.227.83.78

Aug  7 10:02:09 vm-siprouter74 kamailio: WARNING: <core> [core/socket_info.c:1314]: fix_hostname(): could not rev. resolve 129.227.82.79

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/mem/pkg.c:100]: pkg_print_manager(): pkg - using memory manager: q_malloc

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/mem/shm.c:277]: shm_print_manager(): shm - using memory manager: q_malloc

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/cfg/cfg.c:176]: cfg_declare(): DEBUG: register_cfg_def(): new config group has been registered: 'core' (num=52, size=208)

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/cfg/cfg.c:176]: cfg_declare(): DEBUG: register_cfg_def(): new config group has been registered: 'tcp' (num=26, size=104)

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/timer.c:256]: init_timer(): starting with *ticks=1478539463

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/timer.c:298]: init_timer(): timer_list between 0x7f65d9accfd0 and 0x7f65d9b10fd0

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/pt.c:145]: register_procs(): registering new processes: 0 (old) + 1 (new) = 1 (total)

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/daemonize.c:207]: enable_dumpable(): trying enable core dumping...

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: <core> [core/daemonize.c:225]: enable_dumpable(): core dumping is enabled now (1)...

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: DEBUG: <core> [core/daemonize.c:583]: set_core_dump(): core dump limits set to 18446744073709551615

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: DEBUG: <core> [core/async_task.c:108]: async_task_init(): start initializing asynk task framework

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: DEBUG: <core> [core/sr_module.c:971]: init_mod(): db_mysql

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: DEBUG: db_mysql [km_db_mysql.c:86]: kam_mysql_mod_init(): MySQL client version is 10.1.30-MariaDB

 

Then the jsonrpcs mod-init fails to change the owner/group for the /var/run/kamailio/kamailio_rpc_fifo :

 

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: DEBUG: <core> [core/sr_module.c:971]: init_mod(): jsonrpcs

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: DEBUG: jsonrpcs [jsonrpcs_mod.c:1087]: mod_init(): preparing to listen on fifo file: /var/run/kamailio/kamailio_rpc_fifo

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: DEBUG: jsonrpcs [jsonrpcs_fifo.c:151]: jsonrpc_init_fifo_file(): testing if fifo file exists ...

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: DEBUG: jsonrpcs [jsonrpcs_fifo.c:72]: jsonrpc_init_fifo_server(): FIFO created @ /var/run/kamailio/kamailio_rpc_fifo

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: ERROR: jsonrpcs [jsonrpcs_fifo.c:82]: jsonrpc_init_fifo_server(): Failed to change the owner/group for /var/run/kamailio/kamailio_rpc_fifo  to 248.248; Operation not permitted[1]

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: CRITICAL: jsonrpcs [jsonrpcs_fifo.c:209]: jsonrpc_init_fifo_file(): failed to init jsonrpc fifo server file stream

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: ERROR: jsonrpcs [jsonrpcs_fifo.c:539]: jsonrpc_fifo_mod_init(): cannot initialize fifo transport

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: ERROR: jsonrpcs [jsonrpcs_mod.c:1090]: mod_init(): cannot initialize fifo transport

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: ERROR: jsonrpcs [jsonrpcs_fifo.c:539]: jsonrpc_fifo_mod_init(): cannot initialize fifo transport

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: ERROR: jsonrpcs [jsonrpcs_mod.c:1090]: mod_init(): cannot initialize fifo transport

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: ERROR: <core> [core/sr_module.c:974]: init_mod(): Error while initializing module jsonrpcs (/usr/lib64/kamailio/modules/jsonrpcs.so)

 

Then the connection to my MySQL server fails also:

 

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: DEBUG: <core> [core/sr_module.c:698]: find_mod_export_record(): find_export_record: found <db_bind_api> in module db_mysql [/usr/lib64/kamailio/modules/db_mysql.so]

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: DEBUG: <core> [db.c:209]: db_bind_mod(): using db bind api for db_mysql

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: DEBUG: <core> [db.c:314]: db_do_init2(): connection 0x7f65e4974868 not found in pool

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: DEBUG: db_mysql [km_my_con.c:98]: db_mysql_new_connection(): opening connection: mysql://xxxx:xxxx@localhost/siprouter

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: ERROR: db_mysql [km_my_con.c:129]: db_mysql_new_connection(): driver error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2 "No such file or directory")

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: ERROR: <core> [db.c:318]: db_do_init2(): could not add connection to the pool

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: ERROR: htable [ht_db.c:92]: ht_db_open_con(): failed to connect to the database

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: DEBUG: tm [t_funcs.c:86]: tm_shutdown(): DEBUG: tm_shutdown : start

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: DEBUG: tm [t_funcs.c:89]: tm_shutdown(): DEBUG: tm_shutdown : emptying hash table

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: DEBUG: tm [t_funcs.c:91]: tm_shutdown(): DEBUG: tm_shutdown : removing semaphores

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: DEBUG: tm [t_funcs.c:93]: tm_shutdown(): DEBUG: tm_shutdown : destroying tmcb lists

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: DEBUG: tm [t_funcs.c:96]: tm_shutdown(): DEBUG: tm_shutdown : done

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: DEBUG: <core> [core/mem/shm.c:174]: shm_core_lock_destroy(): destroying the shared memory lock

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: DEBUG: <core> [core/mem/shm.c:266]: shm_destroy_manager(): destroying memory manager: q_malloc

Aug  7 10:02:09 vm-siprouter74 /usr/sbin/kamailio[20218]: DEBUG: <core> [core/mem/pkg.c:89]: pkg_destroy_manager(): destroying memory manager: q_malloc

 

Hereafter I can see that kamailio is looping :

 

Aug  7 10:02:09 vm-siprouter74 kamailio: WARNING: <core> [core/cfg.y:3388]: warn_at(): warning in config file /etc/kamailio/kamailio.cfg, line 978, column 6-13: constant value in if(...)

Aug  7 10:02:10 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:546]: print_action(): );

Aug  7 10:02:10 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:448]: print_action(): UNKNOWN(

Aug  7 10:02:10 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:483]: print_action(): type<22>

Aug  7 10:02:10 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:442]: print_action(): assign(

Aug  7 10:02:10 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:483]: print_action(): type<21>

Aug  7 10:02:10 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:517]: print_action(): , type<22>

Aug  7 10:02:10 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:546]: print_action(): );

Aug  7 10:02:10 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:442]: print_action(): assign(

Aug  7 10:02:10 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:483]: print_action(): type<21>

Aug  7 10:02:10 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:517]: print_action(): , type<22>

Aug  7 10:02:10 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:546]: print_action(): );

Aug  7 10:02:10 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:401]: print_action(): if (

Aug  7 10:02:10 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:483]: print_action(): type<22>

Aug  7 10:02:10 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:485]: print_action(): ) {

Aug  7 10:02:10 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:418]: print_action():  external_module_call(

Aug  7 10:02:10 vm-siprouter74 kamailio: DEBUG: <core> [core/route_struct.c:467]: print_action(): f_ptr<0x7f34c32babd0>

 

I’ve been told that the upgrade from 5.0.1 to 5.0.7 would be simple, but it is not.

 

At the moment, I don’t know how to fix the different errors above.

 

So if you or somebody else can help me, that would be good.

 

Cordialement.

Patrick GINHOUX

 

-----Message d'origine-----
De : sr-users <sr-users-bounces@lists.kamailio.org> De la part de Ginhoux, Patrick
Envoyé : samedi 4 août 2018 11:46
À : Henning Westerholt <hw@kamailio.org>; Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org>
Objet : Re: [SR-Users] kamcmd htable.reload propertiesHash problem

 

Hi,

 

I'm thinking about the difficulty to upgrade my Kamailio server from the

5.0.1 level to the 5.0.7 level because of dependencies.

 

This difficulty comes from because the kamailio-perl-5.0.7-1.el7.x86_64.rpm

requires the mod_perl module (and this one no longer exists on a RHEL 7

distro).

 

My question then is what has been changed between the 5.0.1 and the 5.0.7

level to require the mod_perl module ?

As my server still run RHEL 7.4, why I don't not encounter the issue with

the 5.0.1 ?

 

Any thoughts on this analysis ?

 

Cordialement.

Patrick GINHOUX

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginhoux@unisys.com

 

-----Message d'origine-----

De : sr-users <sr-users-bounces@lists.kamailio.org> De la part de Ginhoux,

Patrick

Envoyé : vendredi 3 août 2018 09:30

À : Henning Westerholt <hw@kamailio.org>

Cc : sr-users@lists.kamailio.org

Objet : Re: [SR-Users] kamcmd htable.reload propertiesHash problem

 

Unfortunately, I use the perl module in my kamailio.cfg.

 

So you're correct, I could install the mod_perl from the EPEL project. This

is possible on my test server in my lab.

At the moment, I had collected manually all rpm packages required for 5.0.1

(like Perl or snmp packages), that' was already a huge work.

 

Now if at each stream there is new dependencies, I would have to solve the

dependencies for other repo like with the EPEL repo.

 

But in a next step, I have to do the same installation on a customer site on

preimaged server with the following restrictions :

- from this site, I have no access to the internet (That's why, up to new, I

only download the packages I need)

- the preimaged server are RHEL 7.4 server without no required package

removed.

 

As said, I configured the EPEL repo on my test server and then try to

installed to mod_perl module. I starts ok but fails for other dependencies

(see attached).

 

So upgrading from Kamailio 5.0.1 to 5.0.7 is not as simple as I expected.

 

I hope I'm clear in my explanation.

 

Cordialement.

Patrick GINHOUX

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginhoux@unisys.com

 

 

-----Message d'origine-----

De : Henning Westerholt <hw@kamailio.org>

Envoyé : vendredi 3 août 2018 08:43

À : Ginhoux, Patrick <patrick.ginhoux@fr.unisys.com>

Cc : sr-users@lists.kamailio.org

Objet : Re: [SR-Users] kamcmd htable.reload propertiesHash problem

 

Am Freitag, 3. August 2018, 07:56:28 CEST schrieb Ginhoux, Patrick:

> Instead of installing a new server, I tried to upgrade the one running the

> 5.0.1 level. It has the following packages installed:

>

> kamailio-perl-5.0.1-1.1.x86_64

> kamailio-5.0.1-1.1.x86_64

> kamailio-mysql-5.0.1-1.1.x86_64

> kamailio-snmpstats-5.0.1-1.1.x86_64

>

> So I have download the 5.0.7 packages into a separate folder:

> kamailio-rpms_5.0.7

>

> kamailio-5.0.7-1.el7.x86_64.rpm

> kamailio-mysql-5.0.7-1.el7.x86_64.rpm

> kamailio-perl-5.0.7-1.el7.x86_64.rpm

> kamailio-snmpstats-5.0.7-1.el7.x86_64.rpm

> kamailio-ims-5.0.7-1.el7.x86_64.rpm

>

> The update command “rpm -Uvh --force kamailio*” detects a dependency on

the

> mod_perl package :

>

> warning: kamailio-5.0.7-1.el7.x86_64.rpm: Header V3 DSA/SHA1 Signature,

key

> ID 941fdbdd: NOKEY

>

> error: Failed dependencies:

>         mod_perl is needed by kamailio-perl-5.0.7-1.el7.x86_64

> I try to find this mod_perl package but it does no longer exist for RedHat

> 7. We can find multiple articles referencing this change in RHEL.

>

> It seems there is an alternative way to get this module in a EPEL

repository

> (https://huntingbears.nl/2013/12/17/no-mod_perl-in-rhel-7-and-centos-7/).

>

> It is to me a huge work to simply update my current Kamailio to 5.0.7.

>

> Does this mod_perl change makes sense to you ?

>

> Have you an idea to get rid of this dependency?

 

Hello Patrick,

 

probably a stupid question, but do you actually use the perl module inside

your kamailio cfg? If not - I would suggest to just remove the 5.0.1 perl

module, and also not install it for 5.0.7.

 

If you need it - the quoted artice states that its actually not difficult to

 

install mod_perl from the EPEL repository. This looks quite ok: "EPEL is the

 

high-quality RPM collection for RHEL and CentOS linux, maintened by the

Fedora

project.".

 

Best regards,

 

Henning

 

--

Henning Westerholt

https://skalatan.de/blog/