Hey everyone, I''ve searched through all of the previous posts and tried everything mentioned but I am still getting these messages. Is there anything else I can do? My host machine is running CentOS 5 w/ Xen 3.3.1. My Xen VM is also running CentOS 5. I''ve tried doing: # echo ''hwcap 0 nosegneg'' > /etc/ld.so.conf.d/libc6-xen.conf && ldconfig And rebooted, still happening. I have updated glibc incase I was running an un-patched glibc. I have checked /etc/ld.so.conf.d/kernelcap-2.6.18-92.el5xen.conf and the contents currently read: # hwcap 0 nosegneg Also, if I do a `ldconfig -v -p 2>&1 | grep libc.so` I get the following: [root@web1 ~]# ldconfig -v -p 2>&1 | grep libc.so libc.so.6 (libc6, hwcap: 0x0018000000000000, OS ABI: Linux 2.6.9) => / lib/i686/nosegneg/libc.so.6 libc.so.6 (libc6, OS ABI: Linux 2.6.9) => /lib/libc.so.6 Is there anything else I might be able to do? I am totally lost since that outlines pretty much everything I have read about this problem. The exact messages I get are: May 12 23:55:16 web1 kernel: 4gb seg fixup, process ruby (pid 2170), cs:ip 73:00d52006 May 12 23:55:16 web1 kernel: 4gb seg fixup, process ruby (pid 2170), cs:ip 73:00e78c25 May 12 23:55:16 web1 kernel: 4gb seg fixup, process ruby (pid 2170), cs:ip 73:00673c7d ... Thanks! -- Travis Bell _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello all, I should add, the contents of my /etc/ld.so.conf.d/ kernelcap-2.6.18-92.el5xen.conf does not include the hash (#) I added that by mistake to my email. Thanks again to anyone who can help steer me in the right direction... Cheers, -- Travis Bell On 13/05/2009, at 3:58 PM, Travis Bell wrote:> Hey everyone, > > I''ve searched through all of the previous posts and tried everything > mentioned but I am still getting these messages. Is there anything > else I can do? My host machine is running CentOS 5 w/ Xen 3.3.1. My > Xen VM is also running CentOS 5. > > I''ve tried doing: > > # echo ''hwcap 0 nosegneg'' > /etc/ld.so.conf.d/libc6-xen.conf && > ldconfig > > And rebooted, still happening. > > I have updated glibc incase I was running an un-patched glibc. > > I have checked /etc/ld.so.conf.d/kernelcap-2.6.18-92.el5xen.conf and > the contents currently read: > > # hwcap 0 nosegneg > > Also, if I do a `ldconfig -v -p 2>&1 | grep libc.so` I get the > following: > > [root@web1 ~]# ldconfig -v -p 2>&1 | grep libc.so > libc.so.6 (libc6, hwcap: 0x0018000000000000, OS ABI: Linux 2.6.9) > => /lib/i686/nosegneg/libc.so.6 > libc.so.6 (libc6, OS ABI: Linux 2.6.9) => /lib/libc.so.6 > > Is there anything else I might be able to do? I am totally lost > since that outlines pretty much everything I have read about this > problem. > > The exact messages I get are: > > May 12 23:55:16 web1 kernel: 4gb seg fixup, process ruby (pid 2170), > cs:ip 73:00d52006 > May 12 23:55:16 web1 kernel: 4gb seg fixup, process ruby (pid 2170), > cs:ip 73:00e78c25 > May 12 23:55:16 web1 kernel: 4gb seg fixup, process ruby (pid 2170), > cs:ip 73:00673c7d > ... > > > > Thanks! > > -- > Travis Bell > > > > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 13. Май 2009 03:58, Travis Bell wrote:> Hey everyone, > > I''ve searched through all of the previous posts and tried everything > mentioned but I am still getting these messages. Is there anything else I > can do? My host machine is running CentOS 5 w/ Xen 3.3.1. My Xen VM is > also running CentOS 5.What do you get when you do this: LD_DEBUG=libs /bin/true ? -- Igor Chubin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Igor,
Here''s the output of `LD_DEBUG=libs /bin/true`:
[root@web1 ~]# LD_DEBUG=libs /bin/true
24351: find library=libc.so.6 [0]; searching
24351: search cache=/etc/ld.so.cache
24351: trying file=/lib/i686/nosegneg/libc.so.6
24351:
24351:
24351: prelink checking: ok
24351:
24351: calling init: /lib/i686/nosegneg/libc.so.6
24351:
24351:
24351: initialize program: /bin/true
24351:
24351:
24351: transferring control: /bin/true
24351:
24351:
24351: calling fini: /bin/true [0]
24351:
24351:
24351: calling fini: /lib/i686/nosegneg/libc.so.6 [0]
24351:
[root@web1 ~]#
--
Travis Bell
On May 14, 2009, at 8:49 PM, Igor Chubin wrote:
> On 13. Май 2009 03:58, Travis Bell wrote:
>> Hey everyone,
>>
>> I''ve searched through all of the previous posts and tried
everything
>> mentioned but I am still getting these messages. Is there anything
>> else I
>> can do? My host machine is running CentOS 5 w/ Xen 3.3.1. My Xen VM
>> is
>> also running CentOS 5.
>
>
> What do you get when you do this:
>
> LD_DEBUG=libs /bin/true
>
> ?
>
> --
> Igor Chubin
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On 14. Май 2009 08:58, Travis Bell wrote:> Hi Igor, > > Here''s the output of `LD_DEBUG=libs /bin/true`:The output means that your /etc/ld.so.conf (and its components) is ok. What is the output of LD_DEBUG=libs /usr/bin/ruby ? (press ctrl-d to continue) -- Igor Chubin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Igor,
Thanks for helping me look into this. Here''s the output for ruby:
[root@web1 ~]# LD_DEBUG=libs /usr/local/bin/ruby
27236: find library=librt.so.1 [0]; searching
27236: search cache=/etc/ld.so.cache
27236: trying file=/lib/i686/nosegneg/librt.so.1
27236:
27236: find library=libdl.so.2 [0]; searching
27236: search cache=/etc/ld.so.cache
27236: trying file=/lib/libdl.so.2
27236:
27236: find library=libcrypt.so.1 [0]; searching
27236: search cache=/etc/ld.so.cache
27236: trying file=/lib/libcrypt.so.1
27236:
27236: find library=libm.so.6 [0]; searching
27236: search cache=/etc/ld.so.cache
27236: trying file=/lib/i686/nosegneg/libm.so.6
27236:
27236: find library=libc.so.6 [0]; searching
27236: search cache=/etc/ld.so.cache
27236: trying file=/lib/i686/nosegneg/libc.so.6
27236:
27236: find library=libpthread.so.0 [0]; searching
27236: search cache=/etc/ld.so.cache
27236: trying file=/lib/i686/nosegneg/libpthread.so.0
27236:
27236:
27236: calling init: /lib/i686/nosegneg/libpthread.so.0
27236:
27236:
27236: calling init: /lib/i686/nosegneg/libc.so.6
27236:
27236:
27236: calling init: /lib/i686/nosegneg/libm.so.6
27236:
27236:
27236: calling init: /lib/libcrypt.so.1
27236:
27236:
27236: calling init: /lib/libdl.so.2
27236:
27236:
27236: calling init: /lib/i686/nosegneg/librt.so.1
27236:
27236:
27236: initialize program: /usr/local/bin/ruby
27236:
27236:
27236: transferring control: /usr/local/bin/ruby
27236:
27236:
27236: calling fini: /usr/local/bin/ruby [0]
27236:
27236:
27236: calling fini: /lib/i686/nosegneg/librt.so.1 [0]
27236:
27236:
27236: calling fini: /lib/libdl.so.2 [0]
27236:
27236:
27236: calling fini: /lib/libcrypt.so.1 [0]
27236:
27236:
27236: calling fini: /lib/i686/nosegneg/libm.so.6 [0]
27236:
27236:
27236: calling fini: /lib/i686/nosegneg/libpthread.so.0 [0]
27236:
27236:
27236: calling fini: /lib/i686/nosegneg/libc.so.6 [0]
27236:
[root@web1 ~]#
Cheers,
--
Travis Bell
On May 14, 2009, at 9:31 PM, Igor Chubin wrote:
> On 14. Май 2009 08:58, Travis Bell wrote:
>> Hi Igor,
>>
>> Here''s the output of `LD_DEBUG=libs /bin/true`:
>
>
> The output means that your /etc/ld.so.conf (and its components)
> is ok.
>
> What is the output of
> LD_DEBUG=libs /usr/bin/ruby
> ?
>
> (press ctrl-d to continue)
>
> --
> Igor Chubin
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On 14. Май 2009 09:41, Travis Bell wrote:> Hi Igor, > > Thanks for helping me look into this. Here''s the output for ruby: >Please, show the output of the commands: ldconfig -p | grep libcrypt.so ldconfig -p | grep libdl.so.2> [root@web1 ~]# LD_DEBUG=libs /usr/local/bin/rubyAlso, does the problem occur when you use ruby installed from rpm? -- Igor Chubin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Igor, [root@web1 ~]# ldconfig -p | grep libcrypt.so libcrypt.so.1 (libc6, OS ABI: Linux 2.6.9) => /lib/libcrypt.so.1 libcrypt.so (libc6, OS ABI: Linux 2.6.9) => /usr/lib/libcrypt.so AND [root@web1 ~]# ldconfig -p | grep libdl.so.2 libdl.so.2 (libc6, OS ABI: Linux 2.6.9) => /lib/libdl.so.2 RE: RPM version of Ruby, not sure... never tried. You think that would potentially help? Cheers, -- Travis Bell On May 14, 2009, at 10:31 PM, Igor Chubin wrote:> On 14. Май 2009 09:41, Travis Bell wrote: >> Hi Igor, >> >> Thanks for helping me look into this. Here''s the output for ruby: >> > Please, show the output of the commands: > > ldconfig -p | grep libcrypt.so > ldconfig -p | grep libdl.so.2 > >> [root@web1 ~]# LD_DEBUG=libs /usr/local/bin/ruby > > Also, does the problem occur when you use ruby > installed from rpm? > > -- > Igor Chubin > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 14. Май 2009 10:38, Travis Bell wrote:> Hi Igor, > > [root@web1 ~]# ldconfig -p | grep libcrypt.so > libcrypt.so.1 (libc6, OS ABI: Linux 2.6.9) => /lib/libcrypt.so.1 > libcrypt.so (libc6, OS ABI: Linux 2.6.9) => /usr/lib/libcrypt.so > > AND > > [root@web1 ~]# ldconfig -p | grep libdl.so.2 > libdl.so.2 (libc6, OS ABI: Linux 2.6.9) => /lib/libdl.so.2 > > RE: RPM version of Ruby, not sure... never tried. You think that would > potentially help?Yes, it is very likely that it should help. Two libraries linked with your ruby process are not xenified (they use TLS). These are libcrypt.so and libdl.so. Also, in theory, your ruby process could use TLS itself. I''ve just started CentOS 5.2 installation on Amazon EC2 to check if ruby there uses the same libraries as yours do, and it uses! [root@ip-10-250-7-83:~] ldd `which ruby` linux-gate.so.1 => (0xb7faf000) libruby.so.1.8 => /usr/lib/libruby.so.1.8 (0xb7eb9000) libpthread.so.0 => /lib/i686/nosegneg/libpthread.so.0 (0xb7ea2000) libdl.so.2 => /lib/libdl.so.2 (0xb7e9e000) libcrypt.so.1 => /lib/libcrypt.so.1 (0xb7e6b000) libm.so.6 => /lib/i686/nosegneg/libm.so.6 (0xb7e44000) libc.so.6 => /lib/i686/nosegneg/libc.so.6 (0xb7cfe000) /lib/ld-linux.so.2 (0xb7fb0000) So it''s very likely, that it is your ruby binary that uses TLS itself. Could you try ruby from RPM? -- Igor Chubin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users