node-red error: "Error stopping node: Error: [BaseClient:disconnect] Client is not connected" AND "Error: Connection refused: Not authorized" - ibm-mobilefirst

I am following this tutorial on how to send a picture taken from the pi camera to the CLoudant NoSQL database on Bluemix.
"There are 3 node-red flows in total. The Process Doorbell flow (on the raspberry pi) should send an IBM IoT visitorAlert event message to Node-RED on Bluemix which should, in turn, send an IBM IoT sendPicture command message back to Node-RED on Raspberry Pi. This will eventually create a Base64 encoded image string, package it up with the filename, length and status into a payload that gets sent to Cloudant in Bluemix by the insertPicture node. See if it worked by going to the Bluemix Cloudant dashboard."
I created the flows on node-Red, but am getting this error on the node-red in the pi:
"Error stopping node: Error: [BaseClient:disconnect] Client is not
connected"
I am getting this error on the node-red in Bluemix:
"Error: Connection refused: Not authorized"
What could be the issue?

Related

Getting readiness probe failed: dial tcp <IP>:5672 connect: connection refused error in rabbitmq-cluster pods

I am new to rabbitmq and would appreciate help in the issue I am facing.
I have deployed rabbitmq using the rabbitmq cluster k8s operator on openshift which is hosted on Azure. (This is the guide I referred to deploy the operator).
The operator and cluster is up and running, also able to access the management UI on localhost:15672.
But when I describe the pod, it shows the warning of readiness probe failed:
dial tcp <IP>:5672 connect: connection refused
Due to this, when I try to run the rabbitmq hello world tutorial, it fails with the error:
connect ETIMEDOUT 172.30.69.51:5672
errno: -4039
code: 'ETIMEDOUT'
syscall:'connect'
address: 172.30.69.51
port:5672
(172.30.69.51 is the clusterIP)
From the management UI, I am able to create new exchange, queue and binding and send & publish msgs.
PS. apologies if the conversation format is incorrect, pls feel free to correct me and I'll take care from next time. Thank you.

IOT-HUB device node.js sdk message.on method is not working

Once the Event will be sent to Cloud IOT-HUB from Device thru Device Node.JS sdk, once message is received on IOT-Hub same needs to be acknowledged to nodejs.
We found couple of reference regarding the same and the below mentioned method should work for the same.
client.on('message', function(msg) {
console.log('Received Message from IoT Hub: ' + msg.data);
client.complete(msg, printResultFor('completed'));
// We are done here
});
But this method is not triggering at all in any circumstance.
Please suggest.
Your description of the question and your code lines are inconsistent.
Once the Event will be sent to Cloud IOT-HUB from Device thru Device
Node.JS sdk, once message is received on IOT-Hub same needs to be
acknowledged to nodejs.
It is talking about D2C messages received by IoT Hub.
client.on('message', function(msg) {
console.log('Received Message from IoT Hub: ' + msg.data);
client.complete(msg, printResultFor('completed'));
// We are done here
});
But it is talking about receiving C2D messages on device client end.
To trigger this method client.on you need send a C2D message from IoT Hub server end. For testing purpose, you can simply send a C2D message either from Azure Portal or IoT Hub Device Explorer tool:
If you run this sample: simple_sample_device.js you will receive the D2C message like this(I add this line console.log('client.on triggered!!!'); to the sample code):

MobileFirst - WLClientLogReceiver not writing any client logs in SystemOut.log

IBM MobileFirst Server Version:7.0.0.0020150312-0731
I have WLClientLogReceiver adapter with a procedure "log" to receive the client logs via WL.Logger.send() method.
In device client log, i see the message "Client Logs successfully sent to server"
During this, i do see the below message in server.
[6/17/15 12:12:40:768 CDT] 0000009c ProjectManage I com.worklight.core.jmx.ProjectManagementMXBeanImpl logTransactionDetails FWLSE0275I: Starting transaction with ID 58 for 'commit'. [project mfgulfconsole]
I have a APAR opened for Operations Analytics not loading data over SSL in WAS full profile clustered environment. So i am trying to find the client logs that has been pushed to server in my servers SystemOut.log. No client logs is writing on this file.
I even tried with HPEL Mode of log and trace the text log, nothing writes in this file for WL.Logger.send() call.
Am i searching for the logs in wrong files. Please advice.
AFAIK the analytics data is not stored in the MobileFirst Server logs... they go to the Analytics server and are stored in the ElasticSearch database.

MobileFirst 7.0 Operational Analytics - No Data loaded

I configured the Operational analytics for the MobileFirst 7.0
Configured the JDNI as per the IBM document and created client side log profile in Admin Operation Console. But it always shows 0 data. Not load any client logs / server logs.
Log receiver adapter has been built and deployed in the operation console. Client has the method to push the logs to server via WL.Logger.send(). I see the client log console and logcat, the logs has been pushed to server. In server log also, i see the invoke success log for logReceiverAdapter call.
In Operation Analytics console JNDI, the Queue and Size has been set to 1.
This was identified to be a defect in the product and will be resolved as part of APAR #PI42509 WHEN USING SSL ON WEBSPHERE THE ANALYTICS DATA IS NOT RECEIVED BY THE ANALYTICS SERVER BECAUSE OF THE SSL CONFIGURATION USED
There is no local workaround.
Continue to follow up on the issue in the PMR (support ticket) you have opened.

IBM Worklight server not working after update 6.3

IBM Worklight server not working after update 6.3. The error states Server MobileFirst Development Server failed to start.
Any thoughts about this error? Added a image for reference.
On console, i am getting the error
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750]
Transport already in use: could you have an old copy of the server still running. Unless I can spot the process and kill it I'd restart my machine.