[00:01] -rwxr-xr-x 1 root root 434 Nov 7 23:41 /etc/rc.local [00:01] -rwxrw-r-- 1 urt urt 2185 Nov 7 23:14 /opt/spunky/debian-startscript.sh [00:02] aha, try chmod 775 /opt/spunky/debian-startscript.sh -- or chown root:root /opt/spunky/debian-startscript.sh -- depending upon which you would prefer [00:02] the script gotta be run as root cuz opens up a pid file in /var/run/ [00:03] ok mate lemme try [00:06] ok chmoding didn't worked, will try chowning [00:06] I thought maybe rc.local doesn't support parameters, does it ? [00:11] it should, it's just posix shell [00:11] nope, no luck neither =( [00:12] Is it any other way i coul run that script maybe at loggin time, maybe addin' a line in .bashrc ? [00:13] using systemd maybe ? [00:13] the cron service allows you to use @reboot specifiers; you could add a line like "@reboot root /opt/spunky/debian-startscript.sh start" to /etc/cron.d/spunky [00:14] Oh! thanks will try that [00:14] systemd service and unit files could also work. I found them a bit of a pain in the ass to get working, but once they work they work :) [00:15] https://www.freedesktop.org/software/systemd/man/systemd.unit.html [00:15] https://www.freedesktop.org/software/systemd/man/systemd.service.html# [00:15] https://www.freedesktop.org/software/systemd/man/systemd.exec.html# [00:16] it wasn't added, should i 'crontab -e' ? [00:16] i mean, when i: 'contab -l' can't see the job there -.- [00:17] the cronjobs in /etc/ aren't managed via the 'user' cronjobs; crontab -e and crontab -l work with the user-cronjobs instead [00:18] user root does have the standard user cronjobs too, but when it's system services, it feels like they ought to live in /etc instead [00:18] Hm! [00:19] thanks bruh! now i'll reboot to see if works :) [00:21] Oh! gosh, it didn't worked =( [00:21] dang [00:21] Maybe i'll try systemd [00:21] okay, next steps: ls -ld /opt/ /opt/spunky/ -- and head -2 /opt/spunky/debian-startscript.sh [00:22] wait a second, i just removed spunky's pid file in /var/run/ will reboot again, maybe that was the issue [00:25] curiousx: is your debian-startscript the same as https://github.com/SpunkyBot/spunkybot/blob/master/debian-startscript ? that one looks like it's designed to be used as an init.d script ... [00:26] tarpman: lemme see [00:27] in which case, the way to have it start on boot would be using update-rc.d(8) [00:27] tarpman: yeah, the same one [00:27] tarpman++ [00:28] curiousx: it's documented right there in the script how to install it [00:28] tarpman: update-rc ? lemme check [00:28] curiousx: read the comments in the script, all of that is covered, even the update-rc.d part [00:28] rly ? [00:28] ok [00:28] https://github.com/SpunkyBot/spunkybot/blob/master/debian-startscript#L13-L17 [00:29] much better than nasty crontab hacks :) [00:29] Oh! my... wth, sry, so dumb of me :D [00:30] I mean, well, i'm not a sofisticated guy no more :p but i used tobe :p [00:42] No can't do =( [00:43] idk why tho [00:51] To execute a scrip in 'bashrc' should i prefix a dot ? like: . /etc/init.d/spunkybot start ) [00:51] ?* === Amgine_ is now known as Amgine [09:52] do we still need juju-mongodb3.2 if src:mongodb is at the same version number? [09:53] Juju would need to know which package to use, AFAIK. Also, what happens when Juju's mongodb needs get bumped? As it does get updated in stable releases. [09:53] To be clear, I'm not objecting, just thinking of potential areas that need consideration. [09:55] rbasak, i have no idea how juju-mongodb* is different from mongodb* packages =) [09:55] * xnox simply has to fix boost 1.62 FTBFS twice at the moment, in both mongos [09:56] xnox: it drops in binaries only, in a special path (IIRC). Then when Juju deployds, it sets up a system service specifically for itself using those binaries. [09:58] IIRC, this was a requirement for promoting Juju to main, since the security team didn't want mongodb-at-large to be in main (due to the colossal Javascript engine maintenance burden, etc) [09:58] And at least at that time, Juju's mongodb was built without a bunch of that stuff. === Amgine_ is now known as Amgine === _degorenko|afk is now known as degorenko [10:48] what can cause kernel panic VFS ? [10:49] hypermist: are you referring to a panic due to being unable to mount root on boot? [10:50] yea cpaelzer [10:51] hypermist: (IMHO) mostly broken bootloader configs, followed by broken lvm or rootfs setup, followed by more rare and special cases [10:51] cpaelzer, its just that it was a fresh install so i was like whaat how can that be [10:51] xD [10:52] hypermist: I'd even think that this is the most likely place - on install either manual config was done wrong or the system/HW has a certain setup that leads the automations done on install into a trap creating a broken install [10:52] i'll try re-install and see if it works this time [10:52] :) [10:53] ill change some stuff in the bios and such [10:53] hypermist: ah ok, otherwise I'd assume it would just reproduce [10:55] hypermist: if running into it again I tihnk that covers the most basic solution worth for maybe 75% of the cases http://askubuntu.com/questions/532835/kernel-panic-not-syncing-vfs-unable-to-mount-root-fs-on-unknown-block0-2 [10:55] hypermist: otherwise the recovery mode you reach from there might still be the best way to start understanding what is wrong [10:56] alright thanks cpaelzer :) [10:57] Hi. Does anyone know if and when canonical is going release the patch for memcached (CVE-2016-8704 and two others)? [10:59] ronator: I tihnk that is done already [10:59] did not find any updates neitehr in 14 or 16 repos [10:59] ronator: not sure, but are these links externally reachable http://people.canonical.com/~ubuntu-security/cve/2016/CVE-2016-8704.html [11:00] ronator: https://www.ubuntu.com/usn/usn-3120-1/ [11:00] thank you gyus. btw this is what I see in Ubuntu 16: Version: memcached 1.4.25-2ubuntu1.2 [11:01] ronator: which is the latest update and has the CVE listed in the changelog [11:01] ronator: https://launchpad.net/ubuntu/+source/memcached/1.4.25-2ubuntu1.2 [11:01] ronator: glad I could help [11:01] ah i see .25 is the patched version [11:02] ronator: as it is a released version the fix will go in as SRU, so it will stay 1.4.25-2 in your case but got a .2 at the end for this update [11:02] okay, i was confused because i read version > 1.4.31 is patched but I tend to forget that canonicals folows a different numbering scheme ;-) thx again [11:02] cpaelzer: yes, I see that now [11:03] ronator: see here if you want to learn more https://wiki.ubuntu.com/StableReleaseUpdates [11:03] cpaelzer: thx - will do (have to) :) [11:08] error'd out when it was installing the kernel cpaelzer so maybe thats got something to do with it ? [11:08] hypermist: yeah that should be almost 100% related [11:09] fresh iso download too haha [11:09] :( [11:09] my life today has been so far a fail [11:10] should i just redownload ? [11:11] hypermist: the chance that this is a broken iso by the download is almost 0%, in any case just check the checksum [11:11] hypermist: more likely some sort of incompatibility/issue with your HW [11:12] its an amd apu === mehrdadv is now known as CuriousMind === CuriousMind is now known as mehrdadv [11:32] cpaelzer: "Regarding Dirty Cow": From the nice website you sent, I can find this info for fixed version: Ubuntu 16.04 LTS (Xenial Xerus): released (4.4.0-45.66) - but the newest kernel I have on ubuntu (16) server is Version: 4.4.0.45.48 - does that mean they are vulnerable? [11:33] (afk/brb/coffee) [11:33] pet peeve: there is no such thing as Ubuntu 16 [11:36] there is 16.04 and 16.10 but these are no more closely related than consecutive versions that don't share a calendar year [11:41] To answer the actual question, I can tell from the pattern of dots and dashes that you are comparing a linux-meta version with a linux version. They are different packages and the version numbers are not directly comparable [11:42] i will read SRU now :D [11:42] https://www.ubuntu.com/usn/usn-3106-1/the package names you should be looking at are the ones in the USN : https://www.ubuntu.com/usn/usn-3106-1/ [11:42] ugh, weird paste, but you get the idea [11:47] tried 16.04 also no kernel install error just wont install packages cpaelzer ;( [11:48] what does "DNE" mean in context of security cve patches? [11:50] ronator: 4.4.0-45.66 is latest and available to my machine - maybe just an apt update away? [11:50] So what can i do about that haha :( [11:51] hypermist: from the given info it is hard to recommend more [11:51] yea it's sort of like why does freebsd based OS's install fine xD [11:52] hypermist: on install issues it can be hard to share screen and logs, but often you can use the console fallback for that [11:53] i just have no idea why its failing. considering any other os i've installed has never done that haha :D [11:55] cpaelzer: I did a dist-ugrade right before, that's why I went to check with the cve page ... === JanC_ is now known as JanC [11:56] cpaelzer: what could be the reason for our difference in kernel versions? [11:56] ronator: are you behind an apt mirror that isn't updated? [11:57] (basic ubuntu 16 installation from iso, no repos removed) - no I use the usual repos, e.g. I see this OK:2 http://security.ubuntu.com/ubuntu xenial-security InRelease [11:57] and the german archive repos [11:57] ronator: https://launchpad.net/ubuntu/+source/linux/4.4.0-45.66 here you see it was published on 20th October [11:58] I do believe you [11:58] let me check this more in detail for you [11:59] cpaelzer: I am sorry, I am really confused, so I really do appreciate your help. If I do "aptitude show linux-image-generic" it show me "Version: 4.4.0.45.48". The server is located is Germany. [12:02] ronator: be careful with the various linux-* package names - I often run into that as well [12:02] ronator: what does apt-cache policy linux-image-4.4.0-45-generic tell you? [12:03] oh :) [12:03] cpaelzer: you are the man: Installed: 4.4.0-45.66 [12:04] so I it should be [12:04] bad aptitude :) [12:04] cpaelzer: I guess I learned sth. - thx [12:04] ronator: and for even more security please check out http://blog.dustinkirkland.com/2016/10/canonical-livepatch.html [12:05] yeah, I read sth that ubuntu also wants to offer kernel-live patching. thx, will read. === Ussat is now known as NoLube2016 === NoLube2016 is now known as BendOver2016 [12:59] hello guys [12:59] hi SipriusPT_ [12:59] I am in a big trouble trying do config my mail server to receive mails [13:00] i have wasted a lot of time trying to set this up but still no success [13:00] https://ubuntuforums.org/showthread.php?t=2342513 [13:00] dont know if you can help me =/ [13:00] i have created a tread in ubuntuforuns [13:01] with all the data, if you could help me and need more info i can provide without problem [13:02] P.S. is my first time trying to set a mail server [13:06] SipriusPT_: from reading tzhat a bit this is more on port forwarding and such than mail [13:06] SipriusPT_: right? [13:06] SipriusPT_: as your issue still is that you can't connect at all, not that any part of the mail setup fails [13:08] SipriusPT_: if I read that correctly you have no smtp port bound right? [13:08] SipriusPT_: e.g. no 25 [13:10] SipriusPT_: I can't parse and validate all of your config, but you should focus on getting something bound to a port serving smtp [13:10] SipriusPT_: all the forwarding and such comes later [13:10] as long as your check for e.g. port 25 or equiv shows nothing something is missing [13:11] SipriusPT_: check this for testing (as you did) but also log files https://help.ubuntu.com/lts/serverguide/postfix.html#postfix-testing [13:11] but i have my server in DMZ [13:11] i already made a ping to SMTP and IMAP ports from a outside web site [13:11] and those are all open [13:12] SipriusPT_: you reported this as empty netstat -tnlp tcp | grep '\.25 ' [13:12] so nothing can connect to ..:25 [13:12] ah yes that is from the service [13:13] ah yes [13:13] you are right i used the wrong dns name when was doing ping [13:13] with the right one i got all of them closed [13:14] just the 80 is open as expected i have a web service there [13:14] SipriusPT_: so you can reiterate locally with your mail server setup until you can LOCALLY connect to :25 [13:14] SipriusPT_: then and only then you enter the domain of all the forwarding, maybe MX dns entries and such stuff [13:15] cpaelzer i will come back in a hour, thanks in advance for the help! [13:23] bzr is a memory hog :-/ [13:29] cpaelzer: thank you for the review! [13:30] cpaelzer: I am setting self.running = False on close. [13:32] rbasak: maybe it was not part of the same commit where I thought it was missing [13:32] * cpaelzer is checkking full diff [13:33] rbasak: yeah I see [13:33] rbasak: the good part is that my assumption was right, the bad part that I missed to read that you have already done it [13:33] cpaelzer: good to know you're reviewing properly. Thanks :) [13:33] (rather than saying +1 without checking for things like that!) [13:35] Hmm. I didn't provide a changelog entry in my MP. [13:35] * rbasak adds a commit for that [14:07] cpaelzer: I added strongswan FTBFS in Xenial (bug 1592706) to our backlog. Rationale is that it blocks any SRUs or security updates, so we should prioritise fixing it. [14:07] bug 1592706 in strongswan (Ubuntu) "strongswan fails to build in xenial on amd64 (test timeouts)" [High,Confirmed] https://launchpad.net/bugs/1592706 [14:09] rbasak: yeah that is correct [14:09] rbasak: I already added a backtrace as I think I was able to hit it on a local build [14:09] rbasak: but it is in no way a blocker [14:09] rbasak: it is an unwelcome but transient error [14:10] rbasak: did you pick that up triaging yesterdays updates? [14:10] Ah, only transient? That's not so bad. [14:10] Yes, I'm triaging yesterday's bug updates today. [14:11] rbasak: I can't speak on the "transitivity" of the LP builders, but for me it was one of about nine builds [14:16] cpaelzer are you there? [14:17] SipriusPT_: busy as always but here [14:17] SipriusPT_: and I'm not the #1 postfix expert, so you don't need me in particular :-) [14:17] but i really dont know where the problem is because i can send and receive mail internally [14:17] with local accounts [14:18] at least with mail clients through local host [14:18] SipriusPT_: well they might not really use smtp [14:18] SipriusPT_: does your host now bind one of the smtp ports? [14:18] i have config those users to connect through smtp port [14:18] i will show you [14:19] internally with a mail client [14:19] http://prntscr.com/d4n6yj [14:19] my web mail service is also connected through IMAP and SMTP [14:20] both clients are connected the same way [14:20] but till now i am just testing this in localhost [14:20] i have not tried to use mail app on other pc in this network [14:21] but i am able to login in my web mail service everywhere and send mails to inside or outside email domains [14:22] SipriusPT_: I don't mind the other tests as they could use whatever connection I don't know about [14:22] SipriusPT_: but since you fail to connect to port 25 from the outside as your initial issue [14:22] SipriusPT_: does netstat other than before now report any of the smtp ports as open? [14:24] coreycb: heylo....python-tempest is broken im looking at it right now [14:26] cpaelzer: nop, nothing at 25, 2525, 465 [14:26] with netstat [14:27] when i do telnet to the DNS name pointed to my external IP [14:27] SipriusPT_: the I think your setup is still not complete [14:27] i got connection refuse [14:27] SipriusPT_: sorry my lack of mail server expertise prevents me from suggesting more - but if your test is to connect to port 25 there has to be something binding that port [14:27] it is possible [14:28] all that i could do in my ISP, who is pointing a MX record to this server [14:29] and if i have not receive anything it could be something missing in postfix [14:29] but i have search a lot and all that i can find seems very simple and i already did that =/ it is more easier to receive then send [14:30] from what i have saw of configs [14:30] but thank you very much cpaelzer, at least you try! [14:31] I've gotta ask - is your mail server at your home (residential) network on a non-static IP? [14:31] SipriusPT_: yeah, sorry - I hope you find one with more postfixiness [14:32] SipriusPT_: I've gotta ask - is your mail server at your home (residential) network on a non-static IP? [14:32] those guys dont help easelly [14:34] it is in an office, and right now just for test i have used a dynamic IP (that looks almost static 2 weeks in a row without change), associated with a DNS name with reverse DNS [14:34] teward: o/ [14:34] i will have to add a static IP soon [14:34] teward: so we have a renewed effort to triage bugs on the Canonical server team. We have a schedule and have been able to look at all server bugs touched since August 8th so far. [14:35] teward: what should we do with nginx bugs? For example, bug 1639814. I realised that your schedule probably means that you won't have had a chance to look yet, which is fine. [14:35] bug 1639814 in nginx (Ubuntu) "nginx package upgrade on ubuntu 14.04 rewrites ssl config" [Undecided,New] https://launchpad.net/bugs/1639814 [14:35] rbasak: that ones' tricky [14:35] teward: the trouble is that with our process, we have one opportunity to see it, and if I ignore it now we won't see it again unless it gets touched again. [14:36] rbasak: because that's apt weirdness - ideally apt isn't going to overwrite configs [14:36] but it is doing that [14:36] teward: so in the general case, should I leave all nginx bugs to you unless you flag them up? [14:36] rbasak: yeah, unless it's Security related in which case also ping the SEcurity team [14:36] which is standard process [14:36] OK [14:36] rbasak: i get all the nginx bug notices as they come in [14:36] to two emails [14:36] For this bug, apt surely isn't touching those files - it can only happen through postinsts. [14:36] rbasak: yeah the trouble is i've tried shoring up the postinsts in the past... [14:36] and gotten NACKs [14:37] (for the "code loss" bugs) [14:37] Handling files in /etc is pretty messy due to the policy of "don't mess with users' local changes". [14:37] That makes it hard. [14:37] Making modifications is permitted (seddery) but can lead to conffile prompts, which is also bad. [14:37] rbasak: so i'm stuck between the two evils: (1) don't radically change the structure of the postinst, and (2) add changes that only fix the specific issue [14:37] rbasak: the *other* problem: [14:37] i haven't been able to reproduce [14:38] not even with automated Landscape isntallations of the package code [14:38] it's on my radar to look at [14:38] the merge from Debian is higher on my radar though if only because that needs to land before OpenSSL 1.1.0 ever doews [14:38] Does Debian's packaging have this bug too? [14:38] rbasak: if it does, I haven't seen it reported, but they're also at 1.6.x which is at least a year newer than Trusty [14:39] OK [14:39] Let me know if you need any help when you get to it. [14:39] Thank you for working on these! [14:39] rbasak: my pleasure! Note that i'm also still handling the evils of the recent security fix [14:39] (I'll blurb on it during the server team meeting, provided i'm not dragged through oblivion today) [14:39] Noted. I appreciate not having to worry about it :) [14:40] rbasak: it may not get rapid-fixes for complex issues, but you can see how some bugs have been filed and rapidly closed by me as not a bug. [14:40] so i do see them. [14:40] response time is dependent on my work and study schedules [14:40] and complexity [14:41] Sure. I have no problem with your response time. Also happy to back you up as needed. Just need to make sure our processes don't clash. [14:41] "Canonical is providing the Canonical Livepatch Service to community users of Ubuntu, at no charge for up to 3 machines." That's ridiculous - but typical. (Just my comment, no offense.) [14:41] rbasak: Security issues get forwarded up to the SEcurity team, though i've ended up being the point-of-contact at times to relay [14:41] almost same-day [14:41] though as we all know the SEcurity team is amazing at those thigns [14:42] rbasak: no clash on the processes, though it doesn't hurt to prod me if you're unsure [14:43] email is faster than IRC though, teward AT ubuntu [14:43] OK [14:44] rbasak: wrt that bug, are we 100% certain apt isn't touching? the 'default' config file is in the .install file not the postinst... [14:44] Have you been able to reproduce, or do we just have one reporter claiming it? [14:45] It wouldn't be apt, it'd be dpkg. [14:45] And if using a modern dpkg-source (IIRC, or is it debhelper?), then anything from a .install file to go into /etc will be automatically marked a conffile, and result in a conffile prompt over overriding a user's changes. [14:46] rbasak: i've only seen the one person report [14:46] otherwise i'd have dupe-reported [14:46] Then it might be Invalid. [14:46] s/reported/linked/ [14:46] I'm only speculating of course based on what's common. I haven't actually looked. [14:46] rbasak: i'm in the process of repairing one of my testing servers, happy to nuke/rebuild/nuke/rebuild to try and reproduce [14:46] Thanks [14:46] but i'd need a copy of their configs they had to try and 'test' with [14:46] Also you can do it in a container pretty easily. [14:46] lxc launch ubuntu:trusty foo [14:47] lxc exec foo bash [14:47] rbasak: fun fact: you're right, but I already have a Trusty VM I use for full testing [14:47] OK :) [14:47] rbasak: also, Trusty != Xenial, it doesn't like me with lxc on this system [14:47] rbasak: also, when doing QA testing, the VM allow for full install tests - another reasons I'm in the "VMs > LXC Containers for Testing" niche :) [14:48] oop that reminds me, I need to renew my Landscape licenses... [14:48] IMHO, containers are good enough for most packages. Except for some packages that it isn't. [14:49] rbasak: indeed. But if i have the servers running as test servers to test different things (INCLUDING bad SSL config testing heh), why not use it :) [14:49] Containers tend to be a little quicker :) [14:49] :) [14:50] back in a moment, VPN tunnel construction in progress [14:57] zul, ok I uploaded a new version of tempest yesterday [14:57] coreycb: just uploaded a fixed version [14:57] <-- ninja [14:58] zul, cool [15:03] cpaelzer: the dovecot dep8 test is still failing :-( [15:04] rbasak: but it is failing much nicer now [15:04] Interesting though. Different failure. [15:04] Yeah [15:04] I wonder if that's because the Python 3 imap library produces better (more helpful) exceptions. [15:06] * rbasak requests a retest to see if the results change [15:18] jamespage, when you get a chance can you promote python-glance-store and mistral from newton-staging -> newton-proposed? also could use a flush of mitaka-staging -> mitaka-proposed for openstack-trove, mistral, and python-django. [15:20] cpaelzer: it passed on retry. [15:20] jamespage, also python-novaclient is ready to promote to mitaka-updates [15:25] jamespage, and one more, python-pylxd 2.0.5 is ready to promote to mitaka-updates [15:26] coreycb, looking now [15:28] coreycb, ok shoved the proposed updates for novaclient and pylxd to updates [15:29] flushing staging -> proposed now [15:29] coreycb, it would be good to get that lot tested and out of the door [15:29] there is some ceph stuff in that to [15:30] jamespage, thanks. I'll get testing going on those. [15:32] coreycb: monasca-statsd with proper license has been packaged i uploaded it to the archive and put it in the ppa for now [15:33] zul, awesome thanks [15:33] zul, can you push to lp:~ubuntu-server-dev? [15:33] coreycb: doing it now [15:34] zul, thanks [15:42] anyone familiar with Ubuntu OpenStack? [15:42] in a production environment [16:00] any expert at postfix here? [16:01] sikun: any specific question? [16:01] joelio, I guess just a couple broad questions [16:02] more so on possibly building an OpenStack cluster for a production environment [16:03] well if anyone here have set a postfix server to receive mail from outside please check this tread: [16:03] http://www.linuxforums.org/forum/servers/208607-not-receiving-mail-postfix-external-server-post983645.html?highlight=#post983645 [16:04] The Ubuntu O/S site says a requirement of 5 servers with two disks, two with 2x NICs, I'm guessing the two servers with the drives would just be iSCSI storage targets for the VMs? [16:04] SipriusPT_: I suggest that you summarise the question here. Many able and willing people won't bother to follow your link. [16:04] and the other three along with those two would be compute nodes [16:04] ok rbasak thanks i will post here [16:04] jamespage, pthon-pytest has some pypy dependencies, so I think i'll drop those via ca-patches vs backporting them if you are ok with that [16:05] i am unable to receive mail with my postfix, i can only send to inside and outside domains, and cannot receive from outside or even from my ISP mail server [16:06] I am trying to do a middle mail server between group of people and my ISP mail server [16:06] till now i am only able to send from multi local users to multi external users created at my ISP mail server [16:07] in my ISP mail server i have set a MX record to my public IP [16:07] right now is a dynamic but its pretty stable for testing [16:07] i have a DNS name pointed to that IP, with reverse DNS [16:08] i was able to telnet port 25 locally and then notice that i was unable to telnet to that port externally [16:08] sikun: it depends on what storage backend you chose. You could use local storage or shared storage. Obviously shared storage requires additional nodes, setup etc for the target type (iscsi, ceph etc) but provides true migration capabilities [16:09] SipriusPT_: i would keep in mind a lot of 'dynamic IPs' are in mail blacklists [16:09] so i add it for port forwarding to an expecific external IP but i didnt receive any mail and no socket was open to that port as i have saw in netstat [16:09] joelio, preferably I would like to go with local storage. [16:10] Wondering if 5 nodes is truly necessary [16:10] i know teward but i have check this on before i use it and was just blacklisted in one of a big list [16:10] right now i have no idea on what is doing this [16:10] sikun: no, if you're testing you can run a single node with the service on.. multinode I'd go for 3 at least [16:10] but it depends on your requirements really.. [16:11] I suppose I could just install Ubuntu and the KVM packages and just run it w/o OpenStack but I guess I'm trying to "sell" it as a benefit if we did a full on OpenStack cluster [16:11] it could be from my IP provider? that is blocking this kind of services? [16:12] joelio, I need to condense three 12 year old servers running CentOS 5.? which are the current KVM hosts [16:12] they are going to die soon I just know it, but... I don't want to setup new servers to migrate what's on the VMs as they are all so horribly outdated I just want to move the VMs themselves to a new host [16:14] SipriusPT_: most residential ISPs block mail server ports [16:14] As I said in my meeting the other day... Who knows if a freaking butterfly in China is going to flap its wings and I loose 2 of the three KVM hosts due to hardware failure [16:14] SipriusPT_: if you're on a dynamic IP host, and it's not a business class connection and is residential class, it's likely being blocked at ingress by the ISP [16:14] lol, just as long as I can keep them running for 2 more years tops... that is all I need. [16:14] as i suspect [16:15] i was just counting with the blacklist part of this dynamic IP [16:15] there's also port forwarding that has to be done as well at the NAT level at your connection, but SMTP is probably being blocked [16:16] i am able to send mails from my local server to my ISP mail server and even do SMTP auth [16:16] but receiving it is showing to be a pain in the a** [16:17] SipriusPT_: SMTP outbound is usually not filtered, it's inbound that's usually the problem [16:18] as I said before, ISPs of a residential grade usually don't allow SMTP mail servers on their network for receiving [16:18] ok ok teward thanks a lot! [16:18] some might, but you'd have to check with that ISP [16:18] this could be a noob problem but it is my first time doing it [16:19] sikun: well you could just got native KVM, but you lose all the functionality that openstack provides, API's, Tennencies etc. It entirely depends on your requirements, if you don't need that stuff then maybe just vanilla KVM is fine. If you decide to do anything 'at scale' as it were, you may find openstack (or any other cloud orchestration) a better fit [16:20] there can be quite a lot to take on board when first approaching openstack, I'd recommend looking at devstack first perhaps, get the feel for it (devstack is a cloud in a vagrant vm essentially). [16:20] if it's too much and time pressing, then you know early on at least, in terms of workload required to bootstrap it all [16:20] oh nice [16:22] yeah, I just have to somehow convince 4 people that Ubuntu/Debian is a very reliable production worth OS... [16:22] worthy** [16:24] Well, we run ubuntu here for pretty much everything (not that that counts for much) - this may count more - http://www.zdnet.com/article/ubuntu-linux-continues-to-dominate-openstack-and-other-clouds/ [16:24] awesome, it's current too [16:25] I've ran Debian/Ubuntu for years, in production, dev, personal. [16:25] I'm now in a BSD environment [16:25] where it is either OpenBSD or FreeBSD, and never is the OS that was chosen actually the proper choice of OS for the situation. [16:26] Hey, got nothing wrong with BSD.. just tooling different (although bhybe etc is pretty awesome!) [16:26] *bhyve [16:26] dose nfs-kernel-server replace the kernel or is it a module? [16:27] sikun: VMM on OpenBSD looks promising too, just they don't support any other OS guests yet [16:27] I'd be more apt to use VMM on FreeBSD than OpenBSD [16:28] OBSD is just lacking too much in driver support in my opinion [16:53] mysql-5.7 migrated \o/ [18:06] cpaelzer: new qemu v2.7 hit debian :) [18:11] hallyn, cool [18:20] coreycb: vmware-nsx needs vmware-nsxlib now :( [18:20] zul, yeah, saw that [18:21] coreycb: on it [18:21] zul, thanks. good news is we don't need to get it into main. [19:42] hey all, trying to install libcrypt-ssleay-perl on ubuntu 14.04 but it says is not available, bit reffered to by another package (this may mean that the package is missing, has been obsoleted, or..) [19:43] ssleay was renamed to openssl in 1998 [19:43] woah [19:43] so why does it still show as ssleay here http://packages.ubuntu.com/trusty/libcrypt-ssleay-perl === mburns_ is now known as mburns [19:45] wow, it's still packaged? o_O crazy [19:45] jge: maybe you don't have the 'universe' pocket of the repository enabled? [19:45] yeah that could be it, let me check [19:47] that was it, thx sarnold rbasak [19:47] ignore rbasak (keyboard lag) ;) [20:33] Hi friends. I'm new to linux servers and now choosing distribution for deployment. There is a choise between centos and ubuntu. I like ubuntu, centos seems to conservative for me. But lookin for documentation, i have a question - can you recomended some books or other literature about ubuntu server? Centos = RHEL, and red hat has a dozen manuals at docs.redhat.com. Oficial ubuntu server manual is very short, and don't answers [20:33] kukuruzo: serverguide maybe? [20:34] is too easy and short [20:34] kukuruzo: Whats missing? [20:35] kukuruzo: are you sure you're not confusing the manual with serverguide? https://help.ubuntu.com/lts/serverguide/ [20:36] For example it's don't answers question about apparmor in ubuntu. RH has a lot of docs about selinux. Seems ubuntu supports SElinux, but in server guide are few words about apparmor, and links to novell site. [20:36] nacc - yep i'm sure [20:38] for example - about app armor said "This section is plagued by a bug ( LP #1304134 7 ) and instructions will not work as advertised." [20:38] Launchpad bug 1378095 in apparmor (Ubuntu) "duplicate for #1304134 aa-complain traceback when marking multiple profiles" [High,Fix released] https://launchpad.net/bugs/1378095 [20:39] kukuruzo: and that bug is fixed [20:39]