No starts server in CentOS 6.7

[Фомин Фомин]

Help me.
I downloaded version 0.8.0. I compiled. the latest version. Set the script:

python kbengine/kbe/tools/server/install/installer.py install

In the console writes:

[kbe@localhost ~]$ cd $KBE_ROOT/assets
bash: cd: /root/kbengine//assets: Отказано в доступе
[kbe@localhost ~]$ su
Пароль: 
[root@localhost kbe]# cd $KBE_ROOT/assets
[root@localhost assets]# sh start_server.sh
KBE_ROOT = "/root/kbengine"
KBE_RES_PATH = "/root/kbengine/kbe/res/:/root/kbengine/assets:/root/kbengine/assets/res/:/root/kbengine/assets/scripts/"
KBE_BIN_PATH = "/root/kbengine/kbe/bin/server/"
[root@localhost assets]# log4cxx: setFile(logs/loginapp.8129652375332859700.2016-02-04.log,true) call failed.
log4cxx: IO Exception : status code = 2
log4cxx: No output stream or file set for the appender named [R].
log4cxx: setFile(logs/cellappmgr.2016-02-04.log,true) call failed.
log4cxx: IO Exception : status code = 2
log4cxx: No output stream or file set for the appender named [R].
[ERROR]: BundleBroadcast::receive: failed! It can be caused by the firewall, the broadcastaddr, etc.Maybe broadcastaddr is not a LAN ADDR, or the Machine process is not running.
[ERROR]: Machine::findBroadcastInterface: Broadcast discovery [255.255.255.255] not a valid interface. available interfaces:	[127.0.0.1, 192.168.1.36, ]
[ERROR]: Machine::initNetwork: Failed to determine default broadcast interface. Make sure that your broadcast route is set correctly. e.g. /sbin/ip route add broadcast 255.255.255.255 dev eth0
[ERROR]: app::initialize() is error!
[ERROR]: DBInterfaceMysql::attach: mysql_errno=2002, mysql_error=Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
[ERROR]: DBUtil::createInterface: attach to database failed!
	dbinterface=0xbfa3dd1c
	args=interface=default, dbtype=mysql, ip=localhost, port=3306, currdatabase=kbe, username=kbe, connected=no.

[ERROR]: Dbmgr::initDB(): can't create dbInterface!
[ERROR]: app::initialize() is error!
[ERROR]: BundleBroadcast::receive: failed! It can be caused by the firewall, the broadcastaddr, etc.Maybe broadcastaddr is not a LAN ADDR, or the Machine process is not running.
[ERROR]: Components::findComponents: receive error!
[ERROR]: BundleBroadcast::receive: failed! It can be caused by the firewall, the broadcastaddr, etc.Maybe broadcastaddr is not a LAN ADDR, or the Machine process is not running.
[ERROR]: Components::findComponents: receive error!
[ERROR]: BundleBroadcast::receive: failed! It can be caused by the firewall, the broadcastaddr, etc.Maybe broadcastaddr is not a LAN ADDR, or the Machine process is not running.
[ERROR]: Components::findComponents: receive error!
[ERROR]: BundleBroadcast::receive: failed! It can be caused by the firewall, the broadcastaddr, etc.Maybe broadcastaddr is not a LAN ADDR, or the Machine process is not running.
[ERROR]: Components::findComponents: receive error!
[ERROR]: BundleBroadcast::receive: failed! It can be caused by the firewall, the broadcastaddr, etc.Maybe broadcastaddr is not a LAN ADDR, or the Machine process is not running.
[ERROR]: Components::findComponents: receive error!
[ERROR]: BundleBroadcast::receive: failed! It can be caused by the firewall, the broadcastaddr, etc.Maybe broadcastaddr is not a LAN ADDR, or the Machine process is not running.
[ERROR]: Components::findComponents: receive error!
[ERROR]: BundleBroadcast::receive: failed! It can be caused by the firewall, the broadcastaddr, etc.Maybe broadcastaddr is not a LAN ADDR, or the Machine process is not running.

[kbengine]

1: chmod -R 755 kbengine

2: Check database settings

3: service iptables stop(test)

在 2016年2月4日星期四 UTC+8下午8:40:59，Фомин Фомин写道：