Recent content by wimp9849

hi, my backup runs every 4 hours at minutes 00 and sync jobs every hour at minutes 00, probably i resolve this by setting sync jobx at minutes 30 for example. But if a backup takes more than 30 minutes there is always a chanhce that this could happen.

Hi, we see the same error, when a sync job start during a backup running on the pve, we receive the error " unable to acquire lock on snapshot directory", Maybe this could be managed better, for example let the pbs know that a backup is running and avoid that backup in the sync (as is not...

oh understood, we'll wait for a later version. Thanks

Hi @Chris , i've updated another PBS to 3.3.3-1 but the problem is still there. I have rebooted the server, to load new kernel just in case, i'll check tomorrow after the daily cron has run.

Thank you very much, so it seems something related to syslog as i suspected. We'll wait to be in the enterprise repo. Thanks

Hi, i'm monitoring my proxmox backup server with zabbix and this template: https://github.com/nikosch86/zabbix-proxmox-backup-server. I've an alert about tasks , the api return this...

Hi @Maximiliano, i'm adding it from GUI but running pvesm status solved the problem! I don't know how could it be related, but that's it. Next time i'll try a host reboot, before posting. Thanks

Hi, i think i've found a BUG, if the name of the storage is above 23 character it stays in unknown states, but no error on input. The storage works perfectly and i can read and write backup, but on the GUI it stay with question mark Example: as you can see there are 2 datastore, i've added...

Great, is running fine now. I think the post can be marked as solved. Thanks for the support.

So, i think we need to find if the problem is pmg or the new version of debian. i tried adding manually a line to syslog with command: #logger test message but it is still empty, so i think the problem is on Debian / Rsyslog side. I've reinstalled rsyslog with this command: #sudo apt-get...

Hi, i have the same problem after upgrade, i've tried rebooting yesterday and it solved the issue, but today i have the same error.

Thanks for the answer, already read that post, but there is no mention to unbound settings beside just install it. i've found some setting here: https://forum.proxmox.com/threads/how-to-local-dns-resolver-for-proxmox-mail-gateway.41189/post-201416 i'm trying this setting. My problem is that...

Hi, can you share a valid/optimal config for unbound? Thanks

Hi, regarding this: are you using the LAG used for ceph and vms traffic also for Cluster comunication (corosync) or is on 1 or 2 separate network?

Hi Alwin, i have reboot all the nodes one at a time waiting ceph to rebalance between reboots and now all nodes are on 12.2.12. Thanks for the support.