Re: 64bit linux (lx64) api still broke with 7.6.3?
I've certainly compiled and modified the ARS Perl code - which is in c - when it was needed for new ARS releases. If you are getting an ARERR 90 it is a connectivity error. Misi is right about -malign-double being needed but that is probably a default with your version of gcc. A 90 is always a connectivity error. An ARS Perl not being ready for the current or installed API results (generally) in compile errors. When you say "link" I am assuming you mean "link to the ARS Server" and not the link step of the build of ARS Perl (ie making the .so's). I would suggest you check that you are issuing the SetServerPort if needed (or else issue an export ARTCPPORT=xxx BEFORE firing your Perl code). This is needed if your server is not using portmapper. To see what's happening, simple set ARAPILOGGING=1 before running your code. Ensure you can ping whatever server you have configured in your Perl app. With APILOGGING set, you will get two log files generated. One will tell you what API calls you are making (I think with arguments) and the other the results of said API calls. Cheers Ben Chernys Senior Software Architect Software Tool House Inc. Canada / Deutschland / Germany Mobile: +49 171 380 2329GMT + 1 + [ DST ] Email:<mailto:ben.cher...@softwaretoolhouse.com> Ben.Chernys _AT_ softwaretoolhouse.com Web: <http://www.softwaretoolhouse.com> www.softwaretoolhouse.com Check out Software Tool House's free Diary Editor. Meta-Update, our premium ARS Data tool, lets you automate your imports, migrations, in no time at all, without programming, without staging forms, without merge workflow. <http://www.softwaretoolhouse.com/> http://www.softwaretoolhouse.com/ From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Nathan Neulinger Sent: December-15-10 18:54 To: arslist@ARSLIST.ORG Subject: Re: 64bit linux (lx64) api still broke with 7.6.3? ** Wanted to let you know that I had a few minutes to get back to this and check - the C API definitely works for me - it's specific to linking against perl. I checked with gdb, the content of the control structure is exactly identical between a simple C test app that does an ARInitialization and then ARVerifyUser and the same code in the ars_Login code in the ARS perl module. The C code returns the proper status, the perl code always gets the ARERR #90 can't encode arguments error. The perl module gets the same error whether compiled with -malign-double or not. I'd say without assistance from BMC on the internals of the AR client library or someone who knows a lot more about how this code works it's going to be difficult to debug. (Or someone with access to the source code of the library who could try compiling arsperl (latest cvs) on lx64 platform to see if they can resolve the issue. -- Nathan On Thu, Sep 16, 2010 at 2:45 AM, Misi Mladoniczky wrote: Hi, Did you use the -malign-double compile option? I have forgotten about that some times, and you get unexpected problems... Best Regards - Misi, RRR AB, http://www.rrr.se Products from RRR Scandinavia: * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. Find these products, and many free tools and utilities, at http://rrr.se. > Ugh. That is sounding like it either is a problem ONLY when linking with > perl, or something else is going on. > > Thank you for checking into this, looks like I need to do some further > testing. If it's specific to linking with perl libs, may wind up not being > able to resolve the problem, but at least will know the specifics of the > problem. > > -- Nathan > > > Nathan Neulinger nn...@mst.edu > Missouri S&T Information Technology(573) 612-1412 > System Administrator - Principal KD0DMH > > >> -Original Message- >> From: Action Request System discussion list(ARSList) ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: 64bit linux (lx64) api still broke with 7.6.3?
Wanted to let you know that I had a few minutes to get back to this and check - the C API definitely works for me - it's specific to linking against perl. I checked with gdb, the content of the control structure is exactly identical between a simple C test app that does an ARInitialization and then ARVerifyUser and the same code in the ars_Login code in the ARS perl module. The C code returns the proper status, the perl code always gets the ARERR #90 can't encode arguments error. The perl module gets the same error whether compiled with -malign-double or not. I'd say without assistance from BMC on the internals of the AR client library or someone who knows a lot more about how this code works it's going to be difficult to debug. (Or someone with access to the source code of the library who could try compiling arsperl (latest cvs) on lx64 platform to see if they can resolve the issue. -- Nathan On Thu, Sep 16, 2010 at 2:45 AM, Misi Mladoniczky wrote: > Hi, > > Did you use the -malign-double compile option? I have forgotten about that > some times, and you get unexpected problems... > > > Best Regards - Misi, RRR AB, http://www.rrr.se > > Products from RRR Scandinavia: > * RRR|License - Not enough Remedy licenses? Save money by optimizing. > * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. > Find these products, and many free tools and utilities, at http://rrr.se. > > > Ugh. That is sounding like it either is a problem ONLY when linking with > > perl, or something else is going on. > > > > Thank you for checking into this, looks like I need to do some further > > testing. If it's specific to linking with perl libs, may wind up not > being > > able to resolve the problem, but at least will know the specifics of the > > problem. > > > > -- Nathan > > > > > > Nathan Neulinger nn...@mst.edu > > Missouri S&T Information Technology(573) 612-1412 > > System Administrator - Principal KD0DMH > > > > > >> -Original Message- > >> From: Action Request System discussion list(ARSList) > >> [mailto:arslist@ARSLIST.ORG ] On Behalf Of Misi > Mladoniczky > >> Sent: Wednesday, September 15, 2010 2:35 PM > >> To: arslist@ARSLIST.ORG > >> Subject: Re: 64bit linux (lx64) api still broke with 7.6.3? > >> > >> Hi, > >> > >> I have just compiled RRR|Chive on 64-bit linux with the 7.6.03 API. It > >> seems to work just fine. > >> > >> I have both tried with and without specifying a TCP-port. > >> > >> These are the libraries I am linking to: > >> LDLIBS = -lar_lx64 -lnsl -lpthread -lcurses -ldl > >> > >> Best Regards - Misi, RRR AB, http://www.rrr.se > >> > >> Products from RRR Scandinavia: > >> * RRR|License - Not enough Remedy licenses? Save money by optimizing. > >> * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy > >> logs. > >> Find these products, and many free tools and utilities, at > >> http://rrr.se. > >> > >> > Does anyone have any suggestions on this? Is it even on the radar of > >> > anyone at BMC? > >> > > >> > -- Nathan > >> > > >> > ------------ > >> > Nathan Neulinger nn...@mst.edu > >> > Missouri S&T Information Technology(573) 612-1412 > >> > System Administrator - Principal KD0DMH > >> > > >> > > >> >> -Original Message- > >> >> From: Action Request System discussion list(ARSList) > >> >> [mailto:arslist@ARSLIST.ORG ] On Behalf Of > Neulinger, Nathan > >> >> Sent: Monday, September 13, 2010 9:44 AM > >> >> To: arslist@ARSLIST.ORG > >> >> Subject: 64bit linux (lx64) api still broke with 7.6.3? > >> >> > >> >> Been trying to get ARSperl working on a 64bit linux host for a while > >> >> (snapshots or CVS), but seem to still be having the various 64bit > >> >> issues, even with the latest 7.6.3 build of the ar API. > >> >> > >> >> Does anyone here have any information on this? > >> >> > >> >> I don't have any remedy/BMC support access as our AR server is > >> hosted > >> >> by > >> >> another campus in our system, but we do use the client and API. > >> >> > >&g
Re: 64bit linux (lx64) api still broke with 7.6.3?
Hi, Did you use the -malign-double compile option? I have forgotten about that some times, and you get unexpected problems... Best Regards - Misi, RRR AB, http://www.rrr.se Products from RRR Scandinavia: * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. Find these products, and many free tools and utilities, at http://rrr.se. > Ugh. That is sounding like it either is a problem ONLY when linking with > perl, or something else is going on. > > Thank you for checking into this, looks like I need to do some further > testing. If it's specific to linking with perl libs, may wind up not being > able to resolve the problem, but at least will know the specifics of the > problem. > > -- Nathan > > > Nathan Neulinger nn...@mst.edu > Missouri S&T Information Technology(573) 612-1412 > System Administrator - Principal KD0DMH > > >> -Original Message- >> From: Action Request System discussion list(ARSList) >> [mailto:arsl...@arslist.org] On Behalf Of Misi Mladoniczky >> Sent: Wednesday, September 15, 2010 2:35 PM >> To: arslist@ARSLIST.ORG >> Subject: Re: 64bit linux (lx64) api still broke with 7.6.3? >> >> Hi, >> >> I have just compiled RRR|Chive on 64-bit linux with the 7.6.03 API. It >> seems to work just fine. >> >> I have both tried with and without specifying a TCP-port. >> >> These are the libraries I am linking to: >> LDLIBS = -lar_lx64 -lnsl -lpthread -lcurses -ldl >> >> Best Regards - Misi, RRR AB, http://www.rrr.se >> >> Products from RRR Scandinavia: >> * RRR|License - Not enough Remedy licenses? Save money by optimizing. >> * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy >> logs. >> Find these products, and many free tools and utilities, at >> http://rrr.se. >> >> > Does anyone have any suggestions on this? Is it even on the radar of >> > anyone at BMC? >> > >> > -- Nathan >> > >> > >> > Nathan Neulinger nn...@mst.edu >> > Missouri S&T Information Technology(573) 612-1412 >> > System Administrator - Principal KD0DMH >> > >> > >> >> -Original Message- >> >> From: Action Request System discussion list(ARSList) >> >> [mailto:arsl...@arslist.org] On Behalf Of Neulinger, Nathan >> >> Sent: Monday, September 13, 2010 9:44 AM >> >> To: arslist@ARSLIST.ORG >> >> Subject: 64bit linux (lx64) api still broke with 7.6.3? >> >> >> >> Been trying to get ARSperl working on a 64bit linux host for a while >> >> (snapshots or CVS), but seem to still be having the various 64bit >> >> issues, even with the latest 7.6.3 build of the ar API. >> >> >> >> Does anyone here have any information on this? >> >> >> >> I don't have any remedy/BMC support access as our AR server is >> hosted >> >> by >> >> another campus in our system, but we do use the client and API. >> >> >> >> Only information I have on the previous bug... is this still not >> >> corrected in 7.6.3? >> >> >> >> defect # SW00330613 >> >> Summary: Problems with 64 Bit AR API Libraries under Linux >> >> Status: Open >> >> Type: Product >> >> Product: AR System >> >> Target Release: Esc 7.5.0 Server >> >> Classification Tentatively Targeted >> >> Version: 7.5 >> >> Target Release Version: Future Patch Release >> >> >> >> The symptom I have still is the can't encode arguments rpc error if >> > the >> >> login port isn't specified, and glibc double free errors. If I >> bypass >> >> the glibc memory checks with MALLOC_CHECK env var, it looks like >> it's >> >> still unable to connect properly. >> >> >> >> I'd really like to get moved off of some legacy 32bit systems that >> are >> >> having to be retained to run the AR api, but having to build an >> entire >> >> separate 32bit perl isn't exactly a reasonable alternative. >> >> >> >> -- Nathan >> >> >> >> >> >> Nathan Neulinger
Re: 64bit linux (lx64) api still broke with 7.6.3?
Ugh. That is sounding like it either is a problem ONLY when linking with perl, or something else is going on. Thank you for checking into this, looks like I need to do some further testing. If it's specific to linking with perl libs, may wind up not being able to resolve the problem, but at least will know the specifics of the problem. -- Nathan Nathan Neulinger nn...@mst.edu Missouri S&T Information Technology(573) 612-1412 System Administrator - Principal KD0DMH > -Original Message- > From: Action Request System discussion list(ARSList) > [mailto:arsl...@arslist.org] On Behalf Of Misi Mladoniczky > Sent: Wednesday, September 15, 2010 2:35 PM > To: arslist@ARSLIST.ORG > Subject: Re: 64bit linux (lx64) api still broke with 7.6.3? > > Hi, > > I have just compiled RRR|Chive on 64-bit linux with the 7.6.03 API. It > seems to work just fine. > > I have both tried with and without specifying a TCP-port. > > These are the libraries I am linking to: > LDLIBS = -lar_lx64 -lnsl -lpthread -lcurses -ldl > > Best Regards - Misi, RRR AB, http://www.rrr.se > > Products from RRR Scandinavia: > * RRR|License - Not enough Remedy licenses? Save money by optimizing. > * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy > logs. > Find these products, and many free tools and utilities, at > http://rrr.se. > > > Does anyone have any suggestions on this? Is it even on the radar of > > anyone at BMC? > > > > -- Nathan > > > > > > Nathan Neulinger nn...@mst.edu > > Missouri S&T Information Technology(573) 612-1412 > > System Administrator - Principal KD0DMH > > > > > >> -Original Message- > >> From: Action Request System discussion list(ARSList) > >> [mailto:arsl...@arslist.org] On Behalf Of Neulinger, Nathan > >> Sent: Monday, September 13, 2010 9:44 AM > >> To: arslist@ARSLIST.ORG > >> Subject: 64bit linux (lx64) api still broke with 7.6.3? > >> > >> Been trying to get ARSperl working on a 64bit linux host for a while > >> (snapshots or CVS), but seem to still be having the various 64bit > >> issues, even with the latest 7.6.3 build of the ar API. > >> > >> Does anyone here have any information on this? > >> > >> I don't have any remedy/BMC support access as our AR server is > hosted > >> by > >> another campus in our system, but we do use the client and API. > >> > >> Only information I have on the previous bug... is this still not > >> corrected in 7.6.3? > >> > >>defect # SW00330613 > >>Summary: Problems with 64 Bit AR API Libraries under Linux > >>Status: Open > >>Type: Product > >>Product: AR System > >>Target Release: Esc 7.5.0 Server > >>Classification Tentatively Targeted > >>Version: 7.5 > >>Target Release Version: Future Patch Release > >> > >> The symptom I have still is the can't encode arguments rpc error if > > the > >> login port isn't specified, and glibc double free errors. If I > bypass > >> the glibc memory checks with MALLOC_CHECK env var, it looks like > it's > >> still unable to connect properly. > >> > >> I'd really like to get moved off of some legacy 32bit systems that > are > >> having to be retained to run the AR api, but having to build an > entire > >> separate 32bit perl isn't exactly a reasonable alternative. > >> > >> -- Nathan > >> > >> > >> Nathan Neulinger nn...@mst.edu > >> Missouri S&T Information Technology(573) 612-1412 > >> System Administrator - Principal KD0DMH > >> > >> > > > ___ > >> > >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > >> attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" > > > > > ___ > > > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > > attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" > > > > -- > > This message was scanned by ESVA and is believed to be clean. > > > > > > ___ > > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
Re: 64bit linux (lx64) api still broke with 7.6.3?
Hi, I have just compiled RRR|Chive on 64-bit linux with the 7.6.03 API. It seems to work just fine. I have both tried with and without specifying a TCP-port. These are the libraries I am linking to: LDLIBS = -lar_lx64 -lnsl -lpthread -lcurses -ldl Best Regards - Misi, RRR AB, http://www.rrr.se Products from RRR Scandinavia: * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. Find these products, and many free tools and utilities, at http://rrr.se. > Does anyone have any suggestions on this? Is it even on the radar of > anyone at BMC? > > -- Nathan > > > Nathan Neulinger nn...@mst.edu > Missouri S&T Information Technology(573) 612-1412 > System Administrator - Principal KD0DMH > > >> -Original Message- >> From: Action Request System discussion list(ARSList) >> [mailto:arsl...@arslist.org] On Behalf Of Neulinger, Nathan >> Sent: Monday, September 13, 2010 9:44 AM >> To: arslist@ARSLIST.ORG >> Subject: 64bit linux (lx64) api still broke with 7.6.3? >> >> Been trying to get ARSperl working on a 64bit linux host for a while >> (snapshots or CVS), but seem to still be having the various 64bit >> issues, even with the latest 7.6.3 build of the ar API. >> >> Does anyone here have any information on this? >> >> I don't have any remedy/BMC support access as our AR server is hosted >> by >> another campus in our system, but we do use the client and API. >> >> Only information I have on the previous bug... is this still not >> corrected in 7.6.3? >> >> defect # SW00330613 >> Summary: Problems with 64 Bit AR API Libraries under Linux >> Status: Open >> Type: Product >> Product: AR System >> Target Release: Esc 7.5.0 Server >> Classification Tentatively Targeted >> Version: 7.5 >> Target Release Version: Future Patch Release >> >> The symptom I have still is the can't encode arguments rpc error if > the >> login port isn't specified, and glibc double free errors. If I bypass >> the glibc memory checks with MALLOC_CHECK env var, it looks like it's >> still unable to connect properly. >> >> I'd really like to get moved off of some legacy 32bit systems that are >> having to be retained to run the AR api, but having to build an entire >> separate 32bit perl isn't exactly a reasonable alternative. >> >> -- Nathan >> >> >> Nathan Neulinger nn...@mst.edu >> Missouri S&T Information Technology(573) 612-1412 >> System Administrator - Principal KD0DMH >> >> > ___ >> >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" > > ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" > > -- > This message was scanned by ESVA and is believed to be clean. > > ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
Re: 64bit linux (lx64) api still broke with 7.6.3?
Does anyone have any suggestions on this? Is it even on the radar of anyone at BMC? -- Nathan Nathan Neulinger nn...@mst.edu Missouri S&T Information Technology(573) 612-1412 System Administrator - Principal KD0DMH > -Original Message- > From: Action Request System discussion list(ARSList) > [mailto:arsl...@arslist.org] On Behalf Of Neulinger, Nathan > Sent: Monday, September 13, 2010 9:44 AM > To: arslist@ARSLIST.ORG > Subject: 64bit linux (lx64) api still broke with 7.6.3? > > Been trying to get ARSperl working on a 64bit linux host for a while > (snapshots or CVS), but seem to still be having the various 64bit > issues, even with the latest 7.6.3 build of the ar API. > > Does anyone here have any information on this? > > I don't have any remedy/BMC support access as our AR server is hosted > by > another campus in our system, but we do use the client and API. > > Only information I have on the previous bug... is this still not > corrected in 7.6.3? > > defect # SW00330613 > Summary: Problems with 64 Bit AR API Libraries under Linux > Status: Open > Type: Product > Product: AR System > Target Release: Esc 7.5.0 Server > Classification Tentatively Targeted > Version: 7.5 > Target Release Version: Future Patch Release > > The symptom I have still is the can't encode arguments rpc error if the > login port isn't specified, and glibc double free errors. If I bypass > the glibc memory checks with MALLOC_CHECK env var, it looks like it's > still unable to connect properly. > > I'd really like to get moved off of some legacy 32bit systems that are > having to be retained to run the AR api, but having to build an entire > separate 32bit perl isn't exactly a reasonable alternative. > > -- Nathan > > > Nathan Neulinger nn...@mst.edu > Missouri S&T Information Technology(573) 612-1412 > System Administrator - Principal KD0DMH > > ___ > > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
64bit linux (lx64) api still broke with 7.6.3?
Been trying to get ARSperl working on a 64bit linux host for a while (snapshots or CVS), but seem to still be having the various 64bit issues, even with the latest 7.6.3 build of the ar API. Does anyone here have any information on this? I don't have any remedy/BMC support access as our AR server is hosted by another campus in our system, but we do use the client and API. Only information I have on the previous bug... is this still not corrected in 7.6.3? defect # SW00330613 Summary: Problems with 64 Bit AR API Libraries under Linux Status: Open Type: Product Product: AR System Target Release: Esc 7.5.0 Server Classification Tentatively Targeted Version: 7.5 Target Release Version: Future Patch Release The symptom I have still is the can't encode arguments rpc error if the login port isn't specified, and glibc double free errors. If I bypass the glibc memory checks with MALLOC_CHECK env var, it looks like it's still unable to connect properly. I'd really like to get moved off of some legacy 32bit systems that are having to be retained to run the AR api, but having to build an entire separate 32bit perl isn't exactly a reasonable alternative. -- Nathan Nathan Neulinger nn...@mst.edu Missouri S&T Information Technology(573) 612-1412 System Administrator - Principal KD0DMH ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
