vicidial.org

by **Baylink** » Thu Apr 14, 2011 8:11 am

Fresh install, 3.1.9-32bit on an Athlon quadcore.

Did upgrade OS and to trunk, did not configure any hardware -- to use VoIP as uplink.

Asterisk won't start and stay running, even after a manual restart of the vicidial service, with the message shown in the title (and all the messages commonly associated with that).

updatedb followed by "locate dahdi_dummy" comes up empty -- should I not expect the vicibox-install script to have built dahdi, and/or dahdi_dummy?

Still prowling through the other threads in a search for that error, but haven't found anything yet that's this early in the process.

by **Baylink** » Thu Apr 14, 2011 8:31 am

Further:

vicidial1:~ # dahdi_test
Unable to open dahdi interface: No such file or directory

by **Baylink** » Thu Apr 14, 2011 8:35 am

And here's the actual startup dialog:

vicidial1:~ # svc vicidial start
Loading DAHDI drivers
Starting Sangoma wanrouter driver

ERROR: Wanpipe configuration file not found:
/etc/wanpipe/wanpipe1.conf

Sangoma failed to load! Fallback to dahdi_dummy module!
FATAL: Module dahdi_dummy not found.
dahdi_dummy NOT loaded
vicidial1:~ #

The symptom is that all the cronjobs fail to connect to port 5038, and sure enough, when I check ps, no asterisk process.

Does the Sangoma message suggest that perhaps I misread the polarity of the install question about Sangoma hardware? I'm pretty sure I told it not to look for any cards; the machine -- as noted above -- will be VoIP only.

by **Baylink** » Thu Apr 14, 2011 8:38 am

Hopefully, it's sane to rerun vicibox-install without redoing the entire install; I did, and here were the settings:

OS Update : n
Stop Firewall : y
Use SVN Code : y
Install Core DB : y
Install Web App : y
- Install VTiger : n
Install Telephony : y
- Additional Server : n
- Install Wanpipe : n
- Install Voicetime : n

Same result though.

by **williamconley** » Thu Apr 14, 2011 10:17 am

try using the scratch installation instructions to re-install libpri, dahdi, asterisk.

you'll need dahdi to load (but there is no sep dahdi_dummy, except in lsmod where it's visible).

once you get dahdi to load with modprobe you should be much happier.

by **Baylink** » Thu Apr 14, 2011 10:28 am

I have a libpri, and it would appear I have all the dahdi tools, already:

vicidial1:~ # locate dahdi
/etc/asterisk/chan_dahdi.conf
/etc/dahdi
/etc/dahdi/genconf_parameters
/etc/dahdi/init.conf
/etc/dahdi/modules
/etc/dahdi/system.conf
/etc/modprobe.d/dahdi.blacklist.conf
/etc/modprobe.d/dahdi.conf
/etc/udev/rules.d/dahdi.rules
/etc/wanpipe/wancfg_zaptel/templates/dahdi-channels.conf
/etc/wanpipe/wancfg_zaptel/templates/dahdi_cfg_script
/etc/wanpipe/wancfg_zaptel/wancfg_dahdi
/lib/firmware/.dahdi-fw-hx8-2.06
/lib/firmware/.dahdi-fw-oct6114-064-1.05.01
/lib/firmware/.dahdi-fw-oct6114-128-1.05.01
/lib/firmware/.dahdi-fw-tc400m-MR6.12
/lib/firmware/dahdi-fw-hx8.bin
/lib/firmware/dahdi-fw-oct6114-064.bin
/lib/firmware/dahdi-fw-oct6114-128.bin
/lib/firmware/dahdi-fw-tc400m.bin
/lib/modules/2.6.34-12-pae/extra/dahdi.ko
/lib/modules/2.6.34-12-pae/extra/dahdi_dynamic.ko
/lib/modules/2.6.34-12-pae/extra/dahdi_dynamic_eth.ko
/lib/modules/2.6.34-12-pae/extra/dahdi_dynamic_ethmf.ko
/lib/modules/2.6.34-12-pae/extra/dahdi_dynamic_loc.ko
/lib/modules/2.6.34-12-pae/extra/dahdi_echocan_jpah.ko
/lib/modules/2.6.34-12-pae/extra/dahdi_echocan_kb1.ko
/lib/modules/2.6.34-12-pae/extra/dahdi_echocan_mg2.ko
/lib/modules/2.6.34-12-pae/extra/dahdi_echocan_sec.ko
/lib/modules/2.6.34-12-pae/extra/dahdi_echocan_sec2.ko
/lib/modules/2.6.34-12-pae/extra/dahdi_transcode.ko
/lib/modules/2.6.34-12-pae/extra/dahdi_vpmadt032_loader.ko
/lib/modules/2.6.34-12-pae/extra/voicebus/dahdi_voicebus.ko
/usr/include/dahdi
/usr/include/dahdi/tonezone.h
/usr/lib/asterisk/modules/app_dahdibarge.so
/usr/lib/asterisk/modules/app_dahdiras.so
/usr/lib/asterisk/modules/app_dahdiscan.so
/usr/lib/asterisk/modules/chan_dahdi.so
/usr/lib/asterisk/modules/codec_dahdi.so
/usr/lib/perl5/vendor_perl/5.12.1/Dahdi/Config/Gen/Chandahdi.pm
/usr/sbin/dahdi_cfg
/usr/sbin/dahdi_genconf
/usr/sbin/dahdi_hardware
/usr/sbin/dahdi_maint
/usr/sbin/dahdi_monitor
/usr/sbin/dahdi_registration
/usr/sbin/dahdi_scan
/usr/sbin/dahdi_speed
/usr/sbin/dahdi_test
/usr/sbin/dahdi_tool
/usr/sbin/lsdahdi
/usr/sbin/wancfg_dahdi
/usr/share/dahdi
/usr/share/dahdi/astribank_hook
/usr/share/dahdi/FPGA_1141.hex
/usr/share/dahdi/FPGA_1151.hex
/usr/share/dahdi/FPGA_1161.hex
/usr/share/dahdi/FPGA_FXS.hex
/usr/share/dahdi/init_card_1_30
/usr/share/dahdi/init_card_2_30
/usr/share/dahdi/init_card_3_30
/usr/share/dahdi/init_card_4_30
/usr/share/dahdi/PIC_TYPE_1.hex
/usr/share/dahdi/PIC_TYPE_2.hex
/usr/share/dahdi/PIC_TYPE_3.hex
/usr/share/dahdi/PIC_TYPE_4.hex
/usr/share/dahdi/USB_FW.hex
/usr/share/dahdi/waitfor_xpds
/usr/share/dahdi/XppConfig.pm
/usr/share/dahdi/xpp_fxloader
/usr/share/doc/packages/asterisk-vici/configs/chan_dahdi.conf.sample
/usr/share/man/man8/dahdi_cfg.8.gz
/usr/share/man/man8/dahdi_genconf.8.gz
/usr/share/man/man8/dahdi_hardware.8.gz
/usr/share/man/man8/dahdi_monitor.8.gz
/usr/share/man/man8/dahdi_registration.8.gz
/usr/share/man/man8/dahdi_scan.8.gz
/usr/share/man/man8/dahdi_test.8.gz
/usr/share/man/man8/dahdi_tool.8.gz
/usr/share/man/man8/lsdahdi.8.gz
/var/adm/fillup-templates/sysconfig.dahdi
/var/cache/zypp/packages/home:vicidial_11.3/i586/asterisk-vici-dahdi-1.4.39.1-13.6.i586.rpm
/var/cache/zypp/packages/home:vicidial_11.3/i586/dahdi-2.4.1-16.2.i586.rpm
/var/cache/zypp/packages/home:vicidial_11.3/i586/dahdi-kmp-pae-2.4.1_k2.6.34.0_12-16.2.i586.rpm
/var/cache/zypp/packages/home:vicidial_11.3/i586/dahdi-tools-2.4.1-49.1.i586.rpm
/var/cache/zypp/packages/home:vicidial_11.3/i586/dahdi-tools-devel-2.4.1-49.1.i586.rpm
/var/lib/asterisk/sounds/spy-dahdi.gsm
vicidial1:~ #

But they appear to be built for the wrong kernel:

Linux vicidial1 2.6.34.7-0.7-pae #1 SMP 2010-12-13 11:13:53 +0100 i686 athlon i386 GNU/Linux

Is the "rebuild all the modules after a kernel upgrade" process scripted these days? Or is that the "recompile script" which I note from another post is not *in* the vicibox build anymore?

by **williamconley** » Thu Apr 14, 2011 10:34 am

it's gone. but the process is actually rather simple. if you look at the scratch install instructions, you can skip the "download" portion (since you already have the software). It's just about moving into each of the three directories in order, executing three commands in each of three directories.

by **Baylink** » Thu Apr 14, 2011 10:39 am

Rog. I wasn't sure how closely the vicibox scripting tracked that document.

...

Where the hell *is* the scratch install document these days? :-}

Apparently: here.

And, alas, it assumes a) that I'll have any linux directories in my /usr/src at *all*, after the VB installer runs, and b) that azreal.crashsys still exists. Where are those compile scripts at now?

Well, perhaps you mean the SCRATCH_INSTALL.txt in the distro itself...

by **Baylink** » Thu Apr 14, 2011 11:53 am

Well... it does not appear that the VICIbox build *includes* the sources for Asterisk, et al; I don't see them anywhere on the machine.

So, clearly, recompiling to track an updated kernel is highly non-trivial, unless there's something important I'm missing.

That would seem to make updating the OS during install a bad choice. Here I go to re-run the install from scratch, and say "no" to that.

by **Baylink** » Thu Apr 14, 2011 12:28 pm

Yup, rerunning the install and not updating the OS solves that. Now I'll run YoU by hand.

by **Baylink** » Thu Apr 14, 2011 1:54 pm

And, *even* though I tell it not to update the kernel, it will re-break things anyway. Pants.

Yup. The driver modules are for 2.6.34.0, and my kernel's the shipping 2.6.34.7. I'm not sure how it ran *before* I did the update, though I didn't check the uname, dangit.

Ok, let's install *again*, since, like every other package manager, yast won't let you back out an upgrade...

by **Baylink** » Thu Apr 14, 2011 3:50 pm

Did the install, tried to upgrade everything but the kernel, specifically telling it not to touch dahdi-kmp-pae (which, BTW, is built for a 2.6.34.0 kernel in the installed RPM), not a .7 kernel, which is what we have -- and that blows it up as well.

So I reinstalled it a fifth time, and just didn't do the OS upgrades.

And this time, it boots and everything comes up and sits idle. Like it's supposed to. Where do we file bugs on Vicibox?

by **williamconley** » Thu Apr 14, 2011 3:58 pm

you're already there. but you have to specify the bug (not a bunch of "nothing works" ... of course).

i tried to follow along, but i'm not sure i got it at all. When you have a specific bug to report that you can duplicate and identify ... Kumba will fix

by **Baylink** » Thu Apr 14, 2011 4:12 pm

"Vicibox 3.1.9 installs a 2.6.34.7 kernel, but a dahdi-kmp-pae-2.40 module built and tagged for kernel 2.6.34.0; this means that *anything* you do with YoU after install, either via the vicibox-install script or manually, breaks dahdi, forcing YoU to uninstall it. When there's no dahdi package installed, (and assuming you require dahdi-dummy for lack of hardware drivers), Asterisk 1.4 won't start. Doing no OS upgrade will, for some reason, allow dahdi to load, even though it *is* built for a different kernel".

Is that clean enough? :-)

by **williamconley** » Thu Apr 14, 2011 4:18 pm

seems clear to me

by **Baylink** » Thu Apr 14, 2011 6:07 pm

Posted as bug: http://www.vicidial.org/VICIDIALforum/v ... hp?t=17706

by **Trying** » Fri Apr 15, 2011 4:31 am

Then this must be the same issues I experienced

by **dspaan** » Fri Apr 15, 2011 5:53 am

We seem to have the same problem, been stuck on this for 3 days now.
See topic here: http://www.vicidial.org/VICIDIALforum/v ... highlight=

I tried installing dahdi manually and got this error:

You do not appear to have the sources for the 2.6.34.7-0.7-pae kernel installed.

We already tried installing without zypper up & zypper refresh and without upgrading the OS in phase 2. Can you please tell me how i can workaround this problem, i don't understand what you did to get it working.

by **Baylink** » Fri Apr 15, 2011 7:07 am

When you're prompted, during the install, to upgrade the OS, say *no*. That's the only thing I had to do.

The dahdi module appears to be built against a .0 kernel, and what you get when you run the vicibox installer these days isn't that kernel anymore, it's .7.

While the module will still *work*, this badly confuses the *updater*, which believes it must uninstall that module to avoid a mismatch, and nothing you tell it will convince it otherwise. Even if it *looks like* it's convinced it. :-{

The number of reinstalls it took me to figure out what was actually going on would curl your hair. :-)

by **dspaan** » Fri Apr 15, 2011 7:24 am

You mean after you type 'vicibox-install' in phase 2 right? So you did do phase 1.5 'zypper refresh && zypper up'?

edit: seems to have worked now but i suspect it's because of the change Kumba made.

by **Baylink** » Sat Apr 16, 2011 9:03 pm

No, cause vicibox-install *prompts me if I want to upgrade the OS*. So I don't ever call zypper manually.

Are we talking about different install procedures, here?

vicidial.org

3.1.9 - Asterisk won't start: "Module dahdi_dummy not f

3.1.9 - Asterisk won't start: "Module dahdi_dummy not f

Who is online