Backus to an /backup Directory not working

C

Church23

New Member
Nov 5, 2011
22
0
1
Hello
I has made an Update to get the New Features.
Looks all realy good :cool:
I have an Directory in / with name backup the Size is 250GB = /backup with 250 GB
Now i wanted make an Backup to this Directory.
But the /backup Directory has no Content.
Here the Output from Syslog
Code: 
Nov 19 18:45:01 proxmox /USR/SBIN/CRON[4080]: (root) CMD (vzdump 100 102  104 105 107 --quiet 1 --mode snapshot --mailto xxx@example.com --compress 1 --maxfiles 1 --storage backup)
Nov 19 18:45:02 proxmox /USR/SBIN/CRON[4078]: (CRON) error (grandchild #4080 failed with exit status 2)
Nov 19 18:45:02 proxmox /USR/SBIN/CRON[4078]: (CRON) info (No MTA installed, discarding output)
Nov 19 18:48:54 proxmox pvedaemon[1922]: <root@pam> successful auth for user 'root@pam'
Nov  19 18:52:49 proxmox pvedaemon[1923]: <root@pam> starting task  UPID:proxmox:00001175:000487B6:4EC7ECF1:srvstart:postfix:root@pam:
Nov  19 18:52:49 proxmox pvedaemon[4469]: starting service postfix:  UPID:proxmox:00001175:000487B6:4EC7ECF1:srvstart:postfix:root@pam:
Nov  19 18:52:49 proxmox pvedaemon[4471]: WARNING: Can't exec  "/etc/init.d/postfix": No such file or directory at  /usr/share/perl/5.10/IPC/Open3.pm line 168.
Nov 19 18:52:49 proxmox  pvedaemon[4471]: WARNING: open3: exec of /etc/init.d/postfix start  failed at /usr/share/perl5/PVE/Tools.pm line 229
Nov 19 18:52:49 proxmox pvedaemon[4469]: command '/etc/init.d/postfix start' failed: exit code 255
Nov  19 18:52:49 proxmox pvedaemon[1923]: <root@pam> end task  UPID:proxmox:00001175:000487B6:4EC7ECF1:srvstart:postfix:root@pam:  command '/etc/init.d/postfix start' failed: exit code 255
Nov 19  18:53:10 proxmox pvedaemon[1924]: <root@pam> starting task  UPID:proxmox:00001188:00048FFA:4EC7ED06:srvstart:postfix:root@pam:
Nov  19 18:53:10 proxmox pvedaemon[4488]: starting service postfix:  UPID:proxmox:00001188:00048FFA:4EC7ED06:srvstart:postfix:root@pam:
Nov  19 18:53:10 proxmox pvedaemon[4489]: WARNING: Can't exec  "/etc/init.d/postfix": No such file or directory at  /usr/share/perl/5.10/IPC/Open3.pm line 168.
Nov 19 18:53:10 proxmox  pvedaemon[4489]: WARNING: open3: exec of /etc/init.d/postfix start  failed at /usr/share/perl5/PVE/Tools.pm line 229
Nov 19 18:53:10 proxmox pvedaemon[4488]: command '/etc/init.d/postfix start' failed: exit code 255
Nov  19 18:53:10 proxmox pvedaemon[1924]: <root@pam> end task  UPID:proxmox:00001188:00048FFA:4EC7ED06:srvstart:postfix:root@pam:  command '/etc/init.d/postfix start' failed: exit code 255
Nov 19 18:56:01 proxmox /usr/sbin/cron[1894]: (*system*vzdump) RELOAD (/etc/cron.d/vzdump)
Nov  19 19:00:01 proxmox /USR/SBIN/CRON[4869]: (root) CMD (vzdump 100 102  104 105 107 --quiet 1 --mode snapshot --compress 1 --maxfiles 1  --storage backup)
Nov 19 19:00:01 proxmox /USR/SBIN/CRON[4867]: (CRON) error (grandchild #4869 failed with exit status 2)
Nov 19 19:00:01 proxmox /USR/SBIN/CRON[4867]: (CRON) info (No MTA installed, discarding output)
Nov 19 19:03:37 proxmox rrdcached[1723]: flushing old values
Nov 19 19:03:37 proxmox rrdcached[1723]: rotating journals
Nov 19 19:03:37 proxmox rrdcached[1723]: started new journal /var/lib/rrdcached/journal//rrd.journal.1321725817.754965
So whats going wrong?
 
Can you post your pveversion -v ?

It works for me... did you use the button 'Backup now' ? you have postfix errors...

Alain
 
Code: 
pveversion -v pve-manager: 2.0-10 (pve-manager/2.0/7a10f3e6) running kernel: 2.6.32-6-pve proxmox-ve-2.6.32: 2.0-52 pve-kernel-2.6.32-6-pve: 2.6.32-52 lvm2: 2.02.86-1pve1 clvm: 2.02.86-1pve1 corosync-pve: 1.4.1-1 openais-pve: 1.1.4-1 libqb: 0.6.0-1 redhat-cluster-pve: 3.1.7-1 pve-cluster: 1.0-11 qemu-server: 2.0-4 pve-firmware: 1.0-13 libpve-common-perl: 1.0-7 libpve-access-control: 1.0-2 libpve-storage-perl: 2.0-6 vncterm: 1.0-2 vzctl: 3.0.29-3pve3 vzprocps: not correctly installed vzquota: 3.0.12-3 pve-qemu-kvm: 0.15.0-1 ksm-control-daemon: not correctly installed
The Backup now has not working too , now i has installed sendmail and it works. I testing now the Backup Task. Postfix is not installed it is exim so i saw and now sendmail. So after i has installed sendmail the Backups works.
When i try to start smtp
Code: 
TASK ERROR: command '/etc/init.d/postfix start' failed: exit code 255
because postfix not installed.
I think it is an good feature that Proxmox will install Postfix or Sendmail and configure it.
Code: 
Nov 19 18:56:01 proxmox /usr/sbin/cron[1894]: (*system*vzdump) RELOAD (/etc/cron.d/vzdump)
Nov  19 19:00:01 proxmox /USR/SBIN/CRON[4869]: (root) CMD (vzdump 100 102  104 105 107 --quiet 1 --mode snapshot --compress 1 --maxfiles 1  --storage backup)
Nov 19 19:00:01 proxmox /USR/SBIN/CRON[4867]: (CRON) error (grandchild #4869 failed with exit status 2)
Nov 19 19:00:01 proxmox /USR/SBIN/CRON[4867]: (CRON) info (No MTA installed, discarding output)
Nov 19 19:03:37 proxmox rrdcached[1723]: flushing old values
Nov 19 19:03:37 proxmox rrdcached[1723]: rotating journals
Nov 19 19:03:37 proxmox rrdcached[1723]: started new journal /var/lib/rrdcached/journal//rrd.journal.1321725817.754965
Nov 19 19:03:54 proxmox pvedaemon[1924]: <root@pam> successful auth for user 'root@pam'
Nov 19 19:17:01 proxmox /USR/SBIN/CRON[5807]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Nov 19 19:18:55 proxmox pvedaemon[1924]: <root@pam> successful auth for user 'root@pam'
Nov 19 19:23:07 proxmox sendmail[7226]: alias database /etc/mail/aliases rebuilt by root
Nov 19 19:23:07 proxmox sendmail[7226]: /etc/mail/aliases: 12 aliases, longest 10 bytes, 134 bytes total
Nov 19 19:23:07 proxmox sm-mta[7280]: starting daemon (8.14.3): SMTP+queueing@00:10:00
Nov  19 19:23:16 proxmox pvedaemon[1924]: <root@pam> starting task  UPID:proxmox:00001C95:0007517E:4EC7F414:vzdump::root@pam:
Nov 19  19:23:16 proxmox pvedaemon[7317]: INFO: starting new backup job: vzdump  107 --mode snapshot --compress 1 --storage backup --node proxmox
Nov 19 19:23:16 proxmox pvedaemon[7317]: INFO: Starting Backup of VM 107 (qemu)
Nov 19 19:23:17 proxmox qm[7321]: <root@pam> update VM 107: -lock backup
Nov 19 19:23:20 proxmox kernel: EXT3-fs: barriers disabled
Nov 19 19:23:20 proxmox kernel: kjournald starting.  Commit interval 5 seconds
Nov 19 19:23:20 proxmox kernel: EXT3-fs (dm-3): using internal journal
Nov 19 19:23:20 proxmox kernel: ext3_orphan_cleanup: deleting unreferenced inode 14246292
Nov 19 19:23:20 proxmox kernel: EXT3-fs (dm-3): 1 orphan inode deleted
Nov 19 19:23:20 proxmox kernel: EXT3-fs (dm-3): recovery complete
Nov 19 19:23:20 proxmox kernel: EXT3-fs (dm-3): mounted filesystem with ordered data mode
Nov 19 19:23:51 proxmox pvedaemon[1915]: worker 1923 finished
Nov 19 19:23:51 proxmox pvedaemon[1915]: starting 1 worker(s)
Nov 19 19:23:51 proxmox pvedaemon[1915]: worker 7430 started
Nov 19 19:23:57 proxmox pvedaemon[7317]: INFO: Finished Backup of VM 107 (00:00:41)
Nov 19 19:23:57 proxmox pvedaemon[7317]: INFO: Backup job finished successfully
Nov 19 19:23:57 proxmox pvedaemon[1924]: <root@pam> end task UPID:proxmox:00001C95:0007517E:4EC7F414:vzdump::root@pam: OK
Nov 19 19:25:01 proxmox /usr/sbin/cron[1894]: (*system*vzdump) RELOAD (/etc/cron.d/vzdump)
Nov 19 19:26:01 proxmox /usr/sbin/cron[1894]: (*system*vzdump) RELOAD (/etc/cron.d/vzdump)
Nov  19 19:30:01 proxmox /USR/SBIN/CRON[7826]: (root) CMD (vzdump 100 102  104 105 107 --quiet 1 --mode snapshot --mailto xxx@example.com  --compress 1 --maxfiles 1 --storage backup)
Nov 19 19:30:01 proxmox vzdump[7827]: <root@pam> starting task UPID:proxmox:00001E94:0007EFAD:4EC7F5A9:vzdump::root@pam:
Nov  19 19:30:01 proxmox vzdump[7828]: INFO: starting new backup job: vzdump  100 102 104 105 107 --quiet 1 --mailto xxx@example.com --mode  snapshot --compress 1 --maxfiles 1 --storage backup
Nov 19 19:30:01 proxmox vzdump[7828]: INFO: Starting Backup of VM 100 (qemu)
Nov 19 19:30:02 proxmox qm[7832]: <root@pam> update VM 100: -lock backup
Nov 19 19:31:41 proxmox vzdump[7828]: INFO: Finished Backup of VM 100 (00:01:40)
Nov 19 19:31:41 proxmox vzdump[7828]: INFO: Starting Backup of VM 102 (qemu)
Nov 19 19:31:41 proxmox qm[7948]: <root@pam> update VM 102: -lock backup
Nov 19 19:31:43 proxmox kernel: EXT3-fs: barriers disabled
Nov 19 19:31:43 proxmox kernel: kjournald starting.  Commit interval 5 seconds
Nov 19 19:31:43 proxmox kernel: EXT3-fs (dm-3): using internal journal
Nov 19 19:31:43 proxmox kernel: ext3_orphan_cleanup: deleting unreferenced inode 1720325
Nov 19 19:31:43 proxmox kernel: ext3_orphan_cleanup: deleting unreferenced inode 14246292
Nov 19 19:31:43 proxmox kernel: EXT3-fs (dm-3): 2 orphan inodes deleted
Nov 19 19:31:43 proxmox kernel: EXT3-fs (dm-3): recovery complete
Nov 19 19:31:43 proxmox kernel: EXT3-fs (dm-3): mounted filesystem with ordered data mode
Nov 19 19:33:22 proxmox pvedaemon[1915]: worker 1924 finished
Nov 19 19:33:22 proxmox pvedaemon[1915]: starting 1 worker(s)
Nov 19 19:33:22 proxmox pvedaemon[1915]: worker 8088 started
Nov 19 19:33:41 proxmox vzdump[7828]: INFO: Finished Backup of VM 102 (00:02:00)
Nov 19 19:33:41 proxmox vzdump[7828]: INFO: Starting Backup of VM 104 (qemu)
Nov 19 19:33:41 proxmox pvedaemon[1915]: worker 1922 finished
Nov 19 19:33:41 proxmox pvedaemon[1915]: starting 1 worker(s)
Nov 19 19:33:41 proxmox pvedaemon[1915]: worker 8158 started
Nov 19 19:33:41 proxmox qm[8157]: <root@pam> update VM 104: -lock backup
 
Last edited:
postfix is installed and configured by default. how did you install your system?
 
It's not easy to read your pveverion -v, as each program is not displayed on its own line, as it appears in a console...

Nevertheless, I see this :
vzprocps: not correctly installed
ksm-control-daemon: not correctly installed

And, as tom said, postfix should be installed by default.

So, there is something wrong with your installation. Did you install your server with the proxmox 2.0 beta(x) CD ?

Alain
 
I use the Standard install from Hetzner.
Postfix is not installed.
So what can i do now?

The errors from are now gone i has install they new. Only Postfix not working. Has someone an smaple for an Proxmox installation and configuration from Postfix?

vzprocps: not correctly installed FIXED
ksm-control-daemon: not correctly installed FIXED
 
Last edited:
You should report to Hetzner the errors you see, and ask them how to fix it.

They did an incorrect installation, regarding the standard of Proxmox-ve. They certainly did a custom install, perhaps trying to improve some aspects (?). But we don't know what they did exactly, so it will be hard to help you on this aspect. I often see hosting companies (OVH...) doing an incorrect (or at least non standard) installation.

Sorry if I can't help more...
 
Thank you , i has looked and OVH looks not bad :D
Know anybody how the Bandwidth from OVH Servers with the 1GBit Port is?
Because i has read its not realy good , and the Routing to germany not the best :-(
 
just ask OVH, but they also got testing tools, e.g. http://proof.ovh.net/

btw, this forum is running on OVH.
 
You must log in or register to reply here.
Top Bottom