Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19

Thread: Sever will not reboot remotely

  1. #11
    Join Date
    Oct 2005
    Location
    Wabasha MN
    Beans
    2,561
    Distro
    Ubuntu

    Re: Sever will not reboot remotely

    "not found" does not mean it isn't there. It might have just lost where it is located (e.g. path).
    Code:
    Code:
    /usr/bin/apt
    Just for the record, I changed the path before doing the following:
    Code:
    :/usr/bin$ sudo apt clean
    [sudo] password for irv: 
    sudo: apt: command not found
    irv@wabasha-server:/usr/bin$
    As you can see the sudo and the apt cannot befound.
    Information on my Main laptop. Information on my small laptop Dell 11 3000
    Using a Asus 3632QM laptop with 8gig RAM, 250 SSD.
    Machine Registered 366271, 366273, 366275.
    Registered Ubuntu user number 18630. Registered Linux user number 458093.

  2. #12
    Join Date
    Mar 2010
    Location
    USA
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Sever will not reboot remotely

    LOL. Now I am getting confused. That didn't say that "sudo" was not found, it said that "for" sudo, that command "apt" was not found...

    What version of server, so I can spin up an instance...
    Last edited by MAFoElffen; June 20th, 2021 at 12:54 PM.

    Concurrent coexistance of Windows, Linux and UNIX...
    Ubuntu user # 33563, Linux user # 533637
    Sticky: [all variants] Graphics Resolution- Upgrade /Blank Screen after reboot
    UbuntuForums system-info Script

  3. #13
    Join Date
    Oct 2005
    Location
    Wabasha MN
    Beans
    2,561
    Distro
    Ubuntu

    Re: Sever will not reboot remotely

    16.04, It has a message when I boot into the server:
    Welcome to Ubuntu 16.04.7 LTS (GNU/Linux 4.4.0-38-generic i686)

    * Documentation: https://help.ubuntu.com
    * Management: https://landscape.canonical.com
    * Support: https://ubuntu.com/advantage

    System information as of Sun Jun 20 07:04:24 CDT 2021

    System load: 0.08 Swap usage: 48%
    Usage of /: 82.7% of 227.14GB Processes: 194
    Memory usage: 31% IP address for p3p1: 192.168.1.105

    Graph this data and manage this system at:
    https://landscape.canonical.com/

    203 updates can be applied immediately.
    185 of these updates are standard security updates.
    To see these additional updates run: apt list --upgradable

    New release '18.04.5 LTS' available.
    Run 'do-release-upgrade' to upgrade to it.
    Information on my Main laptop. Information on my small laptop Dell 11 3000
    Using a Asus 3632QM laptop with 8gig RAM, 250 SSD.
    Machine Registered 366271, 366273, 366275.
    Registered Ubuntu user number 18630. Registered Linux user number 458093.

  4. #14
    Join Date
    Mar 2010
    Location
    USA
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Sever will not reboot remotely

    Okay... Do this:
    Code:
    sudo su
    cd /usr/bin/
    ./apt --help
    #should see the apt help text flash by...
    ls -l apt
    # should show the file details
    echo $PATH
    # should show that /usr/bin/ is in the command path
    If it doesn't, then there is something wrong there...

    Concurrent coexistance of Windows, Linux and UNIX...
    Ubuntu user # 33563, Linux user # 533637
    Sticky: [all variants] Graphics Resolution- Upgrade /Blank Screen after reboot
    UbuntuForums system-info Script

  5. #15
    Join Date
    Mar 2010
    Location
    USA
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Sever will not reboot remotely

    Then for 16.04
    Code:
    cd /etc/apt/
    ls
    At 16.04, before systemd in 18.04, there should be a directory called "trusted". This is the directory that stores the keyring files. At 18.04 and newer, the functional directory that stores the apt keys is called "trusted.gpg.d"...

    Concurrent coexistance of Windows, Linux and UNIX...
    Ubuntu user # 33563, Linux user # 533637
    Sticky: [all variants] Graphics Resolution- Upgrade /Blank Screen after reboot
    UbuntuForums system-info Script

  6. #16
    Join Date
    Oct 2005
    Location
    Wabasha MN
    Beans
    2,561
    Distro
    Ubuntu

    Re: Sever will not reboot remotely

    Did not work:
    irv@wabasha-server:~$ sudo su
    [sudo] password for irv:
    root@wabasha-server:/home/irv# ./apt --help
    root@wabasha-server:/home/irv# ls -l apt
    ls: cannot access 'apt': No such file or directory
    root@wabasha-server:/home/irv#
    Information on my Main laptop. Information on my small laptop Dell 11 3000
    Using a Asus 3632QM laptop with 8gig RAM, 250 SSD.
    Machine Registered 366271, 366273, 366275.
    Registered Ubuntu user number 18630. Registered Linux user number 458093.

  7. #17
    Join Date
    Mar 2010
    Location
    USA
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Sever will not reboot remotely

    You didn't change the directory to /usr/bin/ before looking for apt in the current directory, so yes it would not find it in your user home directory... (skipped a step)

    And on the echo of the $PATH variable?

    I PM'ed you... (You have mail)
    Last edited by MAFoElffen; June 20th, 2021 at 01:52 PM.

    Concurrent coexistance of Windows, Linux and UNIX...
    Ubuntu user # 33563, Linux user # 533637
    Sticky: [all variants] Graphics Resolution- Upgrade /Blank Screen after reboot
    UbuntuForums system-info Script

  8. #18
    Join Date
    Mar 2010
    Location
    USA
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Sever will not reboot remotely

    The iso is located at: https://releases.ubuntu.com/16.04/ub...erver-i386.iso

    Transfer it to your server...
    Code:
    scp ~/Downloads/ISO/ubuntu-16.04.6-server-i386.iso irv@wabashaw.server.net:~/Downloads/iso/
    Mount the iso
    Code:
    sudo mkdir /mnt/iso 
    sudo mount -o loop ~/Downloads/iso/ubuntu-16.04.6-server-i386.iso /mnt/iso
    Copy over a backup of your sources list:
    Code:
    # Backup your sources list 
    sudo cp /etc/apt/sources.list /etc/apt/sources.list.old
    Note: This next command will overwrite your sources list with a one-line pointer to the local mounted repo...
    Code:
    sudo echo "deb [trusted=yes] file:/mnt/iso ./" >> /etc/apt/sources.list
    On just listing directories, apt and the keyring was completely missing...

    On the local machine, since the apt package is not installed, on the remote server, go to the iso image locally and extract the apt package and transfer it to the remote server. Installing manually with dpkg.

    Had to do the same with ubuntu.keyring.

    Then try to fix things and clean things up in a little more detail than before...
    Code:
    sudo rm /var/lib/apt/lists/lock
    sudo rm /var/lib/dpkg/lock
    sudo rm /var/lib/dpkg/lock-frontend
    sudo rm /var/cache/apt/archives/lock
    sudo dpkg --configure -a
    sudo apt-get clean
    sudo apt-get update --fix-missing
    sudo apt-get install -f
    sudo dpkg --configure -a
    sudo apt-get upgrade
    But it still had errors.


    What we did was a Zoom call, sharing screens and talking through it...

    The process from this was to get the latest of that ISO image, which was then Local. Transferred it over to the remove server, and mounted it as a local repository.

    Since the remote no longer had apt and ubuntu-keyring packages installed, I talked him through mounting the local ISO image and copying over the two packages to the remote.

    Then using dpkg, installing those two packages manually on the remote server.

    Still had no love, as those two packages installed successfully, but could not be configured, as there were more, further dependencies issues. Apt worked, but not without errors. With the state of the broken Apt system, there was no way to have the apt utilities that usually fix or recommend... available to fix or figure out on the logic nor the logical order on how to repair them manually. I did a quick analysis of potential suspects online. The problem there was that the version is months well past the soured expiration date for support. That and there were major system changes that went on between 16.04 and 18.04 (systemd). The Ubuntu package manager pages for Xenial are not there anymore. By looking at the next supported, I could only guest-a-mate that there were at least 9 other packages, that might have had problems in the tier above, with a myriad of potentials above them (a cascading effect).

    After trying to do this manually without success of reviving Apt, a decision was made at that point. The goal was to upgrade to a newer release anyways... That the further investment in time was better investing in doing a clean install with 20.04:
    - That was good time to call it.
    - Ensure that the data was backed up.
    - Install a current version of server.
    - Migrate to that current version of Server.
    Last edited by MAFoElffen; June 20th, 2021 at 10:16 PM.

    Concurrent coexistance of Windows, Linux and UNIX...
    Ubuntu user # 33563, Linux user # 533637
    Sticky: [all variants] Graphics Resolution- Upgrade /Blank Screen after reboot
    UbuntuForums system-info Script

  9. #19
    Join Date
    Oct 2005
    Location
    Wabasha MN
    Beans
    2,561
    Distro
    Ubuntu

    Re: Sever will not reboot remotely

    I personally what to thank MAFoElffen for doing a zoom meeting with me and working for three hours+ to try and get my old server going. In the end, I am going to do a fresh install of the 20.04 server and get it up to date. I will try to do this sometime this week and will get back to you to let you know how it goes. I have all my data backed up.
    Information on my Main laptop. Information on my small laptop Dell 11 3000
    Using a Asus 3632QM laptop with 8gig RAM, 250 SSD.
    Machine Registered 366271, 366273, 366275.
    Registered Ubuntu user number 18630. Registered Linux user number 458093.

Page 2 of 2 FirstFirst 12

Bookmarks

Posting Permissions

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