You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@vcl.apache.org by "Litchfield, Elwin L." <Le...@sar.usf.edu> on 2015/05/05 02:52:36 UTC
Fw: PROBLEM --
localhost|2:2|timeout|Linux.pm|VM7Cent6VCL1>VM7|vmwarelinux-vm7c2testvcl212-v0|admin
The reservation expired & the VM is still powered on. Where should I be looking?
Lewis Litchfield
Technology Services – Viking Center Lab
University of South Florida Sarasota-Manatee
941-359-4231
________________________________________
From: root@localhost.localdomain <ro...@localhost.localdomain>
Sent: Monday, May 4, 2015 8:37 PM
To: lewis15@mail.usf.edu
Subject: PROBLEM -- localhost|2:2|timeout|Linux.pm|VM7Cent6VCL1>VM7|vmwarelinux-vm7c2testvcl212-v0|admin
failed to add AllowUsers admin to external_sshd_config
------------------------------------------------------------------------
time: 2015-05-04 20:37:36
caller: Linux.pm:delete_user(894)
( 0) Linux.pm, delete_user (line: 894)
(-1) Linux.pm, sanitize (line: 1177)
(-2) reclaim.pm, call_os_sanitize (line: 271)
(-3) reclaim.pm, process (line: 162)
(-4) vcld, make_new_child (line: 571)
(-5) vcld, main (line: 350)
------------------------------------------------------------------------
management node: localhost
reservation PID: 12224
parent vcld PID: 2327
request ID: 2
reservation ID: 2
request state/laststate: timeout/reserved
request start time: 2015-05-04 20:15:00
request end time: 2015-05-04 20:45:00
for imaging: no
log ID: 34
computer: VM7Cent6VCL1
computer id: 6
computer type: virtualmachine
computer eth0 MAC address: 00:50:56:3F:40:E3
computer eth1 MAC address: 00:50:56:3F:40:ED
computer private IP address: 192.168.10.48
computer public IP address: 131.247.29.132
computer in block allocation: no
provisioning module: VCL::Module::Provisioning::VMware::VMware
vm host: VM7
vm host ID: 2
vm host computer ID: 5
vm profile: VMware ESXi - local storage
vm profile VM path: datastore1
vm profile repository path: <undefined>
vm profile datastore path: datastore1
vm profile disk type: dedicated
image: vmwarelinux-vm7c2testvcl212-v0
image display name: vm7c2testvcl2
image ID: 12
image revision ID: 12
image size: 5762 MB
use Sysprep: yes
root access: yes
image owner ID: 1
image owner affiliation: Local
image revision date created: 2015-05-01 09:43:57
image revision production: yes
OS module: VCL::Module::OS::Linux
user: admin
user name: vcl admin
user ID: 1
user affiliation: Local
------------------------------------------------------------------------
RECENT LOG ENTRIES FOR THIS PROCESS:
|12224|2:2|timeout| (-1) Linux.pm, delete_user (line: 871)
|12224|2:2|timeout| (-2) Linux.pm, sanitize (line: 1177)
|12224|2:2|timeout| (-3) reclaim.pm, call_os_sanitize (line: 271)
|12224|2:2|timeout| (-4) reclaim.pm, process (line: 162)
|12224|2:2|timeout| (-5) vcld, make_new_child (line: 571)
2015-05-04 20:37:24|12224|2:2|timeout|utils.pm:run_ssh_command(4902)|executing SSH command on VM7Cent6VCL1:
|12224|2:2|timeout| /usr/bin/ssh -i /etc/vcl/vcl.key -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o ConnectionAttempts=1 -o ConnectTimeout=3 -l root -p 22 -x VM7Cent6VCL1 '/usr/sbin/userdel admin' 2>&1
|12224|2:2|timeout| ---- WARNING ----
|12224|2:2|timeout| 2015-05-04 20:37:24|12224|2:2|timeout|utils.pm:run_ssh_command(5006)|attempt 1/3: failed to execute SSH command on VM7Cent6VCL1: '/usr/sbin/userdel admin', exit status: 255, output:
|12224|2:2|timeout| ssh output (/usr/sbin/...): ssh: connect to host VM7Cent6VCL1 port 22: No route to host
|12224|2:2|timeout| ( 0) utils.pm, run_ssh_command (line: 5006)
|12224|2:2|timeout| (-1) Linux.pm, delete_user (line: 881)
|12224|2:2|timeout| (-2) Linux.pm, sanitize (line: 1177)
|12224|2:2|timeout| (-3) reclaim.pm, call_os_sanitize (line: 271)
|12224|2:2|timeout| (-4) reclaim.pm, process (line: 162)
|12224|2:2|timeout| (-5) vcld, make_new_child (line: 571)
2015-05-04 20:37:24|12224|2:2|timeout|utils.pm:run_ssh_command(4894)|sleeping for 2 seconds before making next SSH attempt
2015-05-04 20:37:26|12224|2:2|timeout|utils.pm:run_ssh_command(4906)|attempt 2/3: executing SSH command on VM7Cent6VCL1:
|12224|2:2|timeout| /usr/bin/ssh -i /etc/vcl/vcl.key -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o ConnectionAttempts=1 -o ConnectTimeout=3 -l root -p 22 -x VM7Cent6VCL1 '/usr/sbin/userdel admin' 2>&1
|12224|2:2|timeout| ---- WARNING ----
|12224|2:2|timeout| 2015-05-04 20:37:26|12224|2:2|timeout|utils.pm:run_ssh_command(5006)|attempt 2/3: failed to execute SSH command on VM7Cent6VCL1: '/usr/sbin/userdel admin', exit status: 255, output:
|12224|2:2|timeout| ssh output (/usr/sbin/...): ssh: connect to host VM7Cent6VCL1 port 22: No route to host
|12224|2:2|timeout| ( 0) utils.pm, run_ssh_command (line: 5006)
|12224|2:2|timeout| (-1) Linux.pm, delete_user (line: 881)
|12224|2:2|timeout| (-2) Linux.pm, sanitize (line: 1177)
|12224|2:2|timeout| (-3) reclaim.pm, call_os_sanitize (line: 271)
|12224|2:2|timeout| (-4) reclaim.pm, process (line: 162)
|12224|2:2|timeout| (-5) vcld, make_new_child (line: 571)
2015-05-04 20:37:26|12224|2:2|timeout|utils.pm:run_ssh_command(4894)|sleeping for 4 seconds before making next SSH attempt
2015-05-04 20:37:30|12224|2:2|timeout|utils.pm:run_ssh_command(4906)|attempt 3/3: executing SSH command on VM7Cent6VCL1:
|12224|2:2|timeout| /usr/bin/ssh -i /etc/vcl/vcl.key -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o ConnectionAttempts=1 -o ConnectTimeout=3 -l root -p 22 -x VM7Cent6VCL1 '/usr/sbin/userdel admin' 2>&1
|12224|2:2|timeout| ---- WARNING ----
|12224|2:2|timeout| 2015-05-04 20:37:30|12224|2:2|timeout|utils.pm:run_ssh_command(5006)|attempt 3/3: failed to execute SSH command on VM7Cent6VCL1: '/usr/sbin/userdel admin', exit status: 255, output:
|12224|2:2|timeout| ssh output (/usr/sbin/...): ssh: connect to host VM7Cent6VCL1 port 22: No route to host
|12224|2:2|timeout| ( 0) utils.pm, run_ssh_command (line: 5006)
|12224|2:2|timeout| (-1) Linux.pm, delete_user (line: 881)
|12224|2:2|timeout| (-2) Linux.pm, sanitize (line: 1177)
|12224|2:2|timeout| (-3) reclaim.pm, call_os_sanitize (line: 271)
|12224|2:2|timeout| (-4) reclaim.pm, process (line: 162)
|12224|2:2|timeout| (-5) vcld, make_new_child (line: 571)
|12224|2:2|timeout| ---- WARNING ----
|12224|2:2|timeout| 2015-05-04 20:37:30|12224|2:2|timeout|utils.pm:run_ssh_command(5043)|failed to run SSH command after 3 attempts, command: /usr/bin/ssh -i /etc/vcl/vcl.key -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o ConnectionAttempts=1 -o ConnectTimeout=3 -l root -p 22 -x VM7Cent6VCL1 '/usr/sbin/userdel admin' 2>&1, exit status: 255, output:
|12224|2:2|timeout| ssh output (/usr/sbin/...): ssh: connect to host VM7Cent6VCL1 port 22: No route to host
|12224|2:2|timeout| ( 0) utils.pm, run_ssh_command (line: 5043)
|12224|2:2|timeout| (-1) Linux.pm, delete_user (line: 881)
|12224|2:2|timeout| (-2) Linux.pm, sanitize (line: 1177)
|12224|2:2|timeout| (-3) reclaim.pm, call_os_sanitize (line: 271)
|12224|2:2|timeout| (-4) reclaim.pm, process (line: 162)
|12224|2:2|timeout| (-5) vcld, make_new_child (line: 571)
2015-05-04 20:37:30|12224|2:2|timeout|utils.pm:run_ssh_command(4902)|executing SSH command on VM7Cent6VCL1:
|12224|2:2|timeout| /usr/bin/ssh -i /etc/vcl/vcl.key -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o ConnectionAttempts=1 -o ConnectTimeout=3 -l root -p 22 -x VM7Cent6VCL1 'sed -i -e "/^AllowUsers .*/d" /etc/ssh/external_sshd_config' 2>&1
|12224|2:2|timeout| ---- WARNING ----
|12224|2:2|timeout| 2015-05-04 20:37:30|12224|2:2|timeout|utils.pm:run_ssh_command(5006)|attempt 1/3: failed to execute SSH command on VM7Cent6VCL1: 'sed -i -e "/^AllowUsers .*/d" /etc/ssh/external_sshd_config', exit status: 255, output:
|12224|2:2|timeout| ssh output (sed -i -e ...): ssh: connect to host VM7Cent6VCL1 port 22: No route to host
|12224|2:2|timeout| ( 0) utils.pm, run_ssh_command (line: 5006)
|12224|2:2|timeout| (-1) Linux.pm, delete_user (line: 890)
|12224|2:2|timeout| (-2) Linux.pm, sanitize (line: 1177)
|12224|2:2|timeout| (-3) reclaim.pm, call_os_sanitize (line: 271)
|12224|2:2|timeout| (-4) reclaim.pm, process (line: 162)
|12224|2:2|timeout| (-5) vcld, make_new_child (line: 571)
2015-05-04 20:37:30|12224|2:2|timeout|utils.pm:run_ssh_command(4894)|sleeping for 2 seconds before making next SSH attempt
2015-05-04 20:37:32|12224|2:2|timeout|utils.pm:run_ssh_command(4906)|attempt 2/3: executing SSH command on VM7Cent6VCL1:
|12224|2:2|timeout| /usr/bin/ssh -i /etc/vcl/vcl.key -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o ConnectionAttempts=1 -o ConnectTimeout=3 -l root -p 22 -x VM7Cent6VCL1 'sed -i -e "/^AllowUsers .*/d" /etc/ssh/external_sshd_config' 2>&1
|12224|2:2|timeout| ---- WARNING ----
|12224|2:2|timeout| 2015-05-04 20:37:32|12224|2:2|timeout|utils.pm:run_ssh_command(5006)|attempt 2/3: failed to execute SSH command on VM7Cent6VCL1: 'sed -i -e "/^AllowUsers .*/d" /etc/ssh/external_sshd_config', exit status: 255, output:
|12224|2:2|timeout| ssh output (sed -i -e ...): ssh: connect to host VM7Cent6VCL1 port 22: No route to host
|12224|2:2|timeout| ( 0) utils.pm, run_ssh_command (line: 5006)
|12224|2:2|timeout| (-1) Linux.pm, delete_user (line: 890)
|12224|2:2|timeout| (-2) Linux.pm, sanitize (line: 1177)
|12224|2:2|timeout| (-3) reclaim.pm, call_os_sanitize (line: 271)
|12224|2:2|timeout| (-4) reclaim.pm, process (line: 162)
|12224|2:2|timeout| (-5) vcld, make_new_child (line: 571)
2015-05-04 20:37:32|12224|2:2|timeout|utils.pm:run_ssh_command(4894)|sleeping for 4 seconds before making next SSH attempt
2015-05-04 20:37:36|12224|2:2|timeout|utils.pm:run_ssh_command(4906)|attempt 3/3: executing SSH command on VM7Cent6VCL1:
|12224|2:2|timeout| /usr/bin/ssh -i /etc/vcl/vcl.key -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o ConnectionAttempts=1 -o ConnectTimeout=3 -l root -p 22 -x VM7Cent6VCL1 'sed -i -e "/^AllowUsers .*/d" /etc/ssh/external_sshd_config' 2>&1
|12224|2:2|timeout| ---- WARNING ----
|12224|2:2|timeout| 2015-05-04 20:37:36|12224|2:2|timeout|utils.pm:run_ssh_command(5006)|attempt 3/3: failed to execute SSH command on VM7Cent6VCL1: 'sed -i -e "/^AllowUsers .*/d" /etc/ssh/external_sshd_config', exit status: 255, output:
|12224|2:2|timeout| ssh output (sed -i -e ...): ssh: connect to host VM7Cent6VCL1 port 22: No route to host
|12224|2:2|timeout| ( 0) utils.pm, run_ssh_command (line: 5006)
|12224|2:2|timeout| (-1) Linux.pm, delete_user (line: 890)
|12224|2:2|timeout| (-2) Linux.pm, sanitize (line: 1177)
|12224|2:2|timeout| (-3) reclaim.pm, call_os_sanitize (line: 271)
|12224|2:2|timeout| (-4) reclaim.pm, process (line: 162)
|12224|2:2|timeout| (-5) vcld, make_new_child (line: 571)
|12224|2:2|timeout| ---- WARNING ----
|12224|2:2|timeout| 2015-05-04 20:37:36|12224|2:2|timeout|utils.pm:run_ssh_command(5043)|failed to run SSH command after 3 attempts, command: /usr/bin/ssh -i /etc/vcl/vcl.key -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o ConnectionAttempts=1 -o ConnectTimeout=3 -l root -p 22 -x VM7Cent6VCL1 'sed -i -e "/^AllowUsers .*/d" /etc/ssh/external_sshd_config' 2>&1, exit status: 255, output:
|12224|2:2|timeout| ssh output (sed -i -e ...): ssh: connect to host VM7Cent6VCL1 port 22: No route to host
|12224|2:2|timeout| ( 0) utils.pm, run_ssh_command (line: 5043)
|12224|2:2|timeout| (-1) Linux.pm, delete_user (line: 890)
|12224|2:2|timeout| (-2) Linux.pm, sanitize (line: 1177)
|12224|2:2|timeout| (-3) reclaim.pm, call_os_sanitize (line: 271)
|12224|2:2|timeout| (-4) reclaim.pm, process (line: 162)
|12224|2:2|timeout| (-5) vcld, make_new_child (line: 571)
2015-05-04 20:37:36|12224|2:2|timeout|DataStructure.pm:get_computer_private_ip_address(1641)|attempting to retrieve private IP address for computer: VM7Cent6VCL1
2015-05-04 20:37:36|12224|2:2|timeout|OS.pm:get_file_contents(1897)|retrieved 12 lines from file on localhost: '/etc/hosts'
2015-05-04 20:37:36|12224|2:2|timeout|DataStructure.pm:get_computer_private_ip_address(1697)|returning IP address from /etc/hosts file: 192.168.10.48
2015-05-04 20:37:36|12224|2:2|timeout|utils.pm:is_inblockrequest(5760)|zero rows were returned from database select
2015-05-04 20:37:36|12224|2:2|timeout|DataStructure.pm:get_image_affiliation_name(2121)|image owner id: 1
2015-05-04 20:37:36|12224|2:2|timeout|DataStructure.pm:retrieve_user_data(1412)|attempting to retrieve and store data for user: user.id = '1'
2015-05-04 20:37:36|12224|2:2|timeout|DataStructure.pm:retrieve_user_data(1475)|data has been retrieved for user: admin (id: 1)
Re: Fw: PROBLEM --
localhost|2:2|timeout|Linux.pm|VM7Cent6VCL1>VM7|vmwarelinux-vm7c2testvcl212-v0|admin
Posted by "Litchfield, Elwin L." <Le...@sar.usf.edu>.
1. VM7Cent6VCL1: vmwarelinux-vm7c2testvcl212-v0(shared) powered on for a reservation and worked remotely as expected. The reservation expired on the management node and was cleared from the web page.
2. VM7Cent6VCL1: vmwarelinux-vm7c2testvcl212-v0(shared) did not power off as expected. Was unable to connect using putty to 192.168.10.48 or 131.247.29.132. ssh -i /etc/vcl/vcl.key 192.168.10.48 failed with -- ssh: connect to host 192.168.10.48 port 22: no route to host also -- ssh -i /etc/vcl/vcl.key 192.168.10.48 failed the same way. The root password does not work any more, but users admin(created by VCL) & vcluser (created at installation time) will work.
3. Restarted VM7Cent6VCL1: vmwarelinux-vm7c2testvcl212-v0(shared) was able to open the putty signon page enter a user id, but the password was rejected. ssh -i /etc/vcl/vcl.key 192.168.10.48 & ssh -i /etc/vcl/vcl.key 192.168.10.48 connected from the management server.
4. Powered down VM7Cent6VCL1: vmwarelinux-vm7c2testvcl212-v0(shared), created a reservation, waited for VM7Cent6VCL1: vmwarelinux-vm7c2testvcl212-v0(shared) to be powered on, logged in with RDP, played around, logged off.
VM7Cent6VCL1: vmwarelinux-vm7c2testvcl212-v0(shared) did not power off as expected. Go back to step 2.
Anything I should look for?
Lewis Litchfield
Technology Services – Viking Center Lab
University of South Florida Sarasota-Manatee
941-359-4231
________________________________________
From: Aaron Peeler <fa...@ncsu.edu>
Sent: Wednesday, May 6, 2015 9:15 AM
To: Elwin Litchfield
Cc: user@vcl.apache.org
Subject: Re: Fw: PROBLEM -- localhost|2:2|timeout|Linux.pm|VM7Cent6VCL1>VM7|vmwarelinux-vm7c2testvcl212-v0|admin
you should always be able to ssh to the node using ssh -i
/etc/vcl/vcl.key 192.168.10.48 from your management node as root.
The admin account is just the user account you made the reservation as
while logged into the VCL web interface.
On Wed, May 6, 2015 at 8:26 AM, Elwin Litchfield <le...@mail.usf.edu> wrote:
> After some investigation I thought the problem connecting via port 22 was in
> external_sshd_config because the LISTENADDRESS 131.247.29.132 was
> configured.
> A new user admin was created, but the root password was changed. I was not
> able to change the LISTENADDRESS to 192.168.10.48, the management network,
> using gedit.
> I was able to change it using vi. sshd service could not be restarted
> because the root password must have been changed when the new admin user was
> created. none of the known user passwords would work to restart sshd.
> After reboot I was able to connect to 192.168.10.48 via putty or WinSCP, but
> not logon. I tried all combinations of known users & passwords, all were
> Access denied. But ssh -i /etc/vcl/vcl.key 192.168.10.48 connected. Also
> the LISTENADDRESS 192.168.10.48 I had configured had changed back to
> 131.247.29.132
>
> Looks like I lost the failing connection via ssh condition by rebooting. I
> checked netstat before the reboot and 192.168.10.48:ssh was there. After
> reboot both 131.247.29.132:ssh & 192.168.10.48:ssh were there.
>
> Any ideas? Or what to look for before rebooting?
>
>
> On Tue, May 5, 2015 at 10:25 AM, Elwin Litchfield <le...@mail.usf.edu>
> wrote:
>>
>> no route to host error means that port 22 is not accessible True unable
>> to putty to the host, also ssh -i /etc/vcl/vcl.key 192.168.10.48 worked in
>> the past, but is now failing. I had a problem with a XenServer Centos 6
>> VM changing the ssh listen IP addresses to other networks from the
>> management network. I removed all networks except the Public & Private
>> networks but have not been able to test yet.
>>
>> Is VM7Cent6VCL1 pingable from the management node? Yes
>>
>> If not check your, maybe your dhcp settings are not correct and it's
>> not getting an address on your VCL private network? DHCP settings
>> match the ifconfig in VM6Cent6VCL1.
>>
>> Also did you figure out the MAC address to use? It looks like
>> 00:50:56:XX:YY:ZZ is ok if the XX is not a high value. 00:50:56:3F:40:E3
>> worked till the VM quit listening to port 22 on the management network. I
>> will research the XX value to determine the range that will work.
>>
>> It appears that I have two image name that point to the same virtual
>> machine - VM7Cent6VCL1, but have two virtual image machines. I am in the
>> process of installing a new VM to test using a clean install without on the
>> fly modifications.
>>
>>
>> On Tue, May 5, 2015 at 9:38 AM, Aaron Peeler <fa...@ncsu.edu> wrote:
>>>
>>> no route to host error means that port 22 is not accessible
>>>
>>> Is VM7Cent6VCL1 pingable from the management node?
>>>
>>> If not check your, maybe your dhcp settings are not correct and it's
>>> not getting an address on your VCL private network?
>>>
>>> Also did you figure out the MAC address to use?
>>>
>>>
>>>
>>>
>>>
>>> On Mon, May 4, 2015 at 8:52 PM, Litchfield, Elwin L.
>>> <Le...@sar.usf.edu> wrote:
>>> > The reservation expired & the VM is still powered on. Where should I
>>> > be looking?
>>> >
>>> > Lewis Litchfield
>>> > Technology Services – Viking Center Lab
>>> > University of South Florida Sarasota-Manatee
>>> > 941-359-4231
>>> >
>>>
>>>
>>>
>>> --
>>> Aaron Peeler
>>> Program Manager
>>> Virtual Computing Lab
>>> NC State University
>>>
>>> All electronic mail messages in connection with State business which
>>> are sent to or received by this account are subject to the NC Public
>>> Records Law and may be disclosed to third parties.
>>
>>
>
--
Aaron Peeler
Program Manager
Virtual Computing Lab
NC State University
All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.
Re: Fw: PROBLEM -- localhost|2:2|timeout|Linux.pm|VM7Cent6VCL1>VM7|vmwarelinux-vm7c2testvcl212-v0|admin
Posted by Aaron Peeler <fa...@ncsu.edu>.
you should always be able to ssh to the node using ssh -i
/etc/vcl/vcl.key 192.168.10.48 from your management node as root.
The admin account is just the user account you made the reservation as
while logged into the VCL web interface.
On Wed, May 6, 2015 at 8:26 AM, Elwin Litchfield <le...@mail.usf.edu> wrote:
> After some investigation I thought the problem connecting via port 22 was in
> external_sshd_config because the LISTENADDRESS 131.247.29.132 was
> configured.
> A new user admin was created, but the root password was changed. I was not
> able to change the LISTENADDRESS to 192.168.10.48, the management network,
> using gedit.
> I was able to change it using vi. sshd service could not be restarted
> because the root password must have been changed when the new admin user was
> created. none of the known user passwords would work to restart sshd.
> After reboot I was able to connect to 192.168.10.48 via putty or WinSCP, but
> not logon. I tried all combinations of known users & passwords, all were
> Access denied. But ssh -i /etc/vcl/vcl.key 192.168.10.48 connected. Also
> the LISTENADDRESS 192.168.10.48 I had configured had changed back to
> 131.247.29.132
>
> Looks like I lost the failing connection via ssh condition by rebooting. I
> checked netstat before the reboot and 192.168.10.48:ssh was there. After
> reboot both 131.247.29.132:ssh & 192.168.10.48:ssh were there.
>
> Any ideas? Or what to look for before rebooting?
>
>
> On Tue, May 5, 2015 at 10:25 AM, Elwin Litchfield <le...@mail.usf.edu>
> wrote:
>>
>> no route to host error means that port 22 is not accessible True unable
>> to putty to the host, also ssh -i /etc/vcl/vcl.key 192.168.10.48 worked in
>> the past, but is now failing. I had a problem with a XenServer Centos 6
>> VM changing the ssh listen IP addresses to other networks from the
>> management network. I removed all networks except the Public & Private
>> networks but have not been able to test yet.
>>
>> Is VM7Cent6VCL1 pingable from the management node? Yes
>>
>> If not check your, maybe your dhcp settings are not correct and it's
>> not getting an address on your VCL private network? DHCP settings
>> match the ifconfig in VM6Cent6VCL1.
>>
>> Also did you figure out the MAC address to use? It looks like
>> 00:50:56:XX:YY:ZZ is ok if the XX is not a high value. 00:50:56:3F:40:E3
>> worked till the VM quit listening to port 22 on the management network. I
>> will research the XX value to determine the range that will work.
>>
>> It appears that I have two image name that point to the same virtual
>> machine - VM7Cent6VCL1, but have two virtual image machines. I am in the
>> process of installing a new VM to test using a clean install without on the
>> fly modifications.
>>
>>
>> On Tue, May 5, 2015 at 9:38 AM, Aaron Peeler <fa...@ncsu.edu> wrote:
>>>
>>> no route to host error means that port 22 is not accessible
>>>
>>> Is VM7Cent6VCL1 pingable from the management node?
>>>
>>> If not check your, maybe your dhcp settings are not correct and it's
>>> not getting an address on your VCL private network?
>>>
>>> Also did you figure out the MAC address to use?
>>>
>>>
>>>
>>>
>>>
>>> On Mon, May 4, 2015 at 8:52 PM, Litchfield, Elwin L.
>>> <Le...@sar.usf.edu> wrote:
>>> > The reservation expired & the VM is still powered on. Where should I
>>> > be looking?
>>> >
>>> > Lewis Litchfield
>>> > Technology Services – Viking Center Lab
>>> > University of South Florida Sarasota-Manatee
>>> > 941-359-4231
>>> >
>>>
>>>
>>>
>>> --
>>> Aaron Peeler
>>> Program Manager
>>> Virtual Computing Lab
>>> NC State University
>>>
>>> All electronic mail messages in connection with State business which
>>> are sent to or received by this account are subject to the NC Public
>>> Records Law and may be disclosed to third parties.
>>
>>
>
--
Aaron Peeler
Program Manager
Virtual Computing Lab
NC State University
All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.
Re: Fw: PROBLEM -- localhost|2:2|timeout|Linux.pm|VM7Cent6VCL1>VM7|vmwarelinux-vm7c2testvcl212-v0|admin
Posted by Elwin Litchfield <le...@mail.usf.edu>.
After some investigation I thought the problem connecting via port 22 was
in external_sshd_config because the LISTENADDRESS 131.247.29.132 was
configured.
A new user admin was created, but the root password was changed. I was not
able to change the LISTENADDRESS to 192.168.10.48, the management network,
using gedit.
I was able to change it using vi. sshd service could not be restarted
because the root password must have been changed when the new admin user
was created. none of the known user passwords would work to restart sshd.
After reboot I was able to connect to 192.168.10.48 via putty or WinSCP,
but not logon. I tried all combinations of known users & passwords, all
were Access denied. But ssh -i /etc/vcl/vcl.key 192.168.10.48 connected.
Also the LISTENADDRESS 192.168.10.48 I had configured had changed back to
131.247.29.132
Looks like I lost the failing connection via ssh condition by rebooting. I
checked netstat before the reboot and 192.168.10.48:ssh was there. After
reboot both 131.247.29.132:ssh & 192.168.10.48:ssh were there.
Any ideas? Or what to look for before rebooting?
On Tue, May 5, 2015 at 10:25 AM, Elwin Litchfield <le...@mail.usf.edu>
wrote:
> no route to host error means that port 22 is not accessible True unable
> to putty to the host, also ssh -i /etc/vcl/vcl.key 192.168.10.48 worked in
> the past, but is now failing. I had a problem with a XenServer Centos 6
> VM changing the ssh listen IP addresses to other networks from the
> management network. I removed all networks except the Public & Private
> networks but have not been able to test yet.
>
> Is VM7Cent6VCL1 pingable from the management node? Yes
>
> If not check your, maybe your dhcp settings are not correct and it's
> not getting an address on your VCL private network? DHCP settings
> match the ifconfig in VM6Cent6VCL1.
>
> Also did you figure out the MAC address to use? It looks like
> 00:50:56:XX:YY:ZZ is ok if the XX is not a high value. 00:50:56:3F:40:E3
> worked till the VM quit listening to port 22 on the management network. I
> will research the XX value to determine the range that will work.
>
> It appears that I have two image name that point to the same virtual
> machine - VM7Cent6VCL1, but have two virtual image machines. I am in the
> process of installing a new VM to test using a clean install without on the
> fly modifications.
>
>
> On Tue, May 5, 2015 at 9:38 AM, Aaron Peeler <fa...@ncsu.edu> wrote:
>
>> no route to host error means that port 22 is not accessible
>>
>> Is VM7Cent6VCL1 pingable from the management node?
>>
>> If not check your, maybe your dhcp settings are not correct and it's
>> not getting an address on your VCL private network?
>>
>> Also did you figure out the MAC address to use?
>>
>>
>>
>>
>>
>> On Mon, May 4, 2015 at 8:52 PM, Litchfield, Elwin L.
>> <Le...@sar.usf.edu> wrote:
>> > The reservation expired & the VM is still powered on. Where should I
>> be looking?
>> >
>> > Lewis Litchfield
>> > Technology Services – Viking Center Lab
>> > University of South Florida Sarasota-Manatee
>> > 941-359-4231
>> >
>>
>>
>>
>> --
>> Aaron Peeler
>> Program Manager
>> Virtual Computing Lab
>> NC State University
>>
>> All electronic mail messages in connection with State business which
>> are sent to or received by this account are subject to the NC Public
>> Records Law and may be disclosed to third parties.
>>
>
>
Re: Fw: PROBLEM -- localhost|2:2|timeout|Linux.pm|VM7Cent6VCL1>VM7|vmwarelinux-vm7c2testvcl212-v0|admin
Posted by Elwin Litchfield <le...@mail.usf.edu>.
no route to host error means that port 22 is not accessible True unable to
putty to the host, also ssh -i /etc/vcl/vcl.key 192.168.10.48 worked in the
past, but is now failing. I had a problem with a XenServer Centos 6 VM
changing the ssh listen IP addresses to other networks from the management
network. I removed all networks except the Public & Private networks but
have not been able to test yet.
Is VM7Cent6VCL1 pingable from the management node? Yes
If not check your, maybe your dhcp settings are not correct and it's
not getting an address on your VCL private network? DHCP settings match
the ifconfig in VM6Cent6VCL1.
Also did you figure out the MAC address to use? It looks like
00:50:56:XX:YY:ZZ is ok if the XX is not a high value. 00:50:56:3F:40:E3
worked till the VM quit listening to port 22 on the management network. I
will research the XX value to determine the range that will work.
It appears that I have two image name that point to the same virtual
machine - VM7Cent6VCL1, but have two virtual image machines. I am in the
process of installing a new VM to test using a clean install without on the
fly modifications.
On Tue, May 5, 2015 at 9:38 AM, Aaron Peeler <fa...@ncsu.edu> wrote:
> no route to host error means that port 22 is not accessible
>
> Is VM7Cent6VCL1 pingable from the management node?
>
> If not check your, maybe your dhcp settings are not correct and it's
> not getting an address on your VCL private network?
>
> Also did you figure out the MAC address to use?
>
>
>
>
>
> On Mon, May 4, 2015 at 8:52 PM, Litchfield, Elwin L.
> <Le...@sar.usf.edu> wrote:
> > The reservation expired & the VM is still powered on. Where should I be
> looking?
> >
> > Lewis Litchfield
> > Technology Services – Viking Center Lab
> > University of South Florida Sarasota-Manatee
> > 941-359-4231
> >
>
>
>
> --
> Aaron Peeler
> Program Manager
> Virtual Computing Lab
> NC State University
>
> All electronic mail messages in connection with State business which
> are sent to or received by this account are subject to the NC Public
> Records Law and may be disclosed to third parties.
>
Re: Fw: PROBLEM -- localhost|2:2|timeout|Linux.pm|VM7Cent6VCL1>VM7|vmwarelinux-vm7c2testvcl212-v0|admin
Posted by Aaron Peeler <fa...@ncsu.edu>.
no route to host error means that port 22 is not accessible
Is VM7Cent6VCL1 pingable from the management node?
If not check your, maybe your dhcp settings are not correct and it's
not getting an address on your VCL private network?
Also did you figure out the MAC address to use?
On Mon, May 4, 2015 at 8:52 PM, Litchfield, Elwin L.
<Le...@sar.usf.edu> wrote:
> The reservation expired & the VM is still powered on. Where should I be looking?
>
> Lewis Litchfield
> Technology Services – Viking Center Lab
> University of South Florida Sarasota-Manatee
> 941-359-4231
>
--
Aaron Peeler
Program Manager
Virtual Computing Lab
NC State University
All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.