You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Karthick N <nk...@gmail.com> on 2016/02/04 02:02:57 UTC
Jmeter-Slave unexpectedly aborted or killed.
down votefavorite
<http://stackoverflow.com/questions/34826786/jmeter-master-unexpectedly-aborted-with-shutdown-hook?noredirect=1#>
Team,
I'm trying to perform load test using Jmeter Master-Slave (distributed) in
CLI mode. apparently the test istops at random interval (approx 2~3
hours) with no much information . But i noticed the slaves is not running
jmeter-server process anymore at the same time there is no assertion of
any failure messages in salves or in OS or in Jmeter.log. So i'm almost running
out of option to debug this issue further. Any help is highly appreciated,
Thanks.
I'm using OpenVZ VPS running centos 6.7 as slaves(1GB RAM). only message i
see in jmeter-server.log is as follows.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------2016/02/03
22:55:41 INFO - jmeter.util.JMeterUtils: Setting Locale to en_US
2016/02/03 22:55:41 INFO - jmeter.JMeter: Loading user properties from:
/opt/apache-jmeter-2.13/bin/user.properties
2016/02/03 22:55:41 INFO - jmeter.JMeter: Loading system properties from:
/opt/apache-jmeter-2.13/bin/system.properties
2016/02/03 22:55:41 INFO - jmeter.JMeter: Setting System property:
server_port=1099
2016/02/03 22:55:41 INFO - jmeter.JMeter: Copyright (c) 1998-2015 The
Apache Software Foundation
2016/02/03 22:55:41 INFO - jmeter.JMeter: Version 2.13 r1665067
2016/02/03 22:55:41 INFO - jmeter.JMeter: java.version=1.8.0_65
2016/02/03 22:55:41 INFO - jmeter.JMeter: java.vm.name=Java HotSpot(TM)
64-Bit Server VM
2016/02/03 22:55:41 INFO - jmeter.JMeter: os.name=Linux
2016/02/03 22:55:41 INFO - jmeter.JMeter: os.arch=amd64
2016/02/03 22:55:41 INFO - jmeter.JMeter: os.version=2.6.32-042stab113.11
2016/02/03 22:55:41 INFO - jmeter.JMeter: file.encoding=UTF-8
2016/02/03 22:55:41 INFO - jmeter.JMeter: Default Locale=English (United
States)
2016/02/03 22:55:41 INFO - jmeter.JMeter: JMeter Locale=English (United
States)
2016/02/03 22:55:41 INFO - jmeter.JMeter:
JMeterHome=/opt/apache-jmeter-2.13
2016/02/03 22:55:41 INFO - jmeter.JMeter: user.dir =/
2016/02/03 22:55:41 INFO - jmeter.JMeter: PWD =/
2016/02/03 22:55:41 INFO - jmeter.JMeter: IP: xx.xx.xx.xx Name: server100
FullName: server100
2016/02/03 22:55:41 INFO - jmeter.engine.RemoteJMeterEngineImpl: Starting
backing engine on 1099
2016/02/03 22:55:41 INFO - jmeter.engine.RemoteJMeterEngineImpl: Local IP
address=xx.xx.xx.xx
2016/02/03 22:55:41 INFO - jmeter.engine.RemoteJMeterEngineImpl: IP
address is a site-local address; this may cause problems with remote access.
Can be overridden by defining the system property
'java.rmi.server.hostname' - see jmeter-server script file
2016/02/03 22:55:41 INFO - jmeter.engine.RemoteJMeterEngineImpl: Creating
RMI registry (server.rmi.create=true)
2016/02/03 22:55:41 WARN - jmeter.engine.RemoteJMeterEngineImpl: Problem
creating registry: java.rmi.server.ExportException: Port already in use:
1099; nested exception is:
java.net.BindException: Address already in use
2016/02/03 22:55:41 INFO - jmeter.engine.RemoteJMeterEngineImpl: Bound to
registry on port 1099
Re: Jmeter-Slave unexpectedly aborted or killed.
Posted by Karthick N <nk...@gmail.com>.
Issue resolved by recreating openvz containers with new set of Jmeter
files. Thanks!
On Thu, Feb 4, 2016 at 9:17 AM, Karthick N <nk...@gmail.com> wrote:
> Hi Steven,
>
> Thanks for the quick response. here is my setup details and my issue
> characterization.
>
> Setup1:
> OpenVz-Master -> OpenVz-Slaves -> System under test => Test fails randomly
> (Jmeter log under master container reported shutdown hook.
> Jmeter-server.log no issue reported but Jmter+jmeter-server.sh were not
> running in slaves)
>
> Setup2:
> Windows Machine - Master -> OpenVz-Slaves -> System under test => Test
> fails randomly (Jmeter log under master has no error or shutdown hook, it
> just hangs as though its waiting for slave request. Jmeter-server.log no
> issue reported but Jmter+jmeter-server.sh were not running in slaves)
>
> Step3:
> Windows Machine - Master(GUI) -> OPenVz-Slaves -> System under tset =>
> Test were running without any issue for days!
>
> Essentially running test from GUI via OpenVz container to the same target
> has no issues. Issue persist only if i run Test through CLI no matter
> whether its windows/linux/conatiner based Master.
>
> Thanks
> Karthick
>
>
> On Thu, Feb 4, 2016 at 8:48 AM, Steven Swor <sw...@gmail.com>
> wrote:
>
>> Hi Karthik,
>>
>> Are you able to confirm the slaves actually do run the test for 2-3 hours
>> before dying? I'm thinking the "Address already in use" message is
>> probably
>> an important clue.
>>
>> Is the JMeter master running on the host system, or in another openvz
>> container?
>>
>> Finally, are the master and slaves all running as containers of the same
>> OpenVZ host?
>>
>> On Thu, Feb 4, 2016 at 12:02 PM, Karthick N <nk...@gmail.com> wrote:
>>
>> > down votefavorite
>> > <
>> >
>> http://stackoverflow.com/questions/34826786/jmeter-master-unexpectedly-aborted-with-shutdown-hook?noredirect=1#
>> > >
>> >
>> > Team,
>> >
>> > I'm trying to perform load test using Jmeter Master-Slave (distributed)
>> in
>> > CLI mode. apparently the test istops at random interval (approx 2~3
>> > hours) with no much information . But i noticed the slaves is not
>> running
>> > jmeter-server process anymore at the same time there is no assertion of
>> > any failure messages in salves or in OS or in Jmeter.log. So i'm almost
>> > running
>> > out of option to debug this issue further. Any help is highly
>> appreciated,
>> > Thanks.
>> >
>> > I'm using OpenVZ VPS running centos 6.7 as slaves(1GB RAM). only
>> message i
>> > see in jmeter-server.log is as follows.
>> >
>> >
>> >
>> -----------------------------------------------------------------------------------------------------------------------------------------------------------------2016/02/03
>> > 22:55:41 INFO - jmeter.util.JMeterUtils: Setting Locale to en_US
>> >
>> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: Loading user properties from:
>> > /opt/apache-jmeter-2.13/bin/user.properties
>> >
>> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: Loading system properties
>> from:
>> > /opt/apache-jmeter-2.13/bin/system.properties
>> >
>> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: Setting System property:
>> > server_port=1099
>> >
>> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: Copyright (c) 1998-2015 The
>> > Apache Software Foundation
>> >
>> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: Version 2.13 r1665067
>> >
>> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: java.version=1.8.0_65
>> >
>> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: java.vm.name=Java
>> HotSpot(TM)
>> > 64-Bit Server VM
>> >
>> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: os.name=Linux
>> >
>> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: os.arch=amd64
>> >
>> > 2016/02/03 22:55:41 INFO - jmeter.JMeter:
>> os.version=2.6.32-042stab113.11
>> >
>> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: file.encoding=UTF-8
>> >
>> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: Default Locale=English
>> (United
>> > States)
>> >
>> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: JMeter Locale=English
>> (United
>> > States)
>> >
>> > 2016/02/03 22:55:41 INFO - jmeter.JMeter:
>> > JMeterHome=/opt/apache-jmeter-2.13
>> >
>> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: user.dir =/
>> >
>> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: PWD =/
>> >
>> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: IP: xx.xx.xx.xx Name:
>> server100
>> > FullName: server100
>> >
>> > 2016/02/03 22:55:41 INFO - jmeter.engine.RemoteJMeterEngineImpl:
>> Starting
>> > backing engine on 1099
>> >
>> > 2016/02/03 22:55:41 INFO - jmeter.engine.RemoteJMeterEngineImpl: Local
>> IP
>> > address=xx.xx.xx.xx
>> >
>> > 2016/02/03 22:55:41 INFO - jmeter.engine.RemoteJMeterEngineImpl: IP
>> > address is a site-local address; this may cause problems with remote
>> > access.
>> >
>> > Can be overridden by defining the system property
>> > 'java.rmi.server.hostname' - see jmeter-server script file
>> >
>> > 2016/02/03 22:55:41 INFO - jmeter.engine.RemoteJMeterEngineImpl:
>> Creating
>> > RMI registry (server.rmi.create=true)
>> >
>> > 2016/02/03 22:55:41 WARN - jmeter.engine.RemoteJMeterEngineImpl:
>> Problem
>> > creating registry: java.rmi.server.ExportException: Port already in use:
>> > 1099; nested exception is:
>> >
>> > java.net.BindException: Address already in use
>> >
>> > 2016/02/03 22:55:41 INFO - jmeter.engine.RemoteJMeterEngineImpl: Bound
>> to
>> > registry on port 1099
>> >
>>
>
>
Re: Jmeter-Slave unexpectedly aborted or killed.
Posted by Karthick N <nk...@gmail.com>.
Hi Steven,
Thanks for the quick response. here is my setup details and my issue
characterization.
Setup1:
OpenVz-Master -> OpenVz-Slaves -> System under test => Test fails randomly
(Jmeter log under master container reported shutdown hook.
Jmeter-server.log no issue reported but Jmter+jmeter-server.sh were not
running in slaves)
Setup2:
Windows Machine - Master -> OpenVz-Slaves -> System under test => Test
fails randomly (Jmeter log under master has no error or shutdown hook, it
just hangs as though its waiting for slave request. Jmeter-server.log no
issue reported but Jmter+jmeter-server.sh were not running in slaves)
Step3:
Windows Machine - Master(GUI) -> OPenVz-Slaves -> System under tset => Test
were running without any issue for days!
Essentially running test from GUI via OpenVz container to the same target
has no issues. Issue persist only if i run Test through CLI no matter
whether its windows/linux/conatiner based Master.
Thanks
Karthick
On Thu, Feb 4, 2016 at 8:48 AM, Steven Swor <sw...@gmail.com>
wrote:
> Hi Karthik,
>
> Are you able to confirm the slaves actually do run the test for 2-3 hours
> before dying? I'm thinking the "Address already in use" message is probably
> an important clue.
>
> Is the JMeter master running on the host system, or in another openvz
> container?
>
> Finally, are the master and slaves all running as containers of the same
> OpenVZ host?
>
> On Thu, Feb 4, 2016 at 12:02 PM, Karthick N <nk...@gmail.com> wrote:
>
> > down votefavorite
> > <
> >
> http://stackoverflow.com/questions/34826786/jmeter-master-unexpectedly-aborted-with-shutdown-hook?noredirect=1#
> > >
> >
> > Team,
> >
> > I'm trying to perform load test using Jmeter Master-Slave (distributed)
> in
> > CLI mode. apparently the test istops at random interval (approx 2~3
> > hours) with no much information . But i noticed the slaves is not running
> > jmeter-server process anymore at the same time there is no assertion of
> > any failure messages in salves or in OS or in Jmeter.log. So i'm almost
> > running
> > out of option to debug this issue further. Any help is highly
> appreciated,
> > Thanks.
> >
> > I'm using OpenVZ VPS running centos 6.7 as slaves(1GB RAM). only message
> i
> > see in jmeter-server.log is as follows.
> >
> >
> >
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------2016/02/03
> > 22:55:41 INFO - jmeter.util.JMeterUtils: Setting Locale to en_US
> >
> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: Loading user properties from:
> > /opt/apache-jmeter-2.13/bin/user.properties
> >
> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: Loading system properties
> from:
> > /opt/apache-jmeter-2.13/bin/system.properties
> >
> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: Setting System property:
> > server_port=1099
> >
> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: Copyright (c) 1998-2015 The
> > Apache Software Foundation
> >
> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: Version 2.13 r1665067
> >
> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: java.version=1.8.0_65
> >
> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: java.vm.name=Java HotSpot(TM)
> > 64-Bit Server VM
> >
> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: os.name=Linux
> >
> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: os.arch=amd64
> >
> > 2016/02/03 22:55:41 INFO - jmeter.JMeter:
> os.version=2.6.32-042stab113.11
> >
> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: file.encoding=UTF-8
> >
> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: Default Locale=English (United
> > States)
> >
> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: JMeter Locale=English (United
> > States)
> >
> > 2016/02/03 22:55:41 INFO - jmeter.JMeter:
> > JMeterHome=/opt/apache-jmeter-2.13
> >
> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: user.dir =/
> >
> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: PWD =/
> >
> > 2016/02/03 22:55:41 INFO - jmeter.JMeter: IP: xx.xx.xx.xx Name:
> server100
> > FullName: server100
> >
> > 2016/02/03 22:55:41 INFO - jmeter.engine.RemoteJMeterEngineImpl:
> Starting
> > backing engine on 1099
> >
> > 2016/02/03 22:55:41 INFO - jmeter.engine.RemoteJMeterEngineImpl: Local
> IP
> > address=xx.xx.xx.xx
> >
> > 2016/02/03 22:55:41 INFO - jmeter.engine.RemoteJMeterEngineImpl: IP
> > address is a site-local address; this may cause problems with remote
> > access.
> >
> > Can be overridden by defining the system property
> > 'java.rmi.server.hostname' - see jmeter-server script file
> >
> > 2016/02/03 22:55:41 INFO - jmeter.engine.RemoteJMeterEngineImpl:
> Creating
> > RMI registry (server.rmi.create=true)
> >
> > 2016/02/03 22:55:41 WARN - jmeter.engine.RemoteJMeterEngineImpl: Problem
> > creating registry: java.rmi.server.ExportException: Port already in use:
> > 1099; nested exception is:
> >
> > java.net.BindException: Address already in use
> >
> > 2016/02/03 22:55:41 INFO - jmeter.engine.RemoteJMeterEngineImpl: Bound
> to
> > registry on port 1099
> >
>
Re: Jmeter-Slave unexpectedly aborted or killed.
Posted by Steven Swor <sw...@gmail.com>.
Hi Karthik,
Are you able to confirm the slaves actually do run the test for 2-3 hours
before dying? I'm thinking the "Address already in use" message is probably
an important clue.
Is the JMeter master running on the host system, or in another openvz
container?
Finally, are the master and slaves all running as containers of the same
OpenVZ host?
On Thu, Feb 4, 2016 at 12:02 PM, Karthick N <nk...@gmail.com> wrote:
> down votefavorite
> <
> http://stackoverflow.com/questions/34826786/jmeter-master-unexpectedly-aborted-with-shutdown-hook?noredirect=1#
> >
>
> Team,
>
> I'm trying to perform load test using Jmeter Master-Slave (distributed) in
> CLI mode. apparently the test istops at random interval (approx 2~3
> hours) with no much information . But i noticed the slaves is not running
> jmeter-server process anymore at the same time there is no assertion of
> any failure messages in salves or in OS or in Jmeter.log. So i'm almost
> running
> out of option to debug this issue further. Any help is highly appreciated,
> Thanks.
>
> I'm using OpenVZ VPS running centos 6.7 as slaves(1GB RAM). only message i
> see in jmeter-server.log is as follows.
>
>
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------2016/02/03
> 22:55:41 INFO - jmeter.util.JMeterUtils: Setting Locale to en_US
>
> 2016/02/03 22:55:41 INFO - jmeter.JMeter: Loading user properties from:
> /opt/apache-jmeter-2.13/bin/user.properties
>
> 2016/02/03 22:55:41 INFO - jmeter.JMeter: Loading system properties from:
> /opt/apache-jmeter-2.13/bin/system.properties
>
> 2016/02/03 22:55:41 INFO - jmeter.JMeter: Setting System property:
> server_port=1099
>
> 2016/02/03 22:55:41 INFO - jmeter.JMeter: Copyright (c) 1998-2015 The
> Apache Software Foundation
>
> 2016/02/03 22:55:41 INFO - jmeter.JMeter: Version 2.13 r1665067
>
> 2016/02/03 22:55:41 INFO - jmeter.JMeter: java.version=1.8.0_65
>
> 2016/02/03 22:55:41 INFO - jmeter.JMeter: java.vm.name=Java HotSpot(TM)
> 64-Bit Server VM
>
> 2016/02/03 22:55:41 INFO - jmeter.JMeter: os.name=Linux
>
> 2016/02/03 22:55:41 INFO - jmeter.JMeter: os.arch=amd64
>
> 2016/02/03 22:55:41 INFO - jmeter.JMeter: os.version=2.6.32-042stab113.11
>
> 2016/02/03 22:55:41 INFO - jmeter.JMeter: file.encoding=UTF-8
>
> 2016/02/03 22:55:41 INFO - jmeter.JMeter: Default Locale=English (United
> States)
>
> 2016/02/03 22:55:41 INFO - jmeter.JMeter: JMeter Locale=English (United
> States)
>
> 2016/02/03 22:55:41 INFO - jmeter.JMeter:
> JMeterHome=/opt/apache-jmeter-2.13
>
> 2016/02/03 22:55:41 INFO - jmeter.JMeter: user.dir =/
>
> 2016/02/03 22:55:41 INFO - jmeter.JMeter: PWD =/
>
> 2016/02/03 22:55:41 INFO - jmeter.JMeter: IP: xx.xx.xx.xx Name: server100
> FullName: server100
>
> 2016/02/03 22:55:41 INFO - jmeter.engine.RemoteJMeterEngineImpl: Starting
> backing engine on 1099
>
> 2016/02/03 22:55:41 INFO - jmeter.engine.RemoteJMeterEngineImpl: Local IP
> address=xx.xx.xx.xx
>
> 2016/02/03 22:55:41 INFO - jmeter.engine.RemoteJMeterEngineImpl: IP
> address is a site-local address; this may cause problems with remote
> access.
>
> Can be overridden by defining the system property
> 'java.rmi.server.hostname' - see jmeter-server script file
>
> 2016/02/03 22:55:41 INFO - jmeter.engine.RemoteJMeterEngineImpl: Creating
> RMI registry (server.rmi.create=true)
>
> 2016/02/03 22:55:41 WARN - jmeter.engine.RemoteJMeterEngineImpl: Problem
> creating registry: java.rmi.server.ExportException: Port already in use:
> 1099; nested exception is:
>
> java.net.BindException: Address already in use
>
> 2016/02/03 22:55:41 INFO - jmeter.engine.RemoteJMeterEngineImpl: Bound to
> registry on port 1099
>