Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

A: This is caused by VM where IxNetwork GUI application is executed. In the past, VSPERF used Intel-POD3, where execution of DAILY job was stable. It means, that performance results were stable among Daily job executions and the execution always took about 12 hours. After the move to a different Intel LAB and to Intel-POD12, the performance started to fluctuate and daily job execution takes more time by each execution. Several attempts to fix these issues were made, but issues still persists. In order to shorten DAILY job execution, it is required to login into VM as "vsperf_ci" user via remote desktop and to restart IxNetwork GUI application.


Q: What to do if Jenkins slave appears to be offline?

A: Check if Jenkins slave process is running:

Code Block
languagebash
[root@pod12-node3 ~]# ps -ef | grep jenkins                                           
jenkins   12995      1  0 Feb13 ?        00:09:40 java -jar slave.jar -jnlpUrl http
s://build.opnfv.org/ci/computer/intel-pod12/slave-agent.jnlp -secret <secret> -noCertificateCheck
root      17681  17647  0 15:23 pts/0    00:00:00 grep --color=auto jenk     


You can also restart it if needed using "monit stop" and  "monit start" commands. Example output:

Code Block
languagebash
[root@pod12-node3 ~]# monit status                                                                                                                                                                                 
Monit 5.25.1 uptime: 73d 5h 29m                                                                                                                                                                                    
                                                                                                                                                                                                                   
Directory 'jenkins_piddir'                                                         
  status                       OK                                                  
  monitoring status            Monitored                                           
  monitoring mode              active                                              
  on reboot                    start                                               
  permission                   755                                                
  uid                          1001                                                
  gid                          1001                             
  access timestamp             Mon, 03 Dec 2018 09:54:12        
  change timestamp             Wed, 13 Feb 2019 14:35:01        
  modify timestamp             Wed, 13 Feb 2019 14:35:01         
  data collected               Thu, 14 Feb 2019 15:23:51                           
                                                                             
Process 'jenkins'                               
  status                       OK                                             
  monitoring status            Monitored
  monitoring mode              active
  on reboot                    start
  pid                          12995
  parent pid                   1
  uid                          1001
  effective uid                1001
  gid                          1001
  uptime                       1d 0h 48m
  threads                      53
  children                     0
  cpu                          0.0%
  cpu total                    0.0%
  memory                       0.7% [443.8 MB]
  memory total                 0.7% [443.8 MB]
  security attribute           (null)
  disk read                    0 B/s [81.8 MB total]
  disk write                   0 B/s [6.8 GB total]
  data collected               Thu, 14 Feb 2019 15:23:51

System 'pod12-node3.opnfv.local'
  status                       OK
  monitoring status            Monitored
  monitoring mode              active
  on reboot                    start
  load average                 [0.00] [0.00] [0.00]
  cpu                          0.0%us 0.0%sy 0.0%wa
  memory usage                 15.2 GB [24.1%]
  swap usage                   0 B [0.0%]
  uptime                       73d 5h 30m
  boot time                    Mon, 03 Dec 2018 09:53:25
  data collected               Thu, 14 Feb 2019 15:23:51



Q: What to do if IxNework TCL Server is Down/Connection Failed ?

A:  Currently there are 3 vsperf user accounts for IxNetwork in Ixia VM. Follow the below procedure to overcome the issue. Basically, all IxNetwork port numbers are pre-configured. You would just need to restart it.

      1. Connect the Ixia VM (Remote Desktop) using 'vsperf_ci' login and password. Once its connected and VM is launched, system should automatically start IxNetwork service on TCL port 9126. Open the Hidden icon's arrow button in task bar and place the mouse pointer on the IxNetwork icon to see whether it shows the TCL Port Configuration. If  it's not started automatically, then double click on the IxNetwork icon and it will start the service at port 9126.

      2. Connect the Ixia VM (Remote Desktop) using 'vsperf_sandbox' login and password. Once its connected and VM is launched, system should automatically start IxNetwork service ion TCL port 9127. Open the Hidden icon's arrow button in task bar and place the mouse pointer on the IxNetwork icon to see whether it shows the TCL Port Configuration. If  it's not started automatically, then double click on the IxNetwork icon and it will start the service at port 9127.

      3. Connect the Ixia VM (Remote Desktop) using 'vsperf_sandbox2' login and password. Once its connected and VM is launched, system should automatically start IxNetwork service ion TCL port 9128. Open the Hidden icon's arrow button in task bar and place the mouse pointer on the IxNetwork icon to see whether it shows the TCL Port Configuration. If  it's not started automatically, then double click on the IxNetwork icon and it will start the service at port 9128.

If above three IxNetwork TCL services are running fine, then you are good to go.

Ideas

Configure 2nd jenkins slave for execution of VSPERF JOBs.

...