asterisk users - Sep 2006 - chan_zap.so stopped working after upgrading CentOS

Everything was working perfect until I updated CentOS using yum update.
errors are like these. Please help, what is the solution for this. Obviously
the zaptel hardware is not loading, byt why? How to load it again?

Sep 13 18:33:34 VERBOSE[1490] logger.c:  [chan_zap.so]Sep 13 18:33:34
VERBOSE[1490] logger.c:  [chan_zap.so] => (Zapata Telephony w/PRI)
Sep 13 18:33:34 VERBOSE[1490] logger.c:   == Parsing
'/etc/asterisk/zapata.conf': Sep 13 18:33:34 VERBOSE[1490] logger.c:  
=Parsing '/etc/asterisk/zapata.conf': Found
Sep 13 18:33:34 VERBOSE[1490] logger.c:   == Parsing '/etc/asterisk/zapata-
auto.conf': Sep 13 18:33:34 VERBOSE[1490] logger.c:   == Parsing
'/etc/asterisk/zapata-auto.conf': Found
Sep 13 18:33:34 VERBOSE[1490] logger.c:   == Parsing
'/etc/asterisk/zapata_additional.conf': Sep 13 18:33:34 VERBOSE[1490]
logger.c:   == Parsing '/etc/asterisk/zapata_additional.conf': Found
Sep 13 18:33:34 WARNING[1490] chan_zap.c: Unable to specify channel 1: No
such device or address
Sep 13 18:33:34 ERROR[1490] chan_zap.c: Unable to open channel 1: No such
device or address
here = 0, tmp->channel = 1, channel = 1
Sep 13 18:33:34 ERROR[1490] chan_zap.c: Unable to register channel
'1-23'
Sep 13 18:33:34 WARNING[1490] loader.c: chan_zap.so: load_module failed,
returning -1
Sep 13 18:33:34 WARNING[1490] loader.c: Loading module chan_zap.so failed!

-- 
Zeeshan A Zakaria
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20060913/ee75a767/attachment-0001.htm

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Zeeshan Zakaria wrote:
> Everything was working perfect until I updated CentOS using yum update.
> errors are like these. Please help, what is the solution for this.
> Obviously
> the zaptel hardware is not loading, byt why? How to load it again?
> 
> Sep 13 18:33:34 VERBOSE[1490] logger.c:  [chan_zap.so]Sep 13 18:33:34
> VERBOSE[1490] logger.c:  [chan_zap.so] => (Zapata Telephony w/PRI)
> Sep 13 18:33:34 VERBOSE[1490] logger.c:   == Parsing
> '/etc/asterisk/zapata.conf': Sep 13 18:33:34 VERBOSE[1490]
logger.c:   => Parsing '/etc/asterisk/zapata.conf': Found
> Sep 13 18:33:34 VERBOSE[1490] logger.c:   == Parsing
'/etc/asterisk/zapata-
> auto.conf': Sep 13 18:33:34 VERBOSE[1490] logger.c:   == Parsing
> '/etc/asterisk/zapata-auto.conf': Found
> Sep 13 18:33:34 VERBOSE[1490] logger.c:   == Parsing
> '/etc/asterisk/zapata_additional.conf': Sep 13 18:33:34
VERBOSE[1490]
> logger.c:   == Parsing '/etc/asterisk/zapata_additional.conf':
Found
> Sep 13 18:33:34 WARNING[1490] chan_zap.c: Unable to specify channel 1: No
> such device or address
> Sep 13 18:33:34 ERROR[1490] chan_zap.c: Unable to open channel 1: No such
> device or address
> here = 0, tmp->channel = 1, channel = 1
> Sep 13 18:33:34 ERROR[1490] chan_zap.c: Unable to register channel
'1-23'
> Sep 13 18:33:34 WARNING[1490] loader.c: chan_zap.so: load_module failed,
> returning -1
> Sep 13 18:33:34 WARNING[1490] loader.c: Loading module chan_zap.so failed!
New kernel maybe?

Zaptel kernel modules compiled for older kernel?

Try recompiling zaptel against new one?

