LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Kernel (https://www.linuxquestions.org/questions/linux-kernel-70/)
-   -   Un derstanding fauilure to srtart a module (https://www.linuxquestions.org/questions/linux-kernel-70/un-derstanding-fauilure-to-srtart-a-module-4175630996/)

boozah 06-01-2018 04:33 PM

Un derstanding fauilure to srtart a module
 
In the output from: systemctl status dahdi.service

I see these lines:
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

Can someone tell me what these lines mean?

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

hydrurga 06-01-2018 04:58 PM

Given the dearth of information you have provided on what this service is and does, and which distro you are running, all I can say is it looks to me as if the service started, did what it had to do and then exited. It didn't know that it had to keep running and act as a daemon, if that's what you're expecting it to do. See the final link for a possible workaround.

https://askubuntu.com/questions/8360...s-includes-bad

https://unix.stackexchange.com/quest...custom-service

http://lists.digium.com/pipermail/as...ry/288334.html

boozah 06-01-2018 05:10 PM

The distro is CentOS 7.5
DAHDI (dahdi.service) is the “Digium Asterisk Hardware Device Interface".
It provides hardware device services to the Asterisk module. I was expecting it to stay loaded and running once it was started. The fact that it is failing somehow is causing problems for Asterisk. I need to get Asterisk running properly, o that I can run VIVCIdial on top of Asterisk and provide automated phone message services to my client's customers.

"State active (exited) means that systemd has successfully run the commands but that it does not know there is a daemon to monitor."

It seems that the daemon isn't running but should be - but then I'm kind of a newbie here.

I hope this helps.

hydrurga 06-01-2018 05:14 PM

Quote:

Originally Posted by boozah (Post 5862331)
The distro is CentOS 7.5
DAHDI (dahdi.service) is the “Digium Asterisk Hardware Device Interface".
It provides hardware device services to the Asterisk module. I was expecting it to stay loaded and running once it was started. The fact that it is failing somehow is causing problems for Asterisk. I need to get Asterisk running properly, o that I can run VIVCIdial on top of Asterisk and provide automated phone message services to my client's customers.

"State active (exited) means that systemd has successfully run the commands but that it does not know there is a daemon to monitor."

It seems that the daemon isn't running but should be - but then I'm kind of a newbie here.

I hope this helps.

Did you have a look at that third link? It suggests installing two other packages.

boozah 06-01-2018 07:01 PM

Yes I did. But I had installed 'dahdi-linux-complete-2.11.1+2.11.1', which includes the contents of those two packages - as well as the base dahdi installation. :(

hydrurga 06-01-2018 07:43 PM

Quote:

Originally Posted by boozah (Post 5862352)
Yes I did. But I had installed 'dahdi-linux-complete-2.11.1+2.11.1', which includes the contents of those two packages - as well as the base dahdi installation. :(

Ok. Have you tried asking here?: https://community.asterisk.org/

hydrurga 06-01-2018 07:48 PM

Also, which instructions did you follow when installing everything?

Here is an example:

https://computingforgeeks.com/how-to...by-step-guide/

boozah 06-01-2018 08:22 PM

I used the instructions here: https://wiki.asterisk.org/wiki/displ...lling+Asterisk

Also, there was some help in the SCRATCH_INSTALL.txt file from the package here:

http://www.vicidial.org/vicidial.php

despite the versions of many packages here being outdated.

The ultimate goal is to get VICIdial running. As of a few minutes ago, I get an error loading the homepage of the /var/www/html folder on the server. I don't know what broke that but apache is clearly still running.

systemctl status httpd
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2018-05-31 19:37:26 UTC; 1 day 5h ago
Docs: man:httpd(8)
man:apachectl(8)
Main PID: 2496 (httpd)
Status: "Total requests: 9; Current requests/sec: 0; Current traffic: 0 B/sec"
CGroup: /system.slice/httpd.service
├─2496 /usr/sbin/httpd -DFOREGROUND
├─2497 /usr/sbin/httpd -DFOREGROUND
├─2498 /usr/sbin/httpd -DFOREGROUND
├─2499 /usr/sbin/httpd -DFOREGROUND
├─2500 /usr/sbin/httpd -DFOREGROUND
├─2501 /usr/sbin/httpd -DFOREGROUND
├─2502 /usr/sbin/httpd -DFOREGROUND
└─2503 /usr/sbin/httpd -DFOREGROUND

Restarting it didn't fix the failure to connect...

This site can’t be reached
157.250.xxx.xxx took too long to respond.

Ugh.

boozah 06-02-2018 09:56 AM

I rebooted the server and that fixed the connectivity problem. I still can't connect to /agc/vicidial.php

AwesomeMachine 06-02-2018 11:58 AM

Is there a file /var/www/html/index.html? Perhaps look at the permissions.

boozah 06-03-2018 09:43 AM

Yes there is. I created that file to verify that the apache server was working properly. When I type {IP_ADDRESS} in the address bar of my browser (Chrome), I see that HTML page.

Its permissions are 644, owner and group are root.

For /var/www/html/agc, owner and group are root and file permissions are currently 755.
For /var/www/html/agc/vicidial, owner and group are root and file permissions are currently 755.
For /var/www/html/agc/vicidial.php, owner and group are both root and file permissions are currently 755.


All times are GMT -5. The time now is 11:29 PM.