[00:34] hi guys [00:34] need some helping fixing an apt-get issue. [00:35] i can't seem to connect to any update servers without apt-get saying could not resolve '' [00:36] i can ping address (ping 8.8.8.8) but nothing with dns [00:36] kaleidoscope, DNS issue? [00:37] Latrina: exactly. but i have one DNS installed which points to my gateway [00:37] can you ping external DNS other than any APT repos? [00:37] i can ping google's DNS (8.8.8.8) perfectly [00:38] can you ping the domain name? [00:38] 8.8.8.8 does not belong to a domain name afaik [00:39] Latrina: i believe not, i'm not exactly sure i set a domain name? [00:39] domainname returns (none) [00:39] a domain name is the url [00:39] anyways add some DNSs in /etc/resolv.conf [00:40] like 80.80.80.80 and 80.80.81.81 [00:40] or whatever you like best [00:40] than fix your DNS server [00:41] Latrina: gotcha, but the resolv.conf warns not to input any DNS entries? wouldn't a reboot wipe out the changes? [00:47] I am not sure honestly. My DHCP controller deal the whole thing [00:48] and I don't quite do network or system administration on linux, particularly on ubuntu [00:48] Latrina: same here, i usually left it up to default install. [00:49] it's okay, i found the solution. apparently my /etc/hosts file was error'd [00:49] '127.0.0.1 localhost.localdomain localhost' this line was missing, which caused the problems [00:49] https://help.ubuntu.com/lts/serverguide/network-configuration.html [00:50] this wiki page has the solution to your answer on how to setting DNS statically [00:50] okay [00:50] gotcha, thank you for the help! [00:50] no worries === sleepypc is now known as hypermist [05:53] good morning === lordievader is now known as Guest95054 === JanC_ is now known as JanC === popey_ is now known as popey [10:54] hello. Anyone familiar with Nginx? Can the `ssl_session_cache` setting be set only once for the entire Nginx configuration? I thought it might be per-site, even the one shared accross workers, since it can be defined in the `server { … }` blocks. Anyone know? [10:59] adrian_1908: yes. context: http, server http://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_session_cache [11:00] fallentree: "Each shared cache should have an arbitrary name" Arrr, I missed that part. I had them set with the same name. === dannf` is now known as dannf [13:41] coreycb: hello, you guys had a good summit in Boston ? [13:46] zioproto: hello, yes it was a good summit === gimmic_ is now known as gimmic [14:10] coreycb: are you guys aware that the last update (pike m1?) seems to have a broken osc client? http://logs.openstack.org/53/464553/1/check/gate-puppet-nova-puppet-beaker-rspec-ubuntu-xenial/2a0b871/console.html#_2017-05-15_12_16_20_658041 [14:13] mwhahaha: hi, yes i believe so. jamespage, is that the same issue you were hitting? [14:13] anyway to get that fixed as it's royally fubared our ci [14:14] * jamespage looks [14:16] that's 3.9.0 of osc [14:24] hmm looks like I need to rev on keystoneauth1, osc-lib and openstackclient itself [14:24] mwhahaha: are you running against proposed or updates for pike? [14:24] updates [14:24] (pretty sure) [14:25] something flipped last friday and broke everything [14:26] https://github.com/openstack/puppet-openstack-integration/blob/master/manifests/repos.pp#L6-L10 which defaults to updates https://github.com/openstack/puppet-openstack_extras/blob/master/manifests/repo/debian/ubuntu.pp#L47 [14:27] mwhahaha: yeah pike1 dropped into updates last friday [14:27] (and no we'd not seen this issue - but our test endpoint is not coupled with the target cloud in the same way the puppet gate tests are) [14:28] you should one of our scenarios in your testing ;) === dames is now known as thedac [14:33] mwhahaha: it will take a bit to work this through - have three layers of versioned depends to land [14:37] Has anyone here had to set up a *nix system on a wired 802.1X protected network ? [14:40] awesome keystoneauth1 does not like py3.6 === avis- is now known as Guest66990 === jdstrand_ is now known as jdstrand [16:49] caribou, o/ === jdstrand is now known as jdstrand_ === jdstrand_ is now known as jdstrand [20:11] I can't install mysql-server-5.7 in artful, this looks like is the error: [20:11] May 15 20:10:26 artful systemd[7938]: mysql.service: Failed at step KEYRING spawning /usr/share/mysql/mysql-systemd-start: Permission denied [20:11] has anybody seen this before? [20:11] I'm using an artful lxd container on xenial [20:11] dmesg is clean, no apparmor messages [20:22] This may be super-basic, but is mysql-systemd-start set to be executable? (chmod +x) [20:24] yes [20:35] worked on artful bare metal [20:36] must be lxd related, I'm asking there [20:58] why is mysql-server-5.7 in xenial-updates ahead of artful? [20:58] mysql-server-5.7 | 5.7.17-0ubuntu1 | artful | amd64, arm64, armhf, i386, ppc64el, s390x [20:58] mysql-server-5.7 | 5.7.18-0ubuntu0.16.04.1 | xenial-updates | amd64, arm64, armhf, i386, powerpc, ppc64el, s390x [21:10] why am i getting a 'connection refused' when i try to ssh to my ubuntu server from my ubuntu laptop? i checked netstat and its listening on my non standard ssh port tcp 0 0 0.0.0.0:22222 0.0.0.0:* LISTEN - ... i can connect when NOT from behind my unlimited VPN. why would this be happening? [21:16] arooni: you can look at the logs on the server or run, perhaps, `ssh` with -vvv. === JanC_ is now known as JanC