I have Kaa Sandbox installed on AWS using default values 'localhost' and port as '27017' in log appender. Is this correct?
Now running the Java SDK for "My first kaa app" is giving the following error on macOS.
error message: INFO org.kaaproject.kaa.client.channel.impl.channels.DefaultOperationTcpChannel - Can't sync. Channel [default_operation_tcp_channel] is waiting for CONNACK message + KAASYNC message
Is this a problem with the IP address/port mentioned in log appender or is this a problem with mongoDB? Is mongoDB installed by default with Kaa Sandbox on AWS or is it missing and needs to be installed separately?
Error msg also includes: [main] INFO org.kaaproject.kaa.client.channel.impl.DefaultChannelManager - Failed to find operations service for channel [default_operation_tcp_channel] type TransportProtocolId [id=1456013202, version=1]
Solved it by using following steps: 1. Changed the ipaddress in the admin panel> general settings to my ec2 host IP address with port as 8080
Using SSH, logged into ec2, changed the user to user:kaa, password:kaa, used: sudo /usr/lib/kaa-sandbox/bin/change_kaa_host.sh host_ip
Downloaded the new SDK and created a new app. Data was received in mongoDB.
Related
At first time i deployed all hono services via minikube and helm chart on my local pc and i was able to use any services. But when i deploy hono services on remote server, i couldnt start Hono Command Line Client as a consumer from my local pc to remote server. i got this message;
09:22:42.438 [vert.x-eventloop-thread-0] WARN o.e.h.c.impl.ConnectionFactoryImpl - can't open connection to container [null] at [amqp://10.0.1.68:15671, role: unknown]: underlying connection was disconnected while opening AMQP connection
09:22:42.439 [vert.x-eventloop-thread-0] INFO o.e.h.client.impl.HonoConnectionImpl - max number of attempts [5] to re-connect to server [10.0.1.68:15671, role: unknown] have been made, giving up
09:22:42.452 [vert.x-eventloop-thread-0] ERROR org.eclipse.hono.cli.app.Receiver - Error occurred during initialization of receiver: failed to connect
unlike the eclipse-hono-dispatch-router-ext services, i can use other services like device registry and mqtt client adapter.Also i tried to run
java -jar hono-cli-*-exec.jar --hono.client.host=$AMQP_NETWORK_IP --hono.client.port=15672 --hono.client.username=consumer#HONO --hono.client.password=verysecret --spring.profiles.active=receiver --tenant.id=$MY_TENANT
this command line on remote server via ssh connection, i got same result.
Can anyone help me? if asked additional information, i will send it.
[![enter image description here][1]][1]
I have deployed node sailsjs app in gCloud and created mysql instance in gCloud but I am getting mysql connection error. I have configured below configuration in datastores object into production file like:
default: {
adapter: 'sails-mysql',
host: 'xx.xxx.xxx.xxx',
user:'root',
password:'xxxx',
database:'xxxx',
port: 3306
}
But I am getting this error each time:
Error: connect ETIMEDOUT
[1]: https://i.stack.imgur.com/UOTeY.png
According to the error message seems that the sails js app is not reaching the Cloud SQL server.
This could happen because the Public IP of your client machine is not allowed on the authorized networks of your Cloud SQL instance.
https://cloud.google.com/sql/docs/mysql/authorize-networks
Go to the Cloud SQL Instances page in the Google Cloud Console.
Click the instance name to open its Instance details page.
Select the Connections tab.
Click Add network.
In the Network field, enter the IP address or address range you want to allow connections from. ...
Optionally, enter a name for this entry.
Click Done.
"If you find yourself encountering a "Handshake inactivity timeout" error when your Sails app interacts with MySQL, you can increase the timeout using the connectTimeout option. This is usually only necessary when queries are running side-by-side with computationally expensive operations (for example, compiling client-side typescript files or running webpack during development)."
https://sailsjs.com/documentation/concepts/extending-sails/adapters/available-adapters
I have configured the Kaa Server on Ubuntu 14.04. I have chosen MongoDB as log appender. When i execute my SDK on the same ubuntu machine the data gets inserted into the Mongo Database. But when i try to execute the SDk on Intel Edison board it gives me Can't get CONNACK+KAASYNC message. I have followed all the rules for installing the Kaa Server.
the logs links are
https://drive.google.com/open?id=0Bx5TGFxgyDWbSkZUVVUzbkhqSTA
https://drive.google.com/open?id=0Bx5TGFxgyDWbalNBZkZBMmRtajQ
Have you opened up the ports used by Kaa. If not Check "Firewall rules configuration" in this installation guide "http://docs.kaaproject.org/display/KAA/Installation+guide"
I think earlier, your app sdk and the kaa server must be on the same machine and hence you faced no issue. Now since intel edison needs to communicate with your kaa host as an external device, you need to configure your kaa host admin and also your log appenders with the external IP address of your kaa host. Pls refer to a similar issue mentioned in this question
It looks like you need to re-configure the Kaa instance for the correct 'Kaa host' setting, then regenerate the Kaa SDK and rebuild your application for Intel Edison board with that new SDK.
The 'Kaa host' should match the IP address of the host the kaa-node
instance is running on and be accessible from the application side by that
IP address. This configuration must be done before the SDK for the
application is generated as the bootstrap IP addresses are embedded into
the SDK.
Please check your node network configuration and re-generate the SDK for
the application.
I have WAS MQ 7.1 Server installed in windows. My application running on unix is trying to connect to this server during which it gives the error "MQ Connect failed 2195" in the application logs. On debugging the code , i found it is while connecting to the q manager that it is throwing this error.
I tried to run a netstat on the MQ Server port no. and do a telnet to check if there is any connection being established . But I could not see any connection being established to the q manager .
The possible issues could be
1. Que Manager has not been started
2. Listener not started
3. Initiation queue not started or created or attached(usually optional depending on set up)
4. Listening to the wrong Port or IP
5. Firewall stopping traffic to Port or IP
6. Queue Manager not created on destination
7. Not authorized to Queue manager and/or channel and/or queue
8. Trial MQ copy expired.
9. Wrong Queue manager name
10. Wrong channel name or password or queue or queue type
Have done the following to check if it is working fine .
1. Tried to put a message from windows to the MQ Server which was successful.
2. Gave auth(setmqaut) permission to Request queue that was created.
3. There is no firewall between application and MQ Server.
4. Channel name , q manager , IP and port no.s are correct.
In my windows MQ Setup i have created the Server connection channel and Client connection Channel.
export the mqm lib to SHLIB_PATH.
Added the application user to mqm group and also the windows user through which I had created the MQ Server setup
Had copied the AMQCLCHL.TAB to the unix machine containing the client program.
exported MQCHLTAB to the table filename
exported MQCHLLIB to the path containing the table name
exported the MQSERVER=QMgrName/CHANNEL1/hostname from the client machine.
Please let me know if I am missing anything w.r.t connection of the application(in Unix) to the MQ Server(in Windows).
2195 is MQRC_UNEXPECTED_ERROR. It implies something that should not have happened, even if you set it up wrong. It may well be accompanied with an FDC file in the errors directory. You should raise a PMR with IBM Service.
I installed ejabberd on my linux mint kde. It installed correctly, I am able to use the admin interface in the browser at http://localhost:5280/admin/ to add users. In the nodes menu it shows me one node running as ejabberd#localhost. There is a virtual host called inspiron-n4050 which it created on its own. Now i registered 2 users from the admin interface lovesh#inspiron-n4050 and test#inspiron-n4050. Now from my IM client(Kopete) i created 2 jabber accounts with jabberIds lovesh#inspiron-n4050 and test#inspiron-n4050. But when i try to connect any of these it shows me error Connection problem with jabber server inspiron-n4050. There was a connection error: Remote closed connection
ejabberd is running because on the shell when i check ejabberdctl status it says
The node ejabberd#localhost is started with status: started
ejabberd 2.1.11 is running in that node
What is wrong?
Reinstalling ejabberd fixed the problem
I used this steps in pidgin xmpp. You can check out similar options on kopete.
Change proxy options to No Proxy
In Connection Security, Use encryption if available
Check allow plain text on unencrypted streams.
After this steps I am able to chat within two pidgin clients over a Intranet.
i noticed that the there is a distinction between username "host" and actual hostname:
https://www.linode.com/docs/applications/messaging/instant-messaging-services-with-ejabberd-on-ubuntu-12-04-precise-pangolin
i had to use these settings to get it to work:
username: username#localhost
hostname: www.theactualserver.com
port: 5222