Re: VMMark 1.1.1 issue while running fileserver te... - Page 2

rajanyadav · ‎12-07-2011

Hi Everyone,

I am trying to run VMmark 1.1.1 (I know its retired but it serves the purpose ) . Not only that I am running just the fileserver test. I have the fileserver VM and the client setup and everythng works fine.

My questions is

Can we rerun the test right after it finishes?

Here is what I see

I made changes to the CONFIG file to just run the fileserver test and that too only for a few minutes

The test runs fine and I can see results files under c:\vmmar\results on my client0

When test is running , I see the following on fileserver0

fileserver:~ # ps -eaf|grep -i dbench

root 3564 1819 0 22:20 ? 00:00:00 sh -c /home/fileserver/dbench/src/lock_mem 25000 > /home/fileserver/dbench/src/lock_mem.out

root 3565 3564 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/lock_mem 25000

root 3567 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3568 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3569 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3570 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3571 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3572 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3573 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3574 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3575 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3576 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3577 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3578 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3579 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3580 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3581 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3582 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3583 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3584 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3585 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3586 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3587 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3588 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3589 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3590 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3591 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3592 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3593 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3594 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3595 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3596 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3597 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3598 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3599 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3600 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3601 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3602 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3603 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3604 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3605 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3606 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3607 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3608 1 0 22:20 ? 00:00:00 /home/fileserver/dbench/src/dbench -c /home/fileserver/dbench/src/client_plain.txt -p 1066 -l 1000 45 client0

root 3692 3623 0 22:31 pts/2 00:00:00 grep -i dbench

But even after the STAXMon shows the test has finished , (logs show up properly in results)there is some dbench related process running on the fileserver0 vm

ileserver:/home/fileserver/dbench/src # ps -eaf| grep -i dbench

root 5984 3967 0 17:25 ? 00:00:00 sh -c /home/fileserver/dbench/src/lock_mem 25000 > /home/fileserver/dbench/src/lock_mem.out

root 5985 5984 0 17:25 ? 00:00:00 /home/fileserver/dbench/src/lock_mem 25000

root 6116 5926 0 18:10 pts/1 00:00:00 grep -i dbench

Question is why are these two processes still runing and what do they mean?

Is it normal/expected behavior?

Reason I ask is because right after my 1st successful run, I re-run the same test case and although the test runs fine, I see much lower numbers in my results

I also see the after the second test has finished, I now have

fileserver:/home/fileserver/dbench/src # ps -eaf| grep -i dbench

root 5984 3967 0 17:25 ? 00:00:00 sh -c /home/fileserver/dbench/src/lock_mem 25000 > /home/fileserver/dbench/src/lock_mem.out

root 5985 5984 0 17:25 ? 00:00:00 /home/fileserver/dbench/src/lock_mem 25000

root 6132 3967 0 18:10 ? 00:00:00 sh -c /home/fileserver/dbench/src/lock_mem 25000 > /home/fileserver/dbench/src/lock_mem.out

root 6133 6132 0 18:10 ? 00:00:00 /home/fileserver/dbench/src/lock_mem 25000

root 6256 5926 0 18:28 pts/1 00:00:00 grep -i dbench

My fileserver vm's performance goes down, performance chart shows high CPU usage and a 3rd run of the test fails with atimeout error

Any insight?

rajanyadav · ‎12-08-2011

fileserver:~ # ps -eaf | grep -i dbench

root 7130 3967 0 14:43 ? 00:00:00 sh -c /home/fileserver/dbench/src/lock_mem 25000 > /home/fileserver/dbench/src/lock_mem.out

root 7131 7130 0 14:43 ? 00:00:00 /home/fileserver/dbench/src/lock_mem 25000

root 7499 5878 0 15:23 pts/0 00:00:00 grep -i dbench

fileserver:~ # cat /home/fileserver/kill.sh

#!/bin/sh

#

# Run script on FileServer VM's to release shared memory held by lock_mem

# and halt dbench processes

#

#kill -9 `ps -aef | grep -i run_dbench | awk '{print $2}'`

#for i in `ps -aef | grep -i tbench_srv | awk '{print $2}'`

#do

# kill -9 $i

#done

echo "Hello there"

for i in `ps -aef | grep -i lock_mem | grep -v grep | awk '{print $2}'`

do

echo $i

kill -9 $i

echo "Kill -9 called"

done

echo "Hello again"

for i in `ps -aef | grep -i client_plain | grep -v grep | awk '{print $2}'`

do

echo $i

kill -9 $i

echo "kill -9 called on $i"

done

echo "Goodbye"

jpschnee · ‎12-08-2011

Looks like you're never entering the loops. Just after the hello and goodbye echos you might try running the ps commands to see what it's going to return when it tries to do it in the loop.

Ex:

echo "Hello there"

ps -aef | grep -i lock_mem | grep -v grep | awk '{print $2}'

echo "Enterring Loop 1"

for i in `ps -aef | grep -i lock_mem | grep -v grep | awk '{print $2}'`

do

echo $i

kill -9 $i

echo "Kill -9 called"

done

... repeat for other loops

-Joshua

rajanyadav · ‎12-08-2011

C:\Documents and Settings\Administrator.GEN-VCS170>staf fileserver0 process star
t shell command "/home/fileserver/kill.sh" wait stderrtostdout returnstdout work
dir "/home/"
Response
--------
{
Return Code: 0
Key        : <None>
Files      : [
    {
      Return Code: 0
      Data       : Enterring Loop 1
Hello there
Enterring Loop 2
Hello again
Enterring Loop 3
Goodbye

}
]
}

Only prints the echo, not even the ps commands, I also tried it without awk, still nothing

jpschnee · ‎12-08-2011

Can you run dos2unix on kill.sh and try again?

-Joshua

RebeccaG · ‎12-08-2011

Doesn't this result make sense, in a way?

When you ran "ps -eaf|grep -i lock_mem" manually on the fileserver via staf, it did not detect the desired lock_mem process.
The command returns the same result (i.e. nothing) within kill.sh.

To me, the command itself appears to be failing to return the desired data. So now the question may be: why not?

rajanyadav · ‎12-08-2011

Tried dos2unix , still no luck

Modifying the script to do a killall lock_mem will work? Tried that. Just added a killall lock_mem at the end of teh script and it worked from commandline staf. Will try it from the STAX now.

rajanyadav · ‎12-08-2011

Exactly,

Its the PS command that is not getting executed through staf. Why? Not sure.

rajanyadav · ‎12-08-2011

Josh,

Thank you verymuch for your help. it works by just adding a killall.

jpschnee · ‎12-08-2011

Glad to hear it. By the way, did you download and use the template fileserver or did you create your own?

Let me know if you need anything else,

-Joshua

rajanyadav · ‎12-08-2011

Downloaded it. Only think I can think of is that I moved it from one server to another, not sure why that would mess up anything though.

jpschnee · ‎12-08-2011

I can only think it maybe something to do with staf or stax (versions?) but you're good to go so it's probably not worth the additional time to you. If you decide otherwise, let me know.

-Joshua

All

VMMark 1.1.1 issue while running fileserver test