Facebook
Twitter
H
-
If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
CentOS2Alma discussion
P
PSCGi
Guest
Ya know I thought I was smokin something reading this until I hit
the same wall without any explanation. I did the upgrades earlier
today for SA, etc. and all was well on my 9.0.X (since I think its
9.0.1 actually), then mysteriously I get this same error on the
Updater page and then Preferences - no way to do anything else!
Doesn't explain to us that the destination's hosed like you mention,
nor a way to really fix it and I bet money Plesk wants money if you
tried to call in now to get a resolution! This nickel and diming stuff
on 9.X is getting nauseating.
So that's what this is, the error in Plesk CP means it can't resolve
or contact Plesk to **** down the latest update information, thus
instead of a nice error page with 'come back later', it's a panic
stricken set of errors none of us can understand?
Anyone finds a fix or workaround for this to a working Plesk server
please add it here?
And Host, don't I recognize you from Miva awhile back?
the same wall without any explanation. I did the upgrades earlier
today for SA, etc. and all was well on my 9.0.X (since I think its
9.0.1 actually), then mysteriously I get this same error on the
Updater page and then Preferences - no way to do anything else!
Doesn't explain to us that the destination's hosed like you mention,
nor a way to really fix it and I bet money Plesk wants money if you
tried to call in now to get a resolution! This nickel and diming stuff
on 9.X is getting nauseating.
So that's what this is, the error in Plesk CP means it can't resolve
or contact Plesk to **** down the latest update information, thus
instead of a nice error page with 'come back later', it's a panic
stricken set of errors none of us can understand?
Anyone finds a fix or workaround for this to a working Plesk server
please add it here?
And Host, don't I recognize you from Miva awhile back?
P
PSCGi
Guest
Oh how nice! Is it me or is it a Freudian slip that Plesk manages
to filter out the word S U C K or what? Methinks someone knew
what words were coming at them when they worked on the
software, don't you think? Even funnier when it's really just a
variation of saying 'download'. Since it doesn't work, I guess that
means they expect us to say Plesk sucks? ROFL
H
Hostasaurus@
Guest
P
PSCGi
Guest
Ya, that's what I thought! Now I remember the logo, etc. Lost everyone once that mailing list busted up and went forums and such, just lost the whole flavor of what was there. Even that magazine one of'em started still shows up every month, but it's a bit different and I'm not sure if any of the gang's even there! Oh the days of a RaQ you could smack and get past things like this and Ensim boxes that didn't give you nightmares... good times, good times <Grin>
Good to see someone familiar here though, so far this rendition of Plesk is very messy. Runs a bit smoother but only if everything you have migrated up from 8.6 right or you started stone cold. Then there's a couple minor issues like this one, still a giant pain though! I mean just tell me - 'dude, it's busted come back later'. Not the error-ridden cryptic message from hell. Sheesh!
Problem here is that since I didn't run right in there and scope out Updater after it was finished and just took the e-mail notification as gospel, I have no idea when this busted. If it was right after the upgrade tried to complete or something, then I'd say whatever they sent us in the update has one character of bad code we can possibly edit, but there's no clues here! And they're round-robining the updates for load balancing, so you really can't tell where you normally point at to be able to even ping the stupid thing.
Just seems strange it showed up after today's latest round of 9.0 patches, then can't find Mommy to check and see what else needs to be fixed waiting to download! LOL
Good to see someone familiar here though, so far this rendition of Plesk is very messy. Runs a bit smoother but only if everything you have migrated up from 8.6 right or you started stone cold. Then there's a couple minor issues like this one, still a giant pain though! I mean just tell me - 'dude, it's busted come back later'. Not the error-ridden cryptic message from hell. Sheesh!
Problem here is that since I didn't run right in there and scope out Updater after it was finished and just took the e-mail notification as gospel, I have no idea when this busted. If it was right after the upgrade tried to complete or something, then I'd say whatever they sent us in the update has one character of bad code we can possibly edit, but there's no clues here! And they're round-robining the updates for load balancing, so you really can't tell where you normally point at to be able to even ping the stupid thing.
Just seems strange it showed up after today's latest round of 9.0 patches, then can't find Mommy to check and see what else needs to be fixed waiting to download! LOL
Looks like the problem is fixed now by the Plesk people. I had the same issues yesterday with the updater running into the "500 Internal Server Error..." but now it works again. My base packages are now dated to Dec 22nd. Strangely enough, I get a little yellow exclamation mark when I go to the updater despite having all packages up to date. Oh well 
H
Hostasaurus@
Guest
I think I saw in the bug thread that the updates available always showing is a bug.
dont forget the important part with this upgrade After upgrade from Parallels Plesk Panel 9.0.0 update1 to 9.0.0 update2 mail message headers have incorrect structure
Brujo
Brujo
H
Hostasaurus@
Guest
I just ran an update from 8.3 to 9.0, on a new box that had not even been licensed yet, and it did the upgrade and then deleted the httpsd.conf, so all the packages are updated but it's inaccessible. The mail package was upgraded to the one in that article though so at least they fixed that.
rpm -Uvh psa-mail-driver-common-9.0.0-cos5.build9 0081222.11.i586.rpm
error: Failed dependencies:
courier-imap >= 3.0.8-cos5.build90081222.11 is needed by psa-mail-driver -common-9.0.0-cos5.build90081222.11.i586
0081222.11.i586.rpm courier-imap-3.0.8-cos5.build90081222.11.i586.rpm90
Preparing... ########################################### [100%]
Stopping Courier-IMAP server:
Stopping imap [ OK ]
Stopping imap-ssl [ OK ]
Stopping pop3 [ OK ]
Stopping pop3-ssl [ OK ]
1:courier-imap ########################################### [ 50%]
Trying to register service xinetd... using /sbin/chkconfig
done
Trying to executing mail_restore to synchronize mail server settings and Plesk Database... done
2
sa-mail-driver-common ########################################### [100%]mv: cannot stat `/var/qmail/control/spf*': No such file or directory
Trying to executing mail_restore to synchronize mail server settings and Plesk Database... done
Is it normal?
Two things: The yellow exclamation mark pops up because there's still a few packages to be upgraded. They just don't show in the update page. The packages are all related to the mail system and they're from December 22nd. You can update them using the plesk installer on the command line. Once that ran through, the yellow exclamation mark changes to a green check. Also, the SPF problems as well as the tcp-env problem with accepting SMTP from localhost will have been fixed. yay.
H
Hostasaurus@
Guest
Ah, I see, psa9 has done away with the old bundled apache running out of /usr/local/psa/admin/ and now there's something new sw-cp-serverd running out of /etc/sw-cp-server/
Should be interesting seeing how to lock that down for pci compliance, looks like it's lighttpd that they've butched into this new role so I'll just have to figure out how to work with its config files.
Should be interesting seeing how to lock that down for pci compliance, looks like it's lighttpd that they've butched into this new role so I'll just have to figure out how to work with its config files.
I had the last update, but I see Yellow exclamation!....
P
PSCGi
Guest
Are you running Postfix instead of Qmail? We've stayed on Qmail due to
all the problems with these upgrades, this update seemingly hasn't done
a thing though I have to review the upgrade e-mails and see if there was
some sort of error. But it came back 'successful', even though I wouldn't
say that was the case...
all the problems with these upgrades, this update seemingly hasn't done
a thing though I have to review the upgrade e-mails and see if there was
some sort of error. But it came back 'successful', even though I wouldn't
say that was the case...
Can someone please explain how to do this for people who are not familiar with UNIX?
Thanks,
Peter O
P
PSCGi
Guest
Huh?
OK, run the autoinstaller for WHAT? You keep skipping all over the place and
none of us have a clue what you mean... He asked about the malformed mail
header bit you mentioned out of the blue that doesn't have anything to do with
this thread, or at least if it does you never told us WHY and now you're saying
we have to screw with headers but there's no explanation as to why or what
exactly you want to have someone do with the Autoinstaller.
And Plesk fixed the 'broken' part this thread started with within about 24-36
hours of when it happened. The AI wouldn't make a bit of difference because
the CP and AI both go to the same place to get the files they need to even
start installing or modifying anything. If you had it on your HDD already, that
would be why it was working. The rest of us where the AI wanted to touch
the Plesk downloading site/mirror before doing anything more - we were 'broken'.
The AI simply installs, upgrades or removes the WHOLE Plesk package and
it's elements, nothing specifically for malformed mail headers like you seem
to be saying. Running that is more wasting time than being productive unless
you can specifically tell us what it is we're going to be changing in settings
in the AI and what's supposed to happen afterwards?
We've got enough problems, confusing the hell outta people isn't going to
help anyone at all.
OK, run the autoinstaller for WHAT? You keep skipping all over the place and
none of us have a clue what you mean... He asked about the malformed mail
header bit you mentioned out of the blue that doesn't have anything to do with
this thread, or at least if it does you never told us WHY and now you're saying
we have to screw with headers but there's no explanation as to why or what
exactly you want to have someone do with the Autoinstaller.
And Plesk fixed the 'broken' part this thread started with within about 24-36
hours of when it happened. The AI wouldn't make a bit of difference because
the CP and AI both go to the same place to get the files they need to even
start installing or modifying anything. If you had it on your HDD already, that
would be why it was working. The rest of us where the AI wanted to touch
the Plesk downloading site/mirror before doing anything more - we were 'broken'.
The AI simply installs, upgrades or removes the WHOLE Plesk package and
it's elements, nothing specifically for malformed mail headers like you seem
to be saying. Running that is more wasting time than being productive unless
you can specifically tell us what it is we're going to be changing in settings
in the AI and what's supposed to happen afterwards?
We've got enough problems, confusing the hell outta people isn't going to
help anyone at all.