Also search for CentOS Zaptel bug in Google.  Something about spinlock.h
or similar if I remember correctly.

- --
Cheers,

Matt Riddell
_______________________________________________

http://www.sineapps.com/news.php (Daily Asterisk News - html)
http://wap.sineapps.com (Daily Asterisk News for your cellphone)
http://feeds.feedburner.com/AsteriskNews (Daily Asterisk News - rss)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFCI5nS6d5vy0jeVcRAqVzAJ0fJtPDx/KYXcrZsjT4ODzjPNU6sgCfWpop
KroqCtApo1M9GDtqjShBwLI=2fHr
-----END PGP SIGNATURE-----

Zeeshan Zakaria wrote:
> Everything was working perfect until I updated CentOS using yum 
> update. errors are like these. Please help, what is the solution for 
> this. Obviously the zaptel hardware is not loading, byt why? How to 
> load it again?
>  
> Sep 13 18:33:34 VERBOSE[1490] logger.c:  [chan_zap.so]Sep 13 18:33:34 
> VERBOSE[1490] logger.c:  [chan_zap.so] => (Zapata Telephony w/PRI)
> Sep 13 18:33:34 VERBOSE[1490] logger.c:   == Parsing 
> '/etc/asterisk/zapata.conf': Sep 13 18:33:34 VERBOSE[1490]
logger.c:
> == Parsing '/etc/asterisk/zapata.conf': Found
> Sep 13 18:33:34 VERBOSE[1490] logger.c:   == Parsing 
> '/etc/asterisk/zapata-auto.conf': Sep 13 18:33:34 VERBOSE[1490] 
> logger.c:   == Parsing '/etc/asterisk/zapata- auto.conf': Found
> Sep 13 18:33:34 VERBOSE[1490] logger.c:   == Parsing 
> '/etc/asterisk/zapata_additional.conf': Sep 13 18:33:34
VERBOSE[1490]
> logger.c:   == Parsing '/etc/asterisk/zapata_additional.conf':
Found
> Sep 13 18:33:34 WARNING[1490] chan_zap.c: Unable to specify channel 1: 
> No such device or address
> Sep 13 18:33:34 ERROR[1490] chan_zap.c: Unable to open channel 1: No 
> such device or address
> here = 0, tmp->channel = 1, channel = 1
> Sep 13 18:33:34 ERROR[1490] chan_zap.c: Unable to register channel
'1-23'
> Sep 13 18:33:34 WARNING[1490] loader.c: chan_zap.so: load_module 
> failed, returning -1
> Sep 13 18:33:34 WARNING[1490] loader.c: Loading module chan_zap.so failed!
>
> -- 
> Zeeshan A Zakaria
> ------------------------------------------------------------------------
>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>   
cd /usr/src/zaptel
make clean
make && make install

Zeeshan Zakaria wrote:
> Everything was working perfect until I updated CentOS using yum 
> update. errors are like these. Please help, what is the solution for 
> this. Obviously the zaptel hardware is not loading, byt why? How to 
> load it again?
>  
> Sep 13 18:33:34 VERBOSE[1490] logger.c:  [chan_zap.so]Sep 13 18:33:34 
> VERBOSE[1490] logger.c:  [chan_zap.so] => (Zapata Telephony w/PRI)
> Sep 13 18:33:34 VERBOSE[1490] logger.c:   == Parsing 
> '/etc/asterisk/zapata.conf': Sep 13 18:33:34 VERBOSE[1490]
logger.c:
> == Parsing '/etc/asterisk/zapata.conf': Found
> Sep 13 18:33:34 VERBOSE[1490] logger.c:   == Parsing 
> '/etc/asterisk/zapata-auto.conf': Sep 13 18:33:34 VERBOSE[1490] 
> logger.c:   == Parsing '/etc/asterisk/zapata- auto.conf': Found
> Sep 13 18:33:34 VERBOSE[1490] logger.c:   == Parsing 
> '/etc/asterisk/zapata_additional.conf': Sep 13 18:33:34
VERBOSE[1490]
> logger.c:   == Parsing '/etc/asterisk/zapata_additional.conf':
Found
> Sep 13 18:33:34 WARNING[1490] chan_zap.c: Unable to specify channel 1: 
> No such device or address
> Sep 13 18:33:34 ERROR[1490] chan_zap.c: Unable to open channel 1: No 
> such device or address
> here = 0, tmp->channel = 1, channel = 1
> Sep 13 18:33:34 ERROR[1490] chan_zap.c: Unable to register channel
'1-23'
> Sep 13 18:33:34 WARNING[1490] loader.c: chan_zap.so: load_module 
> failed, returning -1
> Sep 13 18:33:34 WARNING[1490] loader.c: Loading module chan_zap.so failed!

