• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved update plesk onyx with error

Remigio

Basic Pleskian
Today the plesk update failed due to errors (attached)
so the email I get from plesk was:
: pum is called with arguments: ['--list', '--repo-info', '--json']

2018-08-30 06:27:27 ERROR: E:The repository ...
stretch Release' does not have a Release file.

2018-08-30 06:27:27 ERROR: Exited with returncode 1.

So also in system updates I've a red alert with:
Error: The list of packages can not be obtained: 2018-08-30 08:41:56 INFO: pum is called with arguments: ['--list', '--repo-info', '--json'] 2018-08-30 08:41:57 ERROR: E:The repository 'Atomicorp stretch Release' does not have a Release file. 2018-08-30 08:41:57 ERROR: Exited with returncode 1.
 

Attachments

  • plesk_error.zip
    1.8 KB · Views: 7
Last edited:
Correct repository sources or package dependency issues according to the error message displayed upon the attempt to update packages running APT or YUM.

Note: Resolving issues with the operating system installation consistency is an administrative task.


For more information: Look here
 
fukIQhn
fukIQhn.png
 
First, check in which directory the dumps are located. This information can be found in the file /etc/psa/psa.conf. In general, the dumps should be found in the directory / var / lib / psa / dumps. You need to look in this directory and see the available dumps:

Code:
# cd /var/lib/psa/dumps
[root@s12345678 dumps]# ls -la
total 744drwxr-xr-x 2 psaadm psaadm 4096 Jan 18 03:29 .
drwxr-xr-x 3 root root 4096 Jan 15 16:05 ..
-rw------- 1 root root 187029 Jan 18 03:29 mysql.daily.dump.0.gz
-rw------- 1 root root 186958 Jan 17 03:14 mysql.daily.dump.1.gz
-rw------- 1 root root 191560 Jan 16 03:19 mysql.daily.dump.2.gz
-rw------- 1 root root 181169 Jan 15 17:13 mysql.daily.dump.3.gz

Extract the desired dump file using the command gunzip:
Code:
# gunzip /var/lib/psa/dumps/mysql.daily.dump.1.gz

Now delete the old, defective database from the directory / etc / psa with DROP DATABASE:
Code:
# mysql -uadmin -p`cat /etc/psa/.psa.shadow` -e"DROP DATABASE psa;"


In the last step you restore the psa database from the previously unzipped dump file.
Code:
# mysql -f -uadmin -p`cat /etc/psa/.psa.shadow` < /var/lib/psa/dumps/mysql.daily.dump.1
 
First, check in which directory the dumps are located. This information can be found in the file /etc/psa/psa.conf. In general, the dumps should be found in the directory / var / lib / psa / dumps. You need to look in this directory and see the available dumps:

Code:
# cd /var/lib/psa/dumps
[root@s12345678 dumps]# ls -la
total 744drwxr-xr-x 2 psaadm psaadm 4096 Jan 18 03:29 .
drwxr-xr-x 3 root root 4096 Jan 15 16:05 ..
-rw------- 1 root root 187029 Jan 18 03:29 mysql.daily.dump.0.gz
-rw------- 1 root root 186958 Jan 17 03:14 mysql.daily.dump.1.gz
-rw------- 1 root root 191560 Jan 16 03:19 mysql.daily.dump.2.gz
-rw------- 1 root root 181169 Jan 15 17:13 mysql.daily.dump.3.gz

Extract the desired dump file using the command gunzip:
Code:
# gunzip /var/lib/psa/dumps/mysql.daily.dump.1.gz

Now delete the old, defective database from the directory / etc / psa with DROP DATABASE:
Code:
# mysql -uadmin -p`cat /etc/psa/.psa.shadow` -e"DROP DATABASE psa;"


In the last step you restore the psa database from the previously unzipped dump file.
Code:
# mysql -f -uadmin -p`cat /etc/psa/.psa.shadow` < /var/lib/psa/dumps/mysql.daily.dump.1
all done!
but issue remain.
restore psa db -7 days ago, wordpress toolkit updated with success, but plesk updated with red alert/error.
 
Try this commands:

Code:
aptitude purge nginx-common nginx-full
Code:
aptitude reinstall sw-nginx
Code:
plesk repair installation -y -v
 
root@100asa:~# aptitude purge nginx-common nginx-full
-bash: aptitude: command not found

I'm on debian 9.5
Linux #1 SMP Debian 4.9.110-3+deb9u2 (2018-08-13) x86_64
 
Are you using Centos or Ubuntu?

CentOS:
Code:
systemctl stop nginx.service
Code:
systemctl disable nginx.service
Code:
userdel -r nginx
Code:
rm -rf /etc/nginx
rm -rf /var/log/nginx
rm -rf /var/cache/nginx/
Code:
 rm -rf /usr/lib/systemd/system/nginx.service
 
Okey, try this:

Code:
apt-get remove nginx
Code:
update-rc.d nginx remove
Code:
chkconfig nginx
Code:
systemctl disable nginx.service

As for having nginx files hanging around after a successful purge, something must have gone terribly wrong, or there are still packages lying around. The latter is bound to be the case, as nowadays nginx is not a single package anymore, and you need to remove several packages:

Code:
$apt-cache search nginx | grep ^nginx | awk ' { print $1 } '
 
apt-get remove nginx
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'nginx' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
N: Ignoring file 'plesk.list.ai_back' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
root@100asa:~# update-rc.d nginx remove
root@100asa:~# chkconfig nginx
-bash: chkconfig: command not found
root@100asa:~# ^C
root@100asa:~# systemctl disable nginx.service
Synchronizing state of nginx.service with SysV service script with /lib/systemd/ systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable nginx
insserv: warning: current start runlevel(s) (empty) of script `nginx' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `nginx' ove rrides LSB defaults (0 1 6).
root@100asa:~# $apt-cache search nginx | grep ^nginx | awk ' { print $1 } '
-bash: -cache: command not found
 
And have a look here

Sound's usefull, that packages cannot be updated due to full /boot partition. The partition may be full due to multiple old kernels persisting on the system.
 
Please reinstall nginx and try again.
reinstalled nginx, try to update plesk, same error.
as show here:
apt-get autoremove --purge
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
N: Ignoring file 'plesk.list.ai_back' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
 
Unfortunately, this request to Plesk support does not accept direct support requests from me, because my license belongs to the VPS purchased at 1and1.it and so they say to address my hosting.
But I do not think they are able to solve this problem, or at most they will say to address Plesk support.
I will become a ping-pong ball.
 
Back
Top