I am receiving the following error (that I realize has been discussed in about 15 different threads, but none of the solutions seem to apply to my situation):

Unable to resolve hostname or establish network access to
local host: myactualhost.myactualdomain.com. You should fix this problem prior to installing Plesk. After you are done, run the installation again.

1: when logged in to SSH, hostname gives myactualhost.myactualdomain.com.

2: /etc/hosts has the following two lines:
127.0.0.1 localhost.domain localhost
my.ip.ad.dr myactualhost.myactualdomain.com myactualhost

3: The val in DB: psa, TABLE: misc, PARAM: FullHostName is myactualhost.myactualdomain.com

4: The val in DB: psa, TABLE: dns_recs, type: PTR, host: my.ip.ad.dr is myactualhost.myactualdomain.com

I have the RPM install of Plesk 5.0.5 currently (file location is /home/httpd/...) on a RH7.3 box, and am attempting to upgrade to Plesk 6.0.1 build 030723.13 with the file:
psa-6.01-rh7.3.build030723.13.i586.rpm.

When I attempt to install this RPM (rpm -Uvh), I get:
Preparing... #### [100%]
Trying to define super-server internet daemon type... xinetd
Trying to check if xinetd daemon is running... done
===> Reading /etc/psa/psa.conf ...
and then it hangs indefinitely.

Once I give up and hit Ctrl+C, I get the above error (about hostname identification).

Any ideas?

Thanks,
Edward

does your domain resolve to the server?

IE: do you have an A record in the dns for
myactualhost.myactualdomain.com to my.ip.ad.dr

if not, try that...

The DNS is off-server, but myactualhost.myactualdomain.com resolves to my.ip.ad.dr from my local machine and from the server (whether it is in the hosts file or not).

Edward

ok, just to clarify....your hostname is the one in the error message?
myactualhost.myactualdomain.com ??

And if so...do you have pings disabled?

Well, all that trouble to "generalize" things and I forget to change the one in the error message.

Yes, myactualhost.myactualdomain.com is the hostname that appears "everywhere", including in the error message.

And yes, ping is disabled.

Edward

ok, enable pings during the upgrade....that should sort it...I am going to "generalize" your domain out of my post....feel free to do the same to yours...

Two things:
First, the ungeneralized domain still appears in your quote of my original message.

Second, I have another problem that has popped up during my attempted upgrade that is keeping me from logging in to Plesk, but I'll go ahead and start another thread for that and once I solve that problem, I assume the upgrade will go through.

Edward

ok..fixed that generalization issue...seems I missed the same one you missed orginially..hehe

ok...sounds like a plan.