Ubuntu updating issues
Ubuntu and similar distros are widely considered to be as simple as it gets. For the most part, 98% of the best user experience possible is found out of the box by default. This article will address the top mistakes made by newer Ubuntu users and offer advice on how to avoid those Ubuntu snafus.Before I jump head first into what will be a heated discussion among various Linux enthusiasts, understand this first.On the other side of the coin, however, it's imperative that you keep your Ubuntu installation in-sync with the latest security updates.Point being, everyone should have Important Security Updates enabled and set to install automatically.udeb package during the automated install of ubuntu 14.04.5, the system was suddenly unable to resolve hostnames via dns. I am currently unable to install Ubuntu 14.04.5.10 package it is unable to download the next package because it can no longer resolve the archive.name that it had been resolving prior to the installation of that libc6 library. I also run some authoritative DNS servers, and have seen the same query type from the public - suggesting that other servers out in the wild are experiencing the same issue! I note that -ubuntu6.10 was recently added to the archive. After updating a server (without reboot), the internal DNS servers received odd queries of type TYPE20736 (no idea what that is) 21-Mar-2017 .627 queries: info: client 172.16.x.x#49803 (host.internal.domain IN TYPE20736 (172.16.x.x) After rebooting said server, it starts querying normal type A records again. Rebooting after installing resolved the issue, suggesting the update itself is fine, but the process of updating breaks resolution.
Without that log entry its not possible to guess where the problem is and so its not possible to help here. This log is empty./var/log/apache2/is also empty (just some service restart logs)php-errorrs-log is also empty Edit: Ok, I had to reinstall mysql-server ...If you were able to load websites until you updated Firefox, your Internet security software (including firewalls, antivirus programs, anti-spyware programs, and more) is likely preventing Firefox from connecting to the Internet.This problem occurs when your Internet security program was set to trust the previous version of Firefox, but no longer recognizes your updated version as trusted.After that it refuses to start.issuing the "insync start" command on the commandline gives no respons.issuing one of the insync commands, for instance "insync get_status" gives:"Insync doesn't seem to be running.Start it first." Downgrading to 1.3.16 solves the problem.(my file is set correctly (deb zesty non-free contrib)I'm on Ubuntu-gnome 17.04 (64bit) Could you check out what the problem is?
But what are the issues for 14.04, with the older version?