Not able to start tacker server when tacker installed on compute node

I have installed tacker and ODL on the compute node (Bare metal) of my cloud environment. My deployment is successful via OpNFV (Fuel).

Now when i try to start the tacker server from the compute node by using the below command it fails with an error as mentioned below:

COMMAND:
------------------
python /usr/bin/tacker-server --config-file /etc/tacker/tacker.conf --log-file /var/log/tacker/tacker.log

Error:
---------
root@node-59:/etc/tacker# python /usr/bin/tacker-server --config-file /etc/tacker/tacker.conf --log-file /var/log/tacker/tacker.log
No handlers could be found for logger "oslo_config.cfg"
2017-02-09 21:59:49.129 156739 WARNING oslo_config.cfg [-] Option "rabbit_ha_queues" from group "DEFAULT" is deprecated. Use option "rabbit_ha_queues" from group "oslo_messaging_rabbit".
2017-02-09 21:59:49.129 156739 WARNING oslo_config.cfg [-] Option "rabbit_hosts" from group "DEFAULT" is deprecated. Use option "rabbit_hosts" from group "oslo_messaging_rabbit".
2017-02-09 21:59:49.130 156739 WARNING oslo_config.cfg [-] Option "rabbit_password" from group "DEFAULT" is deprecated. Use option "rabbit_password" from group "oslo_messaging_rabbit".
2017-02-09 21:59:49.130 156739 WARNING oslo_config.cfg [-] Option "rabbit_userid" from group "DEFAULT" is deprecated. Use option "rabbit_userid" from group "oslo_messaging_rabbit".
2017-02-09 21:59:49.130 156739 WARNING oslo_config.cfg [-] Option "rabbit_virtual_host" from group "DEFAULT" is deprecated. Use option "rabbit_virtual_host" from group "oslo_messaging_rabbit".
2017-02-09 21:59:49.130 156739 WARNING oslo_config.cfg [-] Option "lock_path" from group "DEFAULT" is deprecated. Use option "lock_path" from group "oslo_concurrency".
2017-02-09 21:59:50.125 156739 WARNING oslo_config.cfg [-] Option "auth_plugin" from group "keystone_authtoken" is deprecated. Use option "auth_type" from group "keystone_authtoken".
2017-02-09 21:59:50.126 156739 WARNING oslo_config.cfg [-] Option "username" from group "keystone_authtoken" is deprecated. Use option "user-name" from group "keystone_authtoken".
2017-02-09 21:59:50.127 156739 WARNING keystonemiddleware.auth_token [-] signing_dir is not owned by 0
2017-02-09 22:00:20.178 156739 ERROR tacker.service [-] Unrecoverable error: please check log for details.
2017-02-09 22:00:20.178 156739 TRACE tacker.service Traceback (most recent call last):
2017-02-09 22:00:20.178 156739 TRACE tacker.service File "/usr/lib/python2.7/dist-packages/tacker/service.py", line 95, in serve_wsgi
2017-02-09 22:00:20.178 156739 TRACE tacker.service service.start()
2017-02-09 22:00:20.178 156739 TRACE tacker.service File "/usr/lib/python2.7/dist-packages/tacker/service.py", line 66, in start
2017-02-09 22:00:20.178 156739 TRACE tacker.service self.wsgi_app = _run_wsgi(self.app_name)
2017-02-09 22:00:20.178 156739 TRACE tacker.service File "/usr/lib/python2.7/dist-packages/tacker/service.py", line 111, in _run_wsgi
2017-02-09 22:00:20.178 156739 TRACE tacker.service workers=cfg.CONF.api_workers)
2017-02-09 22:00:20.178 156739 TRACE tacker.service File "/usr/lib/python2.7/dist-packages/tacker/wsgi.py", line 209, in start
2017-02-09 22:00:20.178 156739 TRACE tacker.service backlog=backlog)
2017-02-09 22:00:20.178 156739 TRACE tacker.service File "/usr/lib/python2.7/dist-packages/tacker/wsgi.py", line 188, in _get_socket
2017-02-09 22:00:20.178 156739 TRACE tacker.service 'time': CONF.retry_until_window})
2017-02-09 22:00:20.178 156739 TRACE tacker.service RuntimeError: Could not bind to 192.168.8.3:8889 after trying for 30 seconds
2017-02-09 22:00:20.178 156739 TRACE tacker.service
ERROR: Could not bind to 192.168.8.3:8889 after trying for 30 seconds

Any help would be highly appreciable.

Regards
Anurag.