Failure to unload zaptel drivers when shutting down?

[dswartz]

I've found similar threads involving kernel panics, but that is not happening for me. What I *do* see is shutting down the zaptel service (either explicitly with 'service zaptel stop' or implicitly with 'shutdown -r now'), it complains that it is unable to unload zaptel and the rhino driver because they are in use. Stopping asterisk first avoids this. Threads I saw referred to renaming rc0.d/K92zaptel to rc0.d/K92zaptel so it will run after rc0.d/K94asterisk (this is from trixbox, btw.) Unfortunately, PIAF does not have a K94asterisk, so nothing (apparently) shuts down asterisk before the shutdown attempt on zaptel. I guess I can create a script K01asterisk and put a link to it in rc0.d and have it do 'amportal kill' or whatever - just wondering why that isn't already there?

 

[jroper]

Hi

In FreePBX it is Amportal that starts and stops asterisk, in a vanilla install, asterisk is run as a service.

So you would need to do amportal kill first then shutdown.

Maybe the easiest way is to do a little custom shutdown script, rather than typing reboot.

e.g. /usr/local/sbin/bouncebox.sh

#!/bin/sh
#This code shuts down asterisk and then reboots the system.
amportal kill
reboot

ALthough not relavant to your problem - adding the following line to /etc/sysctl.conf will reboot the box 20 seconds after a kernel panic

kernel.panic = 20

 

[dswartz]

That's a thought, thanks. I'd like to have this associated with zaptel shutdown though - another case is where I want to install updated zaptel drivers and do 'service zaptel stop' and it fails. Yes, I know that 'amportal stop' fixes that, but it would be nice to have it all work automatically I guess that would be a change to the zaptel script in the stop case, but then if you're doing restart, it won't restart amportal I guess I'm making this too complicated...