Search results

If there's a conflict, the course of action is to remove the conflicts. That's what the package manager attempts to do. I took a look at why it was attempting to remove MariaDB exactly. It appears MariaDB bundles mytop: So when you install mytop from another repository, there's a conflict...

Did you pass the -y flag? Or hit return twice?

It's not a Plesk issue. MyTop doesn't like MariaDB, so it tries to remove it, which kicks of a dependency chain leading to the removal of Plesk. Here's an example (fresh ubuntu install): # apt-get install mariadb-server # dpkg -S mysql-server mariadb-server-10.1: /etc/logrotate.d/mysql-server...

But the output you pasted shows otherwise: It prompted for confirmation. Yum/apt/dnf/whatever doesn't treat more "important" packages as more "important" and give a more severe warning, unfortunately. There's no way to do that.

Same concept. plesk installer is a wrapper for the package manager.

Yeah - best way to learn is by doing :) - just not on production I get where you're coming from. But Linux is supposed to be operated with the understanding that you know what the command/operation you run can/is supposed to do and the implications. It does note that there are dependency issues...

I explained this here: Question - Catastrophic apt-get install removes Plesk?? But basically comes down to dependency resolution going wrong. EDIT: Well, not going wrong, just not doing what one might expect it to do

This is not a Plesk issue. Running apt-get remove apache2 would yield the same result. Maybe a sanity check can be built into the plesk installer, but that's extremely limited and doesn't prevent the above issue. On any system, if you remove a necessary dependency, you either remove all the...

I stand corrected. The conflict on RHEL-based systems was related to this bug - not a dependency issue.

I can't seem to reproduce this.

You could say that about any command. rf -rf? find -delete? dd? echo? There are a million fun ways you could destroy a server. apt-get/yum is far from innocent. If you run apt-get remove apache2 what would happen?

The issue stems from dependency resolution. If a package conflicts with another, you may be prompted to remove/uninstall it. If another package depends on the package you just removed, it'll need to be removed to (it doesn't need to be removed, but package managers like yum will do this. rpm -e...

Be careful about user input validation - the ideal way is pm_Cli's callSbin function, which will escalate a script's permissions to root

What?

Try:

The thread is many months old. I'm also pretty sure blatant advertising isn't allowed.

You're not caching wp-login.php right?

From what I see of the error message, it's having trouble with outgoing connections. Are you able to curl that url?

Plesk is a tool, not a replacement for a team/person to manage the server. Plesk is certainly non-comprehensive in all the things you should do, and there's a lot of ways you can screw something up, even directly via the Plesk GUI. I agree with @Liwindo

You shouldn't be symlinking content across subscription. Put then in one, share a doc root or add as alias