[00:00] <teward> is there an easy way to let my user run `sudo service bind9 restart` or `sudo service bind9 *` without having to enter my password?
[00:00] <teward> (where the * indicates any directive that would be passed to the init scripts)
[00:01] <teward> init.d scripts*
[00:22] <RoyK> teward: visudo - add NOPASSWD for those commands you don't want to enter a password
[00:22] <teward> RoyK: including the arguments?
[00:22] <teward> (such as the arguments given to 'service')
[00:29] <RoyK> teward: see the manual
[01:11] <repozitor> i have successfully setup mail server, by this tutorial
[01:11] <repozitor> https://help.ubuntu.com/lts/serverguide/postfix.html
[01:11] <repozitor> now i don't know how to login to mail account, using thunderbird!!!!
[01:11] <repozitor> any idea?
[01:24] <AvatarA> if you want to also send mail from that server your difficulties have only just begun
[01:24] <repozitor> AvatarA, so is there exist any tutorial?
[01:25] <AvatarA> very few good ones but you need to understand what is happening if you want to be able to tweak and fix things
[01:26] <repozitor> AvatarA, just show me a proper url, please.
[01:28] <AvatarA> https://scaron.info/blog/debian-mail-postfix-dovecot.html
[01:28] <AvatarA> also see the follow up on SPF and DKIM if you want to send mail without it ending up filtered in spam or just refused
[01:29] <AvatarA> also search google for PTR records
[01:29] <repozitor> i know how to setup ptr
[01:40] <patdk-lap> do you have a /24?
[01:40] <patdk-lap> if not, ask your isp
[05:50] <caliculk> Hello, I seem to be having issues with a Ubuntu Server 14.04 LTS instance. It seems to randomly shut off, there is no reason being as to why in syslog. I have ran memtest, fsck, and spinrite on the primary drives.
[05:50] <caliculk> I would really appreciate any help in trying to narrow down the problem. The most recent thing I did before it seemed to crash was to delete an ipset rule and then run a script to update it with the latest IPs, but I have done that before and it doesn't crash, so I don't think that was the contributing factor to the machine crashing.
[09:44] <rbasak> teward: sounds perfectly reasonable.
[09:49] <Raj009> Hi! How can I check the encryption method used for a partition? Basically I want to know if a passphrase is used or random key is used for encryption.
[09:58] <TJ-> Raj009: if a random key is used that implies the encrypted partition won't be accessible after a reboot
[09:59] <Raj009> I intended to use random key for my swap. But not sure which partition I chose - whether root or swap.
[10:00] <Raj009> So can I assume that if I had used random key on root, I wouldn't be able to boot at all?
[10:00] <TJ-> Raj009: did you do the encrpytion config manaully or via the installer? if it was automated the config will be in /etc/crypttab
[10:00] <Raj009> it was done via the installer, but I did not use the guided paritioning - instead I chose the manual parititioning
[10:01] <TJ-> cryptswap usually uses /dev/random to generate a one-time key, and that would be in the 'key-file' column of /etc/crypttab
[10:09] <Raj009> thanks @TJ.. I will check this file.
[10:13] <jamespage> coreycb, https://bugs.launchpad.net/ubuntu/+source/ceilometer/+bug/1515409
[10:37] <jamespage> coreycb, we probably need to consider how we deal with that - both ceilometerclient and neutronclient have minor version bumped on stable/kilo branches; the problem is that all of our stock testing passes just fine - until someone touches an edge case like that we don't see this type of problem.
[12:58] <coreycb> jamespage, great
[12:59] <coreycb> jamespage, I'm not sure what we can do other than picking up new releases
[12:59] <coreycb> jamespage, I suppose we might be able to get away with patching requirements.txt
[13:15] <pmatulis> morning
[15:59] <ayr-ton> If I use bind9 geo dns features, placing different IPs for each region, users around the globe will ask records from my DNS servers everytime? Or the DNS servers around the globe would cache this information according to my lease time?
[16:04] <patdk-wk> cache
[16:05] <patdk-wk> why would dns servers not process dns traffic correctly?
[16:05] <patdk-wk> though, you should perfer the infomation to be cached, unless your attempt to do some kind of failover usage
[16:06] <patdk-wk> and the geo dns feature does not work very well
[16:06] <patdk-wk> it only works if the user and the dns server they are using, are closely located
[16:10] <ayr-ton> patdk-wk: Do you have some documentation for this? About this behaviour?
[16:10] <ayr-ton> showing that doesn't work well if the dns server are not close?
[16:10] <ayr-ton> Or why the feature doesn't work very well?
[16:18] <patdk-wk> heh? documentation?
[16:18] <patdk-wk> what more documentation about this behavure do you need than the dns rfc from like 30 years ago
[16:19] <patdk-wk> your dns server ONLY sees the location of the requesting dns server
[16:19] <patdk-wk> you have no idea where the client is
[16:19] <patdk-wk> how can you possibly geoip a client correctly, assuming your geoip tables are accurate if you have no idea where it is?
[16:19] <patdk-wk> you can assume the client and the dns server it is using is close, but there is no way to know
[16:20] <patdk-wk> if this worked, and worked well, no one would bother attempting to do anycasted services
[16:20] <patdk-wk> anycasted dns will work better then geoip dns, but still have some of the issues
[16:20] <patdk-wk> if you attempting to route traffic
[18:46] <hallyn> smb`: bug 1465935, there isn't a testcase (no sru justification at all) in description?
[19:15] <hallyn> arges: d'oh!  i am so far behind.  I didn't realize you had already merged libvirt from unstable in wily!
[19:15] <hallyn> i assume zul wasn't as ignorant as i..
[19:15] <hallyn> so i will not do a upstream merge, that would be a step backwrad.
[19:15] <hallyn> thanks for that!
[19:26] <arges> hallyn: yea did it for wily not x
[19:29] <hallyn> arges: ?  it says wily in changelog
[19:30] <hallyn> 1.2.16-2ubuntu2) wily;
[19:42] <arges> hallyn: sorry just agreeing with your earlier statement
[19:51] <hallyn> doh, misread
[19:52] <kgirthofer_> can I grep by color?
[19:52] <kgirthofer_> i.e. grep things that are shown in red
[19:57] <sarnold> kgirthofer_: it'll be a little difficult, there's multiple ways to express 'red' in ansi color escapes
[19:57] <kgirthofer_> ah ok
[19:57] <kgirthofer_> makes sense
[19:58] <sarnold> kgirthofer_: try this: grep "\e[31"
[19:58] <sarnold> (I stole the thing from http://misc.flogisoft.com/bash/tip_colors_and_formatting )
[20:00] <sarnold> if that doesn't work, it might be because of the <esc> encoding.. ^V<esc> should insert a raw escape into a command line, so something like grep ^V<esc>[31   ought to do it too, but that probably can't be copy-pasted, is hard to work into scripts, etc.
[21:57] <bryn__>  I keep getting permission denied everywhere on my server. From opening text files to creating a directory. How do I change to permissions so that I can access the whole project file on the server?
[22:08] <keithzg> bryn__: If it's just a specific folder, you can always go "sudo chmod -R go+rw foldername". That will change it so that all members of the owning group (hence "g") and also *all other users anyways* (that's the "o") gain ("+") read and write ("rw") permission to that folder, and all its contents recursively ("-R").
[22:09] <keithzg> Be *very careful* with this though because you're making it so that any user can write to any file in that hierarchy.
[22:09] <bryn__> Hey, thanks for the reply, can you check this: http://pastebin.com/uij4YWGa
[22:10] <keithzg> bryn__: Looks like your sudoers file is messed up. Did you try and change it at some point?
[22:10] <ikonia> I suspect it's more than the sudoers file
[22:10] <ikonia> based on what he's saying in #ubuntu
[22:10] <bryn__> Over 100 people working on this server, most likely.
[22:11] <ikonia> bryn__: talk to your systems administrator
[22:11] <keithzg> ikonia: Fair enough, not on #ubuntu right now; I'll bow out then :)
[22:11] <bryn__> I am the sysadmin
[22:11] <ikonia> there is a lot of information not being shared
[22:11] <ikonia> bryn__: impossible
[22:11] <ikonia> bryn__: hire a professional system to recover this server properly
[22:11] <bryn__> I prefer Google
[22:12] <ikonia> and thats why your server is broke
[22:12] <ikonia> and why you don't know how to change file system permissions
[22:12] <bryn__> I'm learning
[22:12] <ikonia> clearly not
[22:12] <bryn__> learning through failure
[22:12] <keithzg> Yeah frankly if you're the sysadmin of a server with over 100 users and you don't know something as basic as that, you need to hand the keys to the kingdom over to someone else until you learn a LOT more.
[22:12] <ikonia> I suspect your server will have problems that will start to grow with time as more files in /etc are parsed
[22:13] <keithzg> Play around with a VM first, with snapshots you can revert to when you screw up, if you're determined to learn by breaking things
[22:14] <bryn__> I'm trying this: http://ubuntuforums.org/showthread.php?t=1772599
[22:14] <ikonia> do not try anything else
[22:14] <ikonia> you will make things a lot worse and potentially stop 100 people
[22:14] <ikonia> contact/hire a professional sysadmin for a recovery / re-install with data transfer job
[22:15] <bryn__> I call you
[22:15] <ikonia> no
[22:16] <bryn__> it worked now, using that link
[22:16] <ikonia> as I said, based on what you've said, I suspect a lot more has been changed in /etc
[22:16] <ikonia> and your server will have more problems
[22:17] <bryn__> Perhaps
[22:17]  * keithzg figures bryn__ is just trolling at this point
[22:17] <ikonia> I also don't think you're being honest
[22:17] <bryn__> about?
[22:17] <ikonia> as gksu woudn't be on your distro or present on a server install
[22:18] <bryn__> I installed it. The permissions like good for now.
[22:18] <keithzg> ikonia: Eh, now *that* I wouldn't be so sure of. Anyone who'd hire this guy as a sysadmin---if we believe that part---may well install a desktop version of Ubuntu!
[22:18] <ikonia> he couldn't use sudo - but he managed to install gksu
[22:18] <keithzg> Yeah, I'll definitely agree things weren't adding up.
[22:19] <ikonia> the whole thing in #ubuntu was miss-direction
[22:23] <bryn__> Someone remove admin rights from Ikonia he is trolling and banning me for no reason.
[22:23] <bryn__> This is completely unfair
[22:23] <bekks> bryn__: *plonk*
[22:24] <bryn__> Im having technical issues and because im learning and new to this stuff he kicks me.
[22:24] <ikonia> I'll remove the ban on you
[22:24] <bryn__> Everyone starts somewhere buddy. What is wrong with you?
[22:25] <ikonia> I don't believe you are being honest
[22:25] <ikonia> win 7
[22:25] <ikonia> I don't have a problem with everyone starting somewhere
[22:25] <bryn__> I am being as honest as possible and you were right. I just tested sudo and it did not work, i was under the assumption i was using sudo but I did not check again.
[22:26] <ikonia> and it did not work
[22:26] <ikonia> you said a minute ago it did work
[22:26] <ikonia> funny that
[22:26] <ikonia> and you said you installed gksu using sudo
[22:26] <bryn__> I thought I had because i was able to access some files, but they were outside the "etc"
[22:26] <ikonia> how did you install gksu without sudo
[22:27] <bryn__> I thought I had, sorry.
[22:27] <ikonia> no you didn't think you had
[22:27] <ikonia> as if you type gksu and it's not there it will tell you it's not there
[22:27] <ikonia> you said you tried that ubuntu thread, install gksu - ran the command and it worked
[22:28] <ikonia> what's really going on here ?
[22:28] <bryn__> I just told you I thought i had, but you are right now that I try it it says that UI error.
[22:28] <ikonia> how did you think you had installed it
[22:28] <ikonia> what command did you use to install it ?
[22:29] <keithzg> bryn__: If you really are the sysadmin of this, to even start to fix things you'll be best off rebooting the system into recovery mode. If you aren't able to do that, then frankly you clearly don't have valid access to the machine in question...
[22:29] <bryn__> I'm in a rush and trying to solve this ASAP, i clearly missed it, and proceeded with the other stuff.
[22:29] <bryn__> I tried this: sudo apt-get install gksu
[22:29] <ikonia> bryn__: so that command would have errored
[22:29] <ikonia> so thats problem one
[22:30] <ikonia> the second command you run to launch gksu
[22:30] <ikonia> "gksu" would have complained that the command wasn't there
[22:30] <ikonia> so how did you tell me you had installed gksu, ran the command in the forum post and it had worked
[22:30] <ikonia> when a.) it's clear gksu did not install b.) it's clear gksu did not work as it wasn't installed
[22:31] <ikonia> I strongly suggest you hire someone to get your system in a production state, then take some lessons on the basics of learning linux,
[22:31] <bryn__> The only option is a server reset, yeah?
[22:32] <ikonia> I'll leave you to your own work as I'm not comfortable that you are telling the truth
[22:32] <bryn__> Could you unban me from the Ubuntu please
[22:32] <ikonia> you are
[22:32] <ikonia> although I'd suggest you keep it in this channel
[22:32] <ikonia> as this is the channel for server discussion
[22:33] <bryn__> Thanks, yeah - I will. Thanks for your feedback also, but a little harsh on that previous ban.
[22:33] <ikonia> possibly
[22:33] <ikonia> but as I said, I don't believe you are being honest
[22:33] <bekks> I guess the /etc/sudoers not being owned by UID 0 is a clear sign of a totally broken system.
[22:34] <bryn__> I believe it is
[22:34] <bryn__> I will my a** kicked tomorrow
[22:34] <sarnold> hint: _always_ use visudo when you're modifying the /etc/sudoers file. infact forget the name entirely, pretend the only way to work with the file is via visudo.
[22:35] <bekks> bryn__: Soyou messed up the server like that?
[22:35] <bryn__> I tried changing permissions for a directory and ended up getting UID 0 error.
[22:36] <bekks> So what was the command you issued?
[22:36] <bryn__> sudo chown -R jesus: /var/www
[22:36] <bekks> That command will not touch /etc/sudoers
[22:37] <bryn__> Yeah that, and other that touched the whole server directory
[22:37] <bekks> Which other command?
[22:38] <bryn__> Don't remember exactly, but sudo chown -R jesus: /jesus
[22:38] <bekks> That command will not touch /etc/sudoers either.
[22:38] <bryn__> etc is within "jesus"
[22:38] <bekks> No.
[22:39] <bekks>  /etc/sudoers is clearly outside of /jesus
[22:39] <sarnold> did you symlink /etc to someplace within /jesus???
[22:39] <ikonia> you can't symlink etc
[22:39] <ikonia> the machine won't boot
[22:39] <sarnold> or .. mistype the command sudo chown -R jesus: / jesus   perhaps?
[22:39] <sarnold> sure, but it'll keep running "fine"
[22:39] <bekks> ikonia: you could create a symlink TO /etc/sudoers in /jesus
[22:39] <ikonia> bekks: that is fair
[22:39] <bryn__> "jesus" is the root. Its the "/" where everything exists within
[22:39] <Jordan_U> bryn__: Please pastebin the output of "history | grep chown", which should tell us all of the commands you have run (at least within this particular shell session) that include "chown" in them.
[22:40] <bekks> bryn__: / is the root.
[22:40] <ikonia> jesus is not the root
[22:40] <bekks> bryn__: /jesus is a directory under /
[22:40] <bryn__> Yeah I didn't remember exact, I thought jesus was root
[22:41] <bryn__> Now I recall I did do sudo ... /
[22:41] <ikonia> your a sysadmin on a server with 100+ users and you don't know where the root file system is
[22:41] <ikonia> this is a huge concern
[22:41] <bryn__> I feel the same
[22:41] <bekks> Its quite unresponsible of his boss.
[22:41] <ikonia> I don't believe it to be honest
[22:41] <bekks> me neither.
[22:42] <bekks> And we stell got no pastebin of "history | grep chown".
[22:42] <bryn__> It isn't a "business" so its nothing to seriously worry about.
[22:42] <sarnold> ikonia: I dunno, seems about average experience level of the usual "I want to set up a minecraft server" admin :)
[22:43] <patdk-lap> I want to setup a wordpress server
[22:44] <bryn__> bekks I did history | grep chow
[22:44] <bekks> bryn__: Pastebin it.
[22:46] <bekks> bryn__: Do not pm that to me. Pastebin it and provide the URL to your pastebin.
[22:46] <bryn__> Honestly, I did the command, but can't see any list of commands used.
[22:47] <bekks> Pastebin the output.
[22:47] <bryn__> sure
[22:47] <patdk-lap> !pastebin
[22:47] <bryn__> http://pastebin.com/W2D8wueW
[22:47] <bekks> Why do we have to ask you 5 times for getting a pastebin.
[22:48] <ikonia> why is the sudo command for the install of gksu not there
[22:48] <ikonia> or the running of gksu ?
[22:48] <bekks> Because he is not honest.
[22:49] <bryn__> idk
[22:49] <bekks> I am out of this issue.
[22:49] <ikonia> you'd see the history command too
[22:49] <bryn__> It doesn't matter though, since sudo isnt installed. It wouldn't work
[22:49] <ikonia> the fact tha tthe lines jump from 109 to 121 shows it's being edited
[22:50] <ikonia> bryn__: it does matter
[22:50] <ikonia> as it's something you said you did
[22:50] <ikonia> and yet for some reason it's not logging commands
[22:50] <ikonia> just 2 commands with random numbers
[22:50] <sarnold> bryn__: sudo _is_ installed, you just broke it with something you did.
[22:51] <ikonia> bryn__: did you edit the pastebin to not show all commands ?
[22:51] <bryn__> I am very new to this. I am not sure what I am looking at in terms of commands and such with terminals.
[22:51] <bryn__> That's the exact copy paste
[22:51] <ikonia> bryn__: did you edit the pastebin ?
[22:51] <bryn__> No
[22:51] <bryn__> Why?
[22:51] <Jordan_U> ikonia: It's expected that the number as part of the history would jump. I asked them to use grep, which will filter out other commands with other numbers.
[22:52] <ikonia> so your history starts at 109, rahter than 0, misses out 110-120 and shows 121
[22:52] <ikonia> Jordan_U: idiot - I missed the grep, thank you
[22:52] <sarnold> because the two spaces in front of '121' got there _somehow_, and the easiest explanation is that you fiddled with the output..
[22:52] <bryn__> I didn't fiddle with the output nor do I have ambitions to do so
[22:52] <Jordan_U> ikonia: You're welcome.
[22:52] <ikonia> Jordan_U: my fault toally, good spot
[22:53] <bryn__> What grep?
[22:53] <bekks> the one you typed.
[22:53] <ikonia> it filters results
[22:53] <bryn__> Yeah
[22:54] <Jordan_U> Unfortunately without histappend (which I think should be the default in bash, or at least some better solution) we can't be sure that all commands (even recent ones) are reflected in the history.
[22:54] <ikonia> certainly default on an ubuntu install
[22:55] <patdk-lap> not on any of my installs using ubuntu defaults
[22:55] <bryn__> I'm just going to reset the server tomorrow. But I have a question, I shoudn't get permission errors on a fresh install right?
[22:55] <ikonia> patdk-lap: got it on a 14.04 install here
[22:55] <patdk-lap> none of mine, but then I only do jeos installs
[22:55] <sarnold> bryn__: it depends what operations you're trying to perform.
[22:56] <bryn__> creating new directories in the var/www and editing etc/couchdb
[22:56] <Jordan_U> bryn__: By "reset" do you mean re-install, restore from backup, or something else?
[22:57] <bryn__> I have a snapshot
[22:57] <ikonia> how did you snapshot ?
[22:57] <bekks> Snapshot? Isnt that a physical server?
[22:57] <bryn__> Yes
[22:58] <bekks> So it is a virtual machine?
[22:58] <bryn__> I don't know
[22:58] <bekks> Then how did you snapshot?
[22:58] <thebwt> lvm snapshot?
[22:58] <bryn__> A colleague is taking care of that part
[22:58] <bryn__> So I have no clue
[22:59] <Jordan_U> bryn__: Is that colleague also taking care of restoring based on that snapshot?
[22:59] <bryn__> Yes
[22:59] <Jordan_U> Great.
[22:59] <bekks> So get your hands off that machine and leave the rest to him :)
[23:00] <bryn__> He's like me :)
[23:00] <bekks> Then hire someone who isnt.
[23:00] <bryn__> Yeah
[23:01] <bryn__> But we don't want any help from hiring people,
[23:02] <bryn__> Since its a fiddle n' diddle thing
[23:04] <bekks> So he broke the production server, and knows he'll have to tell his boss, very soon.

[23:05] <sarnold> definitely the kinds of learning mistakes best made on a personal system :)
[23:06] <ikonia> sorry but I don't believe almost any of it
[23:06] <bekks> I'm just sure he broke something :)