Errors - Githubissues

fmetze commented 8 years ago

When doing "vagrant ssh" in a clean build, I get the following:

New release '16.04.1 LTS' available. Run 'do-release-upgrade' to upgrade to it.

/usr/bin/xauth: file /home/vagrant/.Xauthority does not exist

Maybe fix these two issues?

riebling commented 8 years ago

The .Xauthority error always happens, it's safe to ignore, but I'm not sure how to avoid it... 'touch' the file first so it exists?

Also yes, by default, Ubuntu will always pester about release upgrades. I'm hesitant to port from 14.04 in case it breaks something and without testing first. There may be package version incompatibilities in moving OS releases. Even just the names of packages that Vagrantfile apt-get installs are likely to change across OS versions.

So, two solutions:

Locate, and try provisioning from a different 16.04.1 LTS base image (xenial64 vs trusty64) (easiest to try first, if it works)
Turn off update messages. This is also a two part process, getting rid of the cached message, and editing the config file for notifications. Will have to look up how to do, and add to Vagrantfile

The latter might be a better long-term solution. No matter what base version we run from, eventually a newer one will come, and automatic update messages will come back again. Our policy was conflicting: Freeze legacy VMs to a specific OS version, that we know works, and can support - yet also make sure newer systems follow current Ubuntu LTS releases. (every 2 years?)

On 08/03/2016 08:48 PM, Florian Metze wrote:

When doing "vagrant ssh" in a clean build, I get the following:

New release '16.04.1 LTS' available. Run 'do-release-upgrade' to upgrade to it.

/usr/bin/xauth: file /home/vagrant/.Xauthority does not exist

Maybe fix these two issues?

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/srvk/eesen-transcriber/issues/13, or mute the thread https://github.com/notifications/unsubscribe-auth/ACX11ljIzEFCKuMEBhz00iqamCAp7pgOks5qcTbKgaJpZM4JcPHU.

Eric Riebling Interactive Systems Lab er1k@cs.cmu.edu 407 South Craig St.

riebling commented 8 years ago

First try at switching to a more current Ubuntu base box "ubuntu/trusty64" isn't working at all. The VM won't even provision. Quick Google searches indicate problems with this version only accepting password (vs ssh private key) logins. Also a change in the way mesg works. Trying a different 14.04 (server) base box brought in one that was much larger, and demonstrates some of these issues: it gets stuck in the fussing over VirtualBox guest additions. mesg: ttyname failed: Inappropriate ioctl for device and

The following SSH command responded with a non-zero exit status.                                                                              
Vagrant assumes that this means the command failed!                                                                                           

/sbin/ifdown eth1 2> /dev/null                                                                                                                

Stdout from the command:                                                                                                                      

Stderr from the command:                                                                                                                      

mesg: ttyname failed: Inappropriate ioctl for device

Too bad, that could have been an easy fix. But this seems enough of a serious problem / time sink to put off until after this release of the transcriber. We should really not switch OS releases just before releasing. Moving on to investigate solution 2. Worst case, we mention the messages as "Not a real error, please ignore".

riebling commented 8 years ago

Should be fixed now. Let's keep in mind the dialog here when it comes time to port to newer Ubuntu releases.

riebling commented 8 years ago

The suggestion to upgrade to Ubuntu 16 still happens on first 'vagrant up' but not on subsequent ones. The suggested strategy seems to not kick in during first boot:

Edit the configuration file to set upgrade notifications to "never"
Remove the cached notification "MOTD style" message file
Run the command to update the upgrade notifier

Perhaps another stage is required, possibly deleting the actual MOTD file, if it exists.

riebling commented 8 years ago

How about this: if we delete /var/run/motd.dynamic we get a COMPLETELY CLEAN login:

you@computer:/path/to/eesen-transcriber$ vagrant ssh
vagrant@vagrant-ubuntu-trusty-64:~$

Of course, there are always consequences. This works great for a silent first-login, but on subsequent 'vagrant down' 'vagrant up' cycles, we get back the message again (but still without the release upgrade message)

Welcome to Ubuntu 14.04.5 LTS (GNU/Linux 3.13.0-93-generic x86_64)

 * Documentation:  https://help.ubuntu.com/

  System information as of Wed Aug 10 18:21:38 UTC 2016

  System load:  0.0               Users logged in:     0
  Usage of /:   9.9% of 39.34GB   IP address for eth0: 10.0.2.15
  Memory usage: 1%                IP address for eth1: 192.168.56.101
  Swap usage:   0%                IP address for eth2: 192.168.56.101
  Processes:    92

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

  Get cloud support with Ubuntu Advantage Cloud Guest:
    http://www.ubuntu.com/business/services/cloud

Last login: Wed Aug 10 18:16:47 2016 from 10.0.2.2

srvk / eesen-transcriber

Errors #13