> You are correct. /opt/rocks/bin/python is not dynamically link with > libpython.
> So do you have any idea why it is picking up the system wide Python??
> S.
> On 03/02/2012 06:03 PM, Luca Clementi wrote:
>> Dear Steven, >> for some reason anaconda is picking up the system python and not rocks >> python binaries when creating the installer. (System python is compile >> dynamically aka with libpython as an external file).
>> Normally it should pick the /opt/rocks/bin/python python.
>> Luca
>> On Thu, Mar 1, 2012 at 10:00 PM, Steven Lo<s...@hep.caltech.edu> wrote:
>>> Hi,
>>> We continue to debug this problem.
>>> We have replaced the python package with 'rpm --replacepkgs' as >>> suggested:
>>> The reason we suspect the Anaconda build is that we see the following >>> error during the 'make rpm' process:
>>> making "torrent" files for RPMS >>> Buildinstall cmd: ./buildinstall --product "Rocks" --prodpath "RedHat" >>> --version "0.0.0" --release "0"
>>> /state/partition1/rocks-5.3/src/roll/kernel/BUILD/rocks-boot-5.3/enterprise /5/images/x86_64/rocks-dist/x86_64 >>> error: open of d8:announce29:http://10.4.1.1:7625/announce13:creation >>> failed: No such file or directory >>> error: open of
>>> datei1330655008e4:infod6:lengthi1961678e4:name40:anaconda-runtime-11.1.2.19 5-1.x86_64.rpmee >>> failed: No such file or directory >>> Running buildinstall... >>> ~/enterprise/5/images/x86_64/rocks-dist/x86_64/buildinstall.tree.3669 >>> ~/enterprise/5/images/x86_64/anaconda-runtime/usr/lib/anaconda-runtime >>> ~/enterprise/5/images/x86_64/anaconda-runtime/usr/lib/anaconda-runtime
>>> Are these normal error message during the build????????
>>> We still see the following error during the build:
>>> Creating SELinux policy... >>> /usr/bin/python: error while loading shared libraries: >>> libpython2.4.so.1.0: cannot open shared object file: No such file or >>> directory<----- >>> libsemanage.semanage_install_sandbox: genhomedircon returned error code >>> 127.
>>> Any advise on this issue, please ??
>>> Thanks.
>>> Steven.
>>> On 02/22/2012 04:00 PM, Philip Papadopoulos wrote:
>>>> Steven, >>>> you can look at >>>> "yum provides '*/libpython2.4*" >>>> and see which RPMs provide the file. You can attempt a yum reinstall >>>> of the appropriate package. >>>> -P
>>>> not sure what's happen here may be just reinstall >>>> backup your user data and some customer apps
>>>> how big is your cluster? >>>> sorry i donot how to fix your problem, not sure what did you do to >>>> your clusters' frontend
>>>> Sent from my iPad
>>>> On Feb 22, 2012, at 17:47, Steven Lo<s...@hep.caltech.edu >>>> <mailto:s...@hep.caltech.edu>> wrote:
>>>> > >>>> > Is this fixable?? >>>> > >>>> > If not, what is our option?? >>>> > >>>> > Thanks..... >>>> > >>>> > Steven..... >>>> > >>>> > >>>> > On 02/22/2012 02:29 PM, Hung-Sheng Tsao (laoTsao) wrote: >>>> >> imho, your frontend python is broken >>>> >> >>>> >> Sent from my iPad >>>> >> >>>> >> On Feb 22, 2012, at 17:22, Steven Lo<s...@hep.caltech.edu >>>> <mailto:s...@hep.caltech.edu>> wrote: >>>> >> >>>> >>> Hi, >>>> >>> >>>> >>> We have problem installing the service pack: >>>> >>> >>>> >>> # which rocks >>>> >>> /opt/rocks/bin/rocks >>>> >>> >>>> >>> # pwd >>>> >>> /export >>>> >>> >>>> >>> # ls -la *.iso >>>> >>> -rw-r--r-- 1 root root 28297216 Aug 13 2010 >>>> service-pack-5.3.1-1.x86_64.disk1.iso >>>> >>> >>>> >>> # wget
>>>> http://www.rocksclusters.org/ftp-site/pub/rocks/rocks-5.3/linux/servi... >>>> >>> >>>> >>> # rocks remove roll service-pack >>>> >>> error - unknown roll name "service-pack"<-- first sign of >>>> trouble >>>> >>> >>>> >>> # rocks set host attr localhost roll_install_on_the_fly true >>>> shadow=yes >>>> >>> >>>> >>> >>>> >>> #rocks add roll service-pack*iso >>>> >>> Traceback (most recent call last): >>>> >>> File "/opt/rocks/bin/rocks", line 264, in ? >>>> >>> command.runWrapper(name, args[i:]) >>>> >>> File >>>> "/opt/rocks/lib/python2.4/site-packages/rocks/commands/__init__.py", >>>> line 1774, in runWrapper >>>> >>> self.run(self._params, self._args) >>>> >>> File
>>>> "/opt/rocks/lib/python2.4/site-packages/rocks/commands/add/roll/__init__.py ", >>>> line 705, in run >>>> >>> roll_handler = RollHandler(self.arch, self.os, self.db) >>>> >>> File
>>>> "/opt/rocks/lib/python2.4/site-packages/rocks/commands/add/roll/__init__.py ", >>>> line 260, in __init__ >>>> >>> os.makedirs(self.cdrom_mount) >>>> >>> File "/opt/rocks/lib/python2.4/os.py", line 159, in makedirs >>>> >>> mkdir(name, mode) >>>> >>> OSError: [Errno 2] No such file or directory: '/mnt/cdrom' >>>> >>> >>>> >>> # rocks add roll ./service-pack-5.3.1-1.x86_64.disk1.iso >>>> >>> Traceback (most recent call last): >>>> >>> File "/opt/rocks/bin/rocks", line 233, in ? >>>> >>> __import__(s) >>>> >>> ValueError: Empty module name >>>> >>> >>>> >>> >>>> >>> Do you have any idea of what's going on?? >>>> >>> >>>> >>> Since we can not find the instruction for 5.3, instead we are >>>> following the instruction for 5.4: >>>> >>>
>>>> http://www.rocksclusters.org/roll-documentation/service-pack/5.4.2/in... >>>> >>> >>>> >>> >>>> >>> Thanks..... >>>> >>> >>>> >>> Steven..... >>>> >>> >>>> >>> >>>> >>> On 02/22/2012 09:49 AM, Steven Lo wrote: >>>> >>>> Hi, >>>> >>>> >>>> >>>> We have not had the chance to apply the service pack yet >>>> since it does >>>> >>>> require system reboot. Unfortunately, this system is also a >>>> home >>>> >>>> directory for user jobs, therefore coordination is required. >>>> >>>> >>>> >>>> Thanks for the test result. >>>> >>>> >>>> >>>> Steven..... >>>> >>>> >>>> >>>> On 02/22/2012 03:30 AM, "Hung-Sheng Tsao (Lao Tsao ??) Ph.D." >>>> wrote: >>>> >>>>> hi >>>> >>>>> Donot know what did you change your system rock-5.3 >>>> >>>>> I just test on rocks5.3 with service pack and follow the >>>> instruction in the bae-user-guide and your instruction on igb >>>> >>>>> 1)able to make rpm with e1000 >>>> >>>>> 2)able to make rpm with both e1000 and igb >>>> >>>>> no python error >>>> >>>>> 3)able to install compute-node >>>> >>>>> regards >>>> >>>>> >>>> >>>>> >>>> >>>>> >>>> >>>>> >>>> >>>>> On 2/21/2012 1:31 AM, Steven Lo wrote: >>>> >>>>>> We need to add device driver (igb with I350 chip set) to >>>> the image kernel >>>> >>>>>> so that we can kickstart the new server. >>>> >>>>>> >>>> >>>>>> This is what we did: >>>> >>>>>> >>>> >>>>>> # cd /export >>>> >>>>>> >>>> >>>>>> # hg clone http://fyp.rocksclusters.org/hg/rocks-5.3 >>>> >>>>>> >>>> >>>>>>
>> You are correct. /opt/rocks/bin/python is not dynamically link with >> libpython.
>> So do you have any idea why it is picking up the system wide Python??
>> S.
>> On 03/02/2012 06:03 PM, Luca Clementi wrote: >>> Dear Steven, >>> for some reason anaconda is picking up the system python and not rocks >>> python binaries when creating the installer. (System python is compile >>> dynamically aka with libpython as an external file).
>>> Normally it should pick the /opt/rocks/bin/python python.
>>> Luca
>>> On Thu, Mar 1, 2012 at 10:00 PM, Steven Lo<s...@hep.caltech.edu> wrote: >>>> Hi,
>>>> We continue to debug this problem.
>>>> We have replaced the python package with 'rpm --replacepkgs' as >>>> suggested:
>>>> The reason we suspect the Anaconda build is that we see the following >>>> error during the 'make rpm' process:
>>>> making "torrent" files for RPMS >>>> Buildinstall cmd: ./buildinstall --product "Rocks" --prodpath "RedHat" >>>> --version "0.0.0" --release "0"
>>>> /state/partition1/rocks-5.3/src/roll/kernel/BUILD/rocks-boot-5.3/enterprise /5/images/x86_64/rocks-dist/x86_64 >>>> error: open of d8:announce29:http://10.4.1.1:7625/announce13:creation >>>> failed: No such file or directory >>>> error: open of
>>>> datei1330655008e4:infod6:lengthi1961678e4:name40:anaconda-runtime-11.1.2.19 5-1.x86_64.rpmee >>>> failed: No such file or directory >>>> Running buildinstall... >>>> ~/enterprise/5/images/x86_64/rocks-dist/x86_64/buildinstall.tree.3669 >>>> ~/enterprise/5/images/x86_64/anaconda-runtime/usr/lib/anaconda-runtime >>>> ~/enterprise/5/images/x86_64/anaconda-runtime/usr/lib/anaconda-runtime
>>>> Are these normal error message during the build????????
>>>> We still see the following error during the build:
>>>> Creating SELinux policy... >>>> /usr/bin/python: error while loading shared libraries: >>>> libpython2.4.so.1.0: cannot open shared object file: No such file or >>>> directory<----- >>>> libsemanage.semanage_install_sandbox: genhomedircon returned error code >>>> 127.
>>>> Any advise on this issue, please ??
>>>> Thanks.
>>>> Steven.
>>>> On 02/22/2012 04:00 PM, Philip Papadopoulos wrote: >>>>> Steven, >>>>> you can look at >>>>> "yum provides '*/libpython2.4*" >>>>> and see which RPMs provide the file. You can attempt a yum reinstall >>>>> of the appropriate package. >>>>> -P
>>>>> >>> #rocks add roll service-pack*iso >>>>> >>> Traceback (most recent call last): >>>>> >>> File "/opt/rocks/bin/rocks", line 264, in ? >>>>> >>> command.runWrapper(name, args[i:]) >>>>> >>> File >>>>> "/opt/rocks/lib/python2.4/site-packages/rocks/commands/__init__.py", >>>>> line 1774, in runWrapper >>>>> >>> self.run(self._params, self._args) >>>>> >>> File
>>>>> "/opt/rocks/lib/python2.4/site-packages/rocks/commands/add/roll/__init__.py ", >>>>> line 705, in run >>>>> >>> roll_handler = RollHandler(self.arch, self.os, self.db) >>>>> >>> File
>>>>> "/opt/rocks/lib/python2.4/site-packages/rocks/commands/add/roll/__init__.py ", >>>>> line 260, in __init__ >>>>> >>> os.makedirs(self.cdrom_mount) >>>>> >>> File "/opt/rocks/lib/python2.4/os.py", line 159, in makedirs >>>>> >>> mkdir(name, mode) >>>>> >>> OSError: [Errno 2] No such file or directory: '/mnt/cdrom'
>>>>> >>> # rocks add roll ./service-pack-5.3.1-1.x86_64.disk1.iso >>>>> >>> Traceback (most recent call last): >>>>> >>> File "/opt/rocks/bin/rocks", line 233, in ? >>>>> >>> __import__(s) >>>>> >>> ValueError: Empty module name
>>>>> >>> Do you have any idea of what's going on??
>>>>> >>> Since we can not find the instruction for 5.3, instead we are >>>>> following the instruction for 5.4:
>>>>> >>> On 02/22/2012 09:49 AM, Steven Lo wrote: >>>>> >>>> Hi,
>>>>> >>>> We have not had the chance to apply the service pack yet >>>>> since it does >>>>> >>>> require system reboot. Unfortunately, this system is also a >>>>> home >>>>> >>>> directory for user jobs, therefore coordination is required.
>>>>> >>>> Thanks for the test result.
>>>>> >>>> Steven.....
>>>>> >>>> On 02/22/2012 03:30 AM, "Hung-Sheng Tsao (Lao Tsao ??) Ph.D." >>>>> wrote: >>>>> >>>>> hi >>>>> >>>>> Donot know what did you change your system rock-5.3 >>>>> >>>>> I just test on rocks5.3 with service pack and follow the >>>>> instruction in the bae-user-guide and your instruction on igb
Hey Steven, The supported configuration with rocks is with SELinux disable. Enabling SELinux generally can cause problem, so I would try disabling it, rebooting, and then recompiling.
>>> You are correct. /opt/rocks/bin/python is not dynamically link with >>> libpython.
>>> So do you have any idea why it is picking up the system wide Python??
>>> S.
>>> On 03/02/2012 06:03 PM, Luca Clementi wrote: >>>> Dear Steven, >>>> for some reason anaconda is picking up the system python and not rocks >>>> python binaries when creating the installer. (System python is compile >>>> dynamically aka with libpython as an external file).
>>>> Normally it should pick the /opt/rocks/bin/python python.
>>>> Luca
>>>> On Thu, Mar 1, 2012 at 10:00 PM, Steven Lo<s...@hep.caltech.edu> wrote: >>>>> Hi,
>>>>> We continue to debug this problem.
>>>>> We have replaced the python package with 'rpm --replacepkgs' as >>>>> suggested:
>>>>> The reason we suspect the Anaconda build is that we see the following >>>>> error during the 'make rpm' process:
>>>>> making "torrent" files for RPMS >>>>> Buildinstall cmd: ./buildinstall --product "Rocks" --prodpath "RedHat" >>>>> --version "0.0.0" --release "0"
>>>>> /state/partition1/rocks-5.3/src/roll/kernel/BUILD/rocks-boot-5.3/enterprise /5/images/x86_64/rocks-dist/x86_64 >>>>> error: open of d8:announce29:http://10.4.1.1:7625/announce13:creation >>>>> failed: No such file or directory >>>>> error: open of
>>>>> datei1330655008e4:infod6:lengthi1961678e4:name40:anaconda-runtime-11.1.2.19 5-1.x86_64.rpmee >>>>> failed: No such file or directory >>>>> Running buildinstall... >>>>> ~/enterprise/5/images/x86_64/rocks-dist/x86_64/buildinstall.tree.3669 >>>>> ~/enterprise/5/images/x86_64/anaconda-runtime/usr/lib/anaconda-runtime >>>>> ~/enterprise/5/images/x86_64/anaconda-runtime/usr/lib/anaconda-runtime
>>>>> Are these normal error message during the build????????
>>>>> We still see the following error during the build:
>>>>> Creating SELinux policy... >>>>> /usr/bin/python: error while loading shared libraries: >>>>> libpython2.4.so.1.0: cannot open shared object file: No such file or >>>>> directory<----- >>>>> libsemanage.semanage_install_sandbox: genhomedircon returned error code >>>>> 127.
>>>>> Any advise on this issue, please ??
>>>>> Thanks.
>>>>> Steven.
>>>>> On 02/22/2012 04:00 PM, Philip Papadopoulos wrote: >>>>>> Steven, >>>>>> you can look at >>>>>> "yum provides '*/libpython2.4*" >>>>>> and see which RPMs provide the file. You can attempt a yum reinstall >>>>>> of the appropriate package. >>>>>> -P
>>>>>> not sure what's happen here may be just reinstall >>>>>> backup your user data and some customer apps
>>>>>> how big is your cluster? >>>>>> sorry i donot how to fix your problem, not sure what did you do to >>>>>> your clusters' frontend
>>>>>> Sent from my iPad
>>>>>> On Feb 22, 2012, at 17:47, Steven Lo<s...@hep.caltech.edu >>>>>> <mailto:s...@hep.caltech.edu>> wrote:
>>>>>> > >>>>>> > Is this fixable?? >>>>>> > >>>>>> > If not, what is our option?? >>>>>> > >>>>>> > Thanks..... >>>>>> > >>>>>> > Steven..... >>>>>> > >>>>>> > >>>>>> > On 02/22/2012 02:29 PM, Hung-Sheng Tsao (laoTsao) wrote: >>>>>> >> imho, your frontend python is broken >>>>>> >> >>>>>> >> Sent from my iPad >>>>>> >> >>>>>> >> On Feb 22, 2012, at 17:22, Steven Lo<s...@hep.caltech.edu >>>>>> <mailto:s...@hep.caltech.edu>> wrote: >>>>>> >> >>>>>> >>> Hi, >>>>>> >>> >>>>>> >>> We have problem installing the service pack: >>>>>> >>> >>>>>> >>> # which rocks >>>>>> >>> /opt/rocks/bin/rocks >>>>>> >>> >>>>>> >>> # pwd >>>>>> >>> /export >>>>>> >>> >>>>>> >>> # ls -la *.iso >>>>>> >>> -rw-r--r-- 1 root root 28297216 Aug 13 2010 >>>>>> service-pack-5.3.1-1.x86_64.disk1.iso >>>>>> >>> >>>>>> >>> # wget
>>>>>> http://www.rocksclusters.org/ftp-site/pub/rocks/rocks-5.3/linux/servi... >>>>>> >>> >>>>>> >>> # rocks remove roll service-pack >>>>>> >>> error - unknown roll name "service-pack"<-- first sign of >>>>>> trouble >>>>>> >>> >>>>>> >>> # rocks set host attr localhost roll_install_on_the_fly true >>>>>> shadow=yes >>>>>> >>> >>>>>> >>> >>>>>> >>> #rocks add roll service-pack*iso >>>>>> >>> Traceback (most recent call last): >>>>>> >>> File "/opt/rocks/bin/rocks", line 264, in ? >>>>>> >>> command.runWrapper(name, args[i:]) >>>>>> >>> File >>>>>> "/opt/rocks/lib/python2.4/site-packages/rocks/commands/__init__.py", >>>>>> line 1774, in runWrapper >>>>>> >>> self.run(self._params, self._args) >>>>>> >>> File
>>>>>> "/opt/rocks/lib/python2.4/site-packages/rocks/commands/add/roll/__init__.py ", >>>>>> line 705, in run >>>>>> >>> roll_handler = RollHandler(self.arch, self.os, self.db) >>>>>> >>> File
>>>>>> "/opt/rocks/lib/python2.4/site-packages/rocks/commands/add/roll/__init__.py ", >>>>>> line 260, in __init__ >>>>>> >>> os.makedirs(self.cdrom_mount) >>>>>> >>> File "/opt/rocks/lib/python2.4/os.py", line 159, in makedirs >>>>>> >>> mkdir(name, mode) >>>>>> >>> OSError: [Errno 2] No such file or directory: '/mnt/cdrom' >>>>>> >>> >>>>>> >>> # rocks add roll ./service-pack-5.3.1-1.x86_64.disk1.iso >>>>>> >>> Traceback (most recent call last): >>>>>> >>> File "/opt/rocks/bin/rocks", line 233, in ? >>>>>> >>> __import__(s) >>>>>> >>> ValueError: Empty module name >>>>>> >>> >>>>>> >>> >>>>>> >>> Do you have any idea of what's going on?? >>>>>> >>> >>>>>> >>> Since we can not find the instruction for 5.3, instead we are >>>>>> following
We will try disabling SELinux, rebooting and recompiling.
We found this thread before but not sure if that will work. I guess it's worth a try. However, where can we fetch the newer version of vmlinuz and initrd.img?? For which version of Rocks??
> Hey Steven, > The supported configuration with rocks is with SELinux disable. > Enabling SELinux generally can cause problem, so I would try disabling > it, rebooting, and then recompiling.
>>>> You are correct. /opt/rocks/bin/python is not dynamically link with >>>> libpython.
>>>> So do you have any idea why it is picking up the system wide Python??
>>>> S.
>>>> On 03/02/2012 06:03 PM, Luca Clementi wrote: >>>>> Dear Steven, >>>>> for some reason anaconda is picking up the system python and not rocks >>>>> python binaries when creating the installer. (System python is compile >>>>> dynamically aka with libpython as an external file).
>>>>> Normally it should pick the /opt/rocks/bin/python python.
>>>>> Luca
>>>>> On Thu, Mar 1, 2012 at 10:00 PM, Steven Lo<s...@hep.caltech.edu> wrote: >>>>>> Hi,
>>>>>> We continue to debug this problem.
>>>>>> We have replaced the python package with 'rpm --replacepkgs' as >>>>>> suggested:
>>>>>> The reason we suspect the Anaconda build is that we see the following >>>>>> error during the 'make rpm' process:
>>>>>> making "torrent" files for RPMS >>>>>> Buildinstall cmd: ./buildinstall --product "Rocks" --prodpath "RedHat" >>>>>> --version "0.0.0" --release "0"
>>>>>> /state/partition1/rocks-5.3/src/roll/kernel/BUILD/rocks-boot-5.3/enterprise /5/images/x86_64/rocks-dist/x86_64 >>>>>> error: open of d8:announce29:http://10.4.1.1:7625/announce13:creation >>>>>> failed: No such file or directory >>>>>> error: open of
>>>>>> datei1330655008e4:infod6:lengthi1961678e4:name40:anaconda-runtime-11.1.2.19 5-1.x86_64.rpmee >>>>>> failed: No such file or directory >>>>>> Running buildinstall... >>>>>> ~/enterprise/5/images/x86_64/rocks-dist/x86_64/buildinstall.tree.3669 >>>>>> ~/enterprise/5/images/x86_64/anaconda-runtime/usr/lib/anaconda-runtime >>>>>> ~/enterprise/5/images/x86_64/anaconda-runtime/usr/lib/anaconda-runtime
>>>>>> Are these normal error message during the build????????
>>>>>> We still see the following error during the build:
>>>>>> Creating SELinux policy... >>>>>> /usr/bin/python: error while loading shared libraries: >>>>>> libpython2.4.so.1.0: cannot open shared object file: No such file or >>>>>> directory<----- >>>>>> libsemanage.semanage_install_sandbox: genhomedircon returned error code >>>>>> 127.
>>>>>> Any advise on this issue, please ??
>>>>>> Thanks.
>>>>>> Steven.
>>>>>> On 02/22/2012 04:00 PM, Philip Papadopoulos wrote: >>>>>>> Steven, >>>>>>> you can look at >>>>>>> "yum provides '*/libpython2.4*" >>>>>>> and see which RPMs provide the file. You can attempt a yum reinstall >>>>>>> of the appropriate package. >>>>>>> -P
>>>>>>> >>> #rocks add roll service-pack*iso >>>>>>> >>> Traceback (most recent call last): >>>>>>> >>> File "/opt/rocks/bin/rocks", line 264, in ? >>>>>>> >>> command.runWrapper(name, args[i:]) >>>>>>> >>> File >>>>>>> "/opt/rocks/lib/python2.4/site-packages/rocks/commands/__init__.py", >>>>>>> line 1774, in runWrapper >>>>>>> >>> self.run(self._params, self._args) >>>>>>> >>> File
>>>>>>> "/opt/rocks/lib/python2.4/site-packages/rocks/commands/add/roll/__init__.py ", >>>>>>> line 705, in run >>>>>>> >>> roll_handler = RollHandler(self.arch, self.os, self.db) >>>>>>> >>> File
>>>>>>> "/opt/rocks/lib/python2.4/site-packages/rocks/commands/add/roll/__init__.py ", >>>>>>> line 260, in __init__ >>>>>>> >>> os.makedirs(self.cdrom_mount) >>>>>>> >>> File "/opt/rocks/lib/python2.4/os.py", line 159, in makedirs >>>>>>> >>> mkdir(name, mode) >>>>>>> >>> OSError: [Errno 2] No such file or directory: '/mnt/cdrom'
>>>>>>> >>> # rocks add roll ./service-pack-5.3.1-1.x86_64.disk1.iso >>>>>>> >>> Traceback (most recent call last): >>>>>>> >>> File "/opt/rocks/bin/rocks", line
Hi , Its been a long time that I did not post an email to this list ;-)
I try to install the latest rocks distribution and I run again (like the old time) the problem of attributing the wrong ethernet card for the public and private Internet interface.
Apparently , there's nothing new to fix that problem , even thought eth1 is plug to the public network ( with a DHCP server ), Rock choose it as eth0 (private).
I could not find any info about it (WIKI, FAQ, ....) , I can't even search the archive ,when checking archive threads one by one I find one equivalent question ... unanswered !
During my search in the documentation I ran into the swap interface command. Can I do an install and swap eth1 and eth0 ? How can I resolve this problem.
BTW why there's no search option on the mailing list archive , I kind of remember that there were one in the past , right ?
Thanks for any help
Chris
-- -------------------------------------------------------------------------- Christophe Guilbert, Ph.D. Mission Bay Genentech Hall UCSF, Department of Pharmaceutical Chemistry 600 16th Street, Suite # S-126-D Genentech Hall, MC 2280 San Francisco, CA 94158-2517 Office : 415-476-0707 Office fax : 415-476-0688 Email: cguilb...@picasso.ucsf.edu http://mondale.ucsf.edu -------------------------------------------------------------------------- In a world without walls and fences, who needs Windows and Gates? - Sun Microsystems
I was reading some Intel document online which they said from redhat 5.5 on, aka centos 5.5 (but i wouldn't relay to much on this).
I will send you a link to download the development version of rocks 5.7.
First you should fix your issue (you can't kickstart node), replacing the buggy rpm you produced with the original working rpm from your backup and verify that everything works properly (you can kickstart compute nodes).
Be careful because you can make the front-end unbootable, I would first test the commands on a compute node.
On Tue, Mar 6, 2012 at 3:32 PM, Steven Lo <s...@hep.caltech.edu> wrote:
> Hi Luca,
> We will try disabling SELinux, rebooting and recompiling.
> We found this thread before but not sure if that will work. I guess it's > worth a try. However, where can we fetch the newer version of > vmlinuz and initrd.img?? For which version of Rocks??
> Thanks.....
> Steven.....
> On 03/06/2012 02:53 PM, Luca Clementi wrote: >> Hey Steven, >> The supported configuration with rocks is with SELinux disable. >> Enabling SELinux generally can cause problem, so I would try disabling >> it, rebooting, and then recompiling.
>>>>> You are correct. /opt/rocks/bin/python is not dynamically link with >>>>> libpython.
>>>>> So do you have any idea why it is picking up the system wide Python??
>>>>> S.
>>>>> On 03/02/2012 06:03 PM, Luca Clementi wrote: >>>>>> Dear Steven, >>>>>> for some reason anaconda is picking up the system python and not rocks >>>>>> python binaries when creating the installer. (System python is compile >>>>>> dynamically aka with libpython as an external file).
>>>>>> Normally it should pick the /opt/rocks/bin/python python.
>>>>>> Luca
>>>>>> On Thu, Mar 1, 2012 at 10:00 PM, Steven Lo<s...@hep.caltech.edu> wrote: >>>>>>> Hi,
>>>>>>> We continue to debug this problem.
>>>>>>> We have replaced the python package with 'rpm --replacepkgs' as >>>>>>> suggested:
>>>>>>> The reason we suspect the Anaconda build is that we see the following >>>>>>> error during the 'make rpm' process:
>>>>>>> making "torrent" files for RPMS >>>>>>> Buildinstall cmd: ./buildinstall --product "Rocks" --prodpath "RedHat" >>>>>>> --version "0.0.0" --release "0"
>>>>>>> /state/partition1/rocks-5.3/src/roll/kernel/BUILD/rocks-boot-5.3/enterprise /5/images/x86_64/rocks-dist/x86_64 >>>>>>> error: open of d8:announce29:http://10.4.1.1:7625/announce13:creation >>>>>>> failed: No such file or directory >>>>>>> error: open of
>>>>>>> datei1330655008e4:infod6:lengthi1961678e4:name40:anaconda-runtime-11.1.2.19 5-1.x86_64.rpmee >>>>>>> failed: No such file or directory >>>>>>> Running buildinstall... >>>>>>> ~/enterprise/5/images/x86_64/rocks-dist/x86_64/buildinstall.tree.3669 >>>>>>> ~/enterprise/5/images/x86_64/anaconda-runtime/usr/lib/anaconda-runtime >>>>>>> ~/enterprise/5/images/x86_64/anaconda-runtime/usr/lib/anaconda-runtime
>>>>>>> Are these normal error message during the build????????
>>>>>>> We still see the following error during the build:
>>>>>>> Creating SELinux policy... >>>>>>> /usr/bin/python: error while loading shared libraries: >>>>>>> libpython2.4.so.1.0: cannot open shared object file: No such file or >>>>>>> directory<----- >>>>>>> libsemanage.semanage_install_sandbox: genhomedircon returned error code >>>>>>> 127.
>>>>>>> Any advise on this issue, please ??
>>>>>>> Thanks.
>>>>>>> Steven.
>>>>>>> On 02/22/2012 04:00 PM, Philip Papadopoulos wrote: >>>>>>>> Steven, >>>>>>>> you can look at >>>>>>>> "yum provides '*/libpython2.4*" >>>>>>>> and see which RPMs provide the file. You can attempt a yum reinstall >>>>>>>> of the appropriate package. >>>>>>>> -P
cguilb...@picasso.ucsf.edu> wrote: > Hi , > Its been a long time that I did not post an email to this list ;-)
> I try to install the latest rocks distribution and I run again (like the > old time) the problem of attributing the wrong ethernet card for the > public and private Internet interface.
> Apparently , there's nothing new to fix that problem , even thought eth1 > is plug to the public network ( with a DHCP server ), Rock choose it as > eth0 (private).
> I could not find any info about it (WIKI, FAQ, ....) , I can't even search > the archive ,when checking archive threads one by one I find one > equivalent question ... unanswered !
> During my search in the documentation I ran into the swap interface > command. Can I do an install and swap eth1 and eth0 ? > How can I resolve this problem.
> BTW why there's no search option on the mailing list archive , I kind of > remember that there were one in the past , right ?
> Thanks for any help
> Chris
> -- > ------------------------------**------------------------------** > -------------- > Christophe Guilbert, Ph.D. > Mission Bay Genentech Hall > UCSF, Department of Pharmaceutical Chemistry > 600 16th Street, Suite # S-126-D > Genentech Hall, MC 2280 San Francisco, CA 94158-2517 > Office : 415-476-0707 > Office fax : 415-476-0688 > Email: cguilb...@picasso.ucsf.edu > http://mondale.ucsf.edu > ------------------------------**------------------------------** > -------------- > In a world without walls and fences, > who needs Windows and Gates? > - Sun Microsystems
> If you don't stop the network service prior to this, linux seems to hang > on > shutting down the network service and hangs.
> On Tue, Mar 6, 2012 at 8:01 PM, Christophe Guilbert < > cguilb...@picasso.ucsf.edu> wrote:
> > Hi , > > Its been a long time that I did not post an email to this list ;-)
> > I try to install the latest rocks distribution and I run again (like > the > > old time) the problem of attributing the wrong ethernet card for the > > public and private Internet interface.
> > Apparently , there's nothing new to fix that problem , even thought > eth1 > > is plug to the public network ( with a DHCP server ), Rock choose it as > > eth0 (private).
> > I could not find any info about it (WIKI, FAQ, ....) , I can't even > search > > the archive ,when checking archive threads one by one I find one > > equivalent question ... unanswered !
> > During my search in the documentation I ran into the swap interface > > command. Can I do an install and swap eth1 and eth0 ? > > How can I resolve this problem.
> > BTW why there's no search option on the mailing list archive , I kind > of > > remember that there were one in the past , right ?
> > Thanks for any help
> > Chris
> > -- > > ------------------------------**------------------------------** > > -------------- > > Christophe Guilbert, Ph.D. > > Mission Bay Genentech Hall > > UCSF, Department of Pharmaceutical Chemistry > > 600 16th Street, Suite # S-126-D > > Genentech Hall, MC 2280 San Francisco, CA 94158-2517 > > Office : 415-476-0707 > > Office fax : 415-476-0688 > > Email: cguilb...@picasso.ucsf.edu > > http://mondale.ucsf.edu > > ------------------------------**------------------------------** > > -------------- > > In a world without walls and fences, > > who needs Windows and Gates? > > - Sun Microsystems
> -------------- next part -------------- > An HTML attachment was scrubbed... > URL: https://lists.sdsc.edu/pipermail/npaci-rocks- > discussion/attachments/20120306/d2fdaf1f/attachment.html
________________________________ This message contains information that may be confidential, privileged or otherwise protected by law from disclosure. It is intended for the exclusive use of the Addressee(s). Unless you are the addressee or authorized agent of the addressee, you may not review, copy, distribute or disclose to anyone the message or any information contained within. If you have received this message in error, please contact the sender by electronic reply to em...@environcorp.com and immediately delete all copies of the message.
We have tried disable SELinux, reboot the system and then recompile. Unfortunately, result with same error.
We will try reverse to the point where we can kickstart nodes. We will also try the 5.7 kernel disk and see if the kernel (with the driver that we need) that can recognize the onboard ethernet port.
> I was reading some Intel document online which they said from redhat > 5.5 on, aka centos 5.5 (but i wouldn't relay to much on this).
> I will send you a link to download the development version of rocks 5.7.
> First you should fix your issue (you can't kickstart node), replacing > the buggy rpm you produced with the original working rpm from your > backup and verify that everything works properly (you can kickstart > compute nodes).
> Be careful because you can make the front-end unbootable, I would > first test the commands on a compute node.
> Luca
> On Tue, Mar 6, 2012 at 3:32 PM, Steven Lo<s...@hep.caltech.edu> wrote: >> Hi Luca,
>> We will try disabling SELinux, rebooting and recompiling.
>> We found this thread before but not sure if that will work. I guess it's >> worth a try. However, where can we fetch the newer version of >> vmlinuz and initrd.img?? For which version of Rocks??
>> Thanks.....
>> Steven.....
>> On 03/06/2012 02:53 PM, Luca Clementi wrote: >>> Hey Steven, >>> The supported configuration with rocks is with SELinux disable. >>> Enabling SELinux generally can cause problem, so I would try disabling >>> it, rebooting, and then recompiling.
>>>>>> You are correct. /opt/rocks/bin/python is not dynamically link with >>>>>> libpython.
>>>>>> So do you have any idea why it is picking up the system wide Python??
>>>>>> S.
>>>>>> On 03/02/2012 06:03 PM, Luca Clementi wrote: >>>>>>> Dear Steven, >>>>>>> for some reason anaconda is picking up the system python and not rocks >>>>>>> python binaries when creating the installer. (System python is compile >>>>>>> dynamically aka with libpython as an external file).
>>>>>>> Normally it should pick the /opt/rocks/bin/python python.
>>>>>>> Luca
>>>>>>> On Thu, Mar 1, 2012 at 10:00 PM, Steven Lo<s...@hep.caltech.edu> wrote: >>>>>>>> Hi,
>>>>>>>> We continue to debug this problem.
>>>>>>>> We have replaced the python package with 'rpm --replacepkgs' as >>>>>>>> suggested:
>>>>>>>> The reason we suspect the Anaconda build is that we see the following >>>>>>>> error during the 'make rpm' process:
>>>>>>>> making "torrent" files for RPMS >>>>>>>> Buildinstall cmd: ./buildinstall --product "Rocks" --prodpath "RedHat" >>>>>>>> --version "0.0.0" --release "0"
>>>>>>>> /state/partition1/rocks-5.3/src/roll/kernel/BUILD/rocks-boot-5.3/enterprise /5/images/x86_64/rocks-dist/x86_64 >>>>>>>> error: open of d8:announce29:http://10.4.1.1:7625/announce13:creation >>>>>>>> failed: No such file or directory >>>>>>>> error: open of
>>>>>>>> datei1330655008e4:infod6:lengthi1961678e4:name40:anaconda-runtime-11.1.2.19 5-1.x86_64.rpmee >>>>>>>> failed: No such file or directory >>>>>>>> Running buildinstall... >>>>>>>> ~/enterprise/5/images/x86_64/rocks-dist/x86_64/buildinstall.tree.3669 >>>>>>>> ~/enterprise/5/images/x86_64/anaconda-runtime/usr/lib/anaconda-runtime >>>>>>>> ~/enterprise/5/images/x86_64/anaconda-runtime/usr/lib/anaconda-runtime
>>>>>>>> Are these normal error message during the build????????
>>>>>>>> We still see the following error during the build:
>>>>>>>> Creating SELinux policy... >>>>>>>> /usr/bin/python: error while loading shared libraries: >>>>>>>> libpython2.4.so.1.0: cannot open shared object file: No such file or >>>>>>>> directory<----- >>>>>>>> libsemanage.semanage_install_sandbox: genhomedircon returned error code >>>>>>>> 127.
>>>>>>>> Any advise on this issue, please ??
>>>>>>>> Thanks.
>>>>>>>> Steven.
>>>>>>>> On 02/22/2012 04:00 PM, Philip Papadopoulos wrote: >>>>>>>>> Steven, >>>>>>>>> you can look at >>>>>>>>> "yum provides '*/libpython2.4*" >>>>>>>>> and see which RPMs provide the file. You can attempt a yum reinstall >>>>>>>>> of the appropriate package. >>>>>>>>> -P
> We have tried disable SELinux, reboot the system and then recompile. > Unfortunately, result with same error.
> We will try reverse to the point where we can kickstart nodes. We will > also try the 5.7 kernel disk and see if the kernel (with the driver > that we need) that can recognize the onboard ethernet port.
> Thanks.
> S.
> On 03/06/2012 06:41 PM, Luca Clementi wrote: >> I was reading some Intel document online which they said from redhat >> 5.5 on, aka centos 5.5 (but i wouldn't relay to much on this).
>> I will send you a link to download the development version of rocks 5.7.
>> First you should fix your issue (you can't kickstart node), replacing >> the buggy rpm you produced with the original working rpm from your >> backup and verify that everything works properly (you can kickstart >> compute nodes).
>> Be careful because you can make the front-end unbootable, I would >> first test the commands on a compute node.
>> Luca
>> On Tue, Mar 6, 2012 at 3:32 PM, Steven Lo<s...@hep.caltech.edu> wrote: >>> Hi Luca,
>>> We will try disabling SELinux, rebooting and recompiling.
>>> We found this thread before but not sure if that will work. I guess it's >>> worth a try. However, where can we fetch the newer version of >>> vmlinuz and initrd.img?? For which version of Rocks??
>>> Thanks.....
>>> Steven.....
>>> On 03/06/2012 02:53 PM, Luca Clementi wrote: >>>> Hey Steven, >>>> The supported configuration with rocks is with SELinux disable. >>>> Enabling SELinux generally can cause problem, so I would try disabling >>>> it, rebooting, and then recompiling.
>>>>>>> But I thought that's the way it should be.
>>>>>>> You are correct. /opt/rocks/bin/python is not dynamically link with >>>>>>> libpython.
>>>>>>> So do you have any idea why it is picking up the system wide Python??
>>>>>>> S.
>>>>>>> On 03/02/2012 06:03 PM, Luca Clementi wrote: >>>>>>>> Dear Steven, >>>>>>>> for some reason anaconda is picking up the system python and not rocks >>>>>>>> python binaries when creating the installer. (System python is compile >>>>>>>> dynamically aka with libpython as an external file).
>>>>>>>> Normally it should pick the /opt/rocks/bin/python python.
>>>>>>>> Luca
>>>>>>>> On Thu, Mar 1, 2012 at 10:00 PM, Steven Lo<s...@hep.caltech.edu> wrote: >>>>>>>>> Hi,
>>>>>>>>> We continue to debug this problem.
>>>>>>>>> We have replaced the python package with 'rpm --replacepkgs' as >>>>>>>>> suggested:
>>>>>>>>> The reason we suspect the Anaconda build is that we see the following >>>>>>>>> error during the 'make rpm' process:
>>>>>>>>> making "torrent" files for RPMS >>>>>>>>> Buildinstall cmd: ./buildinstall --product "Rocks" --prodpath "RedHat" >>>>>>>>> --version "0.0.0" --release "0"
>>>>>>>>> /state/partition1/rocks-5.3/src/roll/kernel/BUILD/rocks-boot-5.3/enterprise /5/images/x86_64/rocks-dist/x86_64 >>>>>>>>> error: open of d8:announce29:http://10.4.1.1:7625/announce13:creation >>>>>>>>> failed: No such file or directory >>>>>>>>> error: open of
>>>>>>>>> datei1330655008e4:infod6:lengthi1961678e4:name40:anaconda-runtime-11.1.2.19 5-1.x86_64.rpmee >>>>>>>>> failed: No such file or directory >>>>>>>>> Running buildinstall... >>>>>>>>> ~/enterprise/5/images/x86_64/rocks-dist/x86_64/buildinstall.tree.3669 >>>>>>>>> ~/enterprise/5/images/x86_64/anaconda-runtime/usr/lib/anaconda-runtime >>>>>>>>> ~/enterprise/5/images/x86_64/anaconda-runtime/usr/lib/anaconda-runtime
>>>>>>>>> Are these normal error message during the build????????
>>>>>>>>> We still see the following error during the build:
>>>>>>>>> Creating SELinux policy... >>>>>>>>> /usr/bin/python: error while loading shared libraries: >>>>>>>>> libpython2.4.so.1.0: cannot open shared object file: No such file or >>>>>>>>> directory<----- >>>>>>>>> libsemanage.semanage_install_sandbox: genhomedircon returned error code >>>>>>>>> 127.
>>>>>>>>> Any advise on this issue, please ??
>>>>>>>>> Thanks.
>>>>>>>>> Steven.
>>>>>>>>> On 02/22/2012 04:00 PM, Philip Papadopoulos wrote: >>>>>>>>>> Steven, >>>>>>>>>> you can look at >>>>>>>>>> "yum provides '*/libpython2.4*" >>>>>>>>>> and see which RPMs provide the file. You can attempt a yum reinstall >>>>>>>>>> of the appropriate package. >>>>>>>>>> -P
Thanks for the link. I think we do have the kernel which able to recognize the ethernet port. I guess we need to somehow figure out how to PXE boot the system with Rocks.
Anyone has any idea why /usr/bin/python is called instead of /opt/rocks/bin/python?? If /opt/rocks/bin/python is called then the dynamic python library should not be needed.
> On 3/7/2012 4:12 PM, Steven Lo wrote: >> Hi Luca,
>> Thanks for the link for the kernel roll.
>> We have tried disable SELinux, reboot the system and then recompile. >> Unfortunately, result with same error.
>> We will try reverse to the point where we can kickstart nodes. We will >> also try the 5.7 kernel disk and see if the kernel (with the driver >> that we need) that can recognize the onboard ethernet port.
>> Thanks.
>> S.
>> On 03/06/2012 06:41 PM, Luca Clementi wrote: >>> I was reading some Intel document online which they said from redhat >>> 5.5 on, aka centos 5.5 (but i wouldn't relay to much on this).
>>> I will send you a link to download the development version of rocks 5.7.
>>> First you should fix your issue (you can't kickstart node), replacing >>> the buggy rpm you produced with the original working rpm from your >>> backup and verify that everything works properly (you can kickstart >>> compute nodes).
>>> Be careful because you can make the front-end unbootable, I would >>> first test the commands on a compute node.
>>> Luca
>>> On Tue, Mar 6, 2012 at 3:32 PM, Steven Lo<s...@hep.caltech.edu> wrote: >>>> Hi Luca,
>>>> We will try disabling SELinux, rebooting and recompiling.
>>>> We found this thread before but not sure if that will work. I guess it's >>>> worth a try. However, where can we fetch the newer version of >>>> vmlinuz and initrd.img?? For which version of Rocks??
>>>> Thanks.....
>>>> Steven.....
>>>> On 03/06/2012 02:53 PM, Luca Clementi wrote: >>>>> Hey Steven, >>>>> The supported configuration with rocks is with SELinux disable. >>>>> Enabling SELinux generally can cause problem, so I would try disabling >>>>> it, rebooting, and then recompiling.
>>>>>> It was disabled before but we change it to Permissive and see if will >>>>>> make any >>>>>> difference. Same result.
>>>>>>> And then can you paste the full output of the >>>>>>> make rpm >>>>>>> inside rocks-boot, you said it gives you some error, if I remember well.
>>>>>> I have attached the full output of the 'make -d rpm' process.
>>>>>> Thanks again for your help.
>>>>>> Steven.....
>>>>>>> Sincerely, >>>>>>> Luca
>>>>>>> On Fri, Mar 2, 2012 at 7:15 PM, Steven Lo<s...@hep.caltech.edu> wrote: >>>>>>>> Hi Luca,
>>>>>>>> The search path definitely has /usr/bin in front of /opt/rocks/bin (for >>>>>>>> root):
>>>>>>>> But I thought that's the way it should be.
>>>>>>>> You are correct. /opt/rocks/bin/python is not dynamically link with >>>>>>>> libpython.
>>>>>>>> So do you have any idea why it is picking up the system wide Python??
>>>>>>>> S.
>>>>>>>> On 03/02/2012 06:03 PM, Luca Clementi wrote: >>>>>>>>> Dear Steven, >>>>>>>>> for some reason anaconda is picking up the system python and not rocks >>>>>>>>> python binaries when creating the installer. (System python is compile >>>>>>>>> dynamically aka with libpython as an external file).
>>>>>>>>> Normally it should pick the /opt/rocks/bin/python python.
>>>>>>>>> Luca
>>>>>>>>> On Thu, Mar 1, 2012 at 10:00 PM, Steven Lo<s...@hep.caltech.edu> wrote: >>>>>>>>>> Hi,
>>>>>>>>>> We continue to debug this problem.
>>>>>>>>>> We have replaced the python package with 'rpm --replacepkgs' as >>>>>>>>>> suggested:
>>>>>>>>>> The reason we suspect the Anaconda build is that we see the following >>>>>>>>>> error during the 'make rpm' process:
>>>>>>>>>> making "torrent" files for RPMS >>>>>>>>>> Buildinstall cmd: ./buildinstall --product "Rocks" --prodpath "RedHat" >>>>>>>>>> --version "0.0.0" --release "0"
>>>>>>>>>> /state/partition1/rocks-5.3/src/roll/kernel/BUILD/rocks-boot-5.3/enterprise /5/images/x86_64/rocks-dist/x86_64 >>>>>>>>>> error: open of d8:announce29:http://10.4.1.1:7625/announce13:creation >>>>>>>>>> failed: No such file or directory >>>>>>>>>> error: open of
>>>>>>>>>> datei1330655008e4:infod6:lengthi1961678e4:name40:anaconda-runtime-11.1.2.19 5-1.x86_64.rpmee >>>>>>>>>> failed: No such file or directory >>>>>>>>>> Running buildinstall... >>>>>>>>>> ~/enterprise/5/images/x86_64/rocks-dist/x86_64/buildinstall.tree.3669 >>>>>>>>>> ~/enterprise/5/images/x86_64/anaconda-runtime/usr/lib/anaconda-runtime >>>>>>>>>> ~/enterprise/5/images/x86_64/anaconda-runtime/usr/lib/anaconda-runtime
>>>>>>>>>> Are these normal error message during the build????????
>>>>>>>>>> We still see the following error during the build:
>>>>>>>>>> Creating SELinux policy... >>>>>>>>>> /usr/bin/python: error while loading shared libraries: >>>>>>>>>> libpython2.4.so.1.0: cannot open shared object file: No such file or >>>>>>>>>> directory<----- >>>>>>>>>> libsemanage.semanage_install_sandbox: genhomedircon returned error code >>>>>>>>>> 127.
>>>>>>>>>> Any advise on this issue, please ??
>>>>>>>>>> Thanks.
>>>>>>>>>> Steven.
>>>>>>>>>> On 02/22/2012 04:00 PM, Philip Papadopoulos wrote: >>>>>>>>>>> Steven, >>>>>>>>>>> you can look at >>>>>>>>>>> "yum provides '*/libpython2.4*" >>>>>>>>>>> and see which RPMs provide the file. You can attempt a yum reinstall >>>>>>>>>>> of the appropriate package. >>>>>>>>>>> -P
>>>>>>>>>>> not sure what's happen here may be just reinstall >>>>>>>>>>> backup your user data and some customer apps
>>>>>>>>>>> how big is your cluster? >>>>>>>>>>> sorry i donot how to fix your problem, not sure what did you do to >>>>>>>>>>> your clusters' frontend
>>>>>>>>>>> Sent from my iPad
>>>>>>>>>>> On Feb 22, 2012, at 17:47, Steven Lo<s...@hep.caltech.edu >>>>>>>>>>> <mailto:s...@hep.caltech.edu>> wrote:
> I was reading some Intel document online which they said from redhat > 5.5 on, aka centos 5.5 (but i wouldn't relay to much on this).
> I will send you a link to download the development version of rocks 5.7.
> First you should fix your issue (you can't kickstart node), replacing > the buggy rpm you produced with the original working rpm from your > backup and verify that everything works properly (you can kickstart > compute nodes).
> Be careful because you can make the front-end unbootable, I would > first test the commands on a compute node.
> Luca
> On Tue, Mar 6, 2012 at 3:32 PM, Steven Lo<s...@hep.caltech.edu> wrote: >> Hi Luca,
>> We will try disabling SELinux, rebooting and recompiling.
>> We found this thread before but not sure if that will work. I guess it's >> worth a try. However, where can we fetch the newer version of >> vmlinuz and initrd.img?? For which version of Rocks??
>> Thanks.....
>> Steven.....
>> On 03/06/2012 02:53 PM, Luca Clementi wrote: >>> Hey Steven, >>> The supported configuration with rocks is with SELinux disable. >>> Enabling SELinux generally can cause problem, so I would try disabling >>> it, rebooting, and then recompiling.
>>>>>> You are correct. /opt/rocks/bin/python is not dynamically link with >>>>>> libpython.
>>>>>> So do you have any idea why it is picking up the system wide Python??
>>>>>> S.
>>>>>> On 03/02/2012 06:03 PM, Luca Clementi wrote: >>>>>>> Dear Steven, >>>>>>> for some reason anaconda is picking up the system python and not rocks >>>>>>> python binaries when creating the installer. (System python is compile >>>>>>> dynamically aka with libpython as an external file).
>>>>>>> Normally it should pick the /opt/rocks/bin/python python.
>>>>>>> Luca
>>>>>>> On Thu, Mar 1, 2012 at 10:00 PM, Steven Lo<s...@hep.caltech.edu> wrote: >>>>>>>> Hi,
>>>>>>>> We continue to debug this problem.
>>>>>>>> We have replaced the python package with 'rpm --replacepkgs' as >>>>>>>> suggested:
>>>>>>>> The reason we suspect the Anaconda build is that we see the following >>>>>>>> error during the 'make rpm' process:
>>>>>>>> making "torrent" files for RPMS >>>>>>>> Buildinstall cmd: ./buildinstall --product "Rocks" --prodpath "RedHat" >>>>>>>> --version "0.0.0" --release "0"
>>>>>>>> /state/partition1/rocks-5.3/src/roll/kernel/BUILD/rocks-boot-5.3/enterprise /5/images/x86_64/rocks-dist/x86_64 >>>>>>>> error: open of d8:announce29:http://10.4.1.1:7625/announce13:creation >>>>>>>> failed: No such file or directory >>>>>>>> error: open of
>>>>>>>> datei1330655008e4:infod6:lengthi1961678e4:name40:anaconda-runtime-11.1.2.19 5-1.x86_64.rpmee >>>>>>>> failed: No such file or directory >>>>>>>> Running buildinstall... >>>>>>>> ~/enterprise/5/images/x86_64/rocks-dist/x86_64/buildinstall.tree.3669 >>>>>>>> ~/enterprise/5/images/x86_64/anaconda-runtime/usr/lib/anaconda-runtime >>>>>>>> ~/enterprise/5/images/x86_64/anaconda-runtime/usr/lib/anaconda-runtime
>>>>>>>> Are these normal error message during the build????????
>>>>>>>> We still see the following error during the build:
>>>>>>>> Creating SELinux policy... >>>>>>>> /usr/bin/python: error while loading shared libraries: >>>>>>>> libpython2.4.so.1.0: cannot open shared object file: No such file or >>>>>>>> directory<----- >>>>>>>> libsemanage.semanage_install_sandbox: genhomedircon returned error code >>>>>>>> 127.
>>>>>>>> Any advise on this issue, please ??
>>>>>>>> Thanks.
>>>>>>>> Steven.
>>>>>>>> On 02/22/2012 04:00 PM, Philip Papadopoulos wrote: >>>>>>>>> Steven, >>>>>>>>> you can look at >>>>>>>>> "yum provides '*/libpython2.4*" >>>>>>>>> and see which RPMs provide the file. You can attempt a yum reinstall >>>>>>>>> of the appropriate package. >>>>>>>>> -P
Does any has other recommendation on how to over come the 'python library' problem? We now find out that we need to integrate LSI driver (at install time) so that kickstart can recognize the root disk. That means, the 'make rpm' has to work.
Do you think the following will work: * get a new system and install Rocks 5.3.1 on it. * configure Rocks the same as our existing frontend node * 'make rpm' with new drivers and hope that the Python library will not occur * copy rocks-boot*.rpm to our existing frontend node * 'rocks create distro', 'rpm -Uvh rocks-boot*' and then replace /tftpboot/{initrd.img, vmlinuz}
> On 03/06/2012 06:41 PM, Luca Clementi wrote: >> I was reading some Intel document online which they said from redhat >> 5.5 on, aka centos 5.5 (but i wouldn't relay to much on this).
>> I will send you a link to download the development version of rocks 5.7.
>> First you should fix your issue (you can't kickstart node), replacing >> the buggy rpm you produced with the original working rpm from your >> backup and verify that everything works properly (you can kickstart >> compute nodes).
>> Be careful because you can make the front-end unbootable, I would >> first test the commands on a compute node.
>> Luca
>> On Tue, Mar 6, 2012 at 3:32 PM, Steven Lo<s...@hep.caltech.edu> wrote: >>> Hi Luca,
>>> We will try disabling SELinux, rebooting and recompiling.
>>> We found this thread before but not sure if that will work. I guess it's >>> worth a try. However, where can we fetch the newer version of >>> vmlinuz and initrd.img?? For which version of Rocks??
>>> Thanks.....
>>> Steven.....
>>> On 03/06/2012 02:53 PM, Luca Clementi wrote: >>>> Hey Steven, >>>> The supported configuration with rocks is with SELinux disable. >>>> Enabling SELinux generally can cause problem, so I would try disabling >>>> it, rebooting, and then recompiling.
>>>>>>> But I thought that's the way it should be.
>>>>>>> You are correct. /opt/rocks/bin/python is not dynamically link with >>>>>>> libpython.
>>>>>>> So do you have any idea why it is picking up the system wide Python??
>>>>>>> S.
>>>>>>> On 03/02/2012 06:03 PM, Luca Clementi wrote: >>>>>>>> Dear Steven, >>>>>>>> for some reason anaconda is picking up the system python and not rocks >>>>>>>> python binaries when creating the installer. (System python is compile >>>>>>>> dynamically aka with libpython as an external file).
>>>>>>>> Normally it should pick the /opt/rocks/bin/python python.
>>>>>>>> Luca
>>>>>>>> On Thu, Mar 1, 2012 at 10:00 PM, Steven Lo<s...@hep.caltech.edu> wrote: >>>>>>>>> Hi,
>>>>>>>>> We continue to debug this problem.
>>>>>>>>> We have replaced the python package with 'rpm --replacepkgs' as >>>>>>>>> suggested:
>>>>>>>>> The reason we suspect the Anaconda build is that we see the following >>>>>>>>> error during the 'make rpm' process:
>>>>>>>>> making "torrent" files for RPMS >>>>>>>>> Buildinstall cmd: ./buildinstall --product "Rocks" --prodpath "RedHat" >>>>>>>>> --version "0.0.0" --release "0"
>>>>>>>>> /state/partition1/rocks-5.3/src/roll/kernel/BUILD/rocks-boot-5.3/enterprise /5/images/x86_64/rocks-dist/x86_64 >>>>>>>>> error: open of d8:announce29:http://10.4.1.1:7625/announce13:creation >>>>>>>>> failed: No such file or directory >>>>>>>>> error: open of
>>>>>>>>> datei1330655008e4:infod6:lengthi1961678e4:name40:anaconda-runtime-11.1.2.19 5-1.x86_64.rpmee >>>>>>>>> failed: No such file or directory >>>>>>>>> Running buildinstall... >>>>>>>>> ~/enterprise/5/images/x86_64/rocks-dist/x86_64/buildinstall.tree.3669 >>>>>>>>> ~/enterprise/5/images/x86_64/anaconda-runtime/usr/lib/anaconda-runtime >>>>>>>>> ~/enterprise/5/images/x86_64/anaconda-runtime/usr/lib/anaconda-runtime
>>>>>>>>> Are these normal error message during the build????????
>>>>>>>>> We still see the following error during the build:
>>>>>>>>> Creating SELinux policy... >>>>>>>>> /usr/bin/python: error while loading shared libraries: >>>>>>>>> libpython2.4.so.1.0: cannot open shared object file: No such file or >>>>>>>>> directory<----- >>>>>>>>> libsemanage.semanage_install_sandbox: genhomedircon returned error code >>>>>>>>> 127.
>>>>>>>>> Any advise on this issue, please ??
>>>>>>>>> Thanks.
>>>>>>>>> Steven.
>>>>>>>>> On 02/22/2012 04:00 PM, Philip Papadopoulos wrote: >>>>>>>>>> Steven, >>>>>>>>>> you can look at >>>>>>>>>> "yum provides '*/libpython2.4*" >>>>>>>>>> and see which RPMs provide the file. You can attempt a yum reinstall >>>>>>>>>> of the appropriate package. >>>>>>>>>> -P
if centos 5.7 has all the drivers for your nic and hdd then one way is install rocks 5.4.3 with centos5.7, e.g replace os roll with centos 5.7 dvd
your downtime will be just few hours at most rocks demonstrate the installation of 120 nodes in two hours few years back and that was include the racking the servers
if your FE has two hdd then you can install the new env on the 2nd hdd to preserved the old env just in case -LT
Sent from my iPad
On Mar 11, 2012, at 0:05, Steven Lo <s...@hep.caltech.edu> wrote:
> Does any has other recommendation on how to over come the 'python library' > problem? We now find out that we need to integrate LSI driver (at install time) > so that kickstart can recognize the root disk. That means, the 'make rpm' has > to work.
> Do you think the following will work: > * get a new system and install Rocks 5.3.1 on it. > * configure Rocks the same as our existing frontend node > * 'make rpm' with new drivers and hope that the Python library will not occur > * copy rocks-boot*.rpm to our existing frontend node > * 'rocks create distro', 'rpm -Uvh rocks-boot*' and then replace /tftpboot/{initrd.img, vmlinuz}
> Thanks.
> S.
> On 3/8/2012 5:36 PM, Steven Lo wrote: >> Hi Luca,
>> We have reversed some steps to the point where we can kickstart compute >> nodes.
>> On 03/06/2012 06:41 PM, Luca Clementi wrote: >>> I was reading some Intel document online which they said from redhat >>> 5.5 on, aka centos 5.5 (but i wouldn't relay to much on this).
>>> I will send you a link to download the development version of rocks 5.7.
>>> First you should fix your issue (you can't kickstart node), replacing >>> the buggy rpm you produced with the original working rpm from your >>> backup and verify that everything works properly (you can kickstart >>> compute nodes).
>>> Be careful because you can make the front-end unbootable, I would >>> first test the commands on a compute node.
>>> Luca
>>> On Tue, Mar 6, 2012 at 3:32 PM, Steven Lo<s...@hep.caltech.edu> wrote: >>>> Hi Luca,
>>>> We will try disabling SELinux, rebooting and recompiling.
>>>> We found this thread before but not sure if that will work. I guess it's >>>> worth a try. However, where can we fetch the newer version of >>>> vmlinuz and initrd.img?? For which version of Rocks??
>>>> Thanks.....
>>>> Steven.....
>>>> On 03/06/2012 02:53 PM, Luca Clementi wrote: >>>>> Hey Steven, >>>>> The supported configuration with rocks is with SELinux disable. >>>>> Enabling SELinux generally can cause problem, so I would try disabling >>>>> it, rebooting, and then recompiling.
>>>>>> It was disabled before but we change it to Permissive and see if will >>>>>> make any >>>>>> difference. Same result.
>>>>>>> And then can you paste the full output of the >>>>>>> make rpm >>>>>>> inside rocks-boot, you said it gives you some error, if I remember well.
>>>>>> I have attached the full output of the 'make -d rpm' process.
>>>>>> Thanks again for your help.
>>>>>> Steven.....
>>>>>>> Sincerely, >>>>>>> Luca
>>>>>>> On Fri, Mar 2, 2012 at 7:15 PM, Steven Lo<s...@hep.caltech.edu> wrote: >>>>>>>> Hi Luca,
>>>>>>>> The search path definitely has /usr/bin in front of /opt/rocks/bin (for >>>>>>>> root):
>>>>>>>> But I thought that's the way it should be.
>>>>>>>> You are correct. /opt/rocks/bin/python is not dynamically link with >>>>>>>> libpython.
>>>>>>>> So do you have any idea why it is picking up the system wide Python??
>>>>>>>> S.
>>>>>>>> On 03/02/2012 06:03 PM, Luca Clementi wrote: >>>>>>>>> Dear Steven, >>>>>>>>> for some reason anaconda is picking up the system python and not rocks >>>>>>>>> python binaries when creating the installer. (System python is compile >>>>>>>>> dynamically aka with libpython as an external file).
>>>>>>>>> Normally it should pick the /opt/rocks/bin/python python.
>>>>>>>>> Luca
>>>>>>>>> On Thu, Mar 1, 2012 at 10:00 PM, Steven Lo<s...@hep.caltech.edu> wrote: >>>>>>>>>> Hi,
>>>>>>>>>> We continue to debug this problem.
>>>>>>>>>> We have replaced the python package with 'rpm --replacepkgs' as >>>>>>>>>> suggested:
>>>>>>>>>> The reason we suspect the Anaconda build is that we see the following >>>>>>>>>> error during the 'make rpm' process:
>>>>>>>>>> making "torrent" files for RPMS >>>>>>>>>> Buildinstall cmd: ./buildinstall --product "Rocks" --prodpath "RedHat" >>>>>>>>>> --version "0.0.0" --release "0"
>>>>>>>>>> /state/partition1/rocks-5.3/src/roll/kernel/BUILD/rocks-boot-5.3/enterprise /5/images/x86_64/rocks-dist/x86_64 >>>>>>>>>> error: open of d8:announce29:http://10.4.1.1:7625/announce13:creation >>>>>>>>>> failed: No such file or directory >>>>>>>>>> error: open of
>>>>>>>>>> datei1330655008e4:infod6:lengthi1961678e4:name40:anaconda-runtime-11.1.2.19 5-1.x86_64.rpmee >>>>>>>>>> failed: No such file or directory >>>>>>>>>> Running buildinstall... >>>>>>>>>> ~/enterprise/5/images/x86_64/rocks-dist/x86_64/buildinstall.tree.3669 >>>>>>>>>> ~/enterprise/5/images/x86_64/anaconda-runtime/usr/lib/anaconda-runtime >>>>>>>>>> ~/enterprise/5/images/x86_64/anaconda-runtime/usr/lib/anaconda-runtime
>>>>>>>>>> Are these normal error message during the build????????
>>>>>>>>>> We still see the following error during the build:
>>>>>>>>>> Creating SELinux policy... >>>>>>>>>> /usr/bin/python: error while loading shared libraries: >>>>>>>>>> libpython2.4.so.1.0: cannot open shared object file: No such file or >>>>>>>>>> directory<----- >>>>>>>>>> libsemanage.semanage_install_sandbox: genhomedircon returned error code >>>>>>>>>> 127.
>>>>>>>>>> Any advise on this issue, please ??
>>>>>>>>>> Thanks.
>>>>>>>>>> Steven.
>>>>>>>>>> On 02/22/2012 04:00 PM, Philip Papadopoulos wrote: >>>>>>>>>>> Steven, >>>>>>>>>>> you can look at >>>>>>>>>>> "yum provides '*/libpython2.4*" >>>>>>>>>>> and see which RPMs provide the file. You can attempt a yum reinstall >>>>>>>>>>> of the appropriate package. >>>>>>>>>>> -P
