[App_rpt-users] Zaptel timer problem after bootup - 5 minute delay RESOLVED

[Don Hackler]

I downloaded a fresh copy of the ACID distribution and burned a new CD.
Did a fresh install; everything came up immediately and is now working as expected.

I suspect I had some corruption in the original disk or image file. 





On Apr 22, 2012, at 9:35 PM, Don Hackler wrote:

> Still working on getting a new system running...
> 
> When I reboot the server, asterisk exits and restarts every 3-4 seconds for 5 minutes.
> The error message is :
> "Asterisk has detected a problem with your Zaptel configuration and will shutdown for your protection. You have options:  You only have to compile Zaptel support into Asterisk if you need it. One option is to recompile without Zaptel support. You only have to load Zaptel drivers if you want to take advantage of Zaptel services. One option is to unload zaptel modules if you don't need them. If you need Zaptel services, you must correctly configure Zaptel."
> 
> 
> This message is coming from asterisk.c which is attempting to open /dev/zap/timer using ast_wait_for_input() with a 3 second timeout.
> The function is returning zero for almost exactly five minutes, when it finally returns non-zero and asterisk starts up.
> 
> Any ideas on what's going on here?
> 
> 
> Other potential clues:
> all the /dev/zap/* entries are owned by root, but the udev zap configuration seems to imply they should be owned by asterisk.
> There is no asterisk user or group on the system.
> 
> There is no /dev/zap/transcode entry.
> 
>