Not visible the contents of storage.

K

KingLEV

New Member
Jun 13, 2013
10
0
1
Russia, Novosibirsk
I had a problem with one of the servers. Not visible the contents of storage. On the other servers in the cluster storage contents visible(001.jpg)001.jpg
At the same time, the status displays information about used and available space (002.jpg).
002.jpg
On another servers all content is displayed.
003.jpg
What is the problem and how can I solve without reinstalling Proxmox? Reboot not solve this problem.
Proxmox 3.0
 
PMNode003 (not visible content of storage):
pveversion -v
pve-manager: 3.0-23 (pve-manager/3.0/957f0862)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-20-pve: 2.6.32-100
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.0-20
pve-firmware: 1.0-23
libpve-common-perl: 3.0-8
libpve-access-control: 3.0-7
libpve-storage-perl: 3.0-8
vncterm: 1.1-4
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-13
ksm-control-daemon: 1.1-1

PMNode002 (visible content of storage):
pveversion -v
pve-manager: 3.0-20 (pve-manager/3.0/0428106c)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-20-pve: 2.6.32-100
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-4
qemu-server: 3.0-15
pve-firmware: 1.0-22
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-6
vncterm: 1.1-3
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-12
ksm-control-daemon: 1.1-1
 
You can try restart the pve-manager. /etc/init.d/pve-manager restart.
 
tom said:
just to note, you run a very outdated version - consider upgrading to latest 3.3. this will probably fix your issue.

http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_3.x_to_latest_3.3
Click to expand...

I see you all on the one answer in all the ticket. I want to continue to use a completely free version with a complete set of repositories. So I continue to use version 3.0. And I'm interested in the solution of the problem. Headache Treatment Cutting off the head - not a right decision.
 
tom said:
you want a bugfix but you reject to update to the fixed version?

and you also missed that 3.3 is still complete free and there is also a repository for people who do not want to use the pve-enterprise repo.
=> use the pve-no-subscription repository - running 3.0 is a security risk for your hosts.

http://pve.proxmox.com/wiki/Package_repositories#Proxmox_VE_No-Subscription_Repository
Click to expand...

I'm interested in the solution to my problem within the installed version. Security problems solved in another way.
If you can not answer the question without insisting on updating, please do not offtop the ticket.
Thanks.
 
KingLEV said:
I'm interested in the solution to my problem within the installed version. Security problems solved in another way.
If you can not answer the question without insisting on updating, please do not offtop the ticket.
Thanks.
Click to expand...

if you want to find it out, check all your syslog and then compare all applied fixes after 3.0. just use https://git.proxmox.com/.

there is no simple answer to your issue without deep analysis. Debugging a Proxmox VE cluster issue is a challenging task and there are many subsystems involved - its probably easier to just upload the already provided fixes instead of hunting for a probably already fixed bug again - IMHO this could be a waste of (your) time.
 
tom said:
if you want to find it out, check all your syslog and then compare all applied fixes after 3.0. just use https://git.proxmox.com/.

there is no simple answer to your issue without deep analysis. Debugging a Proxmox VE cluster issue is a challenging task and there are many subsystems involved - its probably easier to just upload the already provided fixes instead of hunting for a probably already fixed bug again - IMHO this could be a waste of (your) time.
Click to expand...

Is it possible to rollback versions specified in the server PMNode003 to server versions exist in PMNode002? (Second post in this ticket)
 
yes, but you need to know all packages and you need to manually downgrade each package via CLI.

but all nodes in the cluster needs to be on the same software level, so just upgrading one node is not a solution.
 
tom said:
yes, but you need to know all packages and you need to manually downgrade each package via CLI.

but all nodes in the cluster needs to be on the same software level, so just upgrading one node is not a solution.
Click to expand...

I'm on all three servers are different versions of the packages:
PMNode001:~# pveversion -v
pve-manager: 3.0-23 (pve-manager/3.0/957f0862)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-20-pve: 2.6.32-100
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-4
qemu-server: 3.0-20
pve-firmware: 1.0-22
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-8
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-13
ksm-control-daemon: 1.1-1
---
PMNode002:/# pveversion -v
pve-manager: 3.0-20 (pve-manager/3.0/0428106c)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-20-pve: 2.6.32-100
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-4
qemu-server: 3.0-15
pve-firmware: 1.0-22
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-6
vncterm: 1.1-3
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-12
ksm-control-daemon: 1.1-1
-----
PMNode003:~# pveversion -v
pve-manager: 3.0-23 (pve-manager/3.0/957f0862)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-20-pve: 2.6.32-100
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.0-20
pve-firmware: 1.0-23
libpve-common-perl: 3.0-8
libpve-access-control: 3.0-7
libpve-storage-perl: 3.0-8
vncterm: 1.1-4
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-13
ksm-control-daemon: 1.1-1

But the content of storages visible on the PMNode001 and PMNode002...
 
KingLEV said:
I'm on all three servers are different versions of the packages:
..
Click to expand...

thats a good hint. make always sure that you have identical packages on all hosts.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back