Did you rebuild the zaptel kernel drivers after upgrading the kernel???

Steve

Yes, I did rebuild zaptel after upgrading the OS. And ended up rebuilding
everything, i.e. libpri, zaptel and asterisk, doing make clean on all of
them. But still the problem persists. I have to load CentOS using the old
kernel to keep the things working. As for spinlock, that error is in its
version 4, but I am running ver 3.

So what should I do to build zaptel for the new kernel?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20060913/e533c310/attachment.htm

> So what should I do to build zaptel for the new kernel?
As Steve Totaro said, when running the newer kernel, go to zaptel sources and:

make clean
make && make install

I remembered that i had to "make linux26" && make install, but
not
sure if this is still necessary for newer zaptel drivers.

"No such device or address" Is the error you get, so, i would bet you
dont have the file "/dev/zap/1" and "/proc/zaptel/"
directory do you?
And if you dont have these, it means the zaptel drivers are not
loaded.

Try this:

modprobe zaptel
modprobe <your card driver, like wctdm>

Regards

-- 
"Su nombre es GNU/Linux, no solamente Linux, mas info en
http://www.gnu.org"

Zeeshan Zakaria wrote:
> Yes, I did rebuild zaptel after upgrading the OS. And ended up 
> rebuilding everything, i.e. libpri, zaptel and asterisk, doing make 
> clean on all of them. But still the problem persists. I have to load 
> CentOS using the old kernel to keep the things working. As for 
> spinlock, that error is in its version 4, but I am running ver 3.
>  
> So what should I do to build zaptel for the new kernel?
>
>------------------------------------------------------------------------
>
>_______________________________________________
>--Bandwidth and Colocation provided by Easynews.com --
>
>asterisk-users mailing list
>To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>  
>
I would try that.

Zeeshan Zakaria wrote:
> Yes, I did rebuild zaptel after upgrading the OS. And ended up 
> rebuilding everything, i.e. libpri, zaptel and asterisk, doing make 
> clean on all of them. But still the problem persists. I have to load 
> CentOS using the old kernel to keep the things working. As for 
> spinlock, that error is in its version 4, but I am running ver 3.
>  
> So what should I do to build zaptel for the new kernel?
>
Boot to the new kernel and build zaptel.  Asterisk and libpri should be 
OK without rebuild.

Moises Silva wrote:
>> So what should I do to build zaptel for the new kernel?
>
> As Steve Totaro said, when running the newer kernel, go to zaptel 
> sources and:
>
> make clean
> make && make install
>
> I remembered that i had to "make linux26" && make
install, but not
> sure if this is still necessary for newer zaptel drivers.
>
> "No such device or address" Is the error you get, so, i would bet
you
> dont have the file "/dev/zap/1" and "/proc/zaptel/"
directory do you?
> And if you dont have these, it means the zaptel drivers are not
> loaded.
>
> Try this:
>
> modprobe zaptel
> modprobe <your card driver, like wctdm>
>
> Regards
>
Dont forget ztcfg for good measure.

On 9/13/06, Steve Totaro <stotaro@asteriskhelpdesk.com>
wrote:
> > Try this:
> >
> > modprobe zaptel
> > modprobe <your card driver, like wctdm>
We ran into the same thing, and the only way I can get it to work
(which is goofy, but it does work) is modprobing the same device
multiple times.

So

