Python Fuzzing Server is not updating the test results after finish running the test suit

#1

Hello Autobahn,

i have setup a server on my machine with Autobahn websocket test suite
to test different browser for WebSockets.

For the first time i ran the test for each different browser, an html
page was created along with the results for each test case in
\websockets\reports\clients

however, the issue is now when i run the test again with previously
tested browser, it won't update the result page.

The date is the same as of the last run which was last week.

your assistant are much apppreciated.

Thanks

0 Likes

#2

Which version of Autobahn are you using?

In the shell window where you run the fuzzing server, do you see a log
line like

2011-10-17 20:11:29+0200 [FuzzingServerProtocol,226,127.0.0.1]
Updating reports, requested by peer 127.0.0.1:16843

?

Does the report's index.html file timestamp change?

Do you have one of the generated file's opened in i.e. an editor,
which locks the file?

Maybe try shutting down the fuzzing server, completely remove the
report directory from the filesystem and try again ..

···

On Oct 17, 7:46 pm, Shant Panos <shant....@gmail.com> wrote:

Hello Autobahn,

i have setup a server on my machine with Autobahn websocket test suite
to test different browser for WebSockets.

For the first time i ran the test for each different browser, an html
page was created along with the results for each test case in
\websockets\reports\clients

however, the issue is now when i run the test again with previously
tested browser, it won't update the result page.

The date is the same as of the last run which was last week.

your assistant are much apppreciated.

Thanks

0 Likes

#3

Thanks Tog for the quick reply, Here is the answers for your
questions.

Which version of Autobahn are you using?

I have created a local GIT branch which is checked out to tag v0.4.2
on git://github.com/oberstet/Autobahn.git

In the shell window where you run the fuzzing server, do you see a log
line like
2011-10-17 20:11:29+0200 [FuzzingServerProtocol,226,127.0.0.1]
Updating reports, requested by peer 127.0.0.1:16843

Yes, i was running python fuzzing_server.py on the server and after
the test finishes i saw this line:

2011-10-17 15:50:37-0400 [FuzzingServerProtocol,8,10.137.40.46]
Updating reports, requested by peer 10.137.40.46:4325

Does the report's index.html file timestamp change?

No, it's still dated to the first run which is on Oct 7th

Do you have one of the generated file's opened in i.e. an editor,
which locks the file?

Not really.

Maybe try shutting down the fuzzing server,

Doesn't Help either.

completely remove the
report directory from the filesystem and try again ..

That's what i've done the last time to resolve this issue, so i
decided to contact Autobahn for better resolution.

Here is my setup:
I have a directory under apache ROOT named ws and it's cloning the
above GIT repo, the fuzzing python is running on the same server.

Thanks again

···

On Oct 17, 2:16 pm, tgo <tobias.o...@gmail.com> wrote:

Which version of Autobahn are you using?

In the shell window where you run the fuzzing server, do you see a log
line like

2011-10-17 20:11:29+0200 [FuzzingServerProtocol,226,127.0.0.1]
Updating reports, requested by peer 127.0.0.1:16843

?

Does the report's index.html file timestamp change?

Do you have one of the generated file's opened in i.e. an editor,
which locks the file?

Maybe try shutting down the fuzzing server, completely remove the
report directory from the filesystem and try again ..

On Oct 17, 7:46 pm, Shant Panos <shant....@gmail.com> wrote:

> Hello Autobahn,

> i have setup a server on my machine with Autobahn websocket test suite
> to test different browser for WebSockets.

> For the first time i ran the test for each different browser, an html
> page was created along with the results for each test case in
> \websockets\reports\clients

> however, the issue is now when i run the test again with previously
> tested browser, it won't update the result page.

> The date is the same as of the last run which was last week.

> your assistant are much apppreciated.

> Thanks- Hide quoted text -

- Show quoted text -

0 Likes

#4

ok, given that, I'd say it's probably not an issue with Autobahn,
but the specific setup you're running. here are more things to check:

You're using Apache to serve the generated reports, right?
Does Apache do any caching? Rerun, and then look into index.html
using less/more whatever .. not via Apache. Is the timestamp
within the index.html newer or the same as before?

Maybe Apache is doing caching and/or the filesystem has file
modified date disabled.

File permissions: what are the flags of the generated files?
Is it owned by the user under which the fuzzing server runs?
Maybe (if you're on Unix), the directory is "setuid/setgid" and
any file created within are taken over by some different account.

Also, I'm not sure what the "Apache cloning Git" means. You
should be done by creating a symbolic link under Apache document
root pointing to the report generation directory (this assumes
your Apache conf allows follow sym. links).

···

==

If you just want to have the reports "served" via HTTP, you
could also do:

Use Autobahn HEAD .. master branch with no tag:

The Fuzzing server there contains 2 embedded services:

fuzzer on port 9001
web server on port 9090

In a browser, just open: <IP>:9090/index.html

The 0.4.2 fuzzing server only contains 1 embedded service:

fuzzer on port 9001

--

The embedded web server allows you to access the "test_client.html"
and the generated reports directly from any browser .. even without
local filesystem access.

--

On Oct 17, 10:20 pm, Shant Panos <shant....@gmail.com> wrote:

Thanks Tog for the quick reply, Here is the answers for your
questions.

> Which version of Autobahn are you using?

I have created a local GIT branch which is checked out to tag v0.4.2
on git://github.com/oberstet/Autobahn.git

> In the shell window where you run the fuzzing server, do you see a log
> line like
> 2011-10-17 20:11:29+0200 [FuzzingServerProtocol,226,127.0.0.1]
> Updating reports, requested by peer 127.0.0.1:16843

Yes, i was running python fuzzing_server.py on the server and after
the test finishes i saw this line:

2011-10-17 15:50:37-0400 [FuzzingServerProtocol,8,10.137.40.46]
Updating reports, requested by peer 10.137.40.46:4325

> Does the report's index.html file timestamp change?

No, it's still dated to the first run which is on Oct 7th

> Do you have one of the generated file's opened in i.e. an editor,
> which locks the file?

Not really.

> Maybe try shutting down the fuzzing server,

Doesn't Help either.

> completely remove the
> report directory from the filesystem and try again ..

That's what i've done the last time to resolve this issue, so i
decided to contact Autobahn for better resolution.

Here is my setup:
I have a directory under apache ROOT named ws and it's cloning the
above GIT repo, the fuzzing python is running on the same server.

Thanks again
On Oct 17, 2:16 pm, tgo <tobias.o...@gmail.com> wrote:

> Which version of Autobahn are you using?

> In the shell window where you run the fuzzing server, do you see a log
> line like

> 2011-10-17 20:11:29+0200 [FuzzingServerProtocol,226,127.0.0.1]
> Updating reports, requested by peer 127.0.0.1:16843

> ?

> Does the report's index.html file timestamp change?

> Do you have one of the generated file's opened in i.e. an editor,
> which locks the file?

> Maybe try shutting down the fuzzing server, completely remove the
> report directory from the filesystem and try again ..

> On Oct 17, 7:46 pm, Shant Panos <shant....@gmail.com> wrote:

> > Hello Autobahn,

> > i have setup a server on my machine with Autobahn websocket test suite
> > to test different browser for WebSockets.

> > For the first time i ran the test for each different browser, an html
> > page was created along with the results for each test case in
> > \websockets\reports\clients

> > however, the issue is now when i run the test again with previously
> > tested browser, it won't update the result page.

> > The date is the same as of the last run which was last week.

> > your assistant are much apppreciated.

> > Thanks- Hide quoted text -

> - Show quoted text -

0 Likes

#5

Thanks Again for taking the time to help.

Here is my answers.

ok, given that, I'd say it's probably not an issue with Autobahn,
but the specific setup you're running. here are more things to check:

You're using Apache to serve the generated reports, right?

Yes.

Does Apache do any caching?

Nope, i have disabled caching and the issue still happening.

Rerun, and then look into index.html
using less/more whatever .. not via Apache. Is the timestamp
within the index.html newer or the same as before?

Nope, it is the same.

Maybe Apache is doing caching and/or the filesystem has file
modified date disabled.

If the file modified date was disabled, should i be at least see the
latest results? which is not happening.

File permissions: what are the flags of the generated files?

-rwx------+ 1 Administrators Domain Users 153041 Oct 21 17:56
index.html
-rwx------+ 1 Administrators Domain Users 6704 Oct 21 17:56
safari_535_1_case_1_1_1.html
-rwx------+ 1 Administrators Domain Users 8146 Oct 21 17:56
safari_535_1_case_1_1_2.html
-rwx------+ 1 Administrators Domain Users 8162 Oct 21 17:56
safari_535_1_case_1_1_3.html
-rwx------+ 1 Administrators Domain Users 8170 Oct 21 17:56
safari_535_1_case_1_1_4.html
-rwx------+ 1 Administrators Domain Users 8178 Oct 21 17:56
safari_535_1_case_1_1_5.html
-rwx------+ 1 Administrators Domain Users 14260 Oct 21 17:56
safari_535_1_case_1_1_6.html
-rwx------+ 1 Administrators Domain Users 15090 Oct 21 17:56
safari_535_1_case_1_1_7.html
-rwx------+ 1 Administrators Domain Users 71832 Oct 21 17:56
safari_535_1_case_1_1_8.html
-rwx------+ 1 Administrators Domain Users 6706 Oct 21 17:56
safari_535_1_case_1_2_1.html
-rwx------+ 1 Administrators Domain Users 8610 Oct 21 17:56
safari_535_1_case_1_2_2.html

Is it owned by the user under which the fuzzing server runs?

I'm running the fuzzing server from my domain account.

Maybe (if you're on Unix), the directory is "setuid/setgid" and
any file created within are taken over by some different account.

Well i'm running Windows Server 2003, and my domain account is been
added to the Admin Group

Also, I'm not sure what the "Apache cloning Git" means. You
should be done by creating a symbolic link under Apache document
root pointing to the report generation directory (this assumes
your Apache conf allows follow sym. links).

The Second time, I've just coppied the websockets folder to the apache
ROOT

==

If you just want to have the reports "served" via HTTP, you
could also do:

Use Autobahn HEAD .. master branch with no tag:

The Fuzzing server there contains 2 embedded services:

fuzzer on port 9001
web server on port 9090

In a browser, just open: <IP>:9090/index.html

The 0.4.2 fuzzing server only contains 1 embedded service:

fuzzer on port 9001

--

The embedded web server allows you to access the "test_client.html"
and the generated reports directly from any browser .. even without
local filesystem access.

Alright, it was working just fine last week. it happened when the
server logged my account off for some reason and when i logged back in
and start back the fuzzing server, it won't updated the test
results!!!! Strange!!

You think it might be the account permissions?

Thanks

···

On Oct 17, 5:46 pm, tgo <tobias.o...@gmail.com> wrote:

--

On Oct 17, 10:20 pm, Shant Panos <shant....@gmail.com> wrote:

> Thanks Tog for the quick reply, Here is the answers for your
> questions.

> > Which version of Autobahn are you using?

> I have created a local GIT branch which is checked out to tag v0.4.2
> on git://github.com/oberstet/Autobahn.git

> > In the shell window where you run the fuzzing server, do you see a log
> > line like
> > 2011-10-17 20:11:29+0200 [FuzzingServerProtocol,226,127.0.0.1]
> > Updating reports, requested by peer 127.0.0.1:16843

> Yes, i was running python fuzzing_server.py on the server and after
> the test finishes i saw this line:

> 2011-10-17 15:50:37-0400 [FuzzingServerProtocol,8,10.137.40.46]
> Updating reports, requested by peer 10.137.40.46:4325

> > Does the report's index.html file timestamp change?

> No, it's still dated to the first run which is on Oct 7th

> > Do you have one of the generated file's opened in i.e. an editor,
> > which locks the file?

> Not really.

> > Maybe try shutting down the fuzzing server,

> Doesn't Help either.

> > completely remove the
> > report directory from the filesystem and try again ..

> That's what i've done the last time to resolve this issue, so i
> decided to contact Autobahn for better resolution.

> Here is my setup:
> I have a directory under apache ROOT named ws and it's cloning the
> above GIT repo, the fuzzing python is running on the same server.

> Thanks again
> On Oct 17, 2:16 pm, tgo <tobias.o...@gmail.com> wrote:

> > Which version of Autobahn are you using?

> > In the shell window where you run the fuzzing server, do you see a log
> > line like

> > 2011-10-17 20:11:29+0200 [FuzzingServerProtocol,226,127.0.0.1]
> > Updating reports, requested by peer 127.0.0.1:16843

> > ?

> > Does the report's index.html file timestamp change?

> > Do you have one of the generated file's opened in i.e. an editor,
> > which locks the file?

> > Maybe try shutting down the fuzzing server, completely remove the
> > report directory from the filesystem and try again ..

> > On Oct 17, 7:46 pm, Shant Panos <shant....@gmail.com> wrote:

> > > Hello Autobahn,

> > > i have setup a server on my machine with Autobahn websocket test suite
> > > to test different browser for WebSockets.

> > > For the first time i ran the test for each different browser, an html
> > > page was created along with the results for each test case in
> > > \websockets\reports\clients

> > > however, the issue is now when i run the test again with previously
> > > tested browser, it won't update the result page.

> > > The date is the same as of the last run which was last week.

> > > your assistant are much apppreciated.

> > > Thanks- Hide quoted text -

> > - Show quoted text -- Hide quoted text -

- Show quoted text -

0 Likes

#6

So you are running Apache on Windows server, which probably even is
integrated with Active Directory.

There are many permission settings involved in your setting sprinkled
across Apache, Windows and AD.

I'm pretty sure your problem is caused by some permission/account
settings.

I am sorry, but I can't give you support service on Apache/Win/AD.

···

==

Consider kicking Apache and use the embedded web server. One less
variable.

==

File permissions: what are the flags of the generated files?

-rwx------+ 1 Administrators Domain Users 153041 Oct 21 17:56
index.html

Does not look like a Win listing .. more a directory listing via FTP
client. That might lie to you regarding owners .. and won't show you
real AD permissions.

0 Likes