vtune -collect platform-profiler Error: An unexpected error has occurred.

侯玉山 · ‎10-14-2021

Hello, I encountered such an error when executing VTune - collect platform profiler

This is the command I execute on the command line:

[root@c1 latest]# vtune -collect platform-profiler -data-limit=20 --duration 60 -r ./01platform_profiler
Warning: PMU counter(s) [GP0 ] is/are already in use by other software and the data collected on these counter(s) may be incorrect
vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r ./01platform_profiler -command stop.
vtune: Error: An unexpected error has occurred. Our apologies for this inconvenience. Please gather a description of the steps leading up to the problem and contact Intel customer support.
vtune: Collection detached.
vtune: Collection stopped.
vtune: Platform Profiler report is not available from the command line. To view the result, use VTune Profiler Graphical Interface.

侯玉山 · ‎10-15-2021

And when I changed to VPP collect start collection, I encountered this problem：

[root@c2 collector]# vpp-collect start -d ./1015_vpp_dir
Traceback (most recent call last):
File "/usr/bin/dstat", line 30, in <module>
from pcp import pmapi, pmconfig
ModuleNotFoundError: No module named 'pcp'
Traceback (most recent call last):
File "/usr/bin/dstat", line 30, in <module>
from pcp import pmapi, pmconfig
ModuleNotFoundError: No module named 'pcp'
Traceback (most recent call last):
File "/usr/bin/dstat", line 30, in <module>
from pcp import pmapi, pmconfig
ModuleNotFoundError: No module named 'pcp'
Traceback (most recent call last):
File "/usr/bin/dstat", line 30, in <module>
from pcp import pmapi, pmconfig
ModuleNotFoundError: No module named 'pcp'
Traceback (most recent call last):
File "/usr/bin/dstat", line 30, in <module>
from pcp import pmapi, pmconfig
ModuleNotFoundError: No module named 'pcp'
Traceback (most recent call last):
File "/usr/bin/dstat", line 30, in <module>
from pcp import pmapi, pmconfig
ModuleNotFoundError: No module named 'pcp'
Traceback (most recent call last):
File "/usr/bin/dstat", line 30, in <module>
from pcp import pmapi, pmconfig
ModuleNotFoundError: No module named 'pcp'
Traceback (most recent call last):
File "/usr/bin/dstat", line 30, in <module>
from pcp import pmapi, pmconfig
ModuleNotFoundError: No module named 'pcp'
Traceback (most recent call last):
File "/usr/bin/dstat", line 30, in <module>
from pcp import pmapi, pmconfig
ModuleNotFoundError: No module named 'pcp'

WARNING: Intel Persistent Memory devices could not be detected by PMWatch.
For more details, see /root/vpp-collect.log

Traceback (most recent call last):
File "/usr/bin/dstat", line 30, in <module>
from pcp import pmapi, pmconfig
ModuleNotFoundError: No module named 'pcp'
Collection aborted.

I installed PCP according to the log, but I found that the PCP module can not be installed simply. I don't know why.

thanks for your help.

AthiraM_Intel · ‎10-18-2021

Hi,

Thank you for posting in Intel Communities.

Could you please share your OS details and the VTune version?

We are able to reproduce the issue "vtune: Error: An unexpected error has occurred" using VTune version 2021.8 in Ubuntu 18.04.

Thanks,

侯玉山 · ‎10-18-2021

hi,JananiC_Intel:

Here are the machine information and VTune version information I collected：

uname -a ---> Linux c1 4.18.0-240.15.1.el8_3.x86_64 #1 SMP Mon Mar 1 17:16:16 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

cat /proc/version -----> Linux version 4.18.0-240.15.1.el8_3.x86_64 (mockbuild@kbuilder.bsys.centos.org) (gcc version 8.3.1 20191121 (Red Hat 8.3.1-5) (GCC)) #1 SMP Mon Mar 1 17:16:16 UTC 2021

cat /etc/issue ------->

\S
Kernel \r on an \m

cat /etc/redhat-release ------>

CentOS Linux release 8.4.2105

cpuinfo -------->

===== Processor composition =====
Processor name : Intel(R) Xeon(R) Gold 6330N
Packages(sockets) : 2
Cores : 56
Processors(CPUs) : 112
Cores per package : 28
Threads per core : 2

