-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Prem,
This sounds like an sshd config issue. I'd work with the external_sshd_config
to find what is keeping you from being able to log in. Andy could confirm,
but I'm pretty sure vcld sets that file up to allow password based logins.
I'd compare external_sshd_config from the box that won't let you log in with
sshd_config from a non-VCL machine that will let you use a password to log in.
If you try sshing to it from another linux machine, you can use 'ssh -vvv' to
get quite a bit of debugging info about the connection establishment.
Josh
On Wednesday June 15, 2011, Prem Kumar wrote:
> hello,
>
> one more issue still standing.
>
> with the swap of interfaces for 'IP0' and 'IP1'in 'Linux.pm' file i
> was able login to the reserved node from the management node, but not
> externally.
>
> with the current setup of image capture does it require that the end
> user use public keys to login instead of password authentication?
>
> i am sure this is not a firewall issue, because when i use putty to
> login, i get a prompt to type in the login username, and the moment i
> type in username and hit enter, expecting to type in password, i get
> the following error:
>
> "No supported authentication methods available"
>
> to me this seems to be a 'PAM' issue of 'sshd' config issue.
>
> any thoughts? or leads please?
>
> regards,
> prem.
>
> On Tue, Jun 14, 2011 at 11:55 AM, Prem Kumar <prem.it.ku...@gmail.com>
wrote:
> > hi Andy,
> >
> > i will stick to this workaround for now, and this helps!!!
> >
> > if i were to run a post load or post reservation script, any idea
> > where would that be?
> >
> > regards,
> > prem.
> >
> > On Tue, Jun 14, 2011 at 10:00 AM, Andy Kurth <andy_ku...@ncsu.edu> wrote:
> >> Hello Prem,
> >> We're working to make the code more flexible regarding interface
> >> names. For now, I think you're going to need to modify the code.
> >> Open up lib/VCL/Module/OS/Linux.pm and find the generate_rc_local
> >> subroutine. Find the following 2 lines and swap 'eth0' and 'eth1':
> >>
> >> push(@array2print, 'IP0=$(ifconfig eth0 | grep inet | awk \'{print
> >> $2}\' | awk -F: \'{print $2}\')' . "\n");
> >> push(@array2print, 'IP1=$(ifconfig eth1 | grep inet | awk \'{print
> >> $2}\' | awk -F: \'{print $2}\')' . "\n");
> >>
> >> You will need to save a new revision of your image after making this
> >> change. Once captured, the new revision should hopefully configure
> >> SSH correctly.
> >>
> >> Hope this helps,
> >> Andy
> >>
> >> On Mon, Jun 13, 2011 at 4:45 PM, Prem Kumar <prem.it.ku...@gmail.com>
wrote:
> >>> hello,
> >>>
> >>> every thing went well. have one minor correction to make.
> >>>
> >>> since my eth0 is public and eth1 is private, any idea on how could i
> >>> guarantee that external_sshd_config listens to eth0 and gets the
> >>> public ip and sshd_config listens to eth1 and gets private ip.
> >>>
> >>> because of the above switch of the ip's in sshd_config files, even
> >>> though my reservation finishes it remains locked out.
> >>>
> >>> i also intend to provision using vmware, using the same management
> >>> node and hoping that any changes made to get the above bare-metal
> >>> install working will not affect the other.
> >>>
> >>> regards,
> >>> prem.
> >>>
> >>> On Thu, Jun 9, 2011 at 4:58 PM, Prem Kumar <prem.it.ku...@gmail.com>
wrote:
> >>>> Josh,
> >>>>
> >>>> got it to work!!!
> >>>>
> >>>> 'usepartimageng=0' set it to 1.
> >>>>
> >>>> never mind about the link to download partimage-ng, i was under the
> >>>> impression, that i will have to install partimage-ng, then looked
> >>>> around to realize it already exists in rootimg.gz.
> >>>>
> >>>> sincere thanks for patiently helping, now moving to next step!
> >>>>
> >>>> regards,
> >>>> prem.
> >>>>
> >>>> On Thu, Jun 9, 2011 at 3:50 PM, Prem Kumar <prem.it.ku...@gmail.com>
wrote:
> >>>>> hi Josh,
> >>>>>
> >>>>>> I need to add this to the documentation and should have mentioned it
> >>>>>> earlier. partimage can only capture a few file system types. I
> >>>>>> don't remember the exact list. I know it includes ext2/ext3 and
> >>>>>> ntfs. I also know that it cannot capture ext4 and anything
> >>>>>> involving LVM. That is part of why I included support for
> >>>>>> partimageng. If it doesn't natively know how to handle the file
> >>>>>> system, it will fall back to using dd to capture it. Search for
> >>>>>> 'usepartimageng=0' in the partimageng postscript and change it to
> >>>>>> =1 to switch to using partimageng.
> >>>>>>
> >>>>>> Is the file system to be captured either ext2 or ext3 and without
> >>>>>> having LVM invovled?
> >>>>>
> >>>>> file system involved is ext3 and without 'lvm'. so i am good on that.
> >>>>>
> >>>>> i could not find partimage-ng for download, could you point me to a
> >>>>> genuine source, sourceforege doesn't have it.
> >>>>>
> >>>>> following is the link to /tmp/partimageng.log
> >>>>>
> >>>>>> http://pastebin.com/YrbmsF99
> >>>>>
> >>>>> also noticed following error from partimage log in /var/log
> >>>>>
> >>>>> >> "[Can't read bit map block 0 from image]"
> >>>>>
> >>>>> looking out for that errors tells me that it could be because of
> >>>>> running partimage in 'gui' mode as opposed to batch, still looking
> >>>>> for more reasons.
> >>>>>
> >>>>> meanwhile i will look for other errors and wait for link to
> >>>>> partimage-ng.
> >>>>>
> >>>>> regards,
> >>>>> prem.
- --
- -------------------------------
Josh Thompson
VCL Developer
North Carolina State University
my GPG/PGP key can be found at pgp.mit.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
iEYEARECAAYFAk36PcEACgkQV/LQcNdtPQMEqACffZxf8ZPZMi2ZfwgwvF3xkfxN
hu0AnjnNv4IKhc1Eh3FfkAs6bqoG3yEC
=XVWN
-----END PGP SIGNATURE-----
