Timeout on backup plugin
Currently running
[LIST]
CENTOS 6.9 x86_64 xenpv " webhost
WHM 62.0 (build 20)
No longer able to backup WHM server using BackupPC, get a timeout issue.
Wordpress admin login page just spins in the browser
-
Hello, Are you using any third-party firewall applications such as CSF, or custom iptables rules? If so, have you ruled those firewall rules out as the cause of the issue? No longer able to backup WHM server using BackupPC, get a timeout issue.
Do you notice any output to /usr/local/cpanel/logs/error_log when this happens?Wordpress admin login page just spins in the browser
Do you notice any output to /usr/local/apache/logs/error_log when this happens? Thank you.0 -
Oddly, NSFD was not running, so I started the nfsd daemon and I still can not backup from BackupPC. Times out. Yes I am using CSF, I completely disabled CSF, same issues. Accessing the WordPress Admin page, Apache log shows this: Script timed out before returning headers: admin-ajax.php 0 -
Hello, Could you open a support ticket using the link in my signature so we can take a closer look? You can post the ticket number here so we can update this thread with the outcome. Thank you. 0 -
Hello, Could you open a support ticket using the link in my signature so we can take a closer look? You can post the ticket number here so we can update this thread with the outcome. Thank you.
Ticket ID: ULL-535-576230 -
Ticket ID: ULL-535-57623
Hello, This looks like a ticket number from your provider, as opposed to cPanel. Feel free to update this thread with the outcome once they have replied to your support request. Thank you.0 -
Ticket ID: ULL-535-57623
Not sure what you are referring to, the submit support ticket in WHM gui sent me to either support at BuyCpanel or Cpanel, I chose BuyCpanel support. The only support in the corresponding email is the number I gave you already. There is no other support ticket number from support. I have corresponding back and forth via email with BuyCpanel support.0 -
Not sure what you are referring to, the submit support ticket in WHM gui sent me to either support at BuyCpanel or Cpanel, I chose BuyCpanel support. The only support in the corresponding email is the number I gave you already. There is no other support ticket number from support. I have corresponding back and forth via email with BuyCpanel support.
UPDATE: After going directly to their website and logging in... I found this number next to the support ticket: #1867630 -
Not sure what you are referring to, the submit support ticket in WHM gui sent me to either support at BuyCpanel or Cpanel, I chose BuyCpanel support. The only support in the corresponding email is the number I gave you already. There is no other support ticket number from support. I have corresponding back and forth via email with BuyCpanel support.
Hello, Yes, we recommend seeking out support from your provider first, so you would have been directed to them first when initiating the support request. We won't have access to see the support ticket from your provider, but feel free to let us know the outcome once they respond, or let us know if you have any additional questions. Thank you.0 -
Hello, Yes, we recommend seeking out support from your provider first, so you would have been directed to them first when initiating the support request. We won't have access to see the support ticket from your provider, but feel free to let us know the outcome once they respond, or let us know if you have any additional questions. Thank you.
My "provider", was asking for WHM admin password, SSH access to our server, and WordPress admin password. That is not going to happen, so instead after some research into the situation, I was able to fix the issue by removing an old NFS3 mount command. Apparently after the latest WHM Centos kernel update, NFS4 is strictly being used now and an old NFS3 mount command (resvport) is no longer supported in NFS4. Once I removed that attribute in our mount NFS mount script, viola, everything worked. Case closed.0 -
Hello, I'm happy to see you were able to address the issue. Thank you for updating us with the outcome. 0
Please sign in to leave a comment.
Comments
10 comments