[Home]

Summary:ASTERISK-08839: chan_zap problem after reload
Reporter:St├ęphane HENRY (stef)Labels:
Date Opened:2007-02-19 08:59:36.000-0600Date Closed:2011-06-07 14:02:37
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:We have this stange error sometimes after a reload :



Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Failed to read gains: Invalid argument
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Failed to read gains: Invalid argument
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Updated conferencing on 1, with 0 conference users
Feb 17 15:00:17 VERBOSE[16775] logger.c:     -- Reconfigured channel 1, PRI Signalling signalling
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Failed to read gains: Invalid argument
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Failed to read gains: Invalid argument
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Updated conferencing on 2, with 0 conference users
Feb 17 15:00:17 VERBOSE[16775] logger.c:     -- Reconfigured channel 2, PRI Signalling signalling
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Failed to read gains: Invalid argument
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Failed to read gains: Invalid argument
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Updated conferencing on 3, with 0 conference users
Feb 17 15:00:17 VERBOSE[16775] logger.c:     -- Reconfigured channel 3, PRI Signalling signalling
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Failed to read gains: Invalid argument
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Failed to read gains: Invalid argument
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Updated conferencing on 4, with 0 conference users
Feb 17 15:00:17 VERBOSE[16775] logger.c:     -- Reconfigured channel 4, PRI Signalling signalling
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Failed to read gains: Invalid argument
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Failed to read gains: Invalid argument
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Updated conferencing on 5, with 0 conference users
Feb 17 15:00:17 VERBOSE[16775] logger.c:     -- Reconfigured channel 5, PRI Signalling signalling
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Failed to read gains: Invalid argument
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Failed to read gains: Invalid argument
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Updated conferencing on 6, with 0 conference users
Feb 17 15:00:17 VERBOSE[16775] logger.c:     -- Reconfigured channel 6, PRI Signalling signalling
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Failed to read gains: Invalid argument
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Failed to read gains: Invalid argument
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Updated conferencing on 7, with 0 conference users
Feb 17 15:00:17 VERBOSE[16775] logger.c:     -- Reconfigured channel 7, PRI Signalling signalling
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Failed to read gains: Invalid argument
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Failed to read gains: Invalid argument
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Updated conferencing on 8, with 0 conference users
Feb 17 15:00:17 VERBOSE[16775] logger.c:     -- Reconfigured channel 8, PRI Signalling signalling
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Failed to read gains: Invalid argument
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Failed to read gains: Invalid argument
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Updated conferencing on 9, with 0 conference users
Feb 17 15:00:17 VERBOSE[16775] logger.c:     -- Reconfigured channel 9, PRI Signalling signalling
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Failed to read gains: Invalid argument
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Failed to read gains: Invalid argument
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Updated conferencing on 10, with 0 conference users
Feb 17 15:00:17 VERBOSE[16775] logger.c:     -- Reconfigured channel 10, PRI Signalling signalling
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Failed to read gains: Invalid argument
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Failed to read gains: Invalid argument
Feb 17 15:00:17 DEBUG[16775] chan_zap.c: Updated conferencing on 11, with 0 conference users


****** ADDITIONAL INFORMATION ******

Software we have :
asterisk version : 1.2.14
libpri version : 1.2.4
zaptel version : 1.2.12

Linux software :
Debian Linux stable version (sarge)
kernel version 2.6.8-1-686-smp
gcc-3.3
libc6-dev 2.3.2.ds1-22

Hardware we have :
TE410P driver used : wct4xxp
Intel(R) Pentium(R) 4 CPU 3.20GHz
MemTotal: 2076376 kB
Comments:By: Dwayne Hubbard (dhubbard) 2007-03-05 17:24:57.000-0600

No problem found.  This is a DEBUG message, not an ERROR or WARNING message.  If you don't want to see this message, please modify /etc/asterisk/logger.conf to not include 'debug' in the 'messages' and 'console' entries.  thank you.  :-)