Re: Grinder agent communication shut down when worker process launched

--===============7585723085663085148==
Content-Type: multipart/alternative; boundary=089e0141a22e39febf0524fbde46

--089e0141a22e39febf0524fbde46
Content-Type: text/plain; charset=UTF-8

Hey Alfin,

I have seen this before.  It sounds like the worker processor is not
reporting back.

Why else would a rest call to get agent status report nothing even though
your tests are running?

Have you tried to trace the comms using netstat?  You can do from both the
console and agent host.  The agent host is more interesting.  I am guessing
the worker processor initially opens a socket to the console; but closes
soon after init (which it should not).

HTH,

Ouray

On Thursday, November 19, 2015, Gary Mulder <[email protected]> wrote:

> On 19 November 2015 at 22:09, Ouray Viney <[email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote:
>
>> Hi Alfin ,
>>
>> How restrictive are the firewall rules between the agent and the console?
>>
>
> Firewalls dropping or blocking connections are unlikely to cause
> successful HTTP 200 codes but empty responses.
>
> Chances are you're seeing a blank JSON document because one or more of the
> components that make up the document is not being generated by the worker.
> At the end of the test this value is likely populated and so valid info
> starts getting returned. I'd guess running the worker within a debugger
> might help isolate the issue.
>
> Gary
>


-- 
Sent from Gmail Mobile

Ouray Viney
Blog: https://www.viney.ca
Skype: Ouray Viney
LinkedIn: https://ca.linkedin.com/in/ourayvine

--089e0141a22e39febf0524fbde46
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hey Alfin,<div><br></div><div>I have seen this before.=C2=A0 It sounds like=
 the worker processor is not reporting back. =C2=A0</div><div><br></div><di=
v>Why else would a rest call to get=C2=A0agent status report nothing even t=
hough your tests are running?</div><div><br></div><div>Have you tried to tr=
ace the comms using netstat?=C2=A0 You can do from both the console and age=
nt host.=C2=A0 The agent host is more interesting.=C2=A0 I am guessing the =
worker processor initially opens a socket to the console; but closes soon a=
fter init (which it should not).</div><div><br></div><div>HTH<span></span>,=
</div><div><br></div><div>Ouray</div><div><br>On Thursday, November 19, 201=
5, Gary Mulder &lt;<a href=3D"mailto:[email protected]">flyingkiwiguy=
@gmail.com</a>&gt; wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr=
"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 19 November 2015=
 at 22:09, Ouray Viney <span dir=3D"ltr">&lt;<a href=3D"javascript:_e(%7B%7=
D,&#39;cvml&#39;,&#39;[email protected]&#39;);" target=3D"_blank">ouray@viney.=
ca</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Alfin ,<div><=
br></div><div>How restrictive are the firewall rules between the agent and =
the console?</div></blockquote><div><br></div><div>Firewalls dropping or bl=
ocking connections are unlikely to cause successful HTTP 200 codes but empt=
y responses.</div><div><br></div><div>Chances are you&#39;re seeing a blank=
 JSON document because one or more of the components that make up the docum=
ent is not being generated by the worker. At the end of the test this value=
 is likely populated and so valid info starts getting returned. I&#39;d gue=
ss running the worker within a debugger might help isolate the issue.</div>=
<div><br></div><div>Gary</div></div></div></div>
</blockquote></div><br><br>-- <br>Sent from Gmail Mobile<p>Ouray Viney<br>B=
log: <a href=3D"https://www.viney.ca">https://www.viney.ca</a><br>Skype:  O=
uray Viney<br>LinkedIn: <a href=3D"https://ca.linkedin.com/in/ourayvine">ht=
tps://ca.linkedin.com/in/ourayvine</a><br></p>

--089e0141a22e39febf0524fbde46--


--===============7585723085663085148==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------

--===============7585723085663085148==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
grinder-use mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/grinder-use

--===============7585723085663085148==--