1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

How to Update from 7.1.7 to 7.5.4+ [without updater]

Discussion in 'Plesk for Linux - 8.x and Older' started by jvanv8, Mar 26, 2006.

  1. jvanv8

    jvanv8 Guest

    0
     
    My updater on Plesk conveniently displays a blank screen so I am forced to upgrade from 7.1.7 to 7.5.4 (or whatever gets PHP5 enabled).

    How to I do updates manually via the command line?
    (I have never installed "packages" previously)
    or is there some fix to the blank updater screen?

    Thanks
    - Johnny Newbie
     
  2. eilko

    eilko Regular Pleskian

    28
    73%
    Joined:
    Aug 1, 2001
    Messages:
    468
    Likes Received:
    4
    Location:
    Enschede, Netherlands
    download the correct tar-file with the packages. Unpack the file and read the releasenotes. They decribe a manual installation/upgrade.
     
  3. jvanv8

    jvanv8 Guest

    0
     
    Ok, I figured that the solution to manually updating Plesk was to "download a file and install it" but I guess my question is a little more specific:

    Which file do I need and where do I get it?

    Do I download it to my local PC then FTP it or do I download everything using the command prompt with ssh?

    Which folder do I put the file on the server? Does it matter?

    Once I have the file, what is the command I need to execute to update Plesk? Do I have to untar it? Are there dependancies?

    How long will the site be down for if I sucessfully update Plesk?


    ahhh.. and once all that is done I can START the REAL upgrade that I want which is installing PHP5
    Thanks for helping a new guy out,
    John
     
  4. phoenixisp

    phoenixisp Silver Pleskian

    27
    57%
    Joined:
    Feb 2, 2002
    Messages:
    840
    Likes Received:
    0
    Another way is to use ART's yum project. Then it's as easy as:

    #yum update psa
     
  5. jvanv8

    jvanv8 Guest

    0
     
    I don't have yum installed on the server...
    but I found these directions to install yum:
    http://www.fedorafaq.org/#installsoftware

    But it doesn't work for me
    Code:
    [root@websrv /]# yum update psa
    -bash: yum: command not found
    [root@websrv /]# cd /etc
    [root@websrv etc]# mv -f yum.conf yum.conf.bak
    mv: cannot stat `yum.conf': No such file or directory
    [root@websrv etc]# wget [url]http://www.fedorafaq.orq/samples/yum.conf[/url]
    --15:48:27--  [url]http://www.fedorafaq.orq/samples/yum.conf[/url]
               => `yum.conf'
    Resolving [url]www.fedorafaq.orq...[/url] failed: Host not found.
    [root@websrv etc]# wget [url]http://www.fedorafaq.org/samples/yum.conf[/url]
    --15:48:41--  [url]http://www.fedorafaq.org/samples/yum.conf[/url]
               => `yum.conf'
    Resolving [url]www.fedorafaq.org...[/url] done.
    Connecting to [url]www.fedorafaq.org[/url][70.84.209.18]:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 595 [text/plain]
    
    100%[=================================================================================================================>] 595          581.05K/s    ETA 00:00
    
    15:48:42 (581.05 KB/s) - `yum.conf' saved [595/595]
    
    [root@websrv etc]# rpm -Uhv [url]http://www.fedorafaq.org/yum[/url]
    Retrieving [url]http://www.fedorafaq.org/yum[/url]
    error: Failed dependencies:
            fedora-release = 4 is needed by yum-fedorafaq-4-2006.02.03
            yum is needed by yum-fedorafaq-4-2006.02.03
    
    I guessing I don't have fedora installed (whatever that is)

    ... but that yum thing sure did look easy.
    What about up2date?
    How does that work?
    Could it be used in this situation?

    Thanks
    John
     
  6. phoenixisp

    phoenixisp Silver Pleskian

    27
    57%
    Joined:
    Feb 2, 2002
    Messages:
    840
    Likes Received:
    0
    Go to:

    http://www.atomicrocketturtle.com

    Click on Projects, then Yum. You can download what you need there and get great instructions. Scott (Turtle Man) also has a Forum you can check out.

    I believe he also has an up2date repo as well.
     
  7. jvanv8

    jvanv8 Guest

    0
     
    Thanks Phoenix,
    I ended up downloading the RPM from atomicrocketturtle and ran rpm command on it and I think Yum may work now -- is there a way to test it? I was a little hesitant at fïrst because they said if you are running RH Enterprise Level you have to do certain¨things... Im running RHEL3

    So before I run "yum update psa" what can I expect from this command? Will the server go down for a period of time? Is it likely that something might go wrong? Is there a way to undo or backup the current config -- in case the upgrade doesnt go so well? On a scale of 1 (no risk to 10 (bad stuff will probably happen if you are a newbie... where would this lie?

    or is this basically the same thing that the autoupdater does?
    Thanks
     
  8. phoenixisp

    phoenixisp Silver Pleskian

    27
    57%
    Joined:
    Feb 2, 2002
    Messages:
    840
    Likes Received:
    0
    Once you do 'yum update psa' you will be prompted before anything is downloaded and/or installed. It will tell you what will be installed and what packages will be installed to meet dependencies.

    ART (Scott) makes his rpms to be totally compatible with Plesk, so the danger would be, on your scale, a 1. However, it is always wise to do a backup before you make any configuration changes to your server. Learn about backing it up here:

    http://download1.sw-soft.com/Plesk/Plesk7.5/Doc/plesk-7.5r-backup-restore-html/index.html

    Also, there should be no downtime for your server during the upgrade.
     
  9. jvanv8

    jvanv8 Guest

    0
     
    Damn.

    Did the backup of the config... ran the yum update psa and you guessed it... website is down and won't display pages.... (we may need to ammend the "Risk Level 1" rating).

    So how do I get this back up...
    Here is the current situation:
    - I get a blank screen when you type in the domain name
    - Plesk works (seems to be the new version)
    - any direct url request for a specific page results in a 404
    - pinging the domain name works
    - Historically I always have to do an "service iptables stop" whenever we reboot because otherwise it gives us "Connection Refused" errors... something to do with the firewall settings (?). I'm not getting that error and the iptables is stopped but this maybe helpful for some gurus
    - I restarted the server but get the same problems
    - DNS Site Preview in Plesk yeilds the same blank page that I see on the website
    - DNS settings list the correct ip though

    Here is what is installed... interesting that the PSA versions don't look like they match up (?)
    Code:
    apache	1.3.31
    php		4.3.2-23.ent
    mod_python	3.0.3-3.ent
    bind		9.2.2-21
    courier-imap	3.0.3-rhel3.build71050228.12
    frontpage	5.0.2.2634
    jdk		1.4.2
    tomcat		4.1.24-full.2jpp
    logrotate	3.7
    mysql		3.23.58-16.RHEL3.1
    mailman		2.1.5-25.rhel3
    postgresql	7.3.4-8
    phpmyadmin	2.5.3
    phppgadmin	2.4.2
    proftpd		1.2.9
    qmail		1.03
    webalizer	2.01_10-15.ent
    rblsmtpd	0.70
    mod_perl	1.99_09-10.ent
    perl-Apache-ASP	2.57-rhel3.build71050228.12
    spamassassin	2.63-0.2
    psa-migration-manager	7.1.7-rhel3.build71050228.12
    postgresql-server	7.3.9-2
    SSHTerm		0.2.2-rhel3.build71050228.12
    drweb-qmail	4.31-rhel3.build71040817.01
    drweb		4.31.7-rh1
    httpd		2.0.46-46.ent
    coldfusion	Component was not installed
    psa-qmail	1.03-rhel3.build75050824.12
    psa-proftpd	1.2.9-rhel3.build71050228.12
    psa-logrotate	3.7-rhel3.build71050228.12
    psa-spamassassin	7.1.7-rhel3.build71050228.12
    tomcat4		4.1.24-full.2jpp
    stunnel		4.04-4
    psa-qmail-rblsmtpd	0.70-rhel3.build71040817.01
    psa-tomcat-configurator	7.1.7-rhel3.build71050228.12
    psa-bu		7.5.4-rhel3.build75050926.17
    psa		7.1.7-rhel3.build71050228.12
    psa-agent	1.3.2-2.5
    coldfusion-support	7.3-2.96.128
    psa-api-rpc	7.5.4-rhel3.build75050930.11
    psa-horde	Component was not installed
    psa-imp		Component was not installed
    psa-manual-custom-skin-guide 	Component was not installed
    psa-turba	Component was not installed
    samba		3.0.4-6.3E 
    Please, this is pretty urgent.
    Thanks
    J
     
  10. jvanv8

    jvanv8 Guest

    0
     
    Since Plesk was working, I ran the Auto Updater to update the Base Plesk package and it magically "fixed" the problem so I don't have 404s on the domains now...

    The funny thing is... the Autoupdater actually FAILED!
    Some sort of dependancy problem I guess...
    Code:
    Preparing for packages installation...
    ----- begin of output -----
    Installing 
    /PSA_7.5.4/rpm_RedHat_el3/base/osCommerce-2.2ms2-7513.noarch.rpm
    Installing 
    /PSA_7.5.4/rpm_RedHat_el3/base/psa-hotfix5-7.5.4-rhel3.build75060118.18.i586.rpm
     Trying to stop Admin server... done
     Trying to replace files and set up right permissions...  Trying to 
    start Admin server... done
    done
    Installing 
    /PSA_7.5.4/rpm_RedHat_el3/base/psa-hotfix6-7.5.4-rhel3.build75060321.20.i586.rpm
     Trying to replace files and set up right permissions...  Trying to fix 
    mailman path in psa.conf... done
    done
    Installing /PSA_7.5.4/rpm_RedHat_el3/base/Mambo-4.5.2.3-7504.noarch.rpm
    Installing 
    /PSA_7.5.4/rpm_RedHat_el3/base/psa-horde-3.0.5-rhel3.build75050824.12.noarch.rpm
    Installing 
    /PSA_7.5.4/rpm_RedHat_el3/base/psa-imp-4.0.3-rhel3.build75050824.12.noarch.rpm
     Trying to stop Apache server... done
     Trying to start Apache server... done
    Installing 
    /PSA_7.5.4/rpm_RedHat_el3/base/psa-qmail-1.03-rhel3.build75060321.20.i586.rpm
     Checking for the system groups and users necessary for Qmail...
     Checking for the group 'nofiles'...
     Group 'nofiles' already exists
    
     Checking for the user 'alias'...
     User 'alias' already exists
    
     Checking for the user 'qmaild'...
     User 'qmaild' already exists
    
     Checking for the user 'qmaill'...
     User 'qmaill' already exists
    
     Checking for the user 'qmailp'...
     User 'qmailp' already exists
    
     Checking for the group 'qmail'...
     Group 'qmail' already exists
    
     Checking for the user 'qmailq'...
     User 'qmailq' already exists
    
     Checking for the user 'qmailr'...
     User 'qmailr' already exists
    
     Checking for the user 'qmails'...
     User 'qmails' already exists
    
     Checking for the group 'popuser'...
     Group 'popuser' already exists
    
     Checking for the user 'popuser'...
     User 'popuser' already exists
    
    Stopping : [  OK  ]===> Updating /etc/psa/psa.conf...
     Trying to set up default qmail permissions... done
    
    ===> Installing Qmail server
     Configuring Qmail...
     Trying to generate SSL certificates for TLS sessions... done
     Trying to register service qmail...  using /sbin/chkconfig
    done
     Trying to start Qmail services... done
     Trying to register service qmail...  using /sbin/chkconfig
    done
    Shutting down kernel logger: [  OK  ]
    Shutting down system logger: [  OK  ]
    Starting system logger: [  OK  ]
    Starting kernel logger: [  OK  ]
    Installing 
    /PSA_7.5.4/rpm_RedHat_el3/base/psa-logrotate-3.7-rhel3.build75050824.12.i586.rpm
    Installing 
    /PSA_7.5.4/rpm_RedHat_el3/base/psa-courier-imap-add-7.5.4-rhel3.build75050902.17.i586.rpm
    Installing 
    /PSA_7.5.4/rpm_RedHat_el3/base/courier-imap-3.0.8-rhel3.build75050824.12.i586.rpm
    Stopping Courier-IMAP server:
       Stopping imap [  OK  ]
       Stopping imap-ssl [  OK  ]
       Stopping pop3 [  OK  ]
       Stopping pop3-ssl [  OK  ]
    
    Stopping Courier-IMAP server:
       Stopping imap [  OK  ]
       Stopping imap-ssl [  OK  ]
       Stopping pop3 [  OK  ]
       Stopping pop3-ssl [  OK  ]
    
    Starting Courier-IMAP server:
       Starting imapd [  OK  ]
       Starting imap-ssl [  OK  ]
       Starting pop3 [  OK  ]
       Starting pop3-ssl [  OK  ]
    
    Stopping Courier-IMAP server:
       Stopping imap [  OK  ]
       Stopping imap-ssl [  OK  ]
       Stopping pop3 [  OK  ]
       Stopping pop3-ssl [  OK  ]
    
    Starting Courier-IMAP server:
       Starting imapd [  OK  ]
       Starting imap-ssl [  OK  ]
       Starting pop3 [  OK  ]
       Starting pop3-ssl [  OK  ]
    
    warning: /usr/lib/courier-imap/etc/pop3d.dist saved as 
    /usr/lib/courier-imap/etc/pop3d.dist.rpmsave
    warning: /usr/lib/courier-imap/etc/imapd.dist saved as 
    /usr/lib/courier-imap/etc/imapd.dist.rpmsave
    Installing 
    /PSA_7.5.4/rpm_RedHat_el3/base/psa-api-common-7.5.4-rhel3.build75060321.20.noarch.rpm
    Installing 
    /PSA_7.5.4/rpm_RedHat_el3/base/psa-api-cli-7.5.4-rhel3.build75060321.20.noarch.rpm
    Installing 
    /PSA_7.5.4/rpm_RedHat_el3/opt/api/psa-api-rpc-7.5.4-rhel3.build75060321.20.noarch.rpm
    Installing 
    /PSA_7.5.4/rpm_RedHat_el3/opt/api/psa-agent-1.3.5-75060321.20.noarch.rpm
    	file /usr/local/psa/bin/anonftp.sh from install of 
    psa-api-cli-7.5.4-rhel3.build75060321.20 conflicts with file from package 
    psa-7.1.7-rhel3.build71050228.12
    	file /usr/local/psa/bin/certificate.sh from install of 
    psa-api-cli-7.5.4-rhel3.build75060321.20 conflicts with file from package 
    psa-7.1.7-rhel3.build71050228.12
    	file /usr/local/psa/bin/cfsetting.sh from install of 
    psa-api-cli-7.5.4-rhel3.build75060321.20 conflicts with file from package 
    psa-7.1.7-rhel3.build71050228.12
    	file /usr/local/psa/bin/client.sh from install of 
    psa-api-cli-7.5.4-rhel3.build75060321.20 conflicts with file from package 
    psa-7.1.7-rhel3.build71050228.12
    	file /usr/local/psa/bin/client_pref.sh from install of 
    psa-api-cli-7.5.4-rhel3.build75060321.20 conflicts with file from package 
    psa-7.1.7-rhel3.build71050228.12
    	file /usr/local/psa/bin/cu_plesk_component.sh from install of 
    psa-api-cli-7.5.4-rhel3.build75060321.20 conflicts with file from package 
    psa-7.1.7-rhel3.build71050228.12
    	file /usr/local/psa/bin/cu_plesk_get_menu.sh from install of 
    psa-api-cli-7.5.4-rhel3.build75060321.20 conflicts with file from package 
    psa-7.1.7-rhel3.build71050228.12
    	file /usr/local/psa/bin/database.sh from install of 
    psa-api-cli-7.5.4-rhel3.build75060321.20 conflicts with file from package 
    psa-7.1.7-rhel3.build71050228.12
    	file /usr/local/psa/bin/dns.sh from install of 
    psa-api-cli-7.5.4-rhel3.build75060321.20 conflicts with file from package 
    psa-7.1.7-rhel3.build71050228.12
    	file /usr/local/psa/bin/domain.sh from install of 
    psa-api-cli-7.5.4-rhel3.build75060321.20 conflicts with file from package 
    psa-7.1.7-rhel3.build71050228.12
    	file /usr/local/psa/bin/domain_pref.sh from install of 
    psa-api-cli-7.5.4-rhel3.build75060321.20 conflicts with file from package 
    psa-7.1.7-rhel3.build71050228.12
    	file /usr/local/psa/bin/init_conf.sh from install of 
    psa-api-cli-7.5.4-rhel3.build75060321.20 conflicts with file from package 
    psa-7.1.7-rhel3.build71050228.12
    	file /usr/local/psa/bin/ipmanage.sh from install of 
    psa-api-cli-7.5.4-rhel3.build75060321.20 conflicts with file from package 
    psa-7.1.7-rhel3.build71050228.12
    	file /usr/local/psa/bin/mail.sh from install of 
    psa-api-cli-7.5.4-rhel3.build75060321.20 conflicts with file from package 
    psa-7.1.7-rhel3.build71050228.12
    	file /usr/local/psa/bin/maillist.sh from install of 
    psa-api-cli-7.5.4-rhel3.build75060321.20 conflicts with file from package 
    psa-7.1.7-rhel3.build71050228.12
    	file /usr/local/psa/bin/protdir.sh from install of 
    psa-api-cli-7.5.4-rhel3.build75060321.20 conflicts with file from package 
    psa-7.1.7-rhel3.build71050228.12
    	file /usr/local/psa/bin/server_pref.sh from install of 
    psa-api-cli-7.5.4-rhel3.build75060321.20 conflicts with file from package 
    psa-7.1.7-rhel3.build71050228.12
    	file /usr/local/psa/bin/spamassassin.sh from install of 
    psa-api-cli-7.5.4-rhel3.build75060321.20 conflicts with file from package 
    psa-7.1.7-rhel3.build71050228.12
    	file /usr/local/psa/bin/subdomain.sh from install of 
    psa-api-cli-7.5.4-rhel3.build75060321.20 conflicts with file from package 
    psa-7.1.7-rhel3.build71050228.12
    	file /usr/local/psa/bin/traffic.sh from install of 
    psa-api-cli-7.5.4-rhel3.build75060321.20 conflicts with file from package 
    psa-7.1.7-rhel3.build71050228.12
    	file /usr/local/psa/bin/webuser.sh from install of 
    psa-api-cli-7.5.4-rhel3.build75060321.20 conflicts with file from package 
    psa-7.1.7-rhel3.build71050228.12
    
    ----- end of output -----
    Isn't this suppose to be easy?
     
  11. jas8522

    jas8522 Basic Pleskian

    24
    23%
    Joined:
    Feb 3, 2005
    Messages:
    80
    Likes Received:
    0
    Location:
    Halifax, Nova Scotia Canada
    Conflicts with older install

    Hey,

    Looks like it wont update because it found a 71.7 installation on the box. Assuming you installed 7.5.4 and wish to use that, try running:

    rpm -qa | grep psa

    If you see any RPM's in that list that say psa-7.1.7, run rpm -i <nameofrpm>

    where nameofrpm is just the first part of the RPM filename, like for example:

    psa-7.1.7-rhel3.build71050228.12

    might be 'psa-7.1.7'

    if that doesn't work, you may have to do rpm -e --nodeps <nameofrpm>

    just make sure you don't remove psa-7.5.4. Then once that's done try running the autoupdater again or yum update psa.

    Jordan
     
  12. jvanv8

    jvanv8 Guest

    0
     
    Ok I have the file, I'll give that a shot... is this "safe" :) or should I wait until the wee hours of the morning if I run the
    rpm -i psa-7.1.7-rhel3.build71050228.12
    command?
     
  13. jas8522

    jas8522 Basic Pleskian

    24
    23%
    Joined:
    Feb 3, 2005
    Messages:
    80
    Likes Received:
    0
    Location:
    Halifax, Nova Scotia Canada
    It should be perfectly safe, since -e will remove only that one RPM, which appears to be the only thing blocking your updates.

    You may want to wait anyway just in case it requires that you install 7.5.4 again after removing it... you never know when weird things like that might happen with Plesk ;)

    Jordan
     
  14. jvanv8

    jvanv8 Guest

    0
     
    Updated, email broken, strange autoupdate behavior

    ok, the rpm -i command just said "file not found" but the rpm -e --nodeps seemed to do something.. but there was no output in the terminal window...

    Then ran the autoupdater (no more blank screen problem since yum-ing the 7.5.4 version) and it finished successfully with the report:
    Code:
    Download file versions.inf3: 22%..100% done
    Download file PSA_7.5.4/plesk-7.5.4-rhel3-i386.inf3: 100% done
    Checking for system installed packages...done.
    Check for components installation status
    Reading system installed packages...done.
    Download file plesk-7.5.4-rhel3-i386.hdr.gz: 100% done
    Download file plesk-7.5.4-rhel3-i386.hdr.gz: 100% done
    Resolve components
    There are some also needed components will installed too: 'base'
    Get Plesk product packages.
    Download file 
    opt/sshterm/SSHTerm-0.2.2-rhel3.build75050824.12.noarch.rpm: 56%..100% done
    Get system update packages.
    Start packages installation
    Install package SSHTerm
    Installation done.
    But that was the last email I've gotten (the success report) as now the email on all domains is broken.. not just webmail, all mail. Any guesses or advice on how to fix the email?

    The component info now lists:
    Code:
    psa          7.5.4-rhel3.build75050824.12 
    But now whenever I open the Plesk Updater it tells me that the base package of Plesk 7.5.4 has an update available.... I try to run the autoinstaller but it doesn't update (I never recieve the update email either)

    trying "yum update psa" says I have everything up to date. If it matters my yum.conf has:
    Code:
    [base]
    name=Red Hat Linux $releasever - $basearch - Base
    baseurl=http://3es.atomicrocketturtle.com/atomic/art/$releasever/
    
    
    [updates]
    name=Red Hat Linux $releasever - Updates
    baseurl=http://3es.atomicrocketturtle.com/atomic/psa-7.5/$releasever/
    [atomic] 
    name=Atomic Rocket Turtle - $releasever - Atomic PSA-Compatible RPMS
    baseurl=http://3es.atomicrocketturtle.com/atomic/art/$releasever/
    
    
    [psa-7.5]
    name=Atomic Rocket Turtle - $releasever - SW-Soft PSA 7.5 RPMS
    baseurl=http://3es.atomicrocketturtle.com/atomic/psa-7.5/$releasever/
    
    [atomic-bleeding]
    name=Atomic Rocket Turtle - $releasever - Atomic PSA-Compatible RPMS
    baseurl=http://3es.atomicrocketturtle.com/atomic-bleeding/art/3/
    
    So I tried to just skip finalizing the auto installer for 7.5.4 and went for 8.0.0
    Again, I didn't recieve any email so it doesn't look like the autoinstaller did anything at all...

    Is my installation of 7.5.4 complete even though the autoinstaller says it isn't (and all my Plesk HTML page titles say Plesk 7.1.7 even though they are different from the version I was running before - loading messages etc).

    Should I try for 8? The autoinstaller doesn't seem to work for it... is there a yum entry I should add to get 8?

    err...
     
  15. phoenixisp

    phoenixisp Silver Pleskian

    27
    57%
    Joined:
    Feb 2, 2002
    Messages:
    840
    Likes Received:
    0
    I don't believe Scott has had time to add Plesk 8 to his project. When using the updater I've found that it goes much easier if you update the base package of Plesk by itself. Then go back and install the other updates. When I updated my boxes to Plesk 8 I found that the autoinstaller doesn't (ot didn't) send an email at the beginning of the install as it used to, just at the end.
     
  16. jvanv8

    jvanv8 Guest

    0
     
    I'm pretty sure the reason I'm not getting any emails is because email is broken across all domains.

    It prompts me for the password and never get accepted. When I go to Plesk and change the password for a user account to something else, it never accepts the new password, saying it has to be 5 characters long and not contain the word 'mail' in it

    What could cause this?
    Whenever I try to send mail, it says
    Code:
    Cannot send mail using the server mail."myserver".com
     
  17. phoenixisp

    phoenixisp Silver Pleskian

    27
    57%
    Joined:
    Feb 2, 2002
    Messages:
    840
    Likes Received:
    0
    Check the log at /usr/local/psa/var/log/maillog to see if it's giving any clues.
     
  18. jvanv8

    jvanv8 Guest

    0
     
    I sent an email to myself then checked the tail of the log
    Code:
    Apr 11 07:50:17 websrv qmail: 1144759817.465408 delivery 292: deferral: Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/
    Apr 11 07:50:17 websrv qmail: 1144759817.465458 status: local 0/10 remote 5/20
    Apr 11 07:50:21 websrv qmail: 1144759821.952661 delivery 287: deferral: Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/
    Apr 11 07:50:21 websrv qmail: 1144759821.952711 status: local 0/10 remote 4/20
    
    Apr 11 07:57:10 websrv qmail: 1144760230.169629 status: local 0/10 remote 2/20
    Apr 11 07:57:19 websrv qmail: 1144760239.476741 delivery 300: deferral: Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/
    Apr 11 07:57:19 websrv qmail: 1144760239.476790 status: local 0/10 remote 1/20
    Apr 11 07:57:34 websrv qmail: 1144760254.487472 starting delivery 301: msg 8012902 to remote [email]ing-tones@1-nokia-ring-tones.com[/email]
    Apr 11 07:57:34 websrv qmail: 1144760254.487522 status: local 0/10 remote 2/20
    Apr 11 07:57:34 websrv qmail: 1144760254.597443 delivery 301: deferral: Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/
    Apr 11 07:57:34 websrv qmail: 1144760254.597492 status: local 0/10 remote 1/20
    
    that ringtones address must be some incoming spam I guess (?)
     
  19. phoenixisp

    phoenixisp Silver Pleskian

    27
    57%
    Joined:
    Feb 2, 2002
    Messages:
    840
    Likes Received:
    0
    This could be due to various things. What are the contents of you /etc/hosts and /etc/resolve.conf files?

    Also, in the control panel:

    Server -> Mail

    Under prferences, do you have POP3 checked for authorization? If so, just check smtp and leave POP3 unchecked and try again.
     
  20. jvanv8

    jvanv8 Guest

    0
     
    ok, I'll check on that.... in the meantime, I thought it might be a DNS issue....

    in Plesk my DNS section says:
    Code:
    <domain>.	NS	ns.<domain>.	
    <domain>.	A	<ip>	
    <domain>.	MX (10)	mail.<domain>.	
    <ip> / 24	PTR	<domain>.	
    ftp.<domain>.	CNAME	<domain>.	
    mail.<domain>.	A	<ip>	
    mssql.<domain>.	A	<ip>	
    ns.<domain>.	A	<ip>	
    webmail.<domain>.  A	<ip>
    is it suppose to look like this?
     
Loading...