Recent content by ednt

  1. performance ceph vs linu vm

    One question for you: How many bytes per second you can send over a 1 gigabit/s network card?
  2. Proxmox update from 7.2-4 GRUB update failure

    Same problem with sda and sdb During the install loop I can see:
  3. After migration of Windows Servers 2019 a reboot is needed

    Yes, you were right. I needed to boot both nodes with 5.13.xx to be able to migrate from and to without problems. A very ugly problem.
  4. Some backups are not saved in the namespace

    Since I had no replication running, it was enough to killall pvescheduler until no pvescheduler was running anymore, Then service pvescheduler start. And at least migrate and remograte the VMs, that the new libpbs was used. A reboot was not needed in my case.
  5. After migration of Windows Servers 2019 a reboot is needed

    Ok .... I removed the openvswitch stuff from one node and tried it again. Unfortunately this doesn't solve the problem. To be more precise: If I move a windows server from an old node to an old node and back, it works. If I move a windows server from an old node to a new node it works. But if...
  6. After migration of Windows Servers 2019 a reboot is needed

    Some new tests: The migration to cpu11 was working. The problem starts when migrating back to cpu02. The difference: cpu02 uses openvswitch, while cpu11 didn't. It looks like that the migration from a node without openvswitch to a node with openvswitch results in this behaviour. The interfaces...
  7. After migration of Windows Servers 2019 a reboot is needed

    Always when we migrate Windows Servers they stuck with an error screen. After a reboot they work normal again. Today I migrated some VMs to an other node and back to update the pbs library which is used by the VMs. All 4 VMs needed a restart afterwards. It was a DomainController, 2...
  8. Sync from PBS to PBS failed: too many open files

    On friday I created a sync job to copy files from PBS-02 to PBS-01 PBS-02 has different datastores and PBS-01 uses the 'new' namespace feature. Both PBS are running the latest no-subscription version 2.2.5 Updated 29.07.2022 and both rebootet, On PBS-01 (target) I get...
  9. Some backups are not saved in the namespace

    You are lucky, I found a node where it still is the case: root@pm-cpu-173:~# ps ax|grep pvesche 390618 ? Ss 61:21 pvescheduler 1271153 ? Ss 29:05 pvescheduler 2016484 ? Ss 50:23 pvescheduler 2711818 ? Ss 6:58 pvescheduler 3602118 ? Ss 43:26...
  10. Some backups are not saved in the namespace

    It's working now as expected. kill -9 xxxx was not needed. killall pvescheduler terminates all processes. I found more pve nodes where multiple instances of pvescheduler was 'running'. How can this happen? And why does a start of pvescheduler does not simply terminate all old running...
  11. Some backups are not saved in the namespace

    stop does nearly nothing: root@pm-cpu-175:~# systemctl stop pvescheduler root@pm-cpu-175:~# ps ax|grep pvesched 126214 ? Ss 4:56 pvescheduler 1723109 ? Ss 32:41 pvescheduler 1875725 ? Ss 33:47 pvescheduler 2224202 ? S 0:00 pvescheduler 2224204 pts/0...
  12. Some backups are not saved in the namespace

    There is no tree, only single processes: F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND 1 0 2916892 1 20 0 333232 19788 hrtime Ss ? 39:05 pvescheduler 4 0 608389 1 20 0 15504 5396 do_epo Ss ? 0:02...
  13. Some backups are not saved in the namespace

    journalctl (from the day where I restarted the pvescheduler): Jul 21 18:04:31 pm-cpu-175 systemd[1]: Stopping Proxmox VE scheduler... Jul 21 18:04:32 pm-cpu-175 pvescheduler[3508258]: received signal TERM Jul 21 18:04:32 pm-cpu-175 pvescheduler[3508258]: got shutdown request, signal running jobs...
  14. Some backups are not saved in the namespace

    I did this systemctl restart pvescheduler on friday. Still the same message in the log of the backup job: file /etc/pve/storage.cfg line 158 (section 'pm-pbs01-ednt') - unable to parse value of 'namespace': unexpected property 'namespace'
  15. Some backups are not saved in the namespace

    As written in #18, I did a systemctl reload-or-restart pveproxy pvedaemon pvescheduler It's getting worse. Now a few VMs more (also from other nodes) are not respect the namespace (which were Ok last times): And I can still see: file /etc/pve/storage.cfg line 158 (section 'pm-pbs01-ednt') -...

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!

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 your own in 60 seconds.

Buy now!