=== CiPi is now known as cipi [02:45] Is there any way to see "journalctl -xe" output on failed upgrade root? I tried upgrading a server from 15.04 to 15.10 and it turned itself off at 85% done resulting in an unbootable mess. [02:46] Neither chooting to /mnt/root/@_failed_upgrade before running journalctl -xe nor using jornalctl --root option see the old files... [04:03] when is the next scheduled server team meeting? === Lcawte|Away is now known as Lcawte === Karunamon|2 is now known as Karunamon === Lcawte is now known as Lcawte|Away === Lcawte|Away is now known as Lcawte === cipi is now known as CiPi === Lcawte is now known as Lcawte|Away [09:15] Good morning. === tinyhippo is now known as christmashippo === Lcawte|Away is now known as Lcawte === Lcawte is now known as Lcawte|Away === tinyhipp1 is now known as Guest54786 [11:05] why does php5 install apache2... [11:09] Because that's the default (first) implementation listed in the Depends line [11:10] Install some other variant and uninstall apache2, if you want [11:12] Console only php ain't possible? [11:27] php5-cli [11:32] ren0v0: Install ^ if you just want php. [11:32] Or some other package, depending on what context you want to use php. [11:32] Example php5-cgi or php5-fpm [11:52] Ben64, lordievader thanks [11:52] maxb, it shouldn't have deps, should it [11:53] it doesn't depend on apache2, i don't know why its installed with it [12:20] Does anyone know if php5-fpm service should always be running once started? i assume so, just that mind is stopping itself right away, and i have nothing in its logs t say there is an issue, and i've turned logging level to debug === Piper-Off is now known as Monthrect === Lcawte|Away is now known as Lcawte [16:04] EmilienM, everything is in xenial-proposed right now except for neutron-vpnaas, murano, murano-dashboard, and aodh which are just waiting on a sponsor to upload [16:05] EmilienM, a little work is left to get everything backported to trusty-xenial-proposed === Lcawte is now known as Lcawte|Away [16:37] coreycb: yeah, our CI is running LTS, trusty for now [16:37] coreycb: do you know when ~ can I run mitaka on trusty? [18:44] Is there a way to reinstall the networking in Ubuntu server 14.04 [18:45] +1 [18:45] why do you need to re-install it ? [18:45] as the common sense approach would be to re-install the package [18:45] * tsimonq2 uninstalled network packages once and it would be good to know how to recover them [18:45] what do you mean recover them [18:45] you just install the packages you want [18:45] but you can't if networking is gone [18:45] if you uninstall them and want them back, reinstall the package you just removed [18:46] you can, download them and move them on , or manually configure your networking temporary [18:50] My networking keeps on cutting out and I know it is not my internet it is my server [18:50] That's why I need to reinstall networking [18:50] Also if I have static ip's do I really need network manager [18:50] jvwjgames: that is not a solution [18:51] jvwjgames: your network keeps dropping so you'll re-install network manager ??? [18:51] that is not debugging or a solution, thats just random guessing [18:51] I have checked everything though that I can think of [18:52] why do you think it's network manager ? [18:52] what suggests it is [18:53] I don't think that but I just thought that if I refreshed it it would help [18:53] why would it help ? [18:53] reinstalling a bit of software thats working fine [18:53] what benifit will that do ? [18:54] why don't you focus on understanding what's going on [18:54] I am trying to [18:55] ok - what have you learnt as fact so far [18:55] My /etc/network/interfaces file is correct [18:56] My IP routes are fine [18:56] well you shouldn't be using that if you're using network manager [18:56] so I think we've found one problems straight away [18:56] you've configured the networking file and network manager [18:56] that will create a conflict [18:56] Ok [18:56] ( a conflict that should be managed to be fair - but often doesn't ) [18:56] So then yes uninstall network manager [18:56] if you don't want network manager, sure [18:58] How would that create a conflict [18:58] jvwjgames: so the legacy scripts will parse the networking file and configure the interface, while network manager will also want to create/manage the interface [18:58] network manager "should" ignore the interfaces file if it's populated, but that doesn't always work [18:59] Ah Ok [19:00] Well I nuked network manager I am crossing my fingers I will still have connectivity === Lcawte|Away is now known as Lcawte [19:01] if your interfaces file is correct, you should have zero issue [19:03] Interfaces failed to come up [19:03] ok - so walk the init process, [19:03] try bringing it up manually [19:07] OK I think they are up but no network connectivity [19:08] then they are not up [19:08] or you have a serious problem with your network [19:09] http://picpaste.com/pics/IMAG0250-ZQCQ3fnS.1450984161.jpg [19:10] thats a file [19:10] that doesn't show if they are up or their status [19:13] http://picpaste.com/pics/IMAG0251-4jn39e3q.1450984381.jpg [19:14] jvwjgames: so that means it's got a static IP address, is the inteface actually up, can it talk to anything else at an IP level ? [19:19] http://picpaste.com/pics/IMAG0253-myXabBbX.1450984739.jpg [19:20] there you go then [19:20] it's up and working on the network [19:22] But as you can see it can't get out to the internet [19:24] because your firewall is blocking it [19:24] No firewall on the network [19:24] you can see it's getting to your firewall and the firewall is blocking the next hop [19:25] That domain I assigned by Comcast [19:25] not sure what thats got to do with anything ? [19:25] That is the interface that is still on the local network [19:26] what ? [19:30] Meaning that interface is on my server I am pinging from [19:30] jvwjgames: it's still trying to get out of that device [19:31] look at the gateway that device is trying to use [19:31] it's clear DNS is working as it's getting IP's so it's on the network [19:31] I suspect your router/firewall is screwed [19:31] routing / firewal [19:31] firewall [19:43] The only thing is I don't have a router on the servers network [19:43] And the modem is in pass-through mode [19:43] there must be a gateway to connect you to the internet [19:45] The gateway is on 96.92.80.222 so the gateway is on Comcast side [19:45] it still has to reach that gateway to get out onto the internet [19:49] True [19:50] That's weird I can ping and traceroute to 222 but can't get past that [19:51] what is 222 ? [19:52] The gateway [19:52] ok, so if you can reach the gateway but can't get past it, that suggests it's blocking icmp [19:53] But if I try to do apt it says can't connect [19:54] ok - so if you can get to the gateway but the gateway won't let you out, the gateway is the problem [19:55] OK [19:56] But one last thing I have other devices that can reach the internet on the same modem [19:56] what is their gateway ? [20:26] Sorry about that [20:26] There gateway is also 96.92.80.222 [20:35] Plus my mac works and it is staticly assigned with 96.92.80.222 [20:49] ikonia: uh-oh oh no this is bad I think [21:04] jvwjgames: ?