From kenmcd@melbourne.sgi.com Sun Jan 16 17:42:31 2005 Received: with ECARTIS (v1.0.0; list pcp); Sun, 16 Jan 2005 17:42:36 -0800 (PST) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.13.0/8.13.0) with SMTP id j0H1gTmV002803 for ; Sun, 16 Jan 2005 17:42:30 -0800 Received: from rattle.melbourne.sgi.com (rattle.melbourne.sgi.com [134.14.55.145]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id MAA02274; Mon, 17 Jan 2005 12:42:16 +1100 Date: Mon, 17 Jan 2005 12:42:16 +1100 From: Ken McDonell To: Olivier Tarnus cc: Jan-Frode Myklebust , Subject: Re: PCP for x86_64 ? In-Reply-To: <41C9A987.7060003@free.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV 0.80/650/Sun Jan 2 19:00:02 2005 clamav-milter version 0.80j on 127.0.0.1 X-Virus-Status: Clean X-archive-position: 430 X-ecartis-version: Ecartis v1.0.0 Sender: pcp-bounce@oss.sgi.com Errors-to: pcp-bounce@oss.sgi.com X-original-sender: kenmcd@melbourne.sgi.com Precedence: bulk X-list: pcp Content-Length: 881 Lines: 28 On Wed, 22 Dec 2004, Olivier Tarnus wrote: > kenmcd@melbourne.sgi.com wrote: > > > Thanks, Jan-Frode. > > > > It should come as no surprise that sgi engineers don't have access to > > x86_64 for pcp testing, so assistance from others is most appreciated. > > > Tell me what could help you... Download the source from oss.sgi.com ... try to rebuild it ... send us patches/fixes ... try running the PCP QA (also available from oss.sgi.com) ... etc. > My only limitation is that i actually MUST use SuSE SLES9, and so can't > upgrade automake/autoconf. I believe PCP is _in_ SLES9, and we've been working with SuSE to reduce differences between what they include in their distribution and what's available on oss.sgi.com. So, I'd definitely be interested in hearing about any problems with PCP and SLES9. > But if i can do anything for pcp, it will be a pleasure :-) > > ... From o.tarnus@free.fr Mon Jan 17 02:01:47 2005 Received: with ECARTIS (v1.0.0; list pcp); Mon, 17 Jan 2005 02:01:53 -0800 (PST) Received: from lxdomino01.domain ([194.235.198.134]) by oss.sgi.com (8.13.0/8.13.0) with ESMTP id j0HA1kAI001448 for ; Mon, 17 Jan 2005 02:01:47 -0800 Received: from [192.168.8.100] ([192.168.8.100]) by lxdomino01.domain (Lotus Domino Release 6.0.2CF1) with ESMTP id 2005011711014316-412614 ; Mon, 17 Jan 2005 11:01:43 +0100 Message-ID: <41EB8D08.7040304@free.fr> Date: Mon, 17 Jan 2005 11:01:44 +0100 From: Olivier Tarnus User-Agent: Mozilla Thunderbird 1.0 (X11/20050104) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ken McDonell CC: pcp@oss.sgi.com Subject: Re: PCP for x86_64 ? References: In-Reply-To: X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-MIMETrack: Itemize by SMTP Server on lxdomino01/KCcom(Release 6.0.2CF1|June 9, 2003) at 17/01/2005 11:01:43, Serialize by Router on lxdomino01/KCcom(Release 6.0.2CF1|June 9, 2003) at 17/01/2005 11:01:46, Serialize complete at 17/01/2005 11:01:46 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Virus-Scanned: ClamAV 0.80/650/Sun Jan 2 19:00:02 2005 clamav-milter version 0.80j on 127.0.0.1 X-Virus-Status: Clean X-archive-position: 431 X-ecartis-version: Ecartis v1.0.0 Sender: pcp-bounce@oss.sgi.com Errors-to: pcp-bounce@oss.sgi.com X-original-sender: o.tarnus@free.fr Precedence: bulk X-list: pcp Content-Length: 2822 Lines: 94 Ken McDonell wrote: >On Wed, 22 Dec 2004, Olivier Tarnus wrote: > > > >>kenmcd@melbourne.sgi.com wrote: >> >> >> >>>Thanks, Jan-Frode. >>> >>>It should come as no surprise that sgi engineers don't have access to >>>x86_64 for pcp testing, so assistance from others is most appreciated. >>> >>> >>> >>Tell me what could help you... >> >> > >Download the source from oss.sgi.com ... try to rebuild it ... send us >patches/fixes ... try running the PCP QA (also available from >oss.sgi.com) ... etc. > > > Hi, Except the previous mentioned problem for compilation, i didn't noticed any special problem. It seems that it was linked with 64 bits C library : Andromeda:~ # ldd -v /usr/share/pcp/bin/pmcd libpcp.so.2 => /usr/lib/libpcp.so.2 (0x0000002a9566c000) libdl.so.2 => /lib64/libdl.so.2 (0x0000002a957af000) libc.so.6 => /lib64/tls/libc.so.6 (0x0000002a958b2000) /lib64/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x0000002a95556000) Version information: /usr/share/pcp/bin/pmcd: libdl.so.2 (GLIBC_2.2.5) => /lib64/libdl.so.2 libc.so.6 (GLIBC_2.3) => /lib64/tls/libc.so.6 libc.so.6 (GLIBC_2.2.5) => /lib64/tls/libc.so.6 /usr/lib/libpcp.so.2: libdl.so.2 (GLIBC_2.2.5) => /lib64/libdl.so.2 libc.so.6 (GLIBC_2.3) => /lib64/tls/libc.so.6 libc.so.6 (GLIBC_2.2.5) => /lib64/tls/libc.so.6 /lib64/libdl.so.2: ld-linux-x86-64.so.2 (GLIBC_PRIVATE) => /lib64/ld-linux-x86-64.so.2 libc.so.6 (GLIBC_2.3) => /lib64/tls/libc.so.6 libc.so.6 (GLIBC_PRIVATE) => /lib64/tls/libc.so.6 libc.so.6 (GLIBC_2.2.5) => /lib64/tls/libc.so.6 /lib64/tls/libc.so.6: ld-linux-x86-64.so.2 (GLIBC_2.2.5) => /lib64/ld-linux-x86-64.so.2 ld-linux-x86-64.so.2 (GLIBC_2.3) => /lib64/ld-linux-x86-64.so.2 ld-linux-x86-64.so.2 (GLIBC_PRIVATE) => /lib64/ld-linux-x86-64.so.2 I only tested the pmcd daemon, but not pmlogger. I can run some QA tools as you suggested, but where can i find them? Searching for "pcp QA" on sgi.com return no result ;-) >>My only limitation is that i actually MUST use SuSE SLES9, and so can't >>upgrade automake/autoconf. >> >> > >I believe PCP is _in_ SLES9, and we've been working with SuSE to reduce >differences between what they include in their distribution and what's >available on oss.sgi.com. So, I'd definitely be interested in hearing >about any problems with PCP and SLES9. > > > > After a little verification, i can confirm that pcp is included in SLES9 for x86 but not in SLES9 for x86_64. Regards >>But if i can do anything for pcp, it will be a pleasure :-) >> >>... >> >> > > > From o.tarnus@free.fr Wed Jan 19 07:12:17 2005 Received: with ECARTIS (v1.0.0; list pcp); Wed, 19 Jan 2005 07:12:23 -0800 (PST) Received: from lxdomino01.domain ([194.235.198.134]) by oss.sgi.com (8.13.0/8.13.0) with ESMTP id j0JFCGmd013767 for ; Wed, 19 Jan 2005 07:12:17 -0800 Received: from [192.168.8.100] ([192.168.8.100]) by lxdomino01.domain (Lotus Domino Release 6.0.2CF1) with ESMTP id 2005011916121504-420931 ; Wed, 19 Jan 2005 16:12:15 +0100 Message-ID: <41EE78CE.8000207@free.fr> Date: Wed, 19 Jan 2005 16:12:14 +0100 From: Olivier Tarnus User-Agent: Mozilla Thunderbird 1.0 (X11/20050104) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ken McDonell CC: pcp@oss.sgi.com Subject: Re: PCP for x86_64 ? References: In-Reply-To: X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-MIMETrack: Itemize by SMTP Server on lxdomino01/KCcom(Release 6.0.2CF1|June 9, 2003) at 19/01/2005 16:12:15, Serialize by Router on lxdomino01/KCcom(Release 6.0.2CF1|June 9, 2003) at 19/01/2005 16:12:17, Serialize complete at 19/01/2005 16:12:17 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Virus-Scanned: ClamAV 0.80/650/Sun Jan 2 19:00:02 2005 clamav-milter version 0.80j on 127.0.0.1 X-Virus-Status: Clean X-archive-position: 432 X-ecartis-version: Ecartis v1.0.0 Sender: pcp-bounce@oss.sgi.com Errors-to: pcp-bounce@oss.sgi.com X-original-sender: o.tarnus@free.fr Precedence: bulk X-list: pcp Content-Length: 2656 Lines: 90 Ken McDonell wrote: >On Wed, 22 Dec 2004, Olivier Tarnus wrote: > > > >>kenmcd@melbourne.sgi.com wrote: >> >> >> >>>Thanks, Jan-Frode. >>> >>>It should come as no surprise that sgi engineers don't have access to >>>x86_64 for pcp testing, so assistance from others is most appreciated. >>> >>> >>> >>Tell me what could help you... >> >> > >Download the source from oss.sgi.com ... try to rebuild it ... send us >patches/fixes ... try running the PCP QA (also available from >oss.sgi.com) ... etc. > > > >>My only limitation is that i actually MUST use SuSE SLES9, and so can't >>upgrade automake/autoconf. >> >> > >I believe PCP is _in_ SLES9, and we've been working with SuSE to reduce >differences between what they include in their distribution and what's >available on oss.sgi.com. So, I'd definitely be interested in hearing >about any problems with PCP and SLES9. > > > > >>But if i can do anything for pcp, it will be a pleasure :-) >> >>... >> >> > > > Hi, Here are some comments on my experiments compiling pcp, and running pcp-qa on linux for x86_64. First of all, installing from sources will not create /var/lib/pcp/pmns/root file... Don't know why, running a ./Rebuild in this directory fix this issue. My other problem was starting scripts, which are REALLY dependant on SuSE or RedHat... Some "simplier" scripts will be greatly appreciated for other ditributions. For example i wanted to create an ebuild for Gentoo Linux, but i wasn't able to understand your startup scripts (sorry for this ;) ) to include them... Or perhaps can you provide a little explanation on the overall startup procedure for a pcp infrastructure... Now, regarding x86_64... Installation was fine except already explained issues regarding automake. I hardly managed to have pcp-qa runing on a SuSE SLES 9 x86_64... One encountered issue was regarding the simple pmda. It won't compile by default on x86_64 and i needed to add -fPIC to compilation options. Maybe are other pmdas affected by this issue. I've not run pcp-qa with much setup or options, but here are my results: Not run: 008 009 073 117 127 129 130 142 144 148 150 151 157 212 215 223 233 257 262 284 290 329 330 331 332 333 334 353377 504 545 584 701 702 Failures: 015 025 051 066 069 081 083 115 116 119 122 123 131 149 158 159 160 183 187 199 272 279 282 306 308 325 340 365 374 375 381 414 446 519 539 572 583 587 603 605 622 640 642 Failed 43 of 392 tests I've NOT configured an rsh access!!! Perhaps that explains so much failures!? Who can i safely send my .bad files (i prefer not post them to the maillist...) ??? Regards... Olivier