[bind10-dev] Error: unexpected answer from ConfigManager

[zhanglikun]

Hi Jelte, I find you have changed the command name cmdctl sending to
configmanager,
Could you help to have a look this bug?

BTW, we should find one better way to avoid hardcode command here.

"get_commands_spec"
"get_module_spec"
'get_config'

> 
> >From trunk (including revision 936). Removed the prefix and did a clean
> install. And ran bind10 from there:
> 
> t1:trunk$ /home/reed/opt/bind10/sbin/bind10 --verbose
> BIND 10 v20091030 (Paving the DNS Parking Lot)
> Starting msgq using port 9912
> Started msgq (PID 29965)
> Starting b10-cfgmgr
> Started b10-cfgmgr (PID 29500)
> [XX] starting ccsession
> RETURNING: <class 'isc.config.module_spec.ModuleSpec'>
> [XX] handling new config:
> {}
> [XX] ccsession started
> Starting b10-auth  on port 5300
> Started b10-auth (PID 13651)
> Starting b10-cmdctl on port 8080
> Started b10-cmdctl (PID 29044)
> b10-cmdctl module is starting on :localhost port:8080
> b10-cmdctl send command 'get_commands_spec' to ConfigManager
> My local name is:  4b842c13_5 at t1.m.reedmedia.net
> b10-cmdctl send command 'get_module_spec' to ConfigManager
> Error: unexpected answer from ConfigManager
> b10-cmdctl send command 'get_config' to ConfigManager
> Error: unexpected answer from ConfigManager
> [XX] got config:
> {"result": [ 0, {} ]}
> handleConfigUpdate {}
> handleConfigUpdate {}
> [XX] auth: new config {}
> end handleConfigUpdate {}
> Server started.
> ^Cexit http server
> Received SIGINT.
> Stopping the server.
> Process b10-cfgmgr (PID 29500) died.
> Process msgq (PID 29965) died.
> The msgq process died, shutting down.
> Process b10-cmdctl (PID 29044) died.
> Process b10-auth (PID 13651) died.
> All processes ended, server done.
> https://lists.isc.org/mailman/listinfo/bind10-dev