-
-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proxmox 7 Status? #109
Comments
I have been using the plugin for 6.x to 7.0 update and all 7.0 update. I have had no issue with Proxmox to TrueNAS versions 12.0-U3 - 12.0-U6. |
I am running 3-Node PVE 7.1-1 Cluster with installed FreeNAS ZFS over iSCSI interface on each of them. One of new features of 7.1-1 realese is new scheduler for backups planning - "pvescheduler". This is new daemon pvescheduler.service, it parses jobs from /etc/pve/jobs.cfg. If I run vzdump manualy from CLI or from Web-UI, it works fine. But if it is runned by new service, i get following messages in it's log:
|
Not sure about this. It seems the package or commands to apply the patches to ZFSPlugin.pm did not take. Is the patch/package applied to ALL nodes in the cluster? Not seeing the FreeNAS in the iscsi provider tells me it is not installed. |
Yes, patch/package applied to all nodes via your repo:
Workaround to make backups execute by schedule is to manually add strings to file /etc/pve/vzdump.cron as it was in proxmox before 7.1. P.S. I applied your package BEFORE adding nodes to HA Cluster. Do not know, if it matters. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I don't think it's resolved. Stale maybe, but it takes time... Go away stalebot. |
I have been running a three node Proxmox 7.1-10 and 7.1-11with TrueNAS-Core and TrueNAS-Scale as the NAS and backing up to a TrueNAS-Core using NFS with the new mechanisms you have described and I have not had any issues. Backup jobs finish a I get a report of successful every time. |
Closing due to no activity from original requester. If you are still having issues, please reopen or open a new issue. |
Hello, I've got one more problem after adding VM to HA. When I try to start it, I get such error:
It seems to me that tis problem is the same as I reported pefore. Please, do not close it due to no activity. Or, maybe mention it as a problem to fix in upcoming builds. |
Sorry for bothering you all this time. Restarting pve-ha-lrm solved all the problems. |
So if in an HA cluster, does the pve-ha-lrm need to be restarted for it to work? I have not had to do that but if I need to add to the documentation then please let me know. |
Sorry to add to an old thread. I encountered the same problem as the OP. I am running PVE 7.3-4, TrueNAS 13.0-U3.1. I applied the patches to each of the 5 nodes in the cluster and restarted the pve-ha-lrm, pve-ha-crm. I found that in order for pvescheduler.service to complete the task automatically, without error. pvescheduler.service needs to be restarted on all nodes Hope this helps someone. |
@TruckeeAviator - Thank you for the additional information. I will update the README.md to reflect your recent find and fix. |
I saw a single commit for proxmox 7, and found no issues filed, except one.
Thought I'd start a thread for proxmox 7 status.
How is it?
The text was updated successfully, but these errors were encountered: