I have Jmeter in local windows & application is running in VM Linux.
Note: JMeter is not available in VM machine.
I need to establish connection to VM machine & thereby publish the data in MQTT broker in VM machine.
for VM connection, I have done below changes:
jmeter.properties: I have included:
remote_hosts=XX.XX.XXX.XX:XX
user.properties, i have included:
server.rmi.ssl.disable=true
And when i perform remote run, i could see the error:
"non-jrmp server at remote endpoint"
Am not sure, do I miss any points.
You don't understand the concept of Distributed testing, defining remote_hosts property is needed when you need to connect JMeter to another JMeter so 2 (or more) JMeter instances would act as a single load generator, people normally do it when single JMeter cannot generate the required load because machine is not powerful enough.
If you have JMeter installed on your Windows machine and MQTT broker is running on Linux machine just install MQTT Protocol Support plugin using JMeter Plugins Manager:
once done you will have MQTT Connect sampler where you will be able to configure your Linux machine IP address and port in order to establish connection with it:
More information: Testing the MQTT Messaging Broker for IoT - A Guide
Related
I recently wrote an echoserver / echoclient program in C for the online class I'm taking (Graduate Introduction to Operating Systems, here). I was able to complete it with the help of (and modification from Beej's Network guide (here). I can run it just fine on my Ubuntu 20.04 virtual machine, running on my Windows 10 laptop. However, I'm trying to run the echoserver on an AWS Linux instance and the echoclient from the Ubuntu VM, as my end goal is building a client program that has a central server data repository. However, I'm running into issues where I start the echoserver C code on the AWS EC2 instance through SSH-ing by PuTTy, then I run the echoclient on the Ubuntu VM, but it can't connect (the error I receive on the client side is that it failed the connect phase of the socket call). I've tried the following steps:
Editing the inbound rules of the security configuration of the EC2 instance to allow for 'All TCP' connections from the IP address that comes up when I run curl ifconfig.me on my Ubuntu machine
Changing the network setting of my Ubuntu VM from NAT to Bridged Network
Testing port access by telnet <AWS Public IP> <PortNo> - which led to "Connection Refused" error
Ensuring that my outgoing ports aren't blocked by following these instructions
I've looked through the AWS pages (here) as well as multiple developer / SO threads (best one I found so far here) and I just can't seem to figure out out. If anyone could help me out, I'd really appreciate it. I'm happy to post my server & client code if that would be of help.
Figured it out: was missing the following line of code in my server.
hints.ai_flags = AI_PASSIVE;
I would like to set up an apache spark Standalone cluster using two different computers (windows 10) of the same wifi network as slaves.
I can successfully set up the master using Windows bash(linux subsystem) and connect a slave from the same machine.
The problem is when I'm trying to connect a slave from a different machine (same wifi) using the local ip of the master. I even temporarily opened up all the ports of both the machines and mamaged to view the spark ui from the slave machine using the local ip of the master. But still trying to set up a slave on master-local-ip:7077 didn't work.
I believe that the correct way is to use password-less ssh between them but I'm not sure how to configure it for local ip addresses using the windows bash. I tried to create the key and when I executed ssh-copy-id the connection refused.
Any suggestions?
openstack runs on ip address of the machine but chef server also demands to run on the same ip address on the web console. So what changes to be made to resolve this conflict on the linux os. What configuration files are required to be edited for openstack and chef server
Both OpenStack and Chef Server are generally distributed and installed as appliances. Both expect to control the whole machine. As such, while this is possible, it is very not recommended. That said, if you have OpenStack at your disposal just install Chef Server in a VM and problem solved.
I'm trying to launch two applications in my server using SSH remote connection. These applications are using D-BUS message bus for communication.
If I login to my server computer locally, the communication between these applications works perfectly. However when I try to launch these applications remotely, errors related to D-BUS occurs.
Is there any way to share D-BUS message bus when starting applications remotely on server computer?
My server is running on Ubuntu 12.04.
Finally found a solution to my question.
First I needed to start ssh connection with trusted X11 forwarding enabled:
ssh -2 -Y user#address
In this remote connection I started the application first application with new D-Bus: dbus-launch --autolaunch=machineID app1. Then I opened new SSH connection and also started second application together with D-Bus with the command dbus-launch --autolaunch=machineID app2. MachineID can be found from ~/.dbus/session-bus/ in Linux environment.
That is how I was able to make this two applications to use the same D-Bus message bus in remote connection.
So I have a mac host and some virtual machines. I want to use ossec to monitor my virtual machines and my host, mac OS X lion. (I've already fixed the compliation issue with lion, it compiled). See this
I'm having trouble understanding what all the server and agent's roles are. If you only want ossec to run locally, you set up under local. But I have VMs to monitor, so I must select sever. But does server do what agent does on the host, as in, is there some kind of agent functionality to ensure that the same monitoring and checking is also occurring on the server just as it is on the VMs with agent?
If not, then how do I make sure that the host is also being monitored with ossec? What I had thought was that ossec would have to be set up on the host as both a server and client, but if you go to run the installer twice, it will want to delete the server's installation and remake it as an agent only.
The server does all the things an agent does, and on top of that it centralizes log collection and processing. You don't need to install OSSEC as server and agent on your server, just as server.