===== Processor identification =====
Processor Thread Id. Core Id. Package Id.
0 0 0 0
1 0 1 0
2 0 2 0
3 0 3 0
4 0 4 0
5 0 5 0
6 0 6 0
7 0 7 0
8 0 8 0
9 0 9 0
10 0 10 0
11 0 11 0
12 0 12 0
13 0 13 0
14 0 14 0
15 0 15 0
16 0 16 0
17 0 17 0
18 0 18 0
19 0 19 0
20 0 20 0
21 0 21 0
22 0 22 0
23 0 23 0
24 0 24 0
25 0 25 0
26 0 26 0
27 0 27 0
28 0 0 1
29 0 1 1
30 0 2 1
31 0 3 1
32 0 4 1
33 0 5 1
34 0 6 1
35 0 7 1
36 0 8 1
37 0 9 1
38 0 10 1
39 0 11 1
40 0 12 1
41 0 13 1
42 0 14 1
43 0 15 1
44 0 16 1
45 0 17 1
46 0 18 1
47 0 19 1
48 0 20 1
49 0 21 1
50 0 22 1
51 0 23 1
52 0 24 1
53 0 25 1
54 0 26 1
55 0 27 1
56 1 0 0
57 1 1 0
58 1 2 0
59 1 3 0
60 1 4 0
61 1 5 0
62 1 6 0
63 1 7 0
64 1 8 0
65 1 9 0
66 1 10 0
67 1 11 0
68 1 12 0
69 1 13 0
70 1 14 0
71 1 15 0
72 1 16 0
73 1 17 0
74 1 18 0
75 1 19 0
76 1 20 0
77 1 21 0
78 1 22 0
79 1 23 0
80 1 24 0
81 1 25 0
82 1 26 0
83 1 27 0
84 1 0 1
85 1 1 1
86 1 2 1
87 1 3 1
88 1 4 1
89 1 5 1
90 1 6 1
91 1 7 1
92 1 8 1
93 1 9 1
94 1 10 1
95 1 11 1
96 1 12 1
97 1 13 1
98 1 14 1
99 1 15 1
100 1 16 1
101 1 17 1
102 1 18 1
103 1 19 1
104 1 20 1
105 1 21 1
106 1 22 1
107 1 23 1
108 1 24 1
109 1 25 1
110 1 26 1
111 1 27 1
===== Placement on packages =====
Package Id. Core Id. Processors
0 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27 (0,56)(1,57)(2,58)(3,59)(4,60)(5,61)(6,62)(7,63)(8,64)(9,65)(10,66)(11,67)(12,68)(13,69)(14,70)(15,71)(16,72)(17,73)(18,74)(19,75)(20,76)(21,77)(22,78)(23,79)(24,80)(25,81)(26,82)(27,83)
1 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27 (28,84)(29,85)(30,86)(31,87)(32,88)(33,89)(34,90)(35,91)(36,92)(37,93)(38,94)(39,95)(40,96)(41,97)(42,98)(43,99)(44,100)(45,101)(46,102)(47,103)(48,104)(49,105)(50,106)(51,107)(52,108)(53,109)(54,110)(55,111)

===== Cache sharing =====
Cache Size Processors
L1 48 KB (0,56)(1,57)(2,58)(3,59)(4,60)(5,61)(6,62)(7,63)(8,64)(9,65)(10,66)(11,67)(12,68)(13,69)(14,70)(15,71)(16,72)(17,73)(18,74)(19,75)(20,76)(21,77)(22,78)(23,79)(24,80)(25,81)(26,82)(27,83)(28,84)(29,85)(30,86)(31,87)(32,88)(33,89)(34,90)(35,91)(36,92)(37,93)(38,94)(39,95)(40,96)(41,97)(42,98)(43,99)(44,100)(45,101)(46,102)(47,103)(48,104)(49,105)(50,106)(51,107)(52,108)(53,109)(54,110)(55,111)
L2 1 MB (0,56)(1,57)(2,58)(3,59)(4,60)(5,61)(6,62)(7,63)(8,64)(9,65)(10,66)(11,67)(12,68)(13,69)(14,70)(15,71)(16,72)(17,73)(18,74)(19,75)(20,76)(21,77)(22,78)(23,79)(24,80)(25,81)(26,82)(27,83)(28,84)(29,85)(30,86)(31,87)(32,88)(33,89)(34,90)(35,91)(36,92)(37,93)(38,94)(39,95)(40,96)(41,97)(42,98)(43,99)(44,100)(45,101)(46,102)(47,103)(48,104)(49,105)(50,106)(51,107)(52,108)(53,109)(54,110)(55,111)
L3 42 MB (0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83)(28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111)

VTune version : 2021.6.0

Thanks.

侯玉山 · ‎10-20-2021

hi,

Through your support, the previous problems have been solved and the collection can run successfully. However, when I view the collection results, I can't see the collected data.

Then I use the VPP collect start command to collect. After collection, I check the vpp-collect.log file and report this error:

ipmwatch: error while loading shared libraries: libsafec-3.3.so.3: cannot open shared object file: No such file or directory

Is this "libsafe-3.3. So. 3" dependent on a module of oneapi, Can I import from a module.

thank you

AthiraM_Intel · ‎10-21-2021

Hi,

Could you please share the result folder and the complete log file?

Also share the sample reproducer and the exact steps to reproduce this error.

Thanks.

侯玉山 · ‎10-25-2021

Hi,

I used the following steps to perform the collection:

module load vtune/2021.8.0-nda

source vtune/2021.8.0-nda/vpp/collecter/vpp-collect-vars.sh

vpp-collect start -c "comment" -d /data/test_for_vtune_dir/1026_vpp-collect_dir/

Output on the command line:

[root@c1 collector]# vpp-collect start -c "comment" -d /data/test_for_vtune_dir/1026_vpp-collect_dir/

WARNING: Intel Persistent Memory devices could not be detected by PMWatch.
For more details, see /root/vpp-collect.log

Warning: PMU counter(s) [GP0 GP1 GP2 GP3 GP4 GP5 GP6 GP7 ] is/are already in use by other software and the data collected on these counter(s) may be incorrect
Gathering Platform Profiler collection data. Run vpp-collect stop to finish the collection.
[root@c1 collector]# vpp-collect stop
Collection stopped.
Collection results saved in /data/test_for_vtune_dir/1026_vpp-collect_dir/c1_20211026-1017.tar.gz.

vpp-collect.log and c1_ 20211026-1017.tar.gz I put it in the attachment.

Thanks.

侯玉山 · ‎10-25-2021

Hi,

Sorry, The last vpp-collect.log attachment is the log after collection. The current vpp-collect.log attachment is the log when collection starts.

Thanks.

AthiraM_Intel · ‎10-26-2021

Hi,

We could see that you are using NDA product, please raise the question in priority customer support. Please find the below link to raise the question:

https://www.intel.com/content/www/us/en/developer/get-help/priority-support.html

We are closing this thread. If you need any additional information, please post a new question as this thread will no longer be monitored by Intel.

Thanks.

侯玉山 · ‎10-28-2021

Hi,

OK, thank you for your help.

Thanks.