Proxmox server help

D

dal.01

New Member
Jan 6, 2012
16
0
1
I have 1.9 running with three servers. I got a message saying that my Proxmox host is down (cant ping, cant reach via web browser), but I am able to reach the KVMs.

Any thoughts??
 
I do have a firewall, but have had no issues with the firewall, I've double checked settings in the firewall and nothing has changed. I cant even ssh into the box, I cant ping the box, I cant access the box via web browser, so I dont think that I can get to the log files.

I do not want to restart in case this problem carries over to the virtual machines. I can access each virtual machine fine, but cannot do the above things to access the Proxmox box itself.
 
I dont mean to keep reposing like I am, but this is a major issue for me right now and would love some guidance.


Why would it be that I am not able to reach (ping, traverse via web browser, ssh, any thing) the Proxmox box that is hosting the 3 virtual servers, but AM able to reach the three servers that are running? The Proxmox host has a single NIC in it so all network traffic travels through this one NIC.

Would a restart solve this issue? I am worried that the issue will flow over to the virtual boxes.

I have checked my firewall (sonicwall tz-210) and there is nothing blocking the IP of the Proxmox box. Im out of ideas on ways to solve this issue without the restart of the server, which cant be done during business hours.


Thanks to all for any insight they can pass onto me.
 
Last edited:
dal.01 said:
I dont mean to keep reposing like I am, but this is a major issue for me right now and would love some guidance.


Why would it be that I am not able to reach (ping, traverse via web browser, ssh, any thing) the Proxmox box that is hosting the 3 virtual servers, but AM able to reach the three servers that are running? The Proxmox host has a single NIC in it so all network traffic travels through this one NIC.

Would a restart solve this issue? I am worried that the issue will flow over to the virtual boxes.

I have checked my firewall (sonicwall tz-210) and there is nothing blocking the IP of the Proxmox box. Im out of ideas on ways to solve this issue without the restart of the server, which cant be done during business hours.


Thanks to all for any insight they can pass onto me.
Click to expand...
Hi,
you don't have kvm-access (keyboard-video-mouse) to the server?

Can you ping the pve-host from the running VM (because only one nic, they are in the same network?!)?

Udo
 
So I was able to ping through the vm to the pve-host. I then used putty to ssh into the pve-host. Here are the ouputs of what you requested in your first post:


Code: 
:~# ifconfig -aeth0      Link encap:Ethernet  HWaddr 00:21:85:93:38:0a
          inet6 addr: fe80::221:85ff:fe93:380a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:31198654 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29209351 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:19966028110 (18.5 GiB)  TX bytes:19748466619 (18.3 GiB)
          Interrupt:23 Base address:0x6000


lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:103139 errors:0 dropped:0 overruns:0 frame:0
          TX packets:103139 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:39472251 (37.6 MiB)  TX bytes:39472251 (37.6 MiB)


tap101i0d0 Link encap:Ethernet  HWaddr 96:e3:fa:de:73:bd
          inet6 addr: fe80::94e3:faff:fede:73bd/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:27173084 errors:0 dropped:0 overruns:0 frame:0
          TX packets:28642392 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:19198803404 (17.8 GiB)  TX bytes:19570104409 (18.2 GiB)


tap106i0d0 Link encap:Ethernet  HWaddr de:0e:7e:b1:2c:df
          inet6 addr: fe80::dc0e:7eff:feb1:2cdf/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:49001 errors:0 dropped:0 overruns:0 frame:0
          TX packets:975219 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:3702337 (3.5 MiB)  TX bytes:78722724 (75.0 MiB)


tap107i0d0 Link encap:Ethernet  HWaddr b2:ca:71:89:44:74
          inet6 addr: fe80::b0ca:71ff:fe89:4474/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:237685 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3589244 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:127845667 (121.9 MiB)  TX bytes:318076884 (303.3 MiB)


venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet6 addr: fe80::1/128 Scope:Link
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


vmbr0     Link encap:Ethernet  HWaddr 00:21:85:93:38:0a
          inet addr:10.10.1.251  Bcast:10.10.1.255  Mask:255.255.255.0
          inet6 addr: fe80::221:85ff:fe93:380a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5167087 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1713968 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:455029323 (433.9 MiB)  TX bytes:293560993 (279.9 MiB)










:~# brctl show
bridge name     bridge id               STP enabled     interfaces
vmbr0           8000.00218593380a       no              eth0
                                                        tap101i0d0
                                                        tap106i0d0
                                                        tap107i0d0










:~# cat /etc/network/interfaces
# network interface settings
auto lo
iface lo inet loopback


iface eth0 inet manual


auto vmbr0
iface vmbr0 inet static
        address  10.10.1.251
        netmask  255.255.255.0
        gateway  192.168.1.1
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0

I still cannot access anything outside of the VM.
 
Last edited:
dal.01 said:
So I was able to ping through the vm to the pve-host.
...
Code: 
auto vmbr0
iface vmbr0 inet static
        address  10.10.1.251
        netmask  255.255.255.0
        [B]gateway  192.168.1.1[/B]
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0

I still cannot access anything outside of the VM.
Click to expand...
Hi,
the gateway is wrong!
A gateway must be in the same network - e.g. 10.10.1.1 or 10.10.1.254

Udo
 
JESUS......Feel like a noob. But how would that have changed in the middle of the day?? I use Spiceworks to keep tabs on equipment, was emailing a client and got a message that the server went off line. Checked and went through what I described above in first post...doesnt make sense. Anyhoo...


Thanks for the help udo, I really appreciate it! +rep for the help!!
 
You must log in or register to reply here.
Top Bottom