User Tools

Site Tools


manuals:vps:repair

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
manuals:vps:repair [2016/12/11 19:58] – [VPS Boot Failure] tomsmanuals:vps:repair [2023/02/02 23:46] (current) – deleted openVZ parolek
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 [[manuasl:vps:repair#connecting_rootfs|connecting rootfs]].+Continue by [[manuals:vps:repair#mounting_rootfs|mounting rootfs]].
  
 ==== VPS Is Turned On ==== ==== VPS Is Turned On ====
Line 27: Line 27:
  
  
-===== Connecting rootfs ===== +===== Mounting rootfs ===== 
-vpsAdmin makes it possible to connect **any** dataset to **any** VPS. I.e. it is possible to +vpsAdmin makes it possible to mount **any** dataset to **any** VPS. I.e. it is possible to 
-connect a dataset where the rootfs is a corrupted VPS to a different, working VPS.+mount a dataset with the rootfs of a corrupted VPS to a different, working VPS.
 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 on the connected dataset or not.+It doesn’t matter whether the VPS on the mounted dataset is running or not.
  
 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  for some reason or that this is a bug in +is corrupted for some reason.
-[[http://openvz.org/Vzctl|vzctl]], which might not support +
-the currently installed distro yet. +
- +
-You can check the scripts that [[http://openvz.org/Vzctl|vzctl]] uses to configure the network on a VPS +
-at +
-https://src.openvz.org/projects/OVZL/repos/vzctl/browse/etc/dists.+
  
 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 ''_netdev'' can be written into ''/etc/fstab''. After creating a new website, a bind mount with the parameter ''_netdev'' can be written into ''/etc/fstab''.
-  Because of this, the VPS start-up process will get stuck when mounting+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 ''ifconfig'' from the ''net-tools'' package In order to configure the network properly, you need to have ''ifconfig'' from the ''net-tools'' package
 installed. installed.
- 
-We have seen configurations broken because of various reasons – either an existing 
-''/etc/network/interfaces.head'' or a ''tail'' that only contained a static 
-network configuration and overrode the configuration created by 
-[[http://openvz.org/Vzctl|vzctl]]. 
manuals/vps/repair.1481486339.txt.gz · Last modified: 2016/12/11 19:58 by toms