- Expediere
- 27 august 2026 la 18:23 UTC
- Autor
- Kamo
- Comite
- 53dd494
The stub kazoo.conf.xml 2600Hz ship has no definitions, event-handlers or fetch-handlers sections. mod_kazoo says as much and then faults in its own config thread — the kernel log names it: "traps: erl/config[...] general protection fault ... in libc.so.6". It does this with ecallmgr detached entirely, which rules out fetch, protocol and version skew. Shipping the 60KB document ecallmgr generates as the local config fixes it. Also records that the previous explanation was wrong. The malformed event profile was real, and cleaning it changed nothing: the five "(null)" warnings persisted and all 43 events were verifiably in the built profile. The correlation was a coincidence that cost a build cycle, while the kernel log had named the faulting thread in one line all along. Adds an honest status for the call path: kz_contact answers subscriber_absent even though Crossbar reports the device registered, and originating crashes a different thread (pool/session) while idle is stable.