I recently upgraded to 'Trusty' i.e. Ubuntu 14.04. I tried pinging google.com through the terminal.
ping google.com
ping: unknown host google.com
I tried the following:
sudo apt-get remove --purge resolvconf && sudo apt-get install --reinstall resolvconf
to remove and reinstall the resolv config, but to no avail.
Then I found the official bug here: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1308378
I tried to do the following as instructed there:
cd /etc
sudo ln -s /run/resolvconf/resolv.conf
But it gave an error:
ln: failed to create symbolic link ‘./resolv.conf’: File exists
Internet works fine through my firefox browser. In fact, I'm writing this question through the same system.
I set additional DNS servers in the WiFi settings to the google DNS servers:
8.8.8.8, 8.8.4.4
But to no avail.
Please help.
The problem was solved on Ask Ubuntu.
Here's the link to the answer:
https://askubuntu.com/questions/584528/unresolved-host-upgrade-12-to-14-ubuntu-net-connection-fine-through-browser/584540#584540
Related
Ubuntu 18.04:
It looks like the Remmina Remote Desktop app was updated today and I lost the RDP protocol in the process. VNC, SSH and SPICE are still available but no RDP.
I tried rebooting, uninstalling and reinstalling using:
sudo killall remmina
sudo apt-get purge remmina* -y
rm -Rf /home/`whoami`/.remmina/remmina.pref
sudo apt-get install remmina* -y
This combo'd with a reboot before and after but still no RDP.
I also noticed that the Ubuntu Software (Gnome Software) has 2 Remmina apps listed.
I found a link (the fix) on Remmina website by accident.
The normal install instructions on their site also did not work but then I looked at compiling from source.
https://gitlab.com/Remmina/Remmina/-/wikis/Compilation/Compile-on-Ubuntu-18.04
I added to the "purge" section of the remove command above and this worked:
sudo killall remmina
sudo apt purge "remmina*" "libfreerdp*" "libwinpr*" "freerdp*"
rm -Rf /home/`whoami`/.remmina/remmina.pref
Reboot and then install using the "Ubuntu Software", choose the one with the mostly Blue icon.
It looks like the FreeRDP libraries may have been the issue for me.
I installed DNSMasq with Brew to run virtual hosts but quickly decided I did not want to run vhosts and have uninstalled and (tried to) remove DNSMasq.
I'm unsure what this has done to the machine's nameserver but now my 127.0.0.1 'cannot be reached'. Apache is running but I cannot reach the server. I tried to debug through /etc/NetworkManager/NetworkManager but could not find the directory and I'm unsure where the default network manager configuration file is and how to edit this.
I have a feeling etc/resolver/dev may be causing the issue.
DNSMasq was installed by -
brew install dnsmasq
cd $(brew --prefix); mkdir etc; echo 'address=/.dev/127.0.0.1' > etc/dnsmasq.conf
sudo cp -v $(brew --prefix dnsmasq)/homebrew.mxcl.dnsmasq.plist /Library/LaunchDaemons
sudo launchctl load -w /Library/LaunchDaemons/homebrew.mxcl.dnsmasq.plist
sudo mkdir /etc/resolver
sudo bash -c 'echo "nameserver 127.0.0.1" > /etc/resolver/dev'
I cannot remember now what command I used to uninstall.
/Library/LaunchDaemons/homebrew.mxcl.dnsmasq.plist still remains.
httpd.conf has been reset to original file and vhosts commented out.
Help appreciated.
I have the same issue, but problem was with apache configuration after upgrading brew.
Try this to see the errors: sudo apachectl -t
I am trying to install beanstalkd (http://kr.github.io/beanstalkd/download.html) via the Linux Terminal on a shared hosting account at Godaddy.
The previous link gives commands that should install beanstalkd on the server. I use SSH (with PuTTy) to access the Linux Terminal. I have practically tried all the commands in the previous link and am consistently obtaining errors like:
sudo apt-get install beanstalkd
error message: -bash: sudo: command not found
brew install beanstalkd
error message: -bash: brew: command not found
su -c 'rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-3.noarch.rpm'
su -c 'yum install beanstalkd --enablerepo=epel-testing'
error message: -bash: su: command not found
yaourt -S beanstalkd
error message: -bash: yaourt: command not found
I am not even sure what bash is exactly and if it is causing the problem, or if its because I'm using an SSH connection, or if it's really because the commands don't actually exist on the server (which would be strange because when I do man sudo or man su I do in fact get the complete manual of both commands in the terminal).
QUESTION: Why am I unable to run the previous commands to install beanstalkd on the linux server? Does it have to do with me using PuTTy (ssh connection)? What could I possibly do to get beanstalkd installed? Could it be because its shared hosting with Godaddy, and I might not have full power over the linux terminal?
SERVER INFO: When running cat /proc/version I obtain my linux distribution: Red Hat 4.4.7-16. I have a shared hosting account with Godaddy with a linux server hosting my site.
You have a RedHat distro, and they use rpm+yum for package management.
I see from yum search beanstalkd on my box that I can find it, but only on EPEL.
However, you have a really old version of RedHat, so can't just install the epel-release rpm, also, there doesn't seem to be a built version for RedHat 4.
If you had at least RedHat 5 you could do:
$ sudo yum install https://dl.fedoraproject.org/pub/epel/epel-release-latest-5.noarch.rpm
$ sudo yum install beanstalkd
You may in fact have a restricted instance of batch...
You must go to your provider's interface and do the necessary to have root access. Have you tried something like explained here?
https://uk.godaddy.com/help/enable-adminroot-access-managed-or-fully-managed-12270
If it doesn't work for you, you may also try asking https://serverfault.com/ that seems more relevant for your case.
I tried installing as mentioned here: https://about.gitlab.com/downloads/
sudo yum install openssh-server
sudo yum install postfix
sudo yum install cronie
sudo service postfix start
sudo chkconfig postfix on
sudo lokkit -s http -s ssh
curl -O https://downloads-packages.s3.amazonaws.com/centos-6.6/gitlab-7.7.2_omnibus.5.4.2.ci-1.el6.x86_64.rpm
sudo rpm -i gitlab-7.7.2_omnibus.5.4.2.ci-1.el6.x86_64.rpm
sudo gitlab-ctl reconfigure
It looks like everything went successfully, but but I don't get anything on my hostname. Is there anything I missed?
GitLab will try to setup the FQDN by using the hostname of your machine. To do this manually, open /etc/gitlab/gitlab.rb and edit the external url according to the documentation, which by the way if you haven't already read, I suggest that you do it!
So out of no where I was unable to SSH into my headless linux box.
So I hooked up a screen and started tooling with it.
My server is still fully functional and the box seems in tact. I just wouldn't let me SSH in.
So I tried follow a few online tutorials on adding my IP to the SSH allow file but nothing seemed to work.
I kept getting
"Network Connect: Connection Refused"
when attempting to SSH in with putty.
So I decided to nuke the iptables and do
sudo apt-get remove --purge iptables
which resulted in a failure.
Something like this
"processing tables for mandb " "fopen permission denied"
So I tried doing
sudo apt-get install iptables
which it said the same fopen error.
End result is my server is up and running but I have no ssh capabilities into my box. On that note though I do still have an active samba connection. Take that for what its worth.
The fopen permission denied thing when doing apt-get or dpkg, is very often a sign that your manpages cache at /var/cache/man is owned by root:root instead of man:root. Try changing this with
chown -R man:root /var/cache/man
I followed the instructions below and the problem was solved. I hope it works for you.
sudo apt autoremove
sudo dpkg --configure -a
sudo apt-get update
sudo apt-get upgrade