The console problems and fixes

[khelle]

At the moment the console server is bugged. Sometimes it stops working and needs restart to fix the most common problems, but sometimes the message routing fails or it does not clean after itself.

Right now, the best solution for this problem is not to use console, but stick to alternative start method, which in default configuration is:

$> php ./data/autorun/kraken.process undefined Main Main

This is the logic that works underneath project:create command and it is equal in use. If there are any subprocesses or subthreads in Main, they will also be fired. The only con of this approach is, that you will not be able to use console command, therefore when shuting down the project you will need to kill all processes manually.

This is very urgent problem, and should be prioritized to be done for the release of v0.4

[absiddiqueLive]

Run the following command in Ubuntu

$ php kraken.server
#active the below port
tcp        0      0 127.0.0.1:2060          0.0.0.0:*               LISTEN      6895/php

$ php kraken project:create
#active the below port
tcp        0      0 127.0.0.1:2061          0.0.0.0:*               LISTEN      6906/php7.0

If those port are not close properly then some error happen.

# Why kraken-php needs 3 ports ? (2060,2061,6080)

[khelle]

• 2060 is an entry point used by console server to enable remote use of a console client and is the main communication bus between the two.
• 2061 will be removed in upcoming release, and replacew with unix:// socket, because it does not need to be TCP.
• 6080 is not a port used by framework. It is only used in demo-chat application as HTTP server port.