modprobe zaptel
modprobe zaptel
modprobe <your card driver, like wctdm>
modprobe <your card driver, like wctdm>
ztcfg -vvvvvv

We run centos 4.3 and this is what we have to do .

It has to do something with udev,

also try making with udev as referenced here:

http://www.voip-info.org/tiki-index.php?page=Asterisk+CentOS-4.0+Zaptel

Brent Franks wrote:
> We ran into the same thing, and the only way I can get it to work
> (which is goofy, but it does work) is modprobing the same device
> multiple times.
Try waiting after modprobe zaptel for udev to create the device nodes. I 
do this:

modprobe zaptel
wait 5
modprobe wctdm
ztcfg -vvv

And it works fine for me on CentOS 4.3

cYa,
Avi

-- 
National Manager - Special Projects

< Sydney / Melbourne / Canberra / Hobart / London />
   2/340 Gore Street      T: 1 3000 SQUIZ (77849)
   Fitzroy, VIC           T: +61 (0) 3 9235 5400
   3065                   F: +61 (0) 3 9235 5444
                          W: http://www.squiz.net/

.....>> Open Source  - Own it  -  Squiz.net ...../>

In article <4508D287.9020608@squiz.net>,
Avi Miller <avi.miller@squiz.net> wrote:
> Brent Franks wrote:
> > We ran into the same thing, and the only way I can get it to work
> > (which is goofy, but it does work) is modprobing the same device
> > multiple times.
> 
> Try waiting after modprobe zaptel for udev to create the device nodes. I 
> do this:
> 
> modprobe zaptel
> wait 5
> modprobe wctdm
> ztcfg -vvv
> 
> And it works fine for me on CentOS 4.3
Why oh why do so many people do all this modprobe stuff manually or in
rc.local etc.?????

If you are running a RedHat / Fedora / CentOS distribution, just do
"make config" in the zaptel directory, and it will create a proper
startup script in init.d and set up the rc.d links for invocation at
boot time. This proper script takes care of loading the modules AND
waiting for udev to create the device nodes.

You can also then do "service zaptel stop" and "service zaptel
start"
to unload and reload the drivers if needed.

Cheers
Tony
-- 
Tony Mountifield
Work: tony@softins.co.uk - http://www.softins.co.uk
Play: tony@mountifield.org - http://tony.mountifield.org

> Why oh why do so many people do all this modprobe stuff manually or in
> rc.local etc.?????
>
> If you are running a RedHat / Fedora / CentOS distribution, just do
> "make config" in the zaptel directory, and it will create a
proper
> startup script in init.d and set up the rc.d links for invocation at
> boot time. This proper script takes care of loading the modules AND
> waiting for udev to create the device nodes.
Because they are using slackware??? :)

Seriously, i dont think anyone having a server is doing this manually
(I hope so), but for the sake of simplicity at the time of explaining
what is the minimal thing you have to do to have it working, I think
is better explain the basics, otherwise people get custom to do stuff
that is not available in all distributions in the same way.

Regards
-- 
"Su nombre es GNU/Linux, no solamente Linux, mas info en
http://www.gnu.org"

In article <c4d05cbe0609140717p45c229e6q6049a4a53a828831@mail.gmail.com>,
Moises Silva <moises.silva@gmail.com> wrote:
> > Why oh why do so many people do all this modprobe stuff manually or in
> > rc.local etc.?????
> >
> > If you are running a RedHat / Fedora / CentOS distribution, just do
> > "make config" in the zaptel directory, and it will create a
proper
> > startup script in init.d and set up the rc.d links for invocation at
> > boot time. This proper script takes care of loading the modules AND
> > waiting for udev to create the device nodes.
> 
> Because they are using slackware??? :)
But the TWO preceding messages in this branch of the thread both said
they were running CentOS, and both were doing kludges with individual
modprobes (in one case TWICE!) instead of just using the supplied
script.

Cheers
Tony
-- 
Tony Mountifield
Work: tony@softins.co.uk - http://www.softins.co.uk
Play: tony@mountifield.org - http://tony.mountifield.org