Results 1 to 3 of 3

Thread: Try update Ubuntu 14 to 16 and reboot --> no more ssh / ufw don't work / no ping

  1. #1
    Join Date
    May 2019

    Try update Ubuntu 14 to 16 and reboot --> no more ssh / ufw don't work / no ping

    Hi guys, I'm pretty desperate.


    This week I try an update for my distant server from ubunut 14 to ubuntu 16 with :
    Then the tuto say reboot so I reboot.

    php7.0-fpm start/running, process 25291
       Please reboot the server and run the following command /opt/psa/bin/ to continue.
       STOP Distupgradre


    - ping don't return
    - ssh say connection Time out

    When I launch rescue mode and access via ssh to a linux image (I choose an ubuntu 14) on my distant server :
    (By the way when I connect with rescue mode I do :
    sudo su
    chroot /mnt/sda2 bin/bash

    - ufw status:
    iptables v1.4.21: can't initialize iptables table `filter': Table does not exist

    - uname - a :
    Linux 62-210-253-46 4.2.0-35-generic #40~14.04.1-Ubuntu SMP Fri Mar 18 16:37:35 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

    - lsb_release -a :
    No LSB modules are available.
    Distributor ID: Ubuntu
    Description:    Ubuntu 14.04.6 LTS
    Release:        14.04
    Codename:       trusty

    - ls -lh /lib/module :
    total 8,0K drwxr-xr-x 5 root root 4,0K avril 30 09:55
       3.13.0-169-generic drwxr-xr-x 5 root root 4,0K juil. 23  2015 3.13.0-58-generic
    - I have often the message can't resolve hostname IP-IPI-IPI-IP , but I check hostname and host (could show you content if you want)
    - In syslog I have a message :
    apparmor="DENIED" operation="sendmsg" profile="/usr/sbin/named" name="/run/systemd/journal/dev-log" p

    - ip address :
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet scope host lo
           valid_lft forever preferred_lft forever
        inet6 ::1/128 scope host
           valid_lft forever preferred_lft forever
    2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
        link/ether 0c:c4:7a:0e:9f:da brd ff:ff:ff:ff:ff:ff
        inet brd scope global eth0
           valid_lft forever preferred_lft forever
        inet6 fe80::ec4:7aff:fe0e:9fda/64 scope link
           valid_lft forever preferred_lft forever
    3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
        link/ether 0c:c4:7a:0e:9f:db brd ff:ff:ff:ff:ff:ff
    - cat /etc/network/interface so you see here it's em1 than eth0 above
    # The loopback network interface
    auto lo
    iface lo inet loopback
    # The primary network interface
    auto em1
    iface em1 inet dhcp
    - systemclt or everything else with clt :
    Failed to connect to bus: No file or folder find
    And as I said, I was in an update process, so after the reboot I have to re launch the command
    so I'm a bit afraid of install stuff like
    apt-get install lsb-core

    Many many many thanks for your help !
    Last edited by axelgraphikchannel; May 2nd, 2019 at 11:10 AM. Reason: format

  2. #2
    Join Date
    Nov 2012
    Halloween Town
    Xubuntu Development Release

    Re: Try update Ubuntu 14 to 16 and reboot --> no more ssh / ufw don't work / no ping

    Thread moved to Server Platforms for a better fit

  3. #3
    Join Date
    Mar 2010
    Ubuntu Mate 16.04 Xenial Xerus

    Re: Try update Ubuntu 14 to 16 and reboot --> no more ssh / ufw don't work / no ping

    I have no idea what /opt/psa/bin/ is. It is not the method used to upgrade 14.04 to 16.04 on Ubuntu systems.
    Performing system updates between major releases shouldn't be performed over a network connection. It should only be done using the console.

    I would restore from the backup I made just prior to the upgrade effort, gain console access, then follow approved Canonical upgrade procedures.

    The remaining comments below really doesn't matter if you restore from backup.
    sudo su
    chroot /mnt/sda2 bin/bash
    without context doesn't tell us much.

    In rescue mode, you already are root.
    Never heard of It isn't on any of my Ubuntu servers. Must be something specific to your setup or is that something in the normal rescue mode?
    Setting up a chroot requires more than just that command. I'd have to look it up, but it would be about 5-7 commands, I think.

    16.04 switched to systemd. eth0 is gone. The driver used for the NIC determines the naming for each ethernet device. Usually they are unique and based on the MAC of the device. It is a new world.

    Before doing a system upgrade like this on a production system, always run a few test runs in virtual machines first, so you can iron out any difficulties and not impact production. Always, always, have a know-you-can-restore backup before doing such high risk activities. Upgrading an OS from version to version is like swapping out the engine for a car or doing open heart surgery. Would you 'wing-it' for either of those tasks?

    If an upgrade fails along the way, the only recovery is to start over. Otherwise, you'll never be able to trust the system.

    I get that you are frustrated. Upgrades for systems with zero customizations generally don't break when following the suggested upgrade methods, assuming there aren't file corruption or hardware issues. Please check the system log files for any issues.

Tags for this Thread


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts