rc_avpair_new: unknown attribute 1490026597

Here is the full list of installed modules - am I overlooking something obvious, because I do not see anything that resembles “radius”?

Module Size Used by
bluetooth 83762 2
rfkill 15242 1 bluetooth
iptable_filter 2173 1
ip_tables 9567 1 iptable_filter
tun 13735 0
xpp_usb 13911 0
xpp 155255 1 xpp_usb
wctc4xxp 34301 0
dahdi_transcode 5304 1 wctc4xxp
wcb4xxp 38408 0
opvxec 118409 1 wcb4xxp
zaphfc 14375 0
rcbfx 189607 0
opvxa1200 36183 0
opvxa24xx 219804 0
wctdm 33627 0
wcfxo 9381 0
wctdm24xxp 104252 0
rxt1 130265 0
r1t1 89409 0
tor3e 311464 0
wcte11xp 22672 0
wct1xxp 13032 0
wcte12xp 31409 0
dahdi_voicebus 49490 2 wctdm24xxp,wcte12xp
opvxd115 217126 0
wct4xxp 211650 0
dahdi 198212 19 xpp,dahdi_transcode,wcb4xxp,zaphfc,rcbfx,opvxa1200,opvxa24xx,wctdm,wcfxo,wctdm24xxp,rxt1,r1t1,tor3e,wcte11xp,wct1xxp,wcte12xp,dahdi_voicebus,opvxd115,wct4xxp
crc_ccitt 1337 2 wctdm24xxp,dahdi
ipv6 265868 52
power_meter 7258 0
dcdbas 7095 0
serio_raw 3722 0
iTCO_wdt 11070 0
iTCO_vendor_support 2408 1 iTCO_wdt
sg 24612 0
i7core_edac 14748 0
edac_core 36849 1 i7core_edac
ses 5767 0
enclosure 6330 1 ses
bnx2 70160 0
ext3 208232 2
jbd 65867 1 ext3
mbcache 5976 1 ext3
sr_mod 14245 0
cdrom 34094 1 sr_mod
usb_storage 39108 0
sd_mod 35435 4
crc_t10dif 1217 1 sd_mod
pata_acpi 2513 0
ata_generic 2805 0
ata_piix 19202 0
wmi 5183 0
megaraid_sas 64651 3
dm_mirror 11678 0
dm_region_hash 9801 1 dm_mirror
dm_log 8546 2 dm_mirror,dm_region_hash
dm_mod 67821 2 dm_mirror,dm_log

Bang Bang Mate.

We’re speaking of Asterisk’s loaded modules NOT Linux Kernel’s loaded modules.

You should perform a:

module show like radius

INSIDE your system’s Astersisk CLI.

What you pasted is the result of a “lsmod” from Linux CLI.
Not the same universe.

In my system (with THOSE module disabled as per post) here the result of THAT Asterisk command:

freepbx*CLI> module show like radius
Module Description Use Count
0 modules loaded

Is not enough?

Almost enough. Through the CLI I can see that cdr_radius.so is loaded. I wonder then why there are several posts throughout this forum explicitly stating that adding
’noload => cdr_radius.so’ to the /etc/asterisk/modules.conf file would resolve the issue when clearly is does not.
Would you be so kind as to tell me the correct way to unload this module from Asterisk - on startup? Thanks for your insight and patience.

Read, understand and execute what I previously wrote here (comment n°13).

OK. My initial mistake was presuming that getting to the Asterisk CLI from the Freepbx GUI was the same thing. I now know that is incorrect. However, after following your directions, again, but from the asterisk CLI at the console, the module did in fact unload. EXCEPT, that when the server reboots, the modules is once again loaded. So I ask again, where else does the no unload statement need to go, besides /etc/asterisk/modules.conf, to make it “permanent”?
Thanks again for your time.

This is a cat of modules.conf (under /etc/asterisk folder) on a FreePBX Distro 5.211.65-5:

; ; Asterisk Module Loader configuration file ; ;

[modules]
autoload=yes
;
; Any modules that need to be loaded before the Asterisk core has been
; initialized (just after the logger has been initialized) can be loaded
; using ‘preload’. This will frequently be needed if you wish to map all
; module configuration files into Realtime storage, since the Realtime
; driver will need to be loaded before the modules using those configuration
; files are initialized.
;
; An example of loading ODBC support would be:
;preload => res_odbc.so
;preload => res_config_odbc.so
;
; As FreePBX is using Local as the channel for queue members we need to make sure
; that pbx_config.so and chan_local.so are preloaded. If not, queue members
; will be marked as invalid until app_queue is reloaded.
preload => pbx_config.so
preload => chan_local.so
preload => res_mwi_blf.so ;auto-inserted by FreePBX
;
; Uncomment the following if you wish to use the Speech Recognition API
;preload => res_speech.so
;
; If you want, load the GTK console right away.
; KDE console is obsolete and was removed from Asterisk 2008-01-10
;
noload => pbx_gtkconsole.so
;load => pbx_gtkconsole.so
noload => pbx_kdeconsole.so
;
; Intercom application is obsoleted by
; chan_oss. Don’t load it.
;
noload => app_intercom.so
;
; DON’T load the chan_modem.so, as they are obsolete in * 1.2

noload => chan_modem.so
noload => chan_modem_aopen.so
noload => chan_modem_bestdata.so
noload => chan_modem_i4l.so

; Trunkisavail is a broken module supplied by Trixbox
noload => app_trunkisavail.so

; Ensure that format_* modules are loaded before res_musiconhold
;load => format_ogg_vorbis.so
load => format_wav.so
load => format_pcm.so

; format_au.so is removed from Asterisk 1.4 and later, remove ; to enable
;load => format_au.so

; This isn’t part of ‘Asterisk’ iteslf, it’s part of asterisk-addons. If this isn’t
; installed, asterisk will fail to start. But it does need to go here for native MOH
; to work using mp3’s.
; Note that on a system with a high number of calls, using a compressed audio format for
; musiconhold takes CPU resources. Converting these files to ulaw/alaw makes the job
; much easier for your CPU.
load => format_mp3.so
load => res_musiconhold.so
;
; Load either OSS or ALSA, not both
; By default, load no console driver
;
noload => chan_alsa.so
noload => chan_oss.so
;
noload => app_directory_odbcstorage.so
noload => app_voicemail_odbcstorage.so
noload => cel_radius.so
noload => cdr_radius.so
noload => chan_ooh323.so
noload => chan_unistim.so
noload => chan_mobile.so
noload => cdr_mysql.so

As you can see there are two rows about cel_radius.so and cdr_radius.so (noload).

That should be enough to permanently disable those Asterisk’s modules from loading at each (Asterisk) start up.

I confirm, at least in my updated FreePBX Distro system, with above settings those two modules don’t load and no error messages fill the logs.

there is an alternate and perhaps more intuitive solution

rm -rf /etc/asterisk/radius

oops!

rm -rf /etc/lib/asterisk/modules/radius

I wanted to upgrade to the latest versions of the FreePbx distro and underlying Asterisk before testing and reposting. We are now at: version 5.211.65-6 (FreePBX 2.11 based on CentOS 6.5) with Asterisk 11).
I liked the idea of removing the module as suggested by dicko, but received a “No such file or directory” error when attempting to do so. As for parnassus’ insistence that modifying the modules.conf file to Unload the modules, that does not work for us. After a system reboot the cdr_radius.so still gets loaded. Here is the cat of the modules.conf:
; Asterisk Module Loader configuration file
;
;

[modules]
autoload=yes
;
; Any modules that need to be loaded before the Asterisk core has been
; initialized (just after the logger has been initialized) can be loaded
; using ‘preload’. This will frequently be needed if you wish to map all
; module configuration files into Realtime storage, since the Realtime
; driver will need to be loaded before the modules using those configuration
; files are initialized.
;
; An example of loading ODBC support would be:
;preload => res_odbc.so
;preload => res_config_odbc.so
;
; As FreePBX is using Local as the channel for queue members we need to make sure
; that pbx_config.so and chan_local.so are preloaded. If not, queue members
; will be marked as invalid until app_queue is reloaded.
preload => pbx_config.so
preload => chan_local.so
preload => res_mwi_blf.so ;auto-inserted by FreePBX
;
; Uncomment the following if you wish to use the Speech Recognition API
;preload => res_speech.so
;
; If you want, load the GTK console right away.
; KDE console is obsolete and was removed from Asterisk 2008-01-10
;
noload => pbx_gtkconsole.so
;load => pbx_gtkconsole.so
noload => pbx_kdeconsole.so
;
; Intercom application is obsoleted by
; chan_oss. Don’t load it.
;
noload => app_intercom.so
;
; DON’T load the chan_modem.so, as they are obsolete in * 1.2

noload => chan_modem.so
noload => chan_modem_aopen.so
noload => chan_modem_bestdata.so
noload => chan_modem_i4l.so

; Trunkisavail is a broken module supplied by Trixbox
noload => app_trunkisavail.so

; Ensure that format_* modules are loaded before res_musiconhold
;load => format_ogg_vorbis.so
load => format_wav.so
load => format_pcm.so
load => format_au.so
; This isn’t part of ‘Asterisk’ iteslf, it’s part of asterisk-addons. If this isn’t
; installed, asterisk will fail to start. But it does need to go here for native MOH
; to work using mp3’s.
; Note that on a system with a high number of calls, using a compressed audio format for
; musiconhold takes CPU resources. Converting these files to ulaw/alaw makes the job
; much easier for your CPU.
load => format_mp3.so
load => res_musiconhold.so
;
; Load either OSS or ALSA, not both
; By default, load no console driver
;
noload => chan_alsa.so
noload => chan_oss.so
;
noload => crd_radius.so
noload => cel_radius.so
;
noload => app_directory_odbcstorage.so
noload => app_voicemail_odbcstorage.so
;
;

Clearly there is something different enough on our system that we are seeing different results in this situation. I will look into creating a post-startup script to manually unload the offending module as a work-around. Cheers!

Probably because you INSIST to write/execute crd_ instead of cdr_ isn’t it?

I mean… cdr_* resembles something related to “Call Detail Recording” (CDR) but what crd_* exactly stands for?

Parnassus

First, I sincerely apologize for any offense taken as none was meant. Second, I greatly appreciate the assistance provided here. Third, you were absolutely correct, the problem is resolved. Fourth, our lack of funding, staff and Linux expertise, combined with a slight reading impairment is not an excuse, but merely a feeble attempt at an explanation.
Thank you!

Mate, it’s all OK!

You’re very polite and I’m very happy you definitely solved your issue (and yes, don’t worry too much: executing a bad command or writing erroneous parameter happens very often and it’s quite common…we’re all - mere - mortals, the only difference we could make each others is the way we investigate/explore the world - and so try to solve - our own issues).

So JCelentano, now let FreePBX to sing (Celentano is the surname of a very famous - now old - italian singer and show man!).

We too had this issue after our recent update (FreePBX Distro).
In our case, we were getting entries several each minute to several each second.

Unloading cel_radius.so and cdr_radius.do resolved our issue.

Truly unclear as to why this module is loaded by default.
Also unclear as to why it generated these messages.