I got an error when I using the AWS IoT Embedded C SDK to run on Raspberry Pi 3, It will be appreciate if someone can help.. thanks!
below the info. in my aws_iot_config.h
define AWS_IOT_MQTT_HOST "a3osulxxxxxxxx.iot.us-east-1.amazonaws.com"
define AWS_IOT_MQTT_PORT 8883
define AWS_IOT_MQTT_CLIENT_ID "CsPi6" <br/>
define AWS_IOT_MY_THING_NAME "CsPi6"
define AWS_IOT_ROOT_CA_FILENAME "root-CA.pem"
define AWS_IOT_CERTIFICATE_FILENAME "certificate.pem.crt"
define AWS_IOT_PRIVATE_KEY_FILENAME "private.pem.key"
below the output :
Connecting...
ERROR: iot_tls_connect L#143 TCP Connection error
ERROR: main L#173 Error(-3) connecting to a3osulxxxxxxxx.iot.us-east-1.amazonaws.com:8883
Subscribing...
ERROR: main L#195 Error subscribing
ERROR: main L#235 An error occurred in the loop.
Beside, I tried to ping the endpoint "a3osulxxxxxxxx.iot.us-east-1.amazonaws.com" by using Rpi, it failed. But it success if I use the Mac terminal to ping.
pi#raspberrypi:~ $ ping a3osulxxxxxxxx.iot.us-east-1.amazonaws.com<br/>
ping: unknown host a3osulxxxxxxxx.iot.us-east-1.amazonaws.com<br/>
Related
When I run e2e test suites on VS code getting an unusual error - Error: EADDRINUSE connect EADDRINUSE 127.0.0.1:50596 don't know how to solve this, its happening to all instance and failing all test cases with same error. when I debug this in dev tools getting this error in console log (node:16612) [DEP0005] Deprecation Warning: Buffer() is deprecated due to security and usability issues. Please use the buffer. From() methods instead.
(Use Code --trace-deprecation … to show where the warning was created)
Node version >v11.15.0**
NPM. version >6.7.0
Chrome browser
This error Error: EADDRINUSE connect EADDRINUSE 127.0.0.1:50596 means the address 127.0.0.1:50596 is already used.
You can find out what's using the port 50596, and then kill the process (see https://www.printsupportcenter.com/hc/en-us/articles/115003386949-Determine-which-program-uses-or-blocks-a-port):
Windows:
netstat -ano -p tcp | find "50596"
Linux/Mac:
sudo netstat -ano -p tcp | grep ":50596"
These previous commands will give you the Process IDentifier (PID), which you can then use to kill your process:
Windows:
taskkill /PID <pid_number>
Linux/Mac:
kill <pid_number>
As if right now I am in a bit of a rush to get an answer to my problem. The model has been trained and the server works locally with the NN running in the background, but on the server we get the following error message:
2020-04-08 11:54:15.787274: I tensorflow/core/platform/profile_utils/cpu_utils.cc:94] CPU Frequency: 2799865000 Hz
2020-04-08 11:54:15.787801: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x4b5ca00 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2020-04-08 11:54:15.787830: I tensorflow/compiler/xla/service/service.cc:176] StreamExecutor device (0): Host, Default Version
terminate called after throwing an instance of 'std::system_error'
what(): Resource temporarily unavailable
It seems that the server host doesn't like the fact that Tensorflow is trying to log the following error/warning message:
2020-04-08 11:53:42.453164: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to
use: AVX2
Is there a way in JS to disable these error logs so we can run the trained model on the server? Thanks in advance!
How do I use NMSSH in Swift?
When I execute the code below, I get these messages in my debug console:
2019-11-14 19:15:53.830479+0100 unLock[49480:480479] NMSSH: Start 192.168.178.97 resolution
2019-11-14 19:15:53.832950+0100 unLock[49480:480481] NMSSH: Socket connection to 192.168.178.97 on port 44 failed with reason -1, trying next address...
2019-11-14 19:15:53.833005+0100 unLock[49480:480481] NMSSH: Failure establishing socket connection
2019-11-14 19:15:53.833047+0100 unLock[49480:480481] NMSSH: Disconnected
The code:
let session = NMSSHSession(host: "192.168.178.97:44", andUsername: "root")
session.connect()
if session.isConnected == true{
session.authenticate(byPassword: "alpine")
//if session.isAuthorized == true {
session.channel.execute("killall SpringBoard", error: nil)
print("killed Springboard")
//}
}
What I've done is allowing arbitrary Loads in App Transport Security because I thought the problem may be that the ssh server isn't HTTPS, but it did not help. The fact that I try to SSH into an iPhone isn't the cause Haswell, as I tried it with a Raspberry Pi, same result. Also don't mind port 44 as it is the correct port for checkra1n.
You can see similar type problem here.
How to use NMSSH in swift
Also Read the Readme file for NMSSH and setup this framework using podfile.
pod 'NMSSH'
Read Documentation here
https://github.com/NMSSH/NMSSH
I am trying to get minishift runnin on my machine (Windows 10) with Virtualbox 5.1.24.
Minishift version: 1.0.0+4f8cb6d
CDK Version: 3.0.0-2
Starting minishift gives me the following:
C:\>minishift start --vm-driver virtualbox
Starting local OpenShift cluster using 'virtualbox' hypervisor...
E0727 18:34:21.682796 17204 start.go:176] Error starting the VM: Error
creating new host: Error attempting to get plugin server address for RPC:
Failed to dial the plugin server in 10s. Retrying.
E0727 18:34:31.740746 17204 start.go:176] Error starting the VM: Error
creating new host: Error attempting to get plugin server address for RPC:
Failed to dial the plugin server in 10s. Retrying.
E0727 18:34:41.770667 17204 start.go:176] Error starting the VM: Error
creating new host: Error attempting to get plugin server address for RPC:
Failed to dial the plugin server in 10s. Retrying.
Error starting the VM: Error creating new host: Error attempting to get
plugin server address for RPC: Failed to dial the plugin server in 10s
Error creating new host: Error attempting to get plugin server address for
RPC: Failed to dial the plugin server in 10s
Error creating new host: Error attempting to get plugin server address for
RPC: Failed to dial the plugin server in 10s
I read the comments that it needs to run from the C:\drive but it looks like this did not fix the problem. I am happy about any hints how to fix this. If there is any additional information you need, just let me know.
Sounds like you got it working.
I usually encourage folks who are having trouble starting their minishift VMs to try the following:
Find your preferred virtualization provider from the list of available options
Install the appropriate driver plugin for your system
Persist your VM provider configuration: minishift config set vm-driver virualbox
Chef Server Version : chef-server 12.11.1
knife softlayer server create
--image-id ${image_id}
--ssh-keys ${ssh_keys}
--hostname $node_name
--network-interface-speed 100
--domain $domain_name
--cores ${cores}
--ram ${ram}
--datacenter ${datacenter}
--node-name $node_name
--vlan $public_vlan
--private-vlan $private_vlan
--use-private-network
-x root
-i $USER_HOME/.ssh/id_rsa -VV
Client Output
Launching SoftLayer VM, this may take a few minutes.
............................................................................
............................................................................
................
After 6 minutes it throws this error
ERROR: Excon::Error::Socket: Connection reset by peer (Errno::ECONNRESET)
ERROR: Excon::Error::Socket: Connection reset by peer (Errno::ECONNRESET)
The Softlayer's API has this issue where sometimes the server resets the connection to the client. Currently they are working on a fix but there is not an ETA. The issue showed up long time ago. I only can recommend to try catch the error and try again.