Search results

I might have a similar problem, so I describe it below: 2 sites with Proxmox VE. Site A runs a VM as Wireguard server, Site B works as the Wireguard client. It is intented that all machines from any site can be accessed from all machines of the other site. This seems to work so far. From site...

Thank you. Never thought of that, as its new to me. Will have a look into it.

Following your advice was not successful: root@warnow:/# lvchange -ay /dev/pve/root && fsck /dev/pve/root fsck from util-linux 2.38.1 e2fsck 1.47.0 (5-Feb-2023) /dev/mapper/pve-root is mounted. e2fsck: Cannot continue, aborting. Any hint?

Yes, I did read the posts regarding Wireguard over here, but nothing seems to fit. I connected two site with site-to-site wireguard, site A ist server, side B "client". Everything seems fine both directions. ping and ssh work. Even curl to the remote Proxmox GUI works: curl -v...

I did name that storage after its device name. So that definition just got lost in some configuration file for some unknown reason.

Hi, I did solve the problem in the meantime. But regarding your hints: This is a mount point with existing data, so I had to tell that LXC to accept it again. >> Try naming the volume name as defined by PVE instead of the device name ... How do I find out what the names are that are defined...

Hi Fiona, that did the trick, everything fix. I owe you a drink - or two. Kind regards Wolfgang

root@ems:~# pveversion -v proxmox-ve: 8.0.1 (running kernel: 6.2.16-3-pve) pve-manager: 8.0.3 (running version: 8.0.3/bbf3993334bfa916) pve-kernel-6.2: 8.0.2 pve-kernel-6.2.16-3-pve: 6.2.16-3 ceph-fuse: 17.2.6-pve1+3 corosync: 3.1.7-pve3 criu: 3.17.1-2 glusterfs-client: 10.3-5 ifupdown2...

Nach Stromausfall Neustart Proxmox Server ist OK, aber eine einzelner LXC startet nicht. Startversuch von Shell des Servers root@ems:~# pct start 106 storage 'sdb' does not exist root@ems:~# fdisk -l Disk /dev/sdb: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: WDC...

After power failure restarting the Proxmox server is fine, but a single LXC doesn't start. Trying to start LXC from the servers command line root@ems:~# pct start 106 storage 'sdb' does not exist root@ems:~# fdisk -l Disk /dev/sdb: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk...

This did the trick :)

Additional information as requested (iotop -oPak) see attached file. So "SSDs with QLC flash memory" is a problem. Not easy to fix, needs re-installation of Proxmox VE I presume. No problem. I could move the LXCs incorporated to some other server using M.2 storage. Same problem there?

Installed iotop. See attached file with screenshot. It dows show my database process and my script, but I consider overall load to be quite low.

I don't use ZFS, only LVM and EXT4. And I consider writes < 1 MB/sec not being heavy. :-(

I've got two LXC on the same PVE, one running a script accessing a database server running on the other LXC. Did that several times, but possibly using another VE-Server months ago. Now progress of the script is VERY slow. Looking into the LXCs everthing seems fine, CPU, RAM, network, disk io -...

GUI seams easy, but I've got a headless nginx LXC. Some having hints how to accomplish that if you've only got terminal access via ssh?

Could someone please give some more information on how to accomplish that? Could I just follow https://www.nginx.com/blog/websocket-nginx/ using the examples given there? Nothing to change at the backend (Proxmox)?

How did you enable websocket support noot having nginx manager?

I administer my nginx reverse proxy server by CLI only. How do I enable WebSocket this way?

Indeed, that did it. Silly me. :confused: TX!