=== sarnold_ is now known as sarnold [00:26] i added the universe-repos to my sources.list to install swig3.0 but it still doesn't work after sudo apt-get update, what's wrong? [00:26] paste of my sources.list is following [00:26] !info swig3.0 [00:26] swig3.0 (source: swig): Generate scripting interfaces to C/C++ code. In component universe, is optional. Version 3.0.2-1ubuntu1 (utopic), package size 902 kB, installed size 4435 kB [00:26] http://pastie.org/private/otpc5oigb3dkbxpxkjbjq [00:27] thor77: can you pastebin the output of "sudo apt-get update" please. [00:28] http://pastie.org/private/rqvqycqikkoqebqka1loa [00:31] and now apt-cache search swig please [00:32] http://pastie.org/private/ph6zivoo71njrlk917oewq [00:32] only swig and swig2.0 :/ [00:32] looks like there was an error adding the universe-repo [00:32] where ? [00:33] _i_ think there was an error [00:33] ahhhh hang on [00:33] !info swig3.0 trusty [00:34] Package swig3.0 does not exist in trusty [00:34] yeah, it's not in trusty [00:34] :O [00:34] it's in utopic [00:34] what can i do now? [00:34] thats why you can't see it [00:34] sorry, missed that you where not on the current release [00:36] http://img.thor77.org/22-12-14_01-36.png its the latest available at my hoster :( [00:37] 14.04 should have it [00:37] ahh wait [00:37] no it doesn't [00:37] sorry [00:37] utopic is the first to get it [00:38] i have 14.04 installed [00:38] yeah, and it doesn't have it [00:38] yes [00:38] what can i do know? [00:38] so 14.10 is the first [00:41] the only option is begging my server-provider to provide 14.10 images? [00:42] realistically [00:42] if you want to use stable supported repos [00:42] :/ [00:43] can i download this package somewhere? [00:43] i think i only need this one [00:51] uhm, okey, i will start begging at my hoster to provide me a 14.10 image, thanks for your help ikonia :) [01:17] thor77: i could try and backport the package - it'd be in a ppa and i cant guarantee functionality but... === zz_DenBeiren is now known as DenBeiren [02:29] aloha === zz_DenBeiren is now known as DenBeiren === Lcawte is now known as Lcawte|Away === markthomas|away is now known as markthomas [03:56] rabbitmq === balloons is now known as Guest52943 === markthomas is now known as markthomas|away === Metacity is now known as Metachristmas === balloons_ is now known as balloons === balloons is now known as Guest93916 [05:43] I have a linux server with an xfs filesystem thats access by both windows clients and linux nfs clients. Does this mean that each file/directory contains both windows ACL and Linux ownership/permission information? === Metachristmas is now known as Chelsie [09:16] Good morning. [09:54] yey, begging was successfull, i got an 14.10 image \o/ === Lcawte|Away is now known as Lcawte === Nigel_ is now known as G === l2ksolkov is now known as tiggr === tiggr is now known as l2ksolkov === l2ksolkov is now known as t1gge === t1gge is now known as l2ksolkov [14:57] i've got 14.04 in read-only mode, logged in as a non-root user. im at a remote location currently. is there any hope for rebooting the machine or will i need to wait until i can physically reset the machine? (i can't switch user to root or use sudo) [15:12] esde: sudo reboot should still work [15:12] it doesn't require any write access apart from the securiy log which it should just warn on [15:14] http://pastebin.com/7znUhpJZ === shredding_ is now known as shredding === Guest12912 is now known as Locke2002 [16:19] ikonia, ^ [16:19] what ? [16:23] Hi, I am trying to create an upstart script on my remote server (on cli, no GUI). When I check the syntax using init-checkconfig I get this error: ERROR: failed to ask Upstart to check conf file [17:28] kirkland`: I have an orange box, and I'm having a small problem I hoped you could help me with. Two of the 10 nodes aren't responding to the out of band tools. one of them (node 7) powers on on AC restore, and since it doesn't respond out of band I can't power it off. [17:29] node 4 doesn't appear to be powering on (but also isn't responding to the Out of band bits) [17:29] based on LEDs on the front of the chassis. === l2ksolkov is now known as Spydur007 === Spydur007 is now known as Agent_lsai === Agent_lsai is now known as Isal === Isal is now known as l2ksolkov === swebb_ is now known as swebb [17:57] has NTP been updated for 14.04? [17:57] just saw the post about it... [18:07] MagicMystic: I just ran an update a few hours ago and got it. [18:09] Pici: let the upgrade process begin! Just updated on 2 of 4 machines :-( [18:13] Is that NTP update "security" related? [18:14] is there a bulletin someone can point me at please? [18:14] do people not bother to read? [18:15] patdk-lap: I'd be happy to read. I however don't read every page on the internet. [18:16] I guess I'll add http://www.ubuntu.com/usn/ to the list of daily pages [18:18] i don't read that's what #ubuntu-server i sfor :-P [18:20] for the most part, I pay the junior guys to read for me. ;) [18:21] looks like my nodes will all update between 23:00 and 01:00 tonight. [18:21] and firewall rules should prevent any badness between then and now. === Lcawte is now known as Lcawte|Away [18:25] so many of the issues seem theoretical...the chances of my little machines getting hit seem small [18:25] seem like someone attempting the attack would go after bigger fish [18:26] nonetheless, upgrading is a good idea [18:26] well, ubuntu sends out email alerts for all security updates [18:26] and it's posted [18:26] and well, kindof all over the place [18:27] patdk-lap: yeah...saw it first posted on ars a couple days ago or was it yesterday [18:27] ars? [18:27] I first saw it posted by MagicMystic about 30 minutes ago, above. [18:27] ars technica. [18:27] dunno, been posted all over the place, first saw it on the ntp mailing list [18:28] I can't join any more lists. they all get the same level of attention, which is filtered to another folder that hasn't been looked at in months. [18:28] same here, but attempts to read daily :) [18:28] that's what the Junior guys are for ;) [18:28] though, the unread count going up fast, is normally a given it needs to be read [18:28] or a flamewar [19:24] i forgot to check the "install openssh server"-option on installation of my ubuntu-server, how can i reproduce it after installation? [19:26] thor77: "sudo apt-get install openssh-server" [19:27] it doesn't do anythin else? [19:28] Hmm? [19:28] i think it could be it would configure smth [19:29] Thats done by installing it. [19:48] Hi, is that possible to close root user in ubuntu server, because every day i see a lot of logs hackers are trying to my server with root user and different password [19:48] iman: by default the root user doesn't have a password, and can't be accessed. [19:49] iman: you can further improve security by disabling password auth in ssh. (/etc/ssh/sshd_config) and installing/configuring something like fail2ban or denyhosts [19:49] disabling password auth would require you to use ssh keys to log in remotely [19:51] LarsN: I have another username as root and i dont use root at all, can i do "sudo passwd -l root" ? [19:52] iman: unless I'm mistaken, that's the default state of the root users's password. [19:52] user's... [19:52] iman: By default, you dont need to do that, because that would make using sudo impossible. [19:52] LarsN: You are mistaken :) The root account is not locked, but it has no password "only". :) [19:53] bekks: rgr, yeah I opened man passwd, AFTER i typed that [19:53] you verified, before I got back here. [19:54] bekks: locking the root account doesn't make sudo impossible by default, only if sudo always asks for the root user's password [19:54] the default state for user root however, is a "passwd -d" [19:54] dasjoe: Locking the root user would mean that you cant get a root environment anymore, wouldnt it? [19:55] dasjoe: So that effectively makes using sudo impossible. [19:55] bekks: the passwd -l just locks the password, not the account. [19:55] at least as I read the man page. [19:55] bekks: afaik "locking" only means setting the /etc/passwd password field to x, which disables the password but not the account [19:55] You can still log in via key files [19:55] Or by using sudo when configured to ask for the sudoing user's password [19:56] I have to test that out, for my own curiousity :) [19:56] iman: for your underlying problem of brute force attempts against ssh. the two things I'd suggest are. 1: set password login to false in sshd_config [19:56] and 2: turn on either fail2ban or denyhosts [19:56] bekks: I'm pretty sure, as somebody locked my account on a box but forgot to remove my authorized_keys file [19:56] this will help secure ALL the user's accounts against brute force. === Lcawte|Away is now known as Lcawte [23:21] hello all [23:23] I have a 14.04.1 LTS server that has a drive going bad and apparently I set it up to use LVM. I'm trying to migrate the data (fully bootable move would be nice) to a smaller drive. I've confirmed I'm nowhere near the space limit of the new drive, but since it's LVM, I'm afraid of missing something. I have already created partitions, but am kinda clueless on what to do next. [23:23] if they were the same size I would just DD it [23:46] davidbowlby: mount the old and new partitions, then rsync the data over? [23:57] anyone used kernel 3.18.1 on ubuntu server 14.04.1 lts? [23:58] http://www.yourownlinux.com/2014/12/how-to-install-linux-kernel-3-18-1-in-linux.html [23:59] i tried it but when i noticed, kern.log and syslog files grow in size