allofmex
commented
5 years ago Bish-bosh crashing when receive message in topic
Same with me:
bish-bosh: INFO: Using backend 'openssl' (on path '/usr/bin/openssl') with port '26944'
bish-bosh: DEBUG: Passing options to backend 'openssl' using '/usr/bin/openssl' as 's_client -bugs -quiet -state -verify 5 -connect farmer.cloudmqtt.com:26944 -no_ticket' (please note spaces ARE handled correctly)
bish-bosh: DEBUG: bishbosh_connection_clientPid is 22308
bish-bosh: INFO: Using stdbuf (stdbuf) with od (od)
bish-bosh: DEBUG: bishbosh_connection_hexConversionPid is 22320
verify depth is 5
bish-bosh: INFO: Writing CONNECT
SSL_connect:before/connect initialization
SSL_connect:SSLv2/v3 write client hello A
bish-bosh: DEBUG: bishbosh_connection_processLoopPid is 22325
SSL_connect:unknown state
bish-bosh: DEBUG: Our Pid is 21975
depth=3 C = SE, O = AddTrust AB, OU = AddTrust External TTP Network, CN = AddTrust External CA Root
verify return:1
depth=2 C = GB, ST = Greater Manchester, L = Salford, O = COMODO CA Limited, CN = COMODO RSA Certification Authority
verify return:1
depth=1 C = GB, ST = Greater Manchester, L = Salford, O = COMODO CA Limited, CN = COMODO RSA Domain Validation Secure Server CA
verify return:1
depth=0 OU = Domain Control Validated, OU = PositiveSSbish-bosh: NOTICE: Terminate bish-bosh with kill 21975
L Wildcard, CN = *.cloudmqtt.com
verify return:1
SSL_connect:unknown state
SSL_connect:unknown state
SSL_connect:unknown state
SSL_connect:unknown state
SSL_connect:unknown state
SSL_connect:unknown state
SSL_connect:unknown state
SSL_connect:unknown state
bish-bosh: INFO: Received valid CONNACK
bish-bosh: DEBUG: bishbosh_connection_handler_SUBACK(packetIdentifier=1, returnCodeCount=3, returnCodes=0
bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times
bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times
bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times
bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times
bish-bosh: INFO: Writing PINGREQ
bish-bosh: INFO: Received valid PINGRESP
bish-bosh: DEBUG: bishbosh_connection_handler_PINGRESP()
bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times
bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times
bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times
bish-bosh: INFO: Writing PINGREQ
bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times
bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times
SSL3 alert read:warning:close notify
SSL3 alert write:warning:close notify
bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times
bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times
root@***:/***/bish-bosh# bish-bosh: INFO: processLoop terminating because of signal
bish-bosh: INFO: Writing DISCONNECT
/***/bish-bosh/lib/shellfire/bishbosh/connection/write/DISCONNECT.functions: line 8: printf: write error: Broken pipe
bish-bosh: WARN: Could not write DISCONNECT, probably because the network connection has already died (often due to nc handling SIGINT / Ctrl-C to a process group too quickly)Tried different backends, tls/none, bash/dash/sh... all the same
Raspbian GNU/Linux 8.0 (jessie)
4.4.50
Hello, i have this issue on Debian 9. Bish-bosh crashing when receive message in topic.
./bish-bosh --verbose 3 -- /root/bish-bosh/bish-bosh.cfg bish-bosh: INFO: Using backend 'ncDebianTraditional' (on path '/bin/nc') with port '1883' bish-bosh: DEBUG: Passing options to backend 'ncDebianTraditional' using '/bin/nc' as '-w 30 -v -v 192.168.98.5 1883' (please note spaces ARE handled correctly) bish-bosh: DEBUG: bishbosh_connection_clientPid is 10280 bish-bosh: INFO: Using stdbuf (stdbuf) with od (od) bish-bosh: DEBUG: bishbosh_connection_hexConversionPid is 10291 iot [192.168.98.5] 1883 (?) open bish-bosh: INFO: Writing CONNECT bish-bosh: DEBUG: bishbosh_connection_processLoopPid is 10296 bish-bosh: DEBUG: bishbosh_connection_processingLoopReadInterrupterPid is 10306 bish-bosh: DEBUG: Our Pid is 9923 bish-bosh: NOTICE: Terminate bish-bosh with kill 9923 bish-bosh: INFO: Received valid CONNACK bish-bosh: DEBUG: bishbosh_connection_handler_SUBACK(packetIdentifier=1, returnCodeCount=1, returnCodes=0) bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times sent 414, rcvd 49 bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times root@iot:~/bish-bosh# bish-bosh: INFO: processLoop terminating because of signal bish-bosh: DEBUG: bishbosh_connection_handler_noControlPacketsRead() 10 times bish-bosh: INFO: Writing DISCONNECTIf i comment out
bishbosh_connection_handler_PUBLISH(), then i see messages received.bish-bosh: DEBUG: bishbosh_connection_handler_PUBLISH(packetIdentifier=qos0, retain=0, QoS=0, dup=0, topicLength=15, topicName=, topicNameFilePath=/tmp/bish-bosh.u0sYp8RL8Imu/session/our-packet-identifiers/qos0/topic-name, messageLength=1, messageFilePath=/tmp/bish-bosh.u0sYp8RL8Imu/session/our-packet-identifiers/qos0/message-received)