Hello,
I made a misstake and tried to do a backup into /var/lib/vz and additional it was not enough space left. I solved the problem by putting the node2 out of backup lock and rebooting node2. After that both nodes showed the OS partition with 100% full. The smb on node2 was still reachable. I then deleted the over 90GB *.dat file on node2 and rebooted both servers. I got some error messages for drb files on both servers but they booted, gon online, vm's are running and the OS partition size is back to 2% in use. Everything seems back to normall excluding the smb on node2.
So now the files via smb on node1 are reachable but i can't get a smb connection on node2. I have pinged both ip's of the node and got a pong back. Also i can access both nodes via ssh so i to time have no clue why the smb in node2 isn't reachable.
Some more information:
It look like that some table informations are corrupted or just wrong. I can run the VM's and everything seem's to be ok excluding that the filebox isn't reachable.
http://pic-hoster.net/view/51154/Bil...um16.32.02.png
http://pic-hoster.net/view/51155/Bil...um16.31.33.png
http://pic-hoster.net/view/51157/Bil...um17.00.58.png
I know that i have to update but im new in this company, we dono have a backup server for the importend files and we also dono have a NAS server. Next week we have production week and i dono want to risk to loos the importend data. There for i want to clone the server later, and migrate a 3th backup server after everything is working like it should. If im then have a backup server i can work on the importend serv to update and to get it running. Just to clarify why im still on the v1.9.
And i allready have a big problem in case of that we can't access the file server. :(
Some more information:
fs2:/etc/lvm# pveversion -v
pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-55+ovzfix-1
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.32-6-pve: 2.6.32-55+ovzfix-1
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-2
ksm-control-daemon: 1.0-6
pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-55+ovzfix-1
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.32-6-pve: 2.6.32-55+ovzfix-1
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-2
ksm-control-daemon: 1.0-6
Also i got a email from server telling me this:
<admin@XXX.at> (expanded from <root>): host terminal.sil.at[88.198.105.243]
said: 550-Verification failed for <root@fs1.localdomain> 550-Invalid domain
part in email address 550 Sender verify failed (in reply to RCPT TO
command)
Reporting-MTA: dns; fs1.localdomain
X-Postfix-Queue-ID: C00BB234354
X-Postfix-Sender: rfc822; root@fs1.localdomain
Arrival-Date: Sat, 2 Feb 2013 18:25:37 +0100 (CET)
Final-Recipient: rfc822; admin@XXX.at
Original-Recipient: rfc822; root
Action: failed
Status: 5.0.0
Remote-MTA: dns; terminal.sil.at
Diagnostic-Code: smtp; 550-Verification failed for <root@fs1.localdomain>
550-Invalid domain part in email address 550 Sender verify failed
Von: root@fs1.localdomain (Cron Daemon)
Datum: 02. Februar 2013 06:25:02 MEZ
An: root@fs1.localdomain
Betreff: Cron <root@fs1> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
/etc/cron.daily/man-db:
/usr/bin/mandb: can't write to /var/cache/man/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/ja/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/zh_TW/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/de/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/ko/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/fr/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/it.ISO8859-1/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/ru/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/pl.ISO8859-2/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/pl.UTF-8/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/sv/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/fr.ISO8859-1/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/fi/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/es/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/zh_CN/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/pt_BR/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/id/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/pl/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/cs/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/fr.UTF-8/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/it.UTF-8/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/hu/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/gl/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/tr/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/it/750685: No space left on device
/usr/bin/mandb: can't create index cache /var/cache/man/oldlocal/750685: No space left on device
/usr/bin/mandb: can't create index cache /var/cache/man/local/750685: No space left on device
(i deleted the companys name out of the email address cause i dono know if im allowed to post it.)
I made a misstake and tried to do a backup into /var/lib/vz and additional it was not enough space left. I solved the problem by putting the node2 out of backup lock and rebooting node2. After that both nodes showed the OS partition with 100% full. The smb on node2 was still reachable. I then deleted the over 90GB *.dat file on node2 and rebooted both servers. I got some error messages for drb files on both servers but they booted, gon online, vm's are running and the OS partition size is back to 2% in use. Everything seems back to normall excluding the smb on node2.
So now the files via smb on node1 are reachable but i can't get a smb connection on node2. I have pinged both ip's of the node and got a pong back. Also i can access both nodes via ssh so i to time have no clue why the smb in node2 isn't reachable.
Some more information:
It look like that some table informations are corrupted or just wrong. I can run the VM's and everything seem's to be ok excluding that the filebox isn't reachable.
http://pic-hoster.net/view/51154/Bil...um16.32.02.png
http://pic-hoster.net/view/51155/Bil...um16.31.33.png
http://pic-hoster.net/view/51157/Bil...um17.00.58.png
I know that i have to update but im new in this company, we dono have a backup server for the importend files and we also dono have a NAS server. Next week we have production week and i dono want to risk to loos the importend data. There for i want to clone the server later, and migrate a 3th backup server after everything is working like it should. If im then have a backup server i can work on the importend serv to update and to get it running. Just to clarify why im still on the v1.9.
And i allready have a big problem in case of that we can't access the file server. :(
Some more information:
fs2:/etc/lvm# pveversion -v
pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-55+ovzfix-1
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.32-6-pve: 2.6.32-55+ovzfix-1
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-2
ksm-control-daemon: 1.0-6
pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-55+ovzfix-1
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.32-6-pve: 2.6.32-55+ovzfix-1
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-2
ksm-control-daemon: 1.0-6
Also i got a email from server telling me this:
<admin@XXX.at> (expanded from <root>): host terminal.sil.at[88.198.105.243]
said: 550-Verification failed for <root@fs1.localdomain> 550-Invalid domain
part in email address 550 Sender verify failed (in reply to RCPT TO
command)
Reporting-MTA: dns; fs1.localdomain
X-Postfix-Queue-ID: C00BB234354
X-Postfix-Sender: rfc822; root@fs1.localdomain
Arrival-Date: Sat, 2 Feb 2013 18:25:37 +0100 (CET)
Final-Recipient: rfc822; admin@XXX.at
Original-Recipient: rfc822; root
Action: failed
Status: 5.0.0
Remote-MTA: dns; terminal.sil.at
Diagnostic-Code: smtp; 550-Verification failed for <root@fs1.localdomain>
550-Invalid domain part in email address 550 Sender verify failed
Von: root@fs1.localdomain (Cron Daemon)
Datum: 02. Februar 2013 06:25:02 MEZ
An: root@fs1.localdomain
Betreff: Cron <root@fs1> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
/etc/cron.daily/man-db:
/usr/bin/mandb: can't write to /var/cache/man/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/ja/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/zh_TW/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/de/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/ko/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/fr/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/it.ISO8859-1/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/ru/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/pl.ISO8859-2/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/pl.UTF-8/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/sv/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/fr.ISO8859-1/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/fi/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/es/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/zh_CN/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/pt_BR/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/id/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/pl/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/cs/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/fr.UTF-8/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/it.UTF-8/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/hu/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/gl/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/tr/750685: No space left on device
/usr/bin/mandb: can't write to /var/cache/man/it/750685: No space left on device
/usr/bin/mandb: can't create index cache /var/cache/man/oldlocal/750685: No space left on device
/usr/bin/mandb: can't create index cache /var/cache/man/local/750685: No space left on device
(i deleted the companys name out of the email address cause i dono know if im allowed to post it.)