No, not a typo. The local port forward is being made on the machine you connected to. By my example you would connect to your proxmox server and the webserver for the UI is also listening on localhost port 8006, so in that case it works.
If you are making a ssh connection to something else then...
The easiest way in your current situation would be to forward port 8006 on pfSense to port 22 with destination you proxmox IP. Then with a SSH client like PuTTY you set up a connection to your proxmox server like:
Hostname: 1.1.1.1
Port: 8006
Under category: Connection > SSH > Tunnels:
Source...
Hi Wolfgang,
Nope, it's a standard kernel. The requested output:
root@pmx01:~# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever...
I've got something weird again :(
Noticed yesterday that my servers's network settings are not showing (see attached screenshot). And in the pending changes section there is a: 'Error: failed to open socket (500)'. Rebooted the server, still the same. All vm's are working fine though.
Been...
Just for anyone encountering something similar: During testing i noticed that when i manually mounted the usb drive the backup speed was normal again (actually even faster than before)
...so i'm presuming the usbmount-package i was using was the culprit!
Removed usbmount and i'm now using some...
The speed of the USB3 disk does not seem to be the problem:
root@pmx01:/media/usb0# dd if=/dev/zero of=tmp_file bs=1M count=1024 conv=fdatasync ; rm -f tmp_file
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB) copied, 93.5955 s, 11.5 MB/s
Problem is the same for KVM vm's being backed-up (and not showing the 'mode failure' error), so that does not seem to be related:
Before:
103: Nov 15 01:01:16 INFO: Starting Backup of VM 103 (qemu)
103: Nov 15 01:01:16 INFO: status = running
103: Nov 15 01:01:16 INFO: update VM 103: -lock...
Hi Erk,
Don't know where to find the backup log, this is from the mails before and after the upgrade. Speed dropped from 20MiB/s to 823KiB/s.
Before:
101: Nov 15 01:00:01 INFO: Starting Backup of VM 101 (openvz)
101: Nov 15 01:00:01 INFO: CTID 101 exist mounted running
101: Nov 15 01:00:01...
Hi Erk,
Thanx for your reply.
Server was upgraded to PVE4, no other changes were made. Next backup after upgrade had these problems, same usb3 backup disk.
Just to be sure i checked /etc/vzdump.conf and the bwlimit parameter is commented out.
After upgrading my server to Proxmox VE 4 my backup to USB-disk has become REALLY slow. Excerpts from the backup report mails:
Before upgrade (PVE 3.4-6):
103
webmail
OK
00:13:07
5.04GB
/media/usb0//dump/vzdump-qemu-103-2015_11_15-01_01_16.vma.lzo
After upgrade (PVE 4.0-57)...
Hi Wolfgang,
Saw in that config file that the 'vm-100-state-sme_upds_20150205.raw'-file was from another snapshot, so whent ahead and removed the problematic snapshot-block from the config file. As far as i can tell it looks like it worked, thanks!
Kind regards.
Hi Wolfgang,
Not sure, it's still showing in the webgui. I'm not to familiar on the commandline and with the proxmox related files, so don't shoot me when i got this wrong:
# pwd
/var/lib/vz/images/100
# ll * | grep state
-rw-r--r-- 1 root root 1.2G Feb 5 09:15 vm-100-state-sme_upds_20150205.raw
Hi,
I'm trying to delete an old snapshot, but am getting this error:TASK ERROR: VM 100 qmp command 'delete-drive-snapshot' failed - Device 'drive-ide0' not found
The status of the snapshot says 'delete', but it's still there. The drive on this machine had been 'moved' from RAW to QCOW2 while...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.