manuals:vps:repair
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| manuals:vps:repair [2016/12/11 14:42] – created toms | manuals:vps:repair [2023/02/02 23:46] (current) – deleted openVZ parolek | ||
|---|---|---|---|
| Line 6: | Line 6: | ||
| configurations, | configurations, | ||
| - | This doesn’t mean that our [[informace:podpora|support]] won’t help you with your VPS. However, capable admins | + | This doesn’t mean that our [[information: where_to_write |
| can get their VPS running again quicker and don’t need to wait for our help. | can get their VPS running again quicker and don’t need to wait for our help. | ||
| Line 19: | Line 19: | ||
| The init system or a different important part of the VPS system is either missing or corrupted. | The init system or a different important part of the VPS system is either missing or corrupted. | ||
| - | Continue by [[navody:vps:oprava#pripojenim_rootfs|connecting | + | Continue by [[manuals:vps:repair#mounting_rootfs|mounting |
| ==== VPS Is Turned On ==== | ==== VPS Is Turned On ==== | ||
| Line 27: | Line 27: | ||
| - | ===== Connecting | + | ===== Mounting |
| - | vpsAdmin makes it possible to connect | + | vpsAdmin makes it possible to mount **any** dataset to **any** VPS. I.e. it is possible to |
| - | connect | + | mount a dataset |
| In order to do this, you can use the playground or another VPS running in a production environment. | In order to do this, you can use the playground or another VPS running in a production environment. | ||
| - | It doesn’t matter whether the VPS with rootfs is running | + | It doesn’t matter whether the VPS on the mounted |
| You can create a mount like this: Details of the recovery VPS -> Create mount -> | You can create a mount like this: Details of the recovery VPS -> Create mount -> | ||
| Line 109: | Line 109: | ||
| The the VPS doesn’t have IP addresses or a route, it could mean that either the network configuration | The the VPS doesn’t have IP addresses or a route, it could mean that either the network configuration | ||
| - | is corrupted | + | is corrupted for some reason. |
| - | [[http:// | + | |
| - | the currently installed distro yet. | + | |
| - | + | ||
| - | You can check the scripts that [[http:// | + | |
| - | at | + | |
| - | https:// | + | |
| One of the ways how you can clear iptables via remote console is using | One of the ways how you can clear iptables via remote console is using | ||
| Line 146: | Line 140: | ||
| ===== Ubuntu and ISPConfig ===== | ===== Ubuntu and ISPConfig ===== | ||
| After creating a new website, a bind mount with the parameter '' | After creating a new website, a bind mount with the parameter '' | ||
| - | | + | Because of this, the VPS start-up process will get stuck when mounting |
| file systems. You need to remove it. | file systems. You need to remove it. | ||
| Line 152: | Line 146: | ||
| In order to configure the network properly, you need to have '' | In order to configure the network properly, you need to have '' | ||
| installed. | installed. | ||
| - | |||
| - | We have seen configurations broken because of various reasons – either an existing | ||
| - | ''/ | ||
| - | network configuration and overrode the configuration created by | ||
| - | [[http:// | ||
manuals/vps/repair.1481467369.txt.gz · Last modified: 2016/12/11 14:42 by toms
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
