Tony Graziano wrote: > Similar problem here, but ConfigAgent was disabled. I dropped my > database and recreated, still no joy. >
Probably not the same issue: if you can log in that means that sipXconfig is running. ConfigAgent is really only used for real time ACD stats. It probably was disabled since ACD role is not enabled by default. > I ran sipxproc --start ConfigAgent and was able to log in but > ConfigAgent status changed to "ConfigurationMismatch", I upgraded again > via YUM, same issue. I confirmed the DNS works in all cases (manually > via dig lookup at the console, the system is a test system with named > running and confired), but DNS says "Unkonwn" in preflight, when it > should pass and had passed before upgrading via. Martin complained some time ago that his DNS tests "got stuck"... Maybe you are seeing the same thing. > > Is this a known issue or am I the only one experiencing it? I can start > from scratch, but don;t want to do so if the issue needs to be looked at > more closely. > What's the revision and what exactly is not working now? D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
