[01:24] <fishcooker> no worries Fudge
[03:04] <Fudge> ty
[03:15] <karstensrage> how do i find the multiarch directory
[03:15] <karstensrage> like i386-linux-gnu/
[03:15] <karstensrage> programmatically?
[08:28] <marlinc> I want to set up automated updates on servers because the amount of server that I have to update now is getting quite out of hand
[08:29] <marlinc> I've been thinking of using unattended-upgrades to automatically install updates except for packages that are important for the functioning of the system
[08:29] <marlinc> Like for example mysql-server on a MySQL server, I was thinking of setting those on 'hold'
[08:30] <marlinc> Any thoughts on doing it that way, is there a different route I should look at?
[08:33] <Fudge> marlinc:  just do security so ssl kerns etc are done when they need doing
[08:33] <sivir> how many servers?
[08:33] <marlinc> About 20-30 I'd say
[08:34] <marlinc> Its not that much but its quite a  lot to manually update every time I get a notification from our monitoring system
[08:34] <marlinc> Although in general its only security updates which I could put on auto update safely right?
[08:34] <smb> hallyn_, I wasn't doing a "merge" after FF but I'll keep an eye on the bug report. Jamie did already reply, so right now its waiting for more info.
[08:35] <sivir> isn't landscape free till 20 servers
[08:35] <sivir> and like 300 dollars per year starting
[08:35] <sivir> for more
[08:36] <sivir> https://landscape.canonical.com/
[08:37] <sivir> https://www.youtube.com/watch?v=yaFE4g8EcvI
[08:39] <sivir> I'd say the video is quite comprehensive of it's features
[08:43] <sivir> I'd say it's a huge timesaver, you can do it yourself but still why invent the wheel again (especially if it saves time = money)
[08:44] <BlackDex> Hello there. I have a problem with upstart. There is a process which has been defuncted/zombied. And upstart won't clear it so that i can start a new process
[08:44] <marlinc> The current issue with using Launchpad is mainly that we're a small company (a few students) doing this in our spare time. We don't have huge amounts of money to spend on managed systems like that
[08:45] <BlackDex> The process is linked to init/pid 1, so i can't kill it's parent, and i prefere not to reboot
[08:45] <sivir> well then I'd start by dividing the servers in separate groups
[08:46] <sivir> and start listing what each group has to do and what are critical to which functions for each one
[08:46] <sivir> makes it way easier to plan so you can create different timetables and routines what to update and when
[08:48] <hallyn_> smb: obviously :) (not a merge)
[08:48] <hallyn_> gnight
[08:48] <smb> hallyn_, :) night
[08:49] <marlinc> Okay sivir, I'll look into doing that. Thoughts on doing automated updates for only security updates?
[08:49] <marlinc> Our monitoring system will still notify about any regular updates which we can do manually
[08:50] <sivir> yes, if it's maintained it's all good
[08:50] <sivir> sometimes people leave the automated updates for only security updates but other software gets unattended
[08:57] <lordievader> Good morning.
[08:58] <Siilwyn__> Good morning
[09:00] <Siilwyn__> sarnold, I guess I just found out what happened yesterday, though I have no idea why it behaves like that. Just tried to ssh with my old key and I got a prompt to unlock the new key... So apparently even if I explicitly pass the old one it uses the new one.
[09:01] <Siilwyn__> *with unlock I mean that I have to enter a password since my keys are also password protected.
[09:22] <Walex2> Siilwyn__: depends on the order in which they are listed I think. SSH client will try all keys it has available until it finds one accepted by the SSH server, and will reuse the encryption password if it can
[09:37] <Siilwyn__> Walex2, oh wow I didn't know that! That explains what was happening yesterday.
[09:37] <Siilwyn__> It even does that when I pass a key with the `i` flag?
[15:18] <skylite> is it possible to stop a shellscript with start-stop daemon? I can start it fine but when trying to stop it says: No myscript.sh found running; none killed.
[15:48] <jelly-home> skylite: sure.  It's probably easier if your script creates a pid file.
[16:48] <linuxlove> hello
[16:49] <linuxlove> i am going to install EHCP  on my ubuntu server
[16:50] <linuxlove> my friend use this panel for accessing to server how can i determine a username and password for him on this panel?
[17:02] <pmatulis> linuxlove: i don't see any panel
[17:18] <nacc> rbasak: so, we've updated twig (in xenial) to 1.23.1-ubuntu4, which builds and passes all tests (with a short-term workaround). But it's still in excuses because there was an old binary package (php5-twig) which we no longer generate. Do I need someone to manually intervene and delete the old binary package?
[17:27] <rbasak> nacc: yes, please ask in #ubuntu-release.
[17:27] <nacc> rbasak: ok, thanks
[17:35] <nacc> rbasak: if you have a moment, i've hit a rather tricky issue with php-imagick
[17:38] <rbasak> nacc: go ahead.
[17:38] <nacc> rbasak: as one would expect, there's some dependency on imagemagick from that extension. imagemagick has some "known" issues with openmp & threads. In particular segfaults (per google, not per imagemagick themselves). At some point Debian started experiencing test segfaults (https://ci.debian.net/packages/p/php-imagick/unstable/amd64/ between 12/17 and 12/21). We see those on Ubuntu too with the latest
[17:38] <nacc>  builds. To test, I rebuilt imagemagick without openmp support and the tests stop segfaulting. There is an environment variable for imagemagick to only use one thread (MAGICK_THREAD_LIMIT=1), but it seems to not help and I still see threads in the test (and one of the threads is the one that is segfaulting). So far, the only "workaround" I've found is disabling openmp in imagemagick.
[17:40] <nacc> rbasak: i'm going to see if maybe the latest imagemagick fixes anything (but need to rebuild php-imagick against it). In which case maybe it's a matter of backporting
[17:42] <nacc> but as I was explaining to jgrimm the other day, backporting with imagemagick is a "bad idea" -- there is an exported version string in the imagemagick headers, which php-imagick uses for various version checks (functionality existing or not, etc.) But when we/Debian backport, we don't bump the version, so it loses its meaning.
[17:42] <rbasak> Backporting what exactly? A bugfix for the segfault, or more stuff?
[17:43] <rbasak> How reproducible are the segfaults in Ubuntu?
[17:43] <nacc> 100%
[17:43] <nacc> :/
[17:43] <nacc> but only in the tests
[17:43] <nacc> which is where it matters, of course
[17:43] <nacc> and 100% reproducible in Debian, for that matter
[17:43] <nacc> gdb is useless, sadly (doesn't show the segfault)
[17:43] <nacc> and valgrind just points to a trashed address
[17:43] <nacc> in theory, it'd be backporting just the fix, but that presumes I can find the fix :)
[17:44] <nacc> my concern is, though, what that in turn breaks
[17:44] <rbasak> How sure are you that the bug is in imagemagick and not in the PHP bits?
[17:44] <nacc> i (and the upstream php-imagick maintainer) are fairly sure it's not in php -- the stack isn't deep enough :)
[17:45] <nacc> and like i mentioned, disabling just imagemagick's openmp support makes it work
[17:45] <rbasak> How long have you spent on this so far?
[17:45] <nacc> rbasak: far too long :/
[17:46] <rbasak> :-/
[17:46] <nacc> rbasak: but it's what's holding up php7.0 migration
[17:46] <nacc> in excuses
[17:46] <nacc> because php-imagick is failing its tests
[17:46] <nacc> and that's considerd a regression
[17:46] <rbasak> Would it be difficult to do a bisection if it is fixed upstream?
[17:46] <nacc> since the old version (which had far fewer tests) passed
[17:46] <nacc> rbasak: of imagemagick? probably not, as it's in git. That's what I'm hoping I can get to next
[17:46] <nacc> rbasak: but if it's a race, i have to run the tests a few times to see it happen
[17:46] <rbasak> How far behind is our packaging of imagemagick?
[17:47] <rbasak> (behind upstream's latest release that is)
[17:47] <rbasak> Sorry, many questions :)
[17:48] <rbasak> I think that ideally we'd find the cause and fix it. Failing that, if it's not fixed upstream, then file a bug there, and file a bug in Ubuntu regardless with instructions on how to reproduce.
[17:48] <nacc> 6.8.9.9-7ubuntu1 is what we have in xenial; debian exp is at 6.9.2.10+dfsg-2; upstream is 6.9.3-6
[17:48] <rbasak> If we really can't fix it, I think it might be reasonable to build imagemagick in the archive with threading disabled.
[17:48] <nacc> rbasak: oh, the other issue in all of this, the upstream php-imagick maintainer doesn't think we are doing the right thing in debian/ubuntu and doesnt' support us in any way :)
[17:48] <nacc> so he's helping for now out of his generosity
[17:48] <rbasak> What does he think we should be doing instead?
[17:49] <nacc> rbasak: we should never be backporting
[17:49] <nacc> rbasak: as it breaks assumptions
[17:49] <nacc> and means you can't reliably know what is in a version of imagemagick, across all bases
[17:49] <rbasak> In what way are we backporting? He means we shouldn't be backporting a bugfix?
[17:49] <nacc> rbasak: yeah, so we are on 6.8.9 base with patches
[17:49] <nacc> well, we/debian
[17:49] <nacc> when we/debian patch, we just backport the fix
[17:49] <nacc> we don't bump th eversion string
[17:50] <nacc> so if some code in, say, php-imagick is conditional on the version to do one thing or another
[17:50] <nacc> it stops doing the expected thing, potentially
[17:50] <rbasak> I see. Well, that's what all distros must do after feature freeze, unless he maintains a stable (no features) branch of the version we have at feature freeze time.
[17:50] <nacc> rbasak: we could alter the version string; or we should alter php-imagick in coordination
[17:50] <nacc> rbasak: in that the API dependencies are being forcibly chagned by the backports
[17:50] <rbasak> php-imagick should not be doing anything conditional based on bugfixes.
[17:51] <nacc> so let's say imagemagick X has an API that looks one way, or behaves one way
[17:51] <nacc> and imagemagick Y does it differently
[17:51] <nacc> php-imagick checks for X vs. Y and does the right thing
[17:51] <nacc> it sort of has to
[17:51] <rbasak> That's fine, assuming that X and Y are different feature releases.
[17:51] <nacc> but the values of X and Y don't mean the same thing in the ubuntu versions as they do upstream
[17:51] <nacc> and that's what's broken
[17:52] <rbasak> Debian is backporting features?
[17:52] <nacc> fixes
[17:52] <rbasak> (or feature changes?)
[17:52] <nacc> which might change functionality, in some sense?
[17:52] <nacc> i may not be explaining this very well
[17:52] <rbasak> I think I follow.
[17:53] <rbasak> If distros patch, it's their responsibility to get it right.
[17:53] <nacc> basically, php-imagick (from git) is *only* supported on upstream imagemagick
[17:53] <nacc> so once we patch one or the other, we have to patch them both :)
[17:53] <rbasak> But we also have the power to fix php-imagick, or express versioned dependencies on imagemagick.
[17:53] <Aleksandar86> How can i set default root on ftpd, i have apache installed and I wanna upload file via ftp on /var/www/
[17:53] <Aleksandar86> ?
[17:54] <rbasak> Ideally, distros wouldn't have to patch, because upstreams would maintain stable branches.
[17:54] <nacc> rbasak: yeah, the issue is I don't know what to fix and where yet :) and it means we carry more delta (which is appropriate in this case) -- but this is really broken on debian and we're just inheriting it
[17:54] <rbasak> If they're not maintaining stable branches, then we have no choice _but_ to patch.
[17:54] <nacc> rbasak: right
[17:54] <nacc> rbasak: i'm not saying we shouldn't backport fixes
[17:54] <nacc> rbasak: i'm saying that in this case, it breaks assumptoisn in the code
[17:55] <rbasak> You think these assumptions are causing segfaults? Or unrelated behavioural changes?
[17:55] <rbasak> I need to run in five minutes.
[17:55] <nacc> i'm not 100%. I think they could be leading to segfaults (and note that I found an actual bug in the debian backport that was missing 3 upstream commits ... so not sure how much i trust the backports to begin with at this point :(
[17:56] <nacc> but it also just puts us in this gray area that is harder to figure out :)
[17:56] <nacc> i might try to just build imagemagick from source at the latest git and see if it goes away
[17:56] <nacc> and then that might be my best indicator of where the issue is
[17:56] <rbasak> That's a good idea.
[17:56] <nacc> ok, i'll do that next, just to levelset
[17:57] <nacc> rbasak: really, the issue isn't so much all this background, it's that the error is nonsensical :) and i don't know how to debug it at this point
[17:57] <rbasak> If it does go away, then try bisecting if it's not too much effort.
[17:57] <nacc> yep
[17:57] <rbasak> Let me know how it goes!
[17:57] <nacc> rbasak: thanks
[18:16] <linuxlove>             Errors were encountered while processing:
[18:16] <linuxlove>  nginx-core
[18:16] <linuxlove>  nginx
[18:16] <linuxlove> E: Sub-process /usr/bin/dpkg returned an error code (1)
[18:17] <linuxlove> i get this error from sudo apt-get autoremove what should i do?
[18:24] <linuxlove> i get this error W: Failed to fetch cdrom://Ubuntu 15.10 _Wily Werewolf_ - Release amd64 (20151021)/dists/wily/main/binary-amd64/Packages  Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs after updating what shou;d i do?
[18:25] <nacc> linuxlove: for the first one, i'd try a `apt-get -f install` to let dpkg get to a good state
[18:25] <nacc> not sure how/why you got to that state, with what you pasted, though (and please use pastebin rather than in the channel)O
[18:25] <nacc> linuxlove: for the second, why is there a cdrom line in your apt config? did you try to add it back after installing?
[18:26] <linuxlove> nacc, i just tried to install ehcp on my ubuntu and i get this errors after apt-get update
[18:27] <linuxlove> nacc, what should i do now?
[18:27] <nacc> linuxlove: i don't know what ehcp is and i don't see it in the ubuntu archives
[18:28] <linuxlove> nacc, http://pastebin.com/8pKY43Sq
[18:28] <linuxlove> nacc, i tried to install that from a external source
[18:28] <nacc> linuxlove: we can't help you with random external sources, sorry
[18:29] <linuxlove> it was from ubuntu comunity
[18:29] <linuxlove> please help me to fix
[18:29] <nacc> linuxlove: as to the apt config, it seems like your /etc/apt/sources.list or a file under sources.list.d references the cdrom, comment them out, presuming you're on the network and have well-defined sources
[18:29] <nacc> linuxlove: i don't know what that means
[18:29] <nacc> "from ubuntu community"?
[18:30] <linuxlove> did you see nacc yes
[18:30] <nacc> linuxlove: did i see what?
[18:30] <nacc> linuxlove: what do you mean "from ubuntu community"
[18:32] <linuxlove> i said about pastbin that i sent
[18:32] <nacc> linuxlove: i've answered that already
[18:33] <nacc> linuxlove: please read above
[18:33] <linuxlove> i did what you said
[18:33] <linuxlove> but i get new error
[18:33] <linuxlove> W: Duplicate sources.list
[18:34] <nacc> that's a warning not an error (hence W: prefix)
[18:34] <nacc> and it's pretty clear
[18:34] <nacc> you have two entries in sources.list that are identical
[18:34] <linuxlove> nacc, http://pastebin.com/4VaxbFQ1
[18:35] <nacc> linuxlove: yes?
[18:35] <nacc> linuxlove: read it, think about what it says and fix it ... remove the duplicate line
[18:35] <linuxlove> do i remove i386?
[18:36] <nacc> what?
[18:36] <linuxlove> var/lib/apt/lists/archive.canonical.com_ubuntu_dists_wily_partner_binary-i386_Packages)
[18:36] <nacc> linuxlove: can you pastebin your source.list file?
[18:36] <linuxlove> i am un ubuntu 64 bit
[18:37] <linuxlove> nacc, okay
[18:39] <linuxlove> nacc, http://pastebin.com/SU4brQSW
[18:41] <linuxlove> nacc, did you get it?
[18:43] <nacc> linuxlove: do you have anything under /etc/apt/sources.list.d ?
[18:43] <linuxlove> nacc, are you there
[18:44] <linuxlove> nacc, what do you mean
[18:45] <nacc> linuxlove: are there any files in /etc/apt/sources.list.d/ ?
[18:45] <genii> linuxlove: When you add external repositories, they make a file in the directory /etc/apt/sources.list.d/
[18:45] <linuxlove> nacc, http://pastebin.com/JubnAJMb
[18:46] <nacc> linuxlove: that doesn't help, is there anything *in* sources.list.d ?
[18:46] <linuxlove> nacc, http://pastebin.com/HdTKZEUm
[18:47] <genii> linuxlove: ls /etc/apt/sources.list.d/* | pastebinit
[18:47] <linuxlove> genii, http://pastebin.com/HdTKZEUm
[18:47] <nacc> linuxlove: the duplicate messages are what you get when you run apt-get update?
[18:48] <linuxlove> nacc, yes
[18:49] <nacc> grep partner /etc/apt/sources.list.d/* ? not sure i see the duplicate otherwise
[18:49] <linuxlove> what should i do?
[18:51] <nacc> `grep partner /etc/apt/sources.list.d/*`
[18:51] <nacc> in any case, it's just a warning, it doesn't mean anything is fundamentally broken
[18:52] <linuxlove> nacc, http://pastebin.com/BFgKPwDr
[18:53] <nacc> linuxlove: and there are the duplicates
[18:53] <nacc> see how your sources.list and skype.list have the same lines?
[18:55] <linuxlove> i dunno
[18:56] <linuxlove> i am confused
[18:56] <linuxlove> please help to fix
[18:56] <linuxlove> i have not installed skype
[18:57] <linuxlove> my apt-get update was working without warning before installing ehcp
[18:57] <nacc> linuxlove: you clearly added skype as a repository
[18:57] <linuxlove> yes
[18:57] <nacc> linuxlove: did you append the partner repositories in sources.list as part of that process?
[18:57] <linuxlove> i added it
[18:57] <linuxlove> no
[18:58] <linuxlove> it was a ./install.sh script
[18:58] <linuxlove> and it did everything itself
[18:59] <linuxlove> what is solution now?
[19:00] <linuxlove> i installed skype but i removed it
[19:00] <linuxlove> because it was hang on my 64 bit ubuntu
[19:00] <nacc> linuxlove: so .... "i have not installed skype" wasn't true. And you added a duplicate entry to sources.list and are wondering why apt complains about duplicate entries?
[19:00] <linuxlove> yes
[19:00] <nacc> and an 'install.sh' script means you've altered your system to not be ubuntu any longer
[19:01] <linuxlove> i meant i have not skype now
[19:02] <linuxlove> i was wrong about external source installation
[19:02] <nacc> linuxlove: you shouldn't do stuff as root if you don't know what they are doing. and you don't seem to understand the package management side of things in this case. if you do not need skype, you could delete / rename the skype repositories and it should stop complaining.
[19:03] <linuxlove> yes you are right
[19:07] <linuxlove> nacc, excuse me for getting time
[19:08] <linuxlove> What server control panels are available for Ubuntu Server?
[19:08] <linuxlove> i want one
[19:08] <teward> define "server control panels"
[19:08] <linuxlove> i dont want external sources
[19:09] <linuxlove> teward, what do you mean?
[19:09] <teward> linuxlove: what do you mean by "server control panels"?
[19:09] <linuxlove> i mean one with sudo apt-get install
[19:09] <teward> what do you expect it to do?  What do you expect to see? etc.
[19:10] <linuxlove> teward, i want some controling on server
[19:11] <linuxlove> teward, my friend needs to access to my ubuntu server from him phone and he want accessing to web contents and phpmyadmin
[19:11] <linuxlove> i found one named ehcp
[19:11] <sarnold> linuxlove: skip those; they're universally terrible, they're reponsible for something like 50% of the reason why machines get hacked, and they prevent you from learning how to do things yourself
[19:11] <teward> i agree with sarnold
[19:11] <linuxlove> i said to my friend this
[19:12] <teward> sarnold: btw, i have something to poke you on, unless you tell me I should got to -hardened and poke there, for an old php5-fpm bug in Precise
[19:12] <teward> (one I poked a patch onto, but wanted Sec Team review first)
[19:12] <linuxlove> but he is not familiar with ssh and terminal commands
[19:12] <sarnold> teward: hmm got a bugnumber handy?
[19:12] <teward> sarnold: standby
[19:12] <nacc> teward: we were just talking about that bug on today's triage :)
[19:13] <teward> nacc: heheh
[19:13] <teward> nacc: you mean 1352617 ?
[19:13] <linuxlove> he wants a panel but you are right
[19:13] <nacc> teward: yep
[19:13] <linuxlove> i said to him that i cant provide a panel for him
[19:13] <nacc> rbasak decided you had a handle on it :)
[19:13] <teward> sarnold: 1352617 is the bug in question, the patch I wrote back then would 'work' but i wanted sec team review before, in case it introduces poor changes
[19:13] <teward> nacc: "had a handle on it" as in "wanted sec team review"
[19:13] <teward> now I get to actually req. it :)
[19:14] <nacc> teward: yeah :)
[19:14] <teward> nacc: the big problem being a sec update was the cause of that regression, though I need to test it now
[19:14] <nacc> yep
[19:14] <teward> make sure it still exists
[19:14] <nacc> teward: Son_Goku may be able/willing to help test too
[19:14] <teward> nacc: oh good, 'cause i don't have a Precise machine to test with until i rebuild that VM on my hypervisor xD
[19:15] <nacc> teward: not sure if they do either, but wouldn't hurt to ask
[19:15] <teward> indeed
[19:15] <nacc> linuxlove: sorry, i don't think we want to help you make your computer less secure. I still don't fully understand what you mean by "panel" but it's quite clear that ehcp is not something pacakged by ubuntu and thus would not be supported here.
[19:16] <nacc> linuxlove: finding random things on the internet and installing them is not a good idea
[19:16] <sarnold> teward: oh man I rememer this from ages ago :) heh
[19:16] <teward> sarnold: i wasn't kidding about 'old" either :)
[19:16] <teward> came up during a recent php7.0 discussion in -devel :)
[19:17] <sarnold> :)
[19:18] <teward> sarnold: basically, i wanted the sec team to review the approach and determine if that was acceptable as a response to the regression.  at the time i never looked into how the security update related to it was ever "fixed" to fix the regression of "too tight permissions"
[19:19] <teward> nacc: it did drop off my radar since I updated everything to Trusty+ shortly after that
[19:19] <teward> unfortunately
[19:19] <teward> now it's on it with php7 and such on the radars
[19:20] <nacc> yep
[19:20] <sarnold> honestly if it affects -only- precise it's probably not worth spending time on. we wouldn't want to issue an update that might break installed systems that are only one year away from retirement :)
[19:20] <sarnold> what's the deal with php7?
[19:21] <teward> sarnold: php7.0 i thin was going to get a MIR?  nacc might know more than I
[19:21]  * teward only tracks it in-so-much-that nginx defaults point to php-fpm locations in the default configs' comments
[19:21] <sarnold> I think php7 is just going in without review on the condition that php5 come out :) heh
[19:23] <nacc> sarnold: it's migrated to main, now, we're help up in excuses due to imagemagick
[19:23] <nacc> i hope to have that fixed today
[19:23] <nacc> and then we need to proceed with rebuilding th eworld :)
[19:23] <sarnold> nacc: oh congratulations :)
[19:24] <sarnold> nacc: they threw you right into the deep end when you joined, hehe
[19:24] <nacc> yeah, it's been a bit hairy :)
[19:24] <nacc> learning a lot (too much, sometimes? :)
[19:24] <linuxlove> nacc, you are right
[19:24] <linuxlove> it was my friend suggestion
[19:25] <linuxlove> i say that i cant do this for him
[19:46] <teward> sarnold: with regards to precise, it *did* affect trusty and others
[19:46] <teward> Security team overlooked
[19:46] <teward> sarnold: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1334337 was the one where it was fixed Saucy, Trusty, Utopic +
[19:46] <teward> and Marc handled htat one
[19:46] <teward> the regression was never addressed in Precise
[19:46] <teward> i hear you that it might not be worth the time spent on it
[19:46] <teward> but, it was fixed by the Sec team in later ones
[19:46] <teward> and Precise was never looked at
[19:46] <sarnold> teward: ahhh
[19:46] <teward> (at the time I had precise servers)
[19:47] <teward> not why the bug dropped off my radar, but why i'm poking now
[19:47] <teward> if it were a month to PRecise going EOL i'd not care
[19:47] <teward> but that's not the case, so...
[19:47] <teward> no idea who still uses Precise *shrugs*
[19:48]  * teward tasks his "sbuilder" VM on his hypervisor to build all the tools necessary for sbuild and schroots
[19:48] <sarnold> teward: i'll kick it along to marc; we're feeling more than a bit overwhelmed lately so I can't promise anything but he doesn't like breaking old releases :)
[19:50] <teward> indeed
[19:50] <teward> sarnold: thanks, i don't expect any heavy movement
[19:50] <teward> but that's an old regression
[19:52] <teward> sarnold: i'm not sure if subsequent updates addressed or not though
[19:52] <teward> i was going to test
[19:52]  * teward is downlading the latest 12.04 server ISO now to his hypervisor
[20:01] <sarnold> teward: are you sure this is an issue? in a blank precise vm, apt-get install php5-fpm, sudo lsof | grep www | grep -v REG -> http://paste.ubuntu.com/15276027/
[20:05] <teward> sarnold: as i said, when i filed it it was an issue
[20:05] <teward> it may be resolved since then
[20:05] <teward> hence my needing a blank Precise to test
[20:05]  * teward doesn't keep one around
[20:05] <teward> ah, wait
[20:05] <teward> right, i have a non-standard setup
[20:05] <teward> sarnold: there were documents around the time which configured FPM to use a UNIX socket
[20:05] <teward> the issue exists when FPM is configured to use a UNIX socket
[20:06] <teward> so, still a regression, but not a regression of the defaults
[20:06] <teward> (yet)
[20:06] <teward> SINCE Precise, it was a big one since in Debian they switched FPM to unix sockets by default
[20:08] <sarnold> teward: aha, that makes more sense
[20:49] <patdk-lap> heh, any idea how I can troubleshoot shutdown?
[20:49] <patdk-lap> so far I just get kicked off the network and console, so I cannot see what is stuck
[20:53] <coreycb> beisner, when you get a chance, 1:5.0.2-0ubuntu1~cloud0 and 2:7.0.3-0ubuntu1~cloud0 are ready to promote to trusty-liberty-updates
[20:54] <coreycb> beisner, and 1:2014.1.5-0ubuntu3~cloud0 is ready to promote to precise-icehouse-updates
[20:57] <beisner> coreycb, ceilometer + neutron for liberty;  neutron for icehouse?
[20:57] <coreycb> beisner, yep
[21:01] <EmilienM> coreycb: just tested ceilometer and aodh, alarms do not work for me (mitaka)
[21:04] <beisner> coreycb, ok, pushed neutron+ceilometer proposed-->updates for liberty, and neutron proposed-->updates for icehouse
[21:06] <coreycb> beisner, thanks
[21:07] <coreycb> EmilienM, ok if you have a bug please point me to it and we'll look into it
[21:10] <rattking> Hello, where can I find the logs for tftpd? i am not seeing anythign in the usual places like syslog
[21:13] <rattking> I am trying to debug a pxe boot problem. its getting a dhcp addr but not connecting to the tftp server on the same machine
[21:16] <EmilienM> coreycb: so the tests failures: http://logs.openstack.org/02/288102/1/check/gate-puppet-openstack-integration-scenario001-tempest-dsvm-trusty/9fdafe4/console.html#_2016-03-03_20_46_38_634
[21:17] <EmilienM> all logs/config are here: http://logs.openstack.org/02/288102/1/check/gate-puppet-openstack-integration-scenario001-tempest-dsvm-trusty/9fdafe4/logs/
[21:19] <avid_fan> rattking: You could try to start the tftpd daemon manually and not fork into the background for more clues.
[21:33] <rattking> avid_fan good idea! I figured it out.. firewall, its always the firewall :) but now who changed it
[21:34] <Aleksandar86> I want migrate website with mysql from old Ubuntu 7 to new ubuntu-14.04.4 server. I had Installed, latest apache mysql with phpmyadmin and proFTPD. With PhpMyAdmin I Imported backuped mysql on new Ubuntu, i copy files to new root apach dir....
[21:34] <Aleksandar86> i need small help
[21:35] <Aleksandar86> I don't understund how DOMAIN work... My old Ubuntu server had folder of domain name /var/www/www.domain.com
[21:35] <Aleksandar86> but my new have /var/www/
[21:36] <Aleksandar86> with local IP I can open website on new server
[21:37] <patdk-lap> got my team interface fixed up
[21:37] <Aleksandar86> if i have domain www.domain.co.uk, i must have /var/www/www.domain.co.uk    ????
[21:38] <Aleksandar86> on apach my default root is /var/www/
[21:38] <Aleksandar86> please help me
[21:39] <avid_fan> rattking: Ha! It wasn't me.
[21:40] <mahmoh> hi, I'm seeing a hang with upstart, I tried init=/sbin/init --verbose on the kernel command line with 14.04 to get additional info but that's not working, any ideas?
[22:10] <Executioner> hi
[22:11] <Executioner> I can't seem to be able to install htop-2.0 and apache-2.5 with apt-get, it can't find it within the repositories. Aren't they released now?
[22:13] <nacc> rbasak: sigh, thanks for your help, it does appear imagemagick 6.9.3 fixes the segfault. will see if i can find & backport the fix easily
[22:31] <nacc> rbasak: only 10 bisection steps, so hopefully won't be too bad
[22:33] <patdk-lap> Executioner, 2.5 doesn't exist, so, unlikely to happen