Re: [sisuite-users] Not seeing boel messages on serial console - SOLVED
It urns out the reason my nodes would not boot is that SystemImager or SystemConfigurator removed the following two important lines from the grub.conf file that it creates. serial --unit=0 --speed=9600 terminal --timeout=5 serial console Once I mounted the drive on another system and added these two lines back into the grub.conf file that were there originally on the golden-client system the newly imaged system booted just fine. Is this a fix that can be integrated into Bernard's SIS source tree? What is needed is some way to preserve the serial console settings in the grub.conf file if they are present on the golden-client. -- Steven DuChene -- Storage Efficiency Calculator This modeling tool is based on patent-pending intellectual property that has been used successfully in hundreds of IBM storage optimization engage- ments, worldwide. Store less, Store more with what you own, Move data to the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Not seeing boel messages on serial console
Yes, I finally went into the fstab and grub.conf on my golden client and removed the references to the UUID stuff and replaced them with /dev/sda and /dev/sdb devices as appropriate. That seemed to take care of the grub-install problems I was seeing but the system is still not booting after the install has finished. -- Steven DuChene -Original Message- From: Tristam MacDonald Sent: Jul 13, 2011 8:59 PM To: Steven A. DuChene , sisuite-users@lists.sourceforge.net Subject: Re: [sisuite-users] Not seeing boel messages on serial console On Wed, Jul 13, 2011 at 7:23 PM, Steven A. DuChene linux-clust...@mindspring.com wrote: The following messages about grub appear in the console log file: 2011-7-13 15:7:36 [Boot::Grub :: Line 132] grub supports --no-floppy argument. 2011-7-13 15:7:36 [Boot::Grub :: Line 107] Grub executable set to: /sbin/grub-install. 2011-7-13 15:7:36 [Boot::Grub :: Line 151] bootloader = /sbin/grub-install 2011-7-13 15:7:36 [Boot::Grub :: Line 338] mount: /boot 2011-7-13 15:7:36 [Boot::Grub :: Line 338] mount: / 2011-7-13 15:7:36 [Boot::Grub :: Line 368] calling /sbin/grub-install --no-floppy --recheck UUID=0b8f2f84-5a03-4a80-b853-a624d496e5e7 Probing devices to guess BIOS drives. This may take a long time. Format of install_device not recognized. INSTALL_DEVICE can be a GRUB device name or a system device filename. Has anyone seen this before? Is there someway I can eliminate this --recheck option from being used with grub-install? Or is it that grub just does not like the UUID=0b8f2f84-5a03-4a80-b853-a624d496e5e7 device it is given? If I could figure out where the call was being made I would try to fix it. I tried inserting a hard-coded grub-install line into a couple of different places in the autoinstall master script but it seems no matter where I put ti the script complains that the path is not correct (it cannot find the executable). -- Steven DuChene My understanding is that the UUIDs are specific to a particular device. In other words, unless you are imaging to the machine which served as the golden client, the UUID will not match the device, and the grub install will fail. You can work around this by disabling the use of UUIDs by your OS. That generally means editing your /etc/fstab to replace UUIDs with device paths, and editing your /etc/default/grub to disable UUID support. -- Tristam MacDonald System Administrator, Suffolk University Math CS Department -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Not seeing boel messages on serial console
Is this a dead mailing list or is anyone else reading these messages at all??? If anyone else is on here please respond with any suggestions or even semi-random thoughts. Otherwise I guess I have to assume systemimager is a dead project. If Bernard or Brian are reading this, do I have to turn anything on specifically to get the system to write messages to log files in /tmp ? I see mention in the code of si.log as well as si_monitor.log but I am not sure if either are used by default. -- Steven DuChene -Original Message- From: Steven A. DuChene linux-clust...@mindspring.com Sent: Jul 12, 2011 6:41 PM To: sisuite-users@lists.sourceforge.net Subject: Re: Not seeing boel messages on serial console I did try adding an NFS mount option to the autoinstall master script for my image and then trying to copy over the log file. I can see the remote system mounting the directory but I do not get any files. Still trying to figure out what is going on. -- Steven DuChene -Original Message- From: Steven A. DuChene linux-clust...@mindspring.com Sent: Jul 12, 2011 5:58 PM To: sisuite-users@lists.sourceforge.net Subject: Re: Not seeing boel messages on serial console In looking in the functions file in /etc/init.d of the initrd I see it is also logging to /tmp/si.log Can anyone suggest a way that I can somehow have that file transferred back to my install server just before the node reboots? -- Steven DuChene -Original Message- From: Steven A. DuChene linux-clust...@mindspring.com Sent: Jul 12, 2011 5:45 PM To: sisuite-users@lists.sourceforge.net Subject: No seeing boel messages on serial console I am trying to boot a bunch of nodes in a special microserver blade chassis where the nodes do not have a traditional vga or graphics console. The only console they have were I can see the progress or lack there-of is a serial console. Also the only installation method is via pxe boot. I have passed the console=ttyS0,9600n8 to the kernel in the pxelinux.cfg boot config file and as a result I see the kernel boot messages on the serial console. Once the kernel is done booting however I do not see any further messages except for any rsync bits which are normally quiet other than three or four small rsync status messages at the end. If I use the --listing option when I pull the image from the golden client that is running RHEL6.1 I do indeed see the whole list of files being rsync'ed fly by but this really slows the install down to a crawl. I do not see ANY of the customary boel progress messages at all. I see where initramfs is detected and init called. Then it talks about how init is started with BusyBox v1.9.1 (2011-04-21 16:31:21 PDT), then the disk controller modules are loaded. The last messages I see are: NET: Registered protocal family 10 lo: Disabled Privacy Extensions and then just before the node reboots after rsyncing over all the files are three or four rsnc connect messages and then the node reboots. My basic problem is after the node reboots from the install, it does not boot up to the OS. It just sits there after accessing the default file that tells it to boot from the local disk and goes no further. My suspicion is that some part of the grub execution or something else at the end of the install is not proceeding correctly. But since I cannot see any of the boel or other progress log messages I am not sure what is failing. BTW, I also have a basic RHEL6.1 kickstart environment setup and the same nodes will pxe boot and install just fine from the redhat kickstart environment that also uses the console=ttyS0,9600n8 in the kernel append line. Any thoughts? BTW, I am booting with a RHEL6.1 UYOK kernel and initrd that are generated on the client during the perpareclient step. -- Steven DuChene -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Not seeing boel messages on serial console
I tried adding a ls /tmp /my/nfs/mounted/directory but I got nothing back. Nuts Off to think some more. - Original Message - From: Steven A. DuChene linux-clust...@mindspring.com To: sisuite-users@lists.sourceforge.net Sent: Wednesday, July 13, 2011 12:22 PM Subject: Re: [sisuite-users] Not seeing boel messages on serial console Is this a dead mailing list or is anyone else reading these messages at all??? If anyone else is on here please respond with any suggestions or even semi-random thoughts. Otherwise I guess I have to assume systemimager is a dead project. If Bernard or Brian are reading this, do I have to turn anything on specifically to get the system to write messages to log files in /tmp ? I see mention in the code of si.log as well as si_monitor.log but I am not sure if either are used by default. -- Steven DuChene -Original Message- From: Steven A. DuChene linux-clust...@mindspring.com Sent: Jul 12, 2011 6:41 PM To: sisuite-users@lists.sourceforge.net Subject: Re: Not seeing boel messages on serial console I did try adding an NFS mount option to the autoinstall master script for my image and then trying to copy over the log file. I can see the remote system mounting the directory but I do not get any files. Still trying to figure out what is going on. -- Steven DuChene -Original Message- From: Steven A. DuChene linux-clust...@mindspring.com Sent: Jul 12, 2011 5:58 PM To: sisuite-users@lists.sourceforge.net Subject: Re: Not seeing boel messages on serial console In looking in the functions file in /etc/init.d of the initrd I see it is also logging to /tmp/si.log Can anyone suggest a way that I can somehow have that file transferred back to my install server just before the node reboots? -- Steven DuChene -Original Message- From: Steven A. DuChene linux-clust...@mindspring.com Sent: Jul 12, 2011 5:45 PM To: sisuite-users@lists.sourceforge.net Subject: No seeing boel messages on serial console I am trying to boot a bunch of nodes in a special microserver blade chassis where the nodes do not have a traditional vga or graphics console. The only console they have were I can see the progress or lack there-of is a serial console. Also the only installation method is via pxe boot. I have passed the console=ttyS0,9600n8 to the kernel in the pxelinux.cfg boot config file and as a result I see the kernel boot messages on the serial console. Once the kernel is done booting however I do not see any further messages except for any rsync bits which are normally quiet other than three or four small rsync status messages at the end. If I use the --listing option when I pull the image from the golden client that is running RHEL6.1 I do indeed see the whole list of files being rsync'ed fly by but this really slows the install down to a crawl. I do not see ANY of the customary boel progress messages at all. I see where initramfs is detected and init called. Then it talks about how init is started with BusyBox v1.9.1 (2011-04-21 16:31:21 PDT), then the disk controller modules are loaded. The last messages I see are: NET: Registered protocal family 10 lo: Disabled Privacy Extensions and then just before the node reboots after rsyncing over all the files are three or four rsnc connect messages and then the node reboots. My basic problem is after the node reboots from the install, it does not boot up to the OS. It just sits there after accessing the default file that tells it to boot from the local disk and goes no further. My suspicion is that some part of the grub execution or something else at the end of the install is not proceeding correctly. But since I cannot see any of the boel or other progress log messages I am not sure what is failing. BTW, I also have a basic RHEL6.1 kickstart environment setup and the same nodes will pxe boot and install just fine from the redhat kickstart environment that also uses the console=ttyS0,9600n8 in the kernel append line. Any thoughts? BTW, I am booting with a RHEL6.1 UYOK kernel and initrd that are generated on the client during the perpareclient step. -- Steven DuChene -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how
Re: [sisuite-users] Not seeing boel messages on serial console
Steven, you can imagine that the authors of sisuite can be busy or in holidays. Personally I don't have the answer to your problem Regards Franck - Original Message - From: Steven A. DuChene linux-clust...@mindspring.com To: sisuite-users@lists.sourceforge.net Sent: Wednesday, July 13, 2011 12:22 PM Subject: Re: [sisuite-users] Not seeing boel messages on serial console Is this a dead mailing list or is anyone else reading these messages at all??? If anyone else is on here please respond with any suggestions or even semi-random thoughts. Otherwise I guess I have to assume systemimager is a dead project. If Bernard or Brian are reading this, do I have to turn anything on specifically to get the system to write messages to log files in /tmp ? I see mention in the code of si.log as well as si_monitor.log but I am not sure if either are used by default. -- Steven DuChene -Original Message- From: Steven A. DuChene linux-clust...@mindspring.com Sent: Jul 12, 2011 6:41 PM To: sisuite-users@lists.sourceforge.net Subject: Re: Not seeing boel messages on serial console I did try adding an NFS mount option to the autoinstall master script for my image and then trying to copy over the log file. I can see the remote system mounting the directory but I do not get any files. Still trying to figure out what is going on. -- Steven DuChene -Original Message- From: Steven A. DuChene linux-clust...@mindspring.com Sent: Jul 12, 2011 5:58 PM To: sisuite-users@lists.sourceforge.net Subject: Re: Not seeing boel messages on serial console In looking in the functions file in /etc/init.d of the initrd I see it is also logging to /tmp/si.log Can anyone suggest a way that I can somehow have that file transferred back to my install server just before the node reboots? -- Steven DuChene -Original Message- From: Steven A. DuChene linux-clust...@mindspring.com Sent: Jul 12, 2011 5:45 PM To: sisuite-users@lists.sourceforge.net Subject: No seeing boel messages on serial console I am trying to boot a bunch of nodes in a special microserver blade chassis where the nodes do not have a traditional vga or graphics console. The only console they have were I can see the progress or lack there-of is a serial console. Also the only installation method is via pxe boot. I have passed the console=ttyS0,9600n8 to the kernel in the pxelinux.cfg boot config file and as a result I see the kernel boot messages on the serial console. Once the kernel is done booting however I do not see any further messages except for any rsync bits which are normally quiet other than three or four small rsync status messages at the end. If I use the --listing option when I pull the image from the golden client that is running RHEL6.1 I do indeed see the whole list of files being rsync'ed fly by but this really slows the install down to a crawl. I do not see ANY of the customary boel progress messages at all. I see where initramfs is detected and init called. Then it talks about how init is started with BusyBox v1.9.1 (2011-04-21 16:31:21 PDT), then the disk controller modules are loaded. The last messages I see are: NET: Registered protocal family 10 lo: Disabled Privacy Extensions and then just before the node reboots after rsyncing over all the files are three or four rsnc connect messages and then the node reboots. My basic problem is after the node reboots from the install, it does not boot up to the OS. It just sits there after accessing the default file that tells it to boot from the local disk and goes no further. My suspicion is that some part of the grub execution or something else at the end of the install is not proceeding correctly. But since I cannot see any of the boel or other progress log messages I am not sure what is failing. BTW, I also have a basic RHEL6.1 kickstart environment setup and the same nodes will pxe boot and install just fine from the redhat kickstart environment that also uses the console=ttyS0,9600n8 in the kernel append line. Any thoughts? BTW, I am booting with a RHEL6.1 UYOK kernel and initrd that are generated on the client during the perpareclient step. -- Steven DuChene -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets
Re: [sisuite-users] Not seeing boel messages on serial console
What is going on with the SI? The testing release is no updated for almost 3 years.. Is there an other alternative that is better then SI so the guys are living SI? On Wed, Jul 13, 2011 at 1:39 PM, E-Blokos in...@e-blokos.com wrote: Steven, you can imagine that the authors of sisuite can be busy or in holidays. Personally I don't have the answer to your problem Regards Franck - Original Message - From: Steven A. DuChene linux-clust...@mindspring.com To: sisuite-users@lists.sourceforge.net Sent: Wednesday, July 13, 2011 12:22 PM Subject: Re: [sisuite-users] Not seeing boel messages on serial console Is this a dead mailing list or is anyone else reading these messages at all??? If anyone else is on here please respond with any suggestions or even semi-random thoughts. Otherwise I guess I have to assume systemimager is a dead project. If Bernard or Brian are reading this, do I have to turn anything on specifically to get the system to write messages to log files in /tmp ? I see mention in the code of si.log as well as si_monitor.log but I am not sure if either are used by default. -- Steven DuChene -Original Message- From: Steven A. DuChene linux-clust...@mindspring.com Sent: Jul 12, 2011 6:41 PM To: sisuite-users@lists.sourceforge.net Subject: Re: Not seeing boel messages on serial console I did try adding an NFS mount option to the autoinstall master script for my image and then trying to copy over the log file. I can see the remote system mounting the directory but I do not get any files. Still trying to figure out what is going on. -- Steven DuChene -Original Message- From: Steven A. DuChene linux-clust...@mindspring.com Sent: Jul 12, 2011 5:58 PM To: sisuite-users@lists.sourceforge.net Subject: Re: Not seeing boel messages on serial console In looking in the functions file in /etc/init.d of the initrd I see it is also logging to /tmp/si.log Can anyone suggest a way that I can somehow have that file transferred back to my install server just before the node reboots? -- Steven DuChene -Original Message- From: Steven A. DuChene linux-clust...@mindspring.com Sent: Jul 12, 2011 5:45 PM To: sisuite-users@lists.sourceforge.net Subject: No seeing boel messages on serial console I am trying to boot a bunch of nodes in a special microserver blade chassis where the nodes do not have a traditional vga or graphics console. The only console they have were I can see the progress or lack there-of is a serial console. Also the only installation method is via pxe boot. I have passed the console=ttyS0,9600n8 to the kernel in the pxelinux.cfg boot config file and as a result I see the kernel boot messages on the serial console. Once the kernel is done booting however I do not see any further messages except for any rsync bits which are normally quiet other than three or four small rsync status messages at the end. If I use the --listing option when I pull the image from the golden client that is running RHEL6.1 I do indeed see the whole list of files being rsync'ed fly by but this really slows the install down to a crawl. I do not see ANY of the customary boel progress messages at all. I see where initramfs is detected and init called. Then it talks about how init is started with BusyBox v1.9.1 (2011-04-21 16:31:21 PDT), then the disk controller modules are loaded. The last messages I see are: NET: Registered protocal family 10 lo: Disabled Privacy Extensions and then just before the node reboots after rsyncing over all the files are three or four rsnc connect messages and then the node reboots. My basic problem is after the node reboots from the install, it does not boot up to the OS. It just sits there after accessing the default file that tells it to boot from the local disk and goes no further. My suspicion is that some part of the grub execution or something else at the end of the install is not proceeding correctly. But since I cannot see any of the boel or other progress log messages I am not sure what is failing. BTW, I also have a basic RHEL6.1 kickstart environment setup and the same nodes will pxe boot and install just fine from the redhat kickstart environment that also uses the console=ttyS0,9600n8 in the kernel append line. Any thoughts? BTW, I am booting with a RHEL6.1 UYOK kernel and initrd that are generated on the client during the perpareclient step. -- Steven DuChene -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev
Re: [sisuite-users] Not seeing boel messages on serial console
The testing release is no updated for almost 3 years.. because I think this release is stable but if you encounter some problem try latest svn update Is there an other alternative that is better then SI so the guys are living SI? no, SI works well no ? - Original Message - From: Glauber Eller Martins To: sisuite-users@lists.sourceforge.net Sent: Wednesday, July 13, 2011 1:32 PM Subject: Re: [sisuite-users] Not seeing boel messages on serial console What is going on with the SI? The testing release is no updated for almost 3 years.. Is there an other alternative that is better then SI so the guys are living SI? On Wed, Jul 13, 2011 at 1:39 PM, E-Blokos in...@e-blokos.com wrote: Steven, you can imagine that the authors of sisuite can be busy or in holidays. Personally I don't have the answer to your problem Regards Franck - Original Message - From: Steven A. DuChene linux-clust...@mindspring.com To: sisuite-users@lists.sourceforge.net Sent: Wednesday, July 13, 2011 12:22 PM Subject: Re: [sisuite-users] Not seeing boel messages on serial console Is this a dead mailing list or is anyone else reading these messages at all??? If anyone else is on here please respond with any suggestions or even semi-random thoughts. Otherwise I guess I have to assume systemimager is a dead project. If Bernard or Brian are reading this, do I have to turn anything on specifically to get the system to write messages to log files in /tmp ? I see mention in the code of si.log as well as si_monitor.log but I am not sure if either are used by default. -- Steven DuChene -Original Message- From: Steven A. DuChene linux-clust...@mindspring.com Sent: Jul 12, 2011 6:41 PM To: sisuite-users@lists.sourceforge.net Subject: Re: Not seeing boel messages on serial console I did try adding an NFS mount option to the autoinstall master script for my image and then trying to copy over the log file. I can see the remote system mounting the directory but I do not get any files. Still trying to figure out what is going on. -- Steven DuChene -Original Message- From: Steven A. DuChene linux-clust...@mindspring.com Sent: Jul 12, 2011 5:58 PM To: sisuite-users@lists.sourceforge.net Subject: Re: Not seeing boel messages on serial console In looking in the functions file in /etc/init.d of the initrd I see it is also logging to /tmp/si.log Can anyone suggest a way that I can somehow have that file transferred back to my install server just before the node reboots? -- Steven DuChene -Original Message- From: Steven A. DuChene linux-clust...@mindspring.com Sent: Jul 12, 2011 5:45 PM To: sisuite-users@lists.sourceforge.net Subject: No seeing boel messages on serial console I am trying to boot a bunch of nodes in a special microserver blade chassis where the nodes do not have a traditional vga or graphics console. The only console they have were I can see the progress or lack there-of is a serial console. Also the only installation method is via pxe boot. I have passed the console=ttyS0,9600n8 to the kernel in the pxelinux.cfg boot config file and as a result I see the kernel boot messages on the serial console. Once the kernel is done booting however I do not see any further messages except for any rsync bits which are normally quiet other than three or four small rsync status messages at the end. If I use the --listing option when I pull the image from the golden client that is running RHEL6.1 I do indeed see the whole list of files being rsync'ed fly by but this really slows the install down to a crawl. I do not see ANY of the customary boel progress messages at all. I see where initramfs is detected and init called. Then it talks about how init is started with BusyBox v1.9.1 (2011-04-21 16:31:21 PDT), then the disk controller modules are loaded. The last messages I see are: NET: Registered protocal family 10 lo: Disabled Privacy Extensions and then just before the node reboots after rsyncing over all the files are three or four rsnc connect messages and then the node reboots. My basic problem is after the node reboots from the install, it does not boot up to the OS. It just sits there after accessing the default file that tells it to boot from the local disk and goes no further. My suspicion is that some part of the grub execution or something else at the end of the install is not proceeding correctly. But since I cannot see any of the boel or other progress log messages I am not sure what is failing. BTW, I
Re: [sisuite-users] Not seeing boel messages on serial console
Hi, On Wed, Jul 13, 2011 at 09:22:05AM -0700, Steven A. DuChene wrote: Is this a dead mailing list or is anyone else reading these messages at all??? If anyone else is on here please respond with any suggestions or even semi-random thoughts. give si_monitortk a try: 1) on you master node, make sure that /etc/init.d/systemimager-server-monitord was started 2) add MONITOR_SERVER=192.168.1.1 MONITOR_CONSOLE=yes to the APPEND line of your pxelinux.cfg (where 192.168.1.1 has to be replaced by the IP of your master server) 3) while the node gets imaged, run si_monitortk on the master an double click the node's line you'll get all output in a new window Once the imaging finished, the log file will also be saved in /root/si_install.log on the node. In case that grub did not install correctly, I'd suggest booting your node with grub.exe from grub4dos via PXE (via KERNEL grub.exe). That way, you might get the node initially up even without correct grub on the harddisk. Otherwise I guess I have to assume systemimager is a dead project. the currently greatest version can be found in Bernard's repository http://download.systemimager.org/~bli/systemimager/ These beta-rpms work very well even with ext4 and modern hardware (except one small missing recent patch for HP's cciss controller) Best, thomas If Bernard or Brian are reading this, do I have to turn anything on specifically to get the system to write messages to log files in /tmp ? I see mention in the code of si.log as well as si_monitor.log but I am not sure if either are used by default. -- Steven DuChene -Original Message- From: Steven A. DuChene linux-clust...@mindspring.com Sent: Jul 12, 2011 6:41 PM To: sisuite-users@lists.sourceforge.net Subject: Re: Not seeing boel messages on serial console I did try adding an NFS mount option to the autoinstall master script for my image and then trying to copy over the log file. I can see the remote system mounting the directory but I do not get any files. Still trying to figure out what is going on. -- Steven DuChene -Original Message- From: Steven A. DuChene linux-clust...@mindspring.com Sent: Jul 12, 2011 5:58 PM To: sisuite-users@lists.sourceforge.net Subject: Re: Not seeing boel messages on serial console In looking in the functions file in /etc/init.d of the initrd I see it is also logging to /tmp/si.log Can anyone suggest a way that I can somehow have that file transferred back to my install server just before the node reboots? -- Steven DuChene -Original Message- From: Steven A. DuChene linux-clust...@mindspring.com Sent: Jul 12, 2011 5:45 PM To: sisuite-users@lists.sourceforge.net Subject: No seeing boel messages on serial console I am trying to boot a bunch of nodes in a special microserver blade chassis where the nodes do not have a traditional vga or graphics console. The only console they have were I can see the progress or lack there-of is a serial console. Also the only installation method is via pxe boot. I have passed the console=ttyS0,9600n8 to the kernel in the pxelinux.cfg boot config file and as a result I see the kernel boot messages on the serial console. Once the kernel is done booting however I do not see any further messages except for any rsync bits which are normally quiet other than three or four small rsync status messages at the end. If I use the --listing option when I pull the image from the golden client that is running RHEL6.1 I do indeed see the whole list of files being rsync'ed fly by but this really slows the install down to a crawl. I do not see ANY of the customary boel progress messages at all. I see where initramfs is detected and init called. Then it talks about how init is started with BusyBox v1.9.1 (2011-04-21 16:31:21 PDT), then the disk controller modules are loaded. The last messages I see are: NET: Registered protocal family 10 lo: Disabled Privacy Extensions and then just before the node reboots after rsyncing over all the files are three or four rsnc connect messages and then the node reboots. My basic problem is after the node reboots from the install, it does not boot up to the OS. It just sits there after accessing the default file that tells it to boot from the local disk and goes no further. My suspicion is that some part of the grub execution or something else at the end of the install is not proceeding correctly. But since I cannot see any of the boel or other progress log messages I am not sure what is failing. BTW, I also have a basic RHEL6.1 kickstart environment setup and the same nodes will pxe boot and install just fine from the redhat kickstart environment that also uses the console=ttyS0,9600n8 in the kernel append line. Any thoughts? BTW, I am booting with a RHEL6.1 UYOK kernel and initrd that are generated on the client during the perpareclient step. -- Steven DuChene
Re: [sisuite-users] Not seeing boel messages on serial console
I see that Brenard Li has made some private releases of 4.1.99 that have been updatedas recently as 2011. I don't know where to get Changlogs from him showing what sorts ofchanges he is making.--Steven DuChene-Original Message- From: E-Blokos <in...@e-blokos.com> Sent: Jul 13, 2011 10:41 AM To: sisuite-users@lists.sourceforge.net Subject: Re: [sisuite-users] Not seeing boel messages on serial console The testing release is no updated for almost 3 years..because I think this release is stablebut if you encounter some problem try latest svn updateIs there an other alternative that is better then SI so the guys areliving SI?no, SI works well no ? - Original Message - From: Glauber Eller Martins To: sisuite-users@lists.sourceforge.net Sent: Wednesday, July 13, 2011 1:32 PM Subject: Re: [sisuite-users] Not seeing boel messages on serial console What is going on with the SI? The testing release is no updated for almost 3 years.. Is there an other alternative that is better then SI so the guys are living SI? On Wed, Jul 13, 2011 at 1:39 PM, E-Blokos <in...@e-blokos.com> wrote:Steven,you can imagine that the authors of sisuite can be busy or in holidays.Personally I don't have the answer to your problemRegardsFranck- Original Message -From: "Steven A. DuChene" <linux-clust...@mindspring.com>To: <sisuite-users@lists.sourceforge.net>Sent: Wednesday, July 13, 2011 12:22 PM Subject: Re: [sisuite-users] Not seeing boel messages on serial console Is this a dead mailing list or is anyone else reading these messages at all??? If anyone else is on here please respond with any suggestions or even semi-random thoughts. Otherwise I guess I have to assume systemimager is a dead project. If Bernard or Brian are reading this, do I have to turn anything on specifically to get the system to write messages to log files in /tmp ? I see mention in the code of si.log as well as si_monitor.log but I am not sure if either are used by default. -- Steven DuChene -Original Message-From: "Steven A. DuChene" <linux-clust...@mindspring.com>Sent: Jul 12, 2011 6:41 PMTo: sisuite-users@lists.sourceforge.netSubject: Re: Not seeing boel messages on serial consoleI did try adding an NFS mount option to the autoinstall master scriptfor my image and then trying to copy over the log file. I can see theremote system mounting the directory but I do not get any files.Still trying to figure out what is going on.--Steven DuChene-Original Message-From: "Steven A. DuChene" <linux-clust...@mindspring.com>Sent: Jul 12, 2011 5:58 PMTo: sisuite-users@lists.sourceforge.netSubject: Re: Not seeing boel messages on serial consoleIn looking in the functions file in /etc/init.d of the initrd I seeit is also logging to /tmp/si.logCan anyone suggest a way that I can somehow have that file transferredback to my install server just before the node reboots?--Steven DuChene-Original Message-From: "Steven A. DuChene" <linux-clust...@mindspring.com>Sent: Jul 12, 2011 5:45 PMTo: sisuite-users@lists.sourceforge.netSubject: No seeing boel messages on serial consoleI am trying to boot a bunch of nodes in a special microserver bladechassiswhere the nodes do not have a traditional vga or graphics console. Theonlyconsole they have were I can see the progress or lack there-of is aserialconsole. Also the only installation method is via pxe boot. I havepassedthe "console=ttyS0,9600n8" to the kernel in the pxelinux.cfg boot configfileand as a result I see the kernel boot messages on the serial console.Oncethe kernel is done booting however I do not see any further messagesexceptfor any rsync bits which are normally quiet other than three or foursmallrsync status messages at the end. If I use the "--listing" option when Ipull the image from the golden client that is running RHEL6.1 I doindeedsee the whole list of files being rsync'ed fly by but this really slowstheinstall down to a crawl. I do not see ANY of the customary boel progressmessages at all. I see where initramfs is detected and init called. Thenit talks about how init is started with BusyBox v1.9.1 (2011-04-2116:31:21 PDT),then the disk controller modules are loaded.The last messages I see are:NET: Registered protocal family 10lo: Disabled Privacy Extensionsand then just before the node reboots after rsyncing over all the filesarethree or four rsnc connect messages and then the node reboots.My basic problem is after the node reboots from the install, it does notboot
Re: [sisuite-users] Not seeing boel messages on serial console
Development is going on, but I don't know how close we are to a packaged release. Check the archives of this list. The released versions of SI do not work well on current hardware -- they don't include current drivers, so don't work on our current nodes, for instance. SALI https://subtrac.sara.nl/oss/sali is a current boot image, but it's not 100% compatible. I got part way through shimming it to work, and my notes are now in the SALI wiki, but SI should have a usable image built-in, and the compatibility problems need to be sorted. Chris On 7/13/11 1:41 PM, E-Blokos wrote: The testing release is no updated for almost 3 years.. because I think this release is stable but if you encounter some problem try latest svn update Is there an other alternative that is better then SI so the guys are living SI? no, SI works well no ? - Original Message - *From:* Glauber Eller Martins mailto:glauberel...@gmail.com *To:* sisuite-users@lists.sourceforge.net mailto:sisuite-users@lists.sourceforge.net *Sent:* Wednesday, July 13, 2011 1:32 PM *Subject:* Re: [sisuite-users] Not seeing boel messages on serial console What is going on with the SI? The testing release is no updated for almost 3 years.. Is there an other alternative that is better then SI so the guys are living SI? -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Not seeing boel messages on serial console
Thanks for the info and all the replies. I am using the latest 4.1.99 rpms from Bernard's release area. I was finally able to see what is going on using the si_monitortk application and captured a console log from a couple of my systems. I think the grub install is failing in some unusual way. The call to grub-install is producing a usage message as if it does not like one of the options provided. I see in the usage message that it says the recheck option is unreliable and is strongly discouraged but this option is being used when grub-install is being invoked. The following messages about grub appear in the console log file: 2011-7-13 15:7:36 [Boot::Grub :: Line 132] grub supports --no-floppy argument. 2011-7-13 15:7:36 [Boot::Grub :: Line 107] Grub executable set to: /sbin/grub-install. 2011-7-13 15:7:36 [Boot::Grub :: Line 151] bootloader = /sbin/grub-install 2011-7-13 15:7:36 [Boot::Grub :: Line 338] mount: /boot 2011-7-13 15:7:36 [Boot::Grub :: Line 338] mount: / 2011-7-13 15:7:36 [Boot::Grub :: Line 368] calling /sbin/grub-install --no-floppy --recheck UUID=0b8f2f84-5a03-4a80-b853-a624d496e5e7 Probing devices to guess BIOS drives. This may take a long time. Format of install_device not recognized. Usage: grub-install [OPTION] install_device Install GRUB on your drive. -h, --help print this message and exit -v, --version print the version information and exit --root-directory=DIRinstall GRUB images under the directory DIR instead of the root directory --grub-shell=FILE use FILE as the grub shell --no-floppy do not probe any floppy drive --force-lba force GRUB to use LBA mode even for a buggy BIOS --recheck probe a device map even if it already exists This flag is unreliable and its use is strongly discouraged. INSTALL_DEVICE can be a GRUB device name or a system device filename. grub-install copies GRUB images into the DIR/boot directory specfied by --root-directory, and uses the grub shell to install grub into the boot sector. Report bugs to bug-g...@gnu.org. 2011-7-13 15:7:37 [Boot::Grub :: Line 319] mount: /boot 2011-7-13 15:7:37 [Boot::Grub :: Line 319] mount: / 2011-7-13 15:7:37 [Boot::Grub :: Line 321] mount: / mounts: UUID=0b8f2f84-5a03-4a80-b853-a624d496e5e7 2011-7-13 15:7:37 [Boot::Grub :: Line 247] d = /dev/sda1 2011-7-13 15:7:37 [Boot::Grub :: Line 250] Device: sda; Part: 1 2011-7-13 15:7:37 [Boot::Grub :: Line 252] Biosdev: (hd0) 2011-7-13 15:7:37 [Boot::Grub :: Line 374] Installing GRUB on (hd0,0) 2011-7-13 15:7:37 [Boot::Grub :: Line 377] Grub root set to (hd0,0), bootdev=(hd0) Probing devices to guess BIOS drives. This may take a long time. 2011-7-13 15:7:37 [main :: Line 479] All done. I have modified the following files: /boot/grub/grub.conf /boot/grub/grub.conf /etc/modprobe.conf /etc/modules.conf /etc/sysconfig/network /etc/sysconfig/network-scripts/ifcfg-eth0 Has anyone seen this before? Is there someway I can eliminate this --recheck option from being used with grub-install? Or is it that grub just does not like the UUID=0b8f2f84-5a03-4a80-b853-a624d496e5e7 device it is given? If I could figure out where the call was being made I would try to fix it. I tried inserting a hard-coded grub-install line into a couple of different places in the autoinstall master script but it seems no matter where I put ti the script complains that the path is not correct (it cannot find the executable). -- Steven DuChene -Original Message- From: Chris Pepper pep...@reppep.com Sent: Jul 13, 2011 10:46 AM To: sisuite-users@lists.sourceforge.net Subject: Re: [sisuite-users] Not seeing boel messages on serial console Development is going on, but I don't know how close we are to a packaged release. Check the archives of this list. The released versions of SI do not work well on current hardware -- they don't include current drivers, so don't work on our current nodes, for instance. SALI https://subtrac.sara.nl/oss/sali is a current boot image, but it's not 100% compatible. I got part way through shimming it to work, and my notes are now in the SALI wiki, but SI should have a usable image built-in, and the compatibility problems need to be sorted. Chris -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Not seeing boel messages on serial console
On Wed, Jul 13, 2011 at 7:23 PM, Steven A. DuChene linux-clust...@mindspring.com wrote: The following messages about grub appear in the console log file: 2011-7-13 15:7:36 [Boot::Grub :: Line 132] grub supports --no-floppy argument. 2011-7-13 15:7:36 [Boot::Grub :: Line 107] Grub executable set to: /sbin/grub-install. 2011-7-13 15:7:36 [Boot::Grub :: Line 151] bootloader = /sbin/grub-install 2011-7-13 15:7:36 [Boot::Grub :: Line 338] mount: /boot 2011-7-13 15:7:36 [Boot::Grub :: Line 338] mount: / 2011-7-13 15:7:36 [Boot::Grub :: Line 368] calling /sbin/grub-install --no-floppy --recheck UUID=0b8f2f84-5a03-4a80-b853-a624d496e5e7 Probing devices to guess BIOS drives. This may take a long time. Format of install_device not recognized. INSTALL_DEVICE can be a GRUB device name or a system device filename. Has anyone seen this before? Is there someway I can eliminate this --recheck option from being used with grub-install? Or is it that grub just does not like the UUID=0b8f2f84-5a03-4a80-b853-a624d496e5e7 device it is given? If I could figure out where the call was being made I would try to fix it. I tried inserting a hard-coded grub-install line into a couple of different places in the autoinstall master script but it seems no matter where I put ti the script complains that the path is not correct (it cannot find the executable). -- Steven DuChene My understanding is that the UUIDs are specific to a particular device. In other words, unless you are imaging to the machine which served as the golden client, the UUID will not match the device, and the grub install will fail. You can work around this by disabling the use of UUIDs by your OS. That generally means editing your /etc/fstab to replace UUIDs with device paths, and editing your /etc/default/grub to disable UUID support. -- Tristam MacDonald System Administrator, Suffolk University Math CS Department -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Not seeing boel messages on serial console
In looking in the functions file in /etc/init.d of the initrd I see it is also logging to /tmp/si.log Can anyone suggest a way that I can somehow have that file transferred back to my install server just before the node reboots? -- Steven DuChene -Original Message- From: Steven A. DuChene linux-clust...@mindspring.com Sent: Jul 12, 2011 5:45 PM To: sisuite-users@lists.sourceforge.net Subject: No seeing boel messages on serial console I am trying to boot a bunch of nodes in a special microserver blade chassis where the nodes do not have a traditional vga or graphics console. The only console they have were I can see the progress or lack there-of is a serial console. Also the only installation method is via pxe boot. I have passed the console=ttyS0,9600n8 to the kernel in the pxelinux.cfg boot config file and as a result I see the kernel boot messages on the serial console. Once the kernel is done booting however I do not see any further messages except for any rsync bits which are normally quiet other than three or four small rsync status messages at the end. If I use the --listing option when I pull the image from the golden client that is running RHEL6.1 I do indeed see the whole list of files being rsync'ed fly by but this really slows the install down to a crawl. I do not see ANY of the customary boel progress messages at all. I see where initramfs is detected and init called. Then it talks about how init is started with BusyBox v1.9.1 (2011-04-21 16:31:21 PDT), then the disk controller modules are loaded. The last messages I see are: NET: Registered protocal family 10 lo: Disabled Privacy Extensions and then just before the node reboots after rsyncing over all the files are three or four rsnc connect messages and then the node reboots. My basic problem is after the node reboots from the install, it does not boot up to the OS. It just sits there after accessing the default file that tells it to boot from the local disk and goes no further. My suspicion is that some part of the grub execution or something else at the end of the install is not proceeding correctly. But since I cannot see any of the boel or other progress log messages I am not sure what is failing. BTW, I also have a basic RHEL6.1 kickstart environment setup and the same nodes will pxe boot and install just fine from the redhat kickstart environment that also uses the console=ttyS0,9600n8 in the kernel append line. Any thoughts? BTW, I am booting with a RHEL6.1 UYOK kernel and initrd that are generated on the client during the perpareclient step. -- Steven DuChene -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Not seeing boel messages on serial console
I did try adding an NFS mount option to the autoinstall master script for my image and then trying to copy over the log file. I can see the remote system mounting the directory but I do not get any files. Still trying to figure out what is going on. -- Steven DuChene -Original Message- From: Steven A. DuChene linux-clust...@mindspring.com Sent: Jul 12, 2011 5:58 PM To: sisuite-users@lists.sourceforge.net Subject: Re: Not seeing boel messages on serial console In looking in the functions file in /etc/init.d of the initrd I see it is also logging to /tmp/si.log Can anyone suggest a way that I can somehow have that file transferred back to my install server just before the node reboots? -- Steven DuChene -Original Message- From: Steven A. DuChene linux-clust...@mindspring.com Sent: Jul 12, 2011 5:45 PM To: sisuite-users@lists.sourceforge.net Subject: No seeing boel messages on serial console I am trying to boot a bunch of nodes in a special microserver blade chassis where the nodes do not have a traditional vga or graphics console. The only console they have were I can see the progress or lack there-of is a serial console. Also the only installation method is via pxe boot. I have passed the console=ttyS0,9600n8 to the kernel in the pxelinux.cfg boot config file and as a result I see the kernel boot messages on the serial console. Once the kernel is done booting however I do not see any further messages except for any rsync bits which are normally quiet other than three or four small rsync status messages at the end. If I use the --listing option when I pull the image from the golden client that is running RHEL6.1 I do indeed see the whole list of files being rsync'ed fly by but this really slows the install down to a crawl. I do not see ANY of the customary boel progress messages at all. I see where initramfs is detected and init called. Then it talks about how init is started with BusyBox v1.9.1 (2011-04-21 16:31:21 PDT), then the disk controller modules are loaded. The last messages I see are: NET: Registered protocal family 10 lo: Disabled Privacy Extensions and then just before the node reboots after rsyncing over all the files are three or four rsnc connect messages and then the node reboots. My basic problem is after the node reboots from the install, it does not boot up to the OS. It just sits there after accessing the default file that tells it to boot from the local disk and goes no further. My suspicion is that some part of the grub execution or something else at the end of the install is not proceeding correctly. But since I cannot see any of the boel or other progress log messages I am not sure what is failing. BTW, I also have a basic RHEL6.1 kickstart environment setup and the same nodes will pxe boot and install just fine from the redhat kickstart environment that also uses the console=ttyS0,9600n8 in the kernel append line. Any thoughts? BTW, I am booting with a RHEL6.1 UYOK kernel and initrd that are generated on the client during the perpareclient step. -- Steven DuChene -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
