[03:46] <rbasak> rharper: could you help triage bug 1583819 please? I'm not sure about it.
[03:47] <rbasak> stgraber: do you have an opinion on the proposed fix for bug 1531184 please?
[03:49] <stgraber> rbasak: it's probably fine. Note that anyone who actually has the dnsmasq package installed on their system is likely to run into other problems, so not a big priority for us.
[03:49] <stgraber> rbasak: (dnsmasq-base is what we care about in the distro and that doesn't ship the init script)
[04:08] <rbasak> stgraber: OK, thanks
[06:24] <Milad_amire> hy
[06:24] <andreabedini> I'm having issues preseeding an installation. I have "d-i tasksel/first multiselect standard, cloud-image" in the preseed file but the tasks do not seem to get installed, suggestions?
[06:34] <andreabedini> same with "tasksel tasksel/first multiselect standard, cloud-image"
[09:34] <rightshift> Anyone got any good links on systemd service creation?
[09:34] <rightshift> I've created one that starts a process, but i'm having trouble incorporating the stop
[09:35] <hateball> rightshift: Had a look at https://wiki.ubuntu.com/SystemdForUpstartUsers ?
[09:35] <rightshift> Thanks i'll check it out
[09:42] <radish_> Hi! Does anyone know when https://people.canonical.com/~ubuntu-security/cve/2016/CVE-2016-5696.html will be fixed? I'm just wondering because neither RedHat, SuSe, nor Deboan/Ubuntu have released a patched kernel while distros like Arch and Mageia have already released an update.
[10:05] <maswan> radish_: next regular round, probably no more than a week or two
[10:10] <radish_> maswan: thanks for the information
[10:36] <venkat_330> After enabling apparmor ::  my lightdm session does not open up : operation="mknod" profile="/usr/sbin/lightdm" name="/run/lightdm.pid" .. http://pastebin.com/JQwpB6ev
[10:44] <rbasak> venkat_330: apparmor is enabled by default, so it might help to explain what you have done differently on your system. But also, a lightdm problem isn't a server question, so try asking in #ubuntu. Relatively few people will be able to help you with lightdm here.
[11:02] <rightshift> How do I echo a status for my systemd service e.g. on start it should say "service started" on stop "service stopped" etc
[11:02] <rightshift> i've got it starting and stopping, but it doesnt return any info
[11:02] <OerHeks> systemctl status name.service
[11:47] <FManTropyx> so I do "apt-get install update-manager-core"
[11:48] <FManTropyx> there is a required step that refers to karmic/lucid
[12:05] <FManTropyx> or I just run do-release-upgrade?
[12:17] <Ussat> I am having a odd issue here when installing 2 packages on 16.04. The packages are samtools and bcftools. I am building the server for a researcher here at work. The two packages are disctinctly different, have different uses, commands etc, but sem to conflict and overwrite each other. I install them via standard apt-get commands, please see http://paste.ubuntu.com/23061365/. Any advice here how to get both packages installed at the same
[12:17] <Ussat> time ?
[12:19] <ivoks> Ussat: install them at the same time?
[12:19] <Ussat> have both packages installed.
[12:19] <ivoks> so, here's what packages say:
[12:19] <ivoks> $ apt-cache show samtools
[12:20] <ivoks> all good
[12:20] <Ussat> I have looked at that
[12:20] <ivoks> $ apt-cache show bcftools
[12:20] <ivoks> Breaks: samtools (<< 1.0)
[12:20] <Ussat> Right, I know that
[12:20] <Ussat> that is the problem
[12:20] <Ussat> I need both of them
[12:21] <ivoks> well
[12:21] <ivoks> it looks to me like they do come from the same source
[12:21] <ivoks> Homepage: http://samtools.sourceforge.net
[12:21] <ivoks> Homepage: http://samtools.github.io/bcftools/
[12:22] <ivoks> i'd say samtools is an older version
[12:22] <Ussat> Yes I am aware
[12:22] <Ussat> older version of what ? they are different toolsets
[12:24] <ivoks> samtools package installs samtools, which is outdated and not maintained by the upstream
[12:24] <ivoks> (they say so on their webpage)
[12:24] <ivoks> new version of samtools, 1.x, looks like it's not packaged
[12:24] <Ussat> so youre saying the samtools functionality has been rolled into bcftools ?
[12:25] <ivoks> no, i don't know that
[12:25] <ivoks> https://github.com/samtools/
[12:25] <ivoks> it looks like samtools is now a group of multiple toolsets
[12:25] <ivoks> one of them is called samtools
[12:25] <ivoks> and one is bcftools
[12:26] <ikonia> bcftools isn't bcfg is it ?
[12:26] <ivoks> and it doesn't look like that the version of samtools (from the github) is available in the archive
[12:27] <Ussat> ok.....I see what ya saying now
[12:28] <Ussat> So....latest bcftools is there in archive but not samtools.......so my options look limited, compile up samtools (which is ... eww) but seems like only option
[12:29] <ivoks> it's not that complicated
[12:29] <ivoks> it depends just on couple of libs
[12:29] <ivoks> maybe you are lucky and it has debian/ in its source
[12:30] <ivoks> nope, it doesn't
[12:30] <Ussat> No, not complicated just hate having compiled crap on there because, keepinp updated sucks is all
[12:30] <ivoks> well
[12:31] <ivoks> then there's this thing called snappy
[12:31] <Ussat> not familiar with that
[12:31] <ivoks> http://snapcraft.io/
[12:31] <ivoks> it would allow you to compile once
[12:32] <ivoks> and then just distribute to all your machines automatically
[12:32] <ivoks> and anyone could install it, on any other distro
[12:33] <ivoks> it would require you to invest an hour or so to create your first snap, but it will pay of in the long term
[12:33] <Ussat> fortunately, its only 2 systems
[12:33] <Ussat> test and prod
[12:33] <Ussat> yea reading asbout it now, looks promising, thanks
[12:34] <ivoks> i think i might snap this, just for fun :)
[12:45] <Ussat> thanks for the help ivoks
[12:50] <FManTropyx> Cannot update compressed archives!!!
[12:54] <ivoks> Ussat: i'm building a snap of samtools right now, let me see how usable it will be
[12:55] <Ussat> ok thanks
[12:56] <ivoks> Ussat: these tools usually need access to files you have in your home directory?
[13:03] <Ussat> Well, not nessarially in home dir, but in a folder on the server, yes, the raw genetic data that the tools manipulate
[13:10] <Ussat> so I found a samtools at https://launchpad.net/~nebc/+archive/ubuntu/bio-linux/+packages?field.name_filter=samtools&field.status_filter=published&field.series_filter=
[13:10] <Ussat> opinions on that ?
[13:17] <Bert_2> Hi, since we've upgraded to 16.04 we've been having weird issues with SSH + lookup. We have a backup service that uses a keypair with authorized_keys to do rsync. We use a from entry with the domain of the backup server and this used to work just fine. But since the upgrade auth.log is mentioning that the IP does not match the from. Even though when I nslookup the IP or dig the domain in the from ent
[13:17] <Bert_2> ry they both work fine on the machine in ...
[13:17] <Bert_2> ... question. One machine that still runs 14.04 works fine and when I change the from entry to have the IP instead of hostname/domain it does work fine. Anyone know about some kind of change in 16.04's openssh or resolv system that might have triggered this?
[13:19] <maswan> well, first suggestion is to use "getent hosts" to check resolving instead of dig/nslookup/host which talks directly to dns instead of using the libc resolver
[13:22] <Ussat> ivoks, so I found a samtools at https://launchpad.net/~nebc/+archive/ubuntu/bio-linux/+packages?field.name_filter=samtools&field.status_filter=published&field.series_filter=
[13:23] <ivoks> Ussat: there you go
[13:23] <ivoks> Ussat: still an old version
[13:24] <Ussat> Yea, looks like whats installed by apt-get anyway. Sent a email asking about that
[13:24] <Ussat> seeing these rsmatools, sent a email to researcher about them, they LOOK the same to me, but I wont be the one useing them
[13:28] <Bert_2> maswan: they're not in the hosts file, if that is what you mean
[13:32] <Bert_2> maswan: and getent hosts and then the domain or IP as a lookup give the correct output
[13:37] <maswan> Bert_2: What IP does the auth logs say it connect from?
[13:37] <maswan> or hostname for that matter
[13:38] <Bert_2> maswan: it says the internal it, 192.168.0.238
[13:38] <Bert_2> which backup.intern.ulyssis.org resolves to
[13:38] <Bert_2> and also reverses to
[13:38] <Bert_2> which is all correct
[13:39] <Bert_2> but it seems from auth.log that ssh isn't converting or something
[13:53] <smoser> hallyn, fyi, https://github.com/willsALMANJ/pentadactyl-signed is now providing signed pentadactyl builds
[13:54] <smoser> seems working for me, and seems also to mean i can use the awesome bar again... it was *really* slow in vimperator
[13:55] <rharper> rbasak: sure, I'll look at it
[13:56] <hallyn> smoser: oh, nice, i'll need to try that
[13:56] <hallyn> what is the awesomebar?
[13:56] <hallyn> what kills me invimperator is that ctrl-t to pull up editor often doesn't work
[13:57] <smoser> awesomebar == typing in the location bar (or 'o type here') and watching it complete and picking something
[13:57] <smoser> ie, its the only way i can find anything
[13:57] <smoser> ctrl-t ?
[14:08] <kgirthofer> hey all - what is the best way to dynamically block ddos ips?
[14:12] <maswan> https://www.sunet.se/blogg/showerthoughts-ddosing-an-important-social-institution-and-fixing-it-part1/ and https://www.sunet.se/blogg/showerthoughts-ddosing-an-important-social-institution-and-fixing-it-part2/ has some good ideas
[14:13] <kgirthofer> thanks
[14:14] <maswan> If you're talking about banning IPs on the host to not get through to the application, you're probably better off with a caching layer on top of the application if it is that fragile.
[14:45] <yancho> hi. i'm doing an upgrade and got this error after the restart: A start job is running for raise network interfaces (2 minutes of 5 mins 1 sec) - any idea what I can do please?
[16:18] <jgrimm> rbasak, fyi->https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1613758
[16:19] <jgrimm> rbasak, wrt to your mentioning https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1612627
[16:22] <rbasak> jgrimm: interesting, thanks.
[17:08] <yancho> anyone can offer some guidance as to why my eth0 is not getting a dhcp after I updated from 15.10 to 16.04 please? I removed auto eth0 and did dhclient -r and dhclient but to no avail.
[17:09] <sarnold> did you get error messages in dmesg? logs? on the terminal?
[17:14] <yancho> sarnold: no - no errors .. and with static ip it works
[17:24] <patdk-wk> is there a dhcp server on the network?
[17:49] <yancho> patdk-wk: yes
[20:24] <brianw> better to post here... :)
[20:24] <brianw> Can anyone help me with authenticating to AD on 16.04 Server? I followed this; https://help.ubuntu.com/lts/serverguide/sssd-ad.html . I am able to su to an AD user only from the root user. I get su: System error otherwise. I also cannot SSH to the Ubuntu server using an AD user, stating pam preauth stopped it.
[20:27] <sarnold> can you pastebin the pam errors?
[20:29] <brianw> auth.log ?
[20:30] <brianw> should I increase logging on pam and sssd ?
[20:30] <brianw> I know it authing to the ad, because I get a different error if I use a wrong PW
[20:31] <sarnold> I'd hope the standard verbosity would be useful to start with..
[20:31] <brianw> Which log?
[20:31] <brianw> syslog does not say much
[20:32] <sarnold> auth.log or perhaps journalctl -u su or _COMM=su or something? I'm still getting the hang of these journals..
[20:35] <brianw> http://paste.ubuntu.com/23062716/
[20:35] <brianw> sarnold, me too
[20:49] <sarnold> brianw: argh, sorry, nothing obvious :( good luck, time for me to run..
[20:49] <brianw> thanks
[20:50] <brianw> Forum post I guess. Or mailing list? Which is best for ubuntu server stuff?
[20:50] <brianw> I usualy use centos. The AD server is a centos samba4 server.
[20:57] <eatingthenight> hello, been a little confused by this and was hoping someone here could offer insight. when i connect my sever to my ldap server and sudo su - ldapuser i have a home directory created. However no passwd entry or shadow entry is added because it's handled through pam
[20:57] <eatingthenight> how can i create an ldap user without the extremely hacky `sudo su - ldapuser`
[20:58] <bekks> eatingthenight: just omit su.
[20:59] <bekks> eatingthenight: sudo executes a command as root.
[21:00] <eatingthenight> so you are saying run sudo - ldapuser?
[21:01] <bekks> eatingthenight: no. what are you trying to do? "sudo su - ldapuser" invokes sudo for being able to run "su - ldapuser" which actually logs in as ldapuser.
[21:01] <bekks> eatingthenight: Thats your way of solving a specific issue - which one?
[21:03] <eatingthenight> root issue is create ldapuser on the machine
[21:04] <eatingthenight> having to switch to the user and have pam magically create the user seems hacky
[21:04] <bekks> thats how it works.
[21:04] <eatingthenight> well that works then, just thought someone might have a cleaner way.
[21:04] <bekks> That IS the clean way.
[21:05] <eatingthenight> ha, alright well i feel better about it now.
[21:05] <bekks> The unclean way would be asking the ldap for all users and create all users.
[21:05] <eatingthenight> just wanted a sanity check
[21:05] <eatingthenight> thanks bekks!
[21:06] <eatingthenight> i can remove my "super hack to create ldap user comment from my ansible script now" :)