• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Lightsail AWS - problem installation Clonng 95%

RobertQ

New Pleskian
Hi, today I have a small question about installation Plesk Onyx on Amazon Lighstail
how long wait installation after launched Initializing.
Now status is Cloning [95%] and nothing happened
I use 8GB RAM and 2 cores processor 80GB SSD
Thank You
 
Need more details from installation log /tmp/autoinstaller3.log
 
Hello RobertQ,

I have checked deploy Plesk on Lightsail (my configuration was 1 GB RAM, 1 vCPU, 30 GB SSD) and deploy process took 6 minutes.
I suggest checking /var/log/plesk/amazon_setup.log and wait messages like
Code:
# tail -f /var/log/plesk/amazon_setup.log
[...]
==> [Mon May 21 06:10:17 UTC 2018] Update Plesk
[...]
All patches were applied.
Patches were installed successfully.
The changes were applied successfully.

==> [Mon May 21 06:12:56 UTC 2018] Update extensions
==> [Mon May 21 06:13:08 UTC 2018] Update is finished

P.S. Plesk installs latest updates at 95% of cloning.
 
Last edited:
Hello RobertQ,

I have checked deploy Plesk on Lightsail (my configuration was 1 GB RAM, 1 vCPU, 30 GB SSD) and deploy process took 6 minutes.
I suggest checking /var/log/plesk/amazon_setup.log and wait messages like
Code:
# tail -f /var/log/plesk/amazon_setup.log
[...]
All patches were applied.
Patches were installed successfully.
The changes were applied successfully.

==> [Mon May 21 06:12:56 UTC 2018] Update extensions
==> [Mon May 21 06:13:08 UTC 2018] Update is finished

P.S. Plesk installs latest updates at 95% of cloning.

Hi I added my amazon_setup.log and autoinstaller3.log, maybe some could you help me
 

Attachments

  • backup.zip
    62.6 KB · Views: 1
I have checked logs. Did you reboot your instance while cloning not finished, didn't you? I have added my comment near "[AYamshanov comment:]" inside CODE snippet.

Code:
[AYamshanov comment:] Cloning in progress, installation of updates
Preparing to unpack .../mysql-server-5.7_5.7.22-0ubuntu0.16.04.1_amd64.deb ...
Unpacking mysql-server-5.7 (5.7.22-0ubuntu0.16.04.1) over (5.7.21-0ubuntu0.16.04.1) ...
Preparing to unpack .../mysql-server-core-5.7_5.7.22-0ubuntu0.16.04.1_amd64.deb ...
Unpacking mysql-server-core-5.7 (5.7.22-0ubuntu0.16.04.1) over (5.7.21-0ubuntu0.16.04.1) ...
[AYamshanov comment:] Interrupting the update process, no any new messages regarding cloning/update

[AYamshanov comment:] Looks like booting of VM, new mapping between external and internal IP-addresses.
==> [Sun May 20 18:35:21 UTC 2018] Update mapping between public and internal IP addresses in Plesk
===> Map '18.x.y.n' to '172.26.2.26' (on MAC 0e:e4:2e:6a:f5:e6)
SUCCESS: Update '172.26.2.26' completed.

Could you confirm that VM was rebooted by manual? If not, could you please attach "/var/log/syslog" file too?
 
Back
Top