Fixing cPanel bind problem

[Ulysses]

G'day,

An automated upgrade to our cPanel (to "release" 10.6.0-R16) on Saturday night caused various problems, some of which continue to persist.

After PowerVPS kindly fixed the critical problem manually, we sought wisdom and assistance from the cPanel forum to fix the remaining problems on the following thread:

http://forums.cpanel.net/showthread.php?p=204125

Problems 2. 3, 4 on the original post and our inability to "Rebuild Quota Files" are current outstanding problems, which we assume only cPanel can solve. This being the case we followed up on the advice to submit a "support ticket" to cPanel - who responded with:

In order to diagnose the problem with the server, we will need the main ip address and root password. (a user with root permissions or sudo is not sufficient, as true root access is required since sudo can have limits set and even though a user may be 0 its name may limit certain functions that expect 'root')

Ip Address:
Root Password:

If your system requires login as an unprivileged user before root login please provide an account to login to as well.

Account:
Account Password:

**** If you are having a problem that affects a specific account, please provide the username and password to that account. If this problem affects ALL accounts, please provide ONE or TWO logins and password for the affected accounts. ****

Account:
Account Password: Naturally we don't have access to everything, but even if we did, I'm not entirely sure that it is appropriate for us to permit cPanel to have access to even our area of the server without PowerVPS as a chaparone or guide.

Is everyone having this problem, and if so would PowerVPS like to follow this though, or are we the only ones, in which case what should we do?

Thanks

Ulysses

[Zaf]

I upgraded cPanel a second time and now I have 10.6.0-R26 just a few hours later. I'm not facing any issues so far, but am still to read the details on that thread you mentioned. Will read there first before commenting further.

[ozgreg]

I am also not seeing any of these issues, but I also re-ran the script update, and re-ran the main update again to ensure everything was correctly updated..

[KARanden]

Did a new update on cPanel this morning ( Norwegian time), and it now shows this version: WHM 10.6.0 cPanel 10.6.0-R55.

I also did a update the 18th, and it was updated to 10.6.0 but I'm not sure the release version.

But I have not had any problems whit my VPS, as I know of since 10.6.0 :rolleyes:

I'm using stable realeses, and I forgot that Fantastico was missin in action, but followed some sugestion on the cPanel forum, and got it back.

[Tony]

Problems 2. 3, 4 on the original post and our inability to "Rebuild Quota Files" are current outstanding problems, which we assume only cPanel can solve. This being the case we followed up on the advice to submit a "support ticket" to cPanel - who responded with:

Naturally we don't have access to everything, but even if we did, I'm not entirely sure that it is appropriate for us to permit cPanel to have access to even our area of the server without PowerVPS as a chaparone or guide.

Is everyone having this problem, and if so would PowerVPS like to follow this though, or are we the only ones, in which case what should we do?


No, you're NOT the only ones!

Regarding the quota issue, this is a SWsoft issue, that we have a fix for; drop us a ticket in and we'll get that done for you.

We're working in conjunction with cPanel and SWsoft to get this resolved - I read your post earlier today, and took your server to be a dedi as opposed to a VPS. We're pretty sure at the moment that this is a SWsoft/Redhat 9 issue.

Aside from that, at the moment, we only have a fix to get named up and running and get your sites working - and also to fix the quotas. Please do submit a ticket to us so we can escalate the bind chkservd issue in cPanel's direction.

[Ulysses]

No, you're NOT the only ones!

Regarding the quota issue, this is a SWsoft issue, that we have a fix for; drop us a ticket in and we'll get that done for you.

We're working in conjunction with cPanel and SWsoft to get this resolved - I read your post earlier today, and took your server to be a dedi as opposed to a VPS. We're pretty sure at the moment that this is a SWsoft/Redhat 9 issue.

Aside from that, at the moment, we only have a fix to get named up and running and get your sites working - and also to fix the quotas. Please do submit a ticket to us so we can escalate the bind chkservd issue in cPanel's direction.Thank you Tony.

We have submitted a second ticket to you today, covering all the outstanding problems, so you can fix them or escalate them as you feel appropriate.

Ulysses

[Jad]

I live in history, still running WHM 10.1.0 cPanel 10.2.0-S83 which is stable
still not sure why you guys use release tree even if it's not stable

[ozgreg]

Why? because cpanel is running several versions behind in a more than a few applications and release tree is a tradeoff between the chance of some issues and ensuring the core applications are kept current.

I take a few issues over running a core application that is a few releases behind current..