I'm trying to get Asterisk to build and having big problems.

I'm pretty rusty at using Linux, so I've probably made some mistakes...
(Several years ago, I built ffmpeg "from scratch" and had to install lots of modules on a dedicated server before it would build. I got it built, running, and doing some pretty great things for audio and video podcasts. So...I have some related experience, just not recently.)

I'm working on a VirtualMachine on a server hosted elsewhere.

Operating System: CentOS 7

Initially, the VM was running the 3.10.0-862.3.2.el7.x86_64 kernel

First, I did sudo bash to become root. I did that before installing a lot of other modules on this Virtual Machine...

Pretty much everything is owned by root.

Following these instructions: https://wiki.asterisk.org/wiki/displ...stalling+DAHDI

I've downloaded dahdi-linux-complete-current.tar.gz, libpri-current.tar.gz, and asterisk-14-current.tar.gz into /usr/src

I've run:
tar -zxvf libpri-current.tar.gz
tar -zxvf dahdi-linux-complete-2.X.Y+2.X.Y.tar.gz
tar -zxvf asterisk-14-current.tar.gz

So, I have the source-code folders for the builds.

Now I need to build and install DAHDI (can't install libpri without it because of dependencies)

So...
cd /usr/src/dahdi-linux-complete-2.11.1+2.11.1
make
Fails with this:
You do not appear to have the sources for the 4.16.11-1.el7.elrepo.x86_64 kernel installed.

Previously, I had been running the 3.10.0-862.3.2.el7.x86_64 kernel and had gotten the error
You do not appear to have the sources for the 3.10.0-862.3.2.el7.x86_64 kernel installed.

So I tried installing the latest (as of that day) kernel, which was 4.16.11-1.el7.elrepo.x86_64, in the (false?) hope that it would put the source files in /usr/src/kernels. It didn't. But after a reboot, it's running the newer kernel.

Currently,

uname -r gives me:
4.16.11-1.el7.elrepo.x86_64

uname -a gives me:
Linux ip-192-168-100-8.us-east-2.compute.internal 4.16.11-1.el7.elrepo.x86_64 #1 SMP Tue May 22 15:34:16 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux

In /usr/src/kernels, ls gives me:
3.10.0-862.3.2.el7.x86_64

That looks to me like source code for the 3.10.0-862.3.2.el7.x86_64 kernel. (Is that correct?)

Doing "ls -l" in /usr/libs/modules gives me:
drwxr-xr-x 7 root root 4096 Jan 4 15:31 3.10.0-693.11.6.el7.x86_64
drwxr-xr-x. 7 root root 4096 Nov 27 22:12 3.10.0-693.5.2.el7.x86_64
drwxr-xr-x 7 root root 4096 May 24 19:52 3.10.0-862.3.2.el7.x86_64
drwxr-xr-x 7 root root 4096 May 25 20:32 4.16.11-1.el7.elrepo.x86_64
drwxr-xr-x 7 root root 4096 May 27 17:35 4.16.12-1.el7.elrepo.x86_64

I think that that means all four of those kernels have been built. Is that true?

Hindsight being oh-so-useful, I decided to add /usr/src/kernels to the PATH
echo $PATH reports:
/root/perl5/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/src/kernels

The problem is still that I don't have the kernel sources for 4.16.11-1.el7.elrepo.x86_64 anywhere that the make utility can find them when attempting to build DAHDI.

I've Googled for hours looking for a solution to the missing-sources problem and come up empty. Oh, sure, there were plenty of suggested fixes. I've tried them all without success.

Is it possible to change back to running the 3.10.0-862.3.2.el7.x86_64 kernel so that it would match up with the sources in /usr/src/kernels?

Or is there a way to copy the 4.16.11-1.el7.elrepo.x86_64 from SOMEWHERE into /usr/src/kernels?

Getting DADHDI to build is the 1st hurdle. Hopefully, once that's done the rest will be more straightforward. I ultimately need Asterisk installed and working so that we can build and run VICIdial.

This quote from http://asteriskfaqs.org seems to sum up the problem: "You need to make sure the kernel and kernel-devel packages are the same versions, and that you are running from the same kernel too (make sure you rebooted after any update of the kernel)."

Any help would be greatly appreciated.

so it was written, kernel source mean you need to install kernel-devel package (the same version as your kernel itself)

I'm not sure why it worked the 3rd time and not the 1st or 2nd time, but...

Setting the kernel for which I had sources installed to be the default running kernel (again) and rebooting the system (again) finally worked.

DAHDI is now built and installed.

so if your problem is solved please mark the thread solved.

One problem remains. The DAHDA module refuses to start!

According to: https://wiki.asterisk.org/wiki/displ...r+Installation, I should be able to start dahdi like this:

service dahdi start (Redhat/Centos version)

but the result of that command is:

Redirecting to /bin/systemctl start dahdi.service
Failed to start dahdi.service: Unit not found.

Likewise for:
systemctl start dahdi.service
Failed to start dahdi.service: Unit not found.

Not surprisingly,

lsmod | grep dahdi

returns nothing at all.

Solved (I hope):

Whew! Figured out that somehow(??), /etc/init.d/dahdi was created as an empty folder. It should have been a file containing a shell script. So, I removed the empty /etc/init.d/dahdi directory. Then I fetched the contents of that shell script, created a new file using nano, inserted the code and saved it as /etc/init.d/dahdi.

I had to:

chmod 755 dahdi

so it could execute and now the start command works...sort of.

systemctl status dahdi.service -> gives this output:
● dahdi.service - LSB: DAHDI kernel modules
Loaded: loaded (/etc/rc.d/init.d/dahdi; bad; vendor preset: disabled)
Active: active (exited) since Fri 2018-06-01 14:41:07 UTC; 10min ago
Docs: man:systemd-sysv-generator(8)
Process: 29345 ExecStart=/etc/rc.d/init.d/dahdi start (code=exited, status=0/SUCCESS)

systemctl status dahdi.service gives:
Loaded: loaded (/etc/rc.d/init.d/dahdi; bad; vendor preset: disabled)
Active: active (exited) since Fri 2018-06-01 14:41:07 UTC; 24min ago
Docs: man:systemd-sysv-generator(8)

Jun 01 14:41:07 ip-192-168-100-8.us-east-2.compute.internal systemd[1]: Starting LSB: DAHDI kernel modules...
Jun 01 14:41:07 ip-192-168-100-8.us-east-2.compute.internal dahdi[29345]: /etc/dahdi/system.conf not found. Nothing to do.
Jun 01 14:41:07 ip-192-168-100-8.us-east-2.compute.internal systemd[1]: Started LSB: DAHDI kernel modules.

Looks like I need to work on /etc/rc.d/init.d/dahdi and some configuration file(s)

Can someone tell me what these lines mean:

Loaded: loaded (/etc/rc.d/init.d/dahdi; bad; vendor preset: disabled)
Active: active (exited) since Fri 2018-06-01 15:58:59 UTC; 1h 49min ago

My guess is that dahd started and then something went wrong. I just don't know what or why.

There are some other messages below those, Please post them inside [code] tags.

To: Awesome Machine -- If I'm understanding you right, here's what you asked for. (CentOS 7.5 system)
Command:
# systemctl status dahdi.service
Response:
● dahdi.service - LSB: DAHDI kernel modules
Loaded: loaded (/etc/rc.d/init.d/dahdi; bad; vendor preset: disabled)
Active: active (exited) since Sat 2018-06-02 12:05:51 EDT; 22h ago

there is an error-like message in it: /usr/share/dahdi/waitfor_xpds: line 106: astribank_is_starting: command not found
probably that's why it has exited.