[Home]

Summary:ASTERISK-03456: when stop zaptel, produce a EIP message and don't unload modules
Reporter:Fernando Romo (el_pop)Labels:
Date Opened:2005-02-09 01:05:25.000-0600Date Closed:2011-06-07 14:10:44
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) log_messagges.txt
Description:When try to stop zaptel services send the message "FATAL: Module zaptel is in use." with asterisk stoped before.

****** ADDITIONAL INFORMATION ******

One week ago, i note the CVS head of zaptel change, i recompile the zaptel drivers and test in 4 machines: two with FC3 with kernel 2.6.10, one with FC2 with kernel 2.6.8-1.521, and another with FC2 with kernel 2.6.9.

3 machines has TDM400 instaled and the other has 2 TDM400 and one E100p Card and the behaivor is the same.

in first place a think is a problem with the module order in load and unload sequence in /etc/init.d/zaptel, then i check the MODULES string to check order and test deleting the modules without purpose.

Then when i reboot the servers, i start to notice in the console a lot of messages about the problem with the unload of zaptel modules.

i try to stop and start the services many times and note the message. The load of a zaptel drivers affect the asterisk (start and stop) sequence. in random the * service can start or not.

I feel is not a configuration problem, and cand isolate a log message file (log_messagges.txt) with teh EIP events.
Comments:By: Mark Spencer (markster) 2005-02-09 09:14:30.000-0600

As this involves Digium hardware, please pursue this through Digium technical support and if you are unable to get a satisfactory resolution, please contact me directly.