Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
25% Recurring Discount on NVMe VPS
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Trying to elevate OVH dedicated server

zafouharzafouhar Veteran
edited December 2023 in Help

Was just wondering, i'm trying to elevate my OVH dedicated server from Cloudlinux v7 to v8 but i'm getting this error:

2023-12-08 06:48:33 [WARN] *** Elevation Blocker detected: 
  Your machine has multiple network interface cards (NICs) using kernel-names (ethX).
  Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade.

  Please provide those interfaces new names before continuing the update.

What should I do to resolve this issue?

Comments

  • beanman109beanman109 Member, Host Rep, Megathread Squad

    @zafouhar said: What should I do to resolve this issue?

    Seems like you should

    @zafouhar said: provide those interfaces new names before continuing the update.

    Try renaming them
    eth0 -> nic0
    eth1 -> nic1

  • I can't rename them though as they are controlled by cloud-init

  • beanman109beanman109 Member, Host Rep, Megathread Squad

    @zafouhar said: I can't rename them though as they are controlled by cloud-init

    Don't know too much about cloud-init, what part of cloud-init is preventing you from changing the names on them? As everything I can see in the documentation for it seems to imply that the set-name variable can be used for network interface names.

    https://cloudinit.readthedocs.io/en/latest/reference/network-config-format-v2.html

  • zafouharzafouhar Veteran
    edited December 2023

    Well for example the ifcfg-eth1 doesn't even exist, I already tried creating that file and renaming it but that change doesn't apply when I reboot the server so its reading stuff from somewhere place.

    I thought of completely disabling automatic network configuration and created this file /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg to do that.

    I've also adjusted my ifcfg-eth0 file and changed BOOTPROTO from dhcp to static and added the IP & netmask in the file.

    But i'm not sure if this is the correct way or if I will just break everything.

  • beanman109beanman109 Member, Host Rep, Megathread Squad

    @zafouhar said: Well for example the ifcfg-eth1 doesn't even exist, I already tried creating that file and renaming it but that change doesn't apply when I reboot the server so its reading stuff from somewhere place.

    A quick google showed someone had a similar issue with the changes not applying to ifcfg-eth1, does adding ONBOOT=yes to /etc/sysconfig/network-scripts/ifcfg-eth* work?

    https://unix.stackexchange.com/questions/68295/use-of-etc-sysconfig-network-scripts-ifcfg-eth-files

  • Nothing seems to apply to eth1/eth0, they not controlled by /etc/sysconfig/network-scripts/ so nothing defined there applies.

  • Wouldn't it be much easier if you back up the server, reinstall Cloudlinux v8 and go back to the backup?

  • @hresser said:
    Wouldn't it be much easier if you back up the server, reinstall Cloudlinux v8 and go back to the backup?

    Not in this case unfortunately!

  • tentortentor Member, Host Rep

    Do you have something like net.ifnames=0 in grub configuration?

  • I got really close to succeeding with elevate st OVH. But, in the end I gave up. The old trusty method works best = get a new server, install/setup your cpanel stack on the version you want all fresh and new. Use Transfer Tool to migrate your accounts from old panel to new. Delete the old server and old licenses. It's the safest and easiest route to go imo.

  • vsys_hostvsys_host Member, Patron Provider

    Maybe you implemented the wrong steps during the rename process:
    Here are the exact steps:

    1) Identify your network interfaces by running: ifconfig | grepeth[0-9]

    2) Edit the udev rules file: vi /etc/udev/rules.d/70-persistent-net.rules

    3) Modify the last parameter of each rule to assign desired names to the cards.

    4) rename the previous files that used the old card names. Run:
    cd /etc/sysconfig/network-scripts/
    mv ifcfg-eth0 ifcfg-ens192(your desired name)
    mv ifcfg-eth1 ifcfg-ens224

    Open each renamed file and update the DEVICE parameter to match the new name:

    vi ifcfg-ens192

    Change DEVICE=eth0 to DEVICE=ens192 and save

    Repeat for the other file (ens224).

    After this, interfaces should be renamed.

Sign In or Register to comment.