[00:20] them all does nowdays [00:29] lxd.... been on it all day [00:30] just want a vpn+dnscrypt-proxy that gives out ip's to other containers such as my torrent-lxc [00:31] doesn't each lxd container get their own network stack? i'm curious if 'gives out ips' is realistic or feasible [00:34] they get their ip from the lxcbr0.. managed by dnsmasq.. wonder if a lxc could create a bridge on the host.. [00:41] it could work with static routing [00:45] i'm so tired of my crappy hardware for my "server".. wish esxi har support for the nics.. or if i had money to buy a nic that is supported by esxi === CodeMouse92 is now known as CodeMouse92__ [03:20] How well supported is ZFS in Ubuntu 17.04? I have to decide between Motherboard Raid 0 and a ZFS implementation; any suggestions? [03:21] TLoFP, I made the mistake of ReiserFS a long time ago...I shan't do that again... [03:22] TLoFP, If this is a VM situation - you can experiment..given the time and energy and ambition... [03:22] YankDownUnder: unfortunatly I have no time :P [03:22] TLoFP, THAT can be a problem. [03:22] YankDownUnder: this is going to be an 2x4TB for a video system [03:23] I will have two days to get the system operational, and that includes reinstalling the Hyper-V host [03:23] so I am preparing the ubuntu VM ahead of time so that I will be ready to deploy once the host is operational [03:23] unfortunaly that means I don't get to really play with the direct attach disks untill deployment though [03:24] TLoFP, In considering 1.) Time frame 2.) Application 3.) Priority => I'd not "experiment" with ZFS...too many "unknowns" in the mix for comfort. [03:24] YankDownUnder: thanks, thats kind of what I was trying to feel out with "how well is it supported" [03:25] TLoFP, I'd also RE-THINK using 17.04 - since it is NOT an LTS release... [03:26] I'd love to say that "problems MAY happen in upgrades/updates" - but nowadays I'd be more apt to say "problems WILL happen"...ergo, sticking to LTS releases...yadda yadda yadda. [03:27] YankDownUnder: ture I hadn't thought about that [03:28] I just read ubuntu systems are only supported for 9 months, LTS is 5 years... wow [03:28] I though the regular relases had 2 year support, boy was I wrong [03:28] TLoFP, "Plan the work, work the plan" - K.I.S.S. - saves YOU time and frustration/stress/anxiety. [03:30] so 16.04 must be a little over a year old now, yes? and in about a year we will see 18.04 LTS at which point 16.04 will be 2 years old [03:30] eventually I will have to upgrade.. so I am not sure that the fear of upgrading really makes sense [03:30] plus it is a VM so making a backup and restoring is trivial, shoudl something go awray [03:31] Yeah...something like that...I can wait for 18.04...ain't like it's a stress...and things just work...and if they don't work, there's enough resource that is DEPENDABLE to get it to work...know what I mean? [03:31] Yea [03:31] I think what I am most afraid of is me [03:31] Putting off "upgrades" - like on a two year basis - ain't a bad thing. Gives one time to "work it all out" prior to an actual upgrade... [03:32] in otherwords I "forget" to "maintain/update" 17.04 than in less then a year I am in a bad situation [03:32] whereas 16.04 will continue to install security updates for almost half a decade without me having to do major/if any maintance [03:33] Less work, less stress. [03:34] YankDownUnder: either your old or you work in IT... wise words [03:34] I started in 86, bro. [03:34] i'll stick to 16.04 and upgrade to 18.04 if im in a good place when it comes out [03:35] I run development releases day to day on my laptop but still use LTS for servers [03:35] TLoFP, In giving a solution that is "rock solid" to the client, you're only ensuring your own reputation for "doing the right thing" and being also dependable... [03:35] lol, it's been a while I am afraid I hadn't even seen day light back then [03:36] YankDownUnder: true. This is a high risk / high reward client too. Failure would be unacceptable. (read: the wife) hahah :D [03:36] Wife: Most important client. Do *NOT* fail client. [03:37] Pretty much [03:37] TLoFP, Women do NOT forget. Anything. Ever. Infinitely. [03:38] true words [03:39] that still leavs: crappy on-board raid 0 or ubuntu-software raid 0. [03:39] Kinda been married a few times...AND some...ahem...yersh...MEANWHILE, back to the topic - the entire ideology about building ON and around an LTS release is safer in the long run, and you're warranted support. As well, since it's tried and true and tested, your "support" toward the client would be minimal (without hardware issues). [03:40] unfortunatly I am not a pro, but I know enough that pro's typically look at motherboard raid controllers with distain. But that was years ago and typically had to do with higher raid systems that actually have to do parity calculations [03:40] YankDownUnder: true [03:40] YankDownUnder: i'll take that to heart and play with 17.04 on my desktop sandbox. I get to have both :D [03:41] TLoFP, Software based RAID is easy to fix. Hardware based RAID - well, things can (and generally will) go "south" [03:43] YankDownUnder: and performance of RAID 0? overhead? [03:44] TLoFP, It's a server OS...YOU tweak the performance of the disk i/o...YOU tweak the server to do - well, whatever...and it's all tweak-able...hardware based RAID is, well, not very tweak-able...given the situation with the OS running in a VM and all that lovely jazz...hmm... [03:45] YankDownUnder: I figured i might get away with less dedicated resources to this particular VM, thus freeing up more for others [03:46] TLoFP, You're running a VM on a machine - and the VM is talking to external drives...what is this "host" machine doing aside from just hosting a VM? [03:49] YankDownUnder: the host is being downgraded from 2012 R2 to Win10; it will host a Ubuntu-server install with minimal resources. Three 2012 R2 or 2016 Servers (Storage Server, Domain Controller, Radius Server) and a Ubuntu-Desktop VM [03:49] YankDownUnder: to clarify the drives are internally connted SATA drives. [03:49] I have an absolute dislike/loathing/deep seated hatred for ANYTHING MS based - server or otherwise. Sorry. [03:50] YankDownUnder: I get that, and I don't blame you for it. [03:51] I was around before MS destroyed the industry and turned it into a complete lie/scam/legal nightmare/lie/illusion/lie/scam/lie... [03:51] I have tried to ditch MS many times but my professional career has always prevented me from doing that [03:52] so at some point I decided to put on the waders and embrace the sh*t [03:53] ...hence my move to Mac and linux...clients were told to either switch or be ditched. The ones that switched have all been very happy. The ones that were ditched - whinged about it - some came around eventually - the rest still try to "bait" me into fixing their crud. [03:54] It's not possible in many cases. Allot of software runs only on WinSux [03:55] "That which you allow - continues" - I'll take a higher ground. I will stay away from it and stay in the niche and in the background. MS already has planted the seeds for their own destruction. Long ago. I'll just sit in the background making use of OS's that have lived a longer life...hmm... :) [03:56] YankDownUnder: nice play. Just in case you haven't heard, but apparenlty MS is embracing linux/open source now [03:57] also btw. I am currently having this issue with my boss: how do you explain to people that open-source isn't evil? [03:57] or even, what I take for granted, that open-source is NOT less secure than MS but in fact more secure due to its open-source nature [03:57] idk... that both souded really stupid when I read it back [03:58] but the really is I am dumbfounded when somebody tells me that they think MS is more secure "because it is a closed software and thus people don't know how to exploit it" [03:58] F.O.S.S. newsletters and open document media presentations. Always good to offer information to the uninformed. [03:58] like all exploits ever where discovered by reading the source code.... sigh [03:59] Could show the documentation about "Section 7"...hmm... [04:00] Either which, I digress. [05:36] good morning everybody [06:13] Good morning. [08:38] I could use the advice for 16.04-server. No ufw or isp tables (All disabled/flushed, etc atm) Installed a basic lamp(apache/info.php all work as expected. all defaults)then did basic vsftp server. Functioned with basic setup locally and remotely(did the ssl/userlist/chroot_list setup) everything worked fine up until the chroot_list. Removed/purged reinstalled, default config, no response/connection refused. [08:38] Ever ran into this on a simple vfstp setup or possible have a point in the direction I should be using??. [08:39] Maybe I am missing something for 16.04(14 was the last I was really active with servers at all) [08:40] Skittishtrigger: check netstat -tlnp output to see what state the socket is in [08:41] of course I took long enough to find your question that there's a chance it's already fallen out of the various TIME_WAIT states and is free to use again [08:41] (lol) ya, that was the first think I tried. everything was listening where it should be at the time(in the middle of purging it all again. lol) [08:42] I am probably missing something obvious since I am so tired. [08:42] do you -need- an ftp server? it's a terrible protocol.. [08:43] it is, and I set up ftp then do sftp [08:43] I might have to just go with something like elfnider [08:44] eflnider/slfidner [08:44] screwit. close enough === KaeltenAway is now known as Kaelten [09:31] rbasak: I also mass submit remaining Delta this morning even though hope is low to be taken given what happened last time [09:32] rbasak: I'd guess if we really want that Delta in I'd need to adopt ntp in Debian [09:32] a step I considered but not yet want to take [09:32] we will see how things work with this round of changes [09:32] you also remember the long set of potential-delta we submitted last year [09:32] that isn't in either [09:33] skip the last sentence [09:33] but it is not accepted [09:33] the only thing that was accepted is accepted wrong (bug closed no change done) [09:33] I already reopened [10:34] I am trying to setup a telnet server on an Ubuntu test machine (I need it because I am writing a noddy Telnet client on an eCos platform and want a server to test against). I have tried following a few instructions about installing xinetd and telnetd and editing the /etc/init.d/xinetd files but I don't think the server is accepting traffic. Any time I try to connect in I get a connection refused. Can anyone suggest what I am missing? [10:40] TafThorne: the servers (both inetd and telnetd) will be logging, check their log files. [10:40] start with /var/log/syslog [10:41] TafThorne: also, are you aware that you can run ssh clients on eCos? there are multiple implementations. [10:42] my understanding is that even in RTOS people are starting to move away from insecure protocols wherever possible. [10:43] tomreyn: I am working on a _very_ old version of eCos with a few layers of a 3rd partie's code and then my code on a resource constrained platform. [10:44] okay, i just felt the need to point it out in case you have other options. [10:44] tomreyn: I cannot add new utilities to the eCos system. Only write my own little bif of applicaiton code to run on the side. These coms should all stay inside the metal case of the unit so security on the channel is not that critical. Thanks for checking though. [10:45] tomreyn: all static linking and using 3rd party closed code too. Else I would be looking at getting someone else's anything client installed. [10:46] :-/ hope you can finish that task soon. ;) [10:47] We really, really, really want to move on to a more modern Linux Kernel. [10:48] here are some hints on making inetd log more: http://ubuntuguide.net/install-and-enable-telnet-server-in-ubuntu-linux [10:49] any luck with the logs? [10:49] Anyway back to telnet. In the syslog I can see http://pastebin.ubuntu.com/24504511/ [10:51] And further down I have noticed that freshclam is still moaning "freshclam[1036]: WARNING: getpatch: Can't download daily-21693.cdiff from db.local.clamav.net" becasue once appon a time I used apt-cacherng and it seems to think its a full http mirror proxy even after it is disabled >_< [10:51] can you also share the configuration file(s) you modified? [10:51] Sure [10:51] "missing service keyword [file=/etc/xinetd.d/telnet] [line=1]" sounds like an issue [10:52] That bit did look a bit iffy to me too http://pastebin.ubuntu.com/24504515/ [10:53] i'm not sure about initd configuration really, haven't used it for ages, but i guess this line is wrong, or misplaced: telnet stream tcp nowait telnetd /usr/sbin/tcpd /usr/sbin/in.telnetd [10:55] also uncomment the log_type statement so you actualyl get logs [10:56] so the "telnet stream tcp nowait telnetd /usr/sbin/tcpd /usr/sbin/in.telnetd" line should probably go into /etc/inetd.conf (no 'x' there!) [10:58] (so not into /etc/xinetd.d/telnet where you have it now) [10:58] As a result, /etc/xinetd.d/telnet will start with a 'service' line, which it must. [10:58] (comments as indicated by a # character are ok) [10:59] does this help? [10:59] OK I shall try out those suggestions. I will be AFK for a couple of minutes while I run out to the sandwidch van. [10:59] It does all sound helpful. Thank you. [11:00] hello all [11:00] good luck. i may or may not be around when you return [11:00] hi Haris [11:01] directoryindex is not working on 14.04 lts apache 2.4.7, even after explicit mention in vhost config [11:02] I have a laravel framework in a vhost, where I'm redirecting / to /public via index.html. that index.html is not being found. apache is returning me an empty page for / [11:02] on the vhost [11:02] ..laravel framework install+. ... [11:03] most likely directoryindex function is not working. I'v verified, the dir mod is loaded, so it should be working out of the box [11:04] tomreyn: I am back. I shall give your suggestions a spin. [11:04] chances are you have conflicting or overriding configurations? [11:04] Haris: ^ [11:05] https://httpd.apache.org/docs/2.4/mod/mod_dir.html#directoryindex is the documentation [11:05] I agree. that may be the case [11:05] Haris: maybe you have a .htaccess file with an Options statement aroudn somewhere? [11:05] hmm [11:06] not on / path [11:06] in /public yes [11:06] temporarily disabling .htaccess files via https://httpd.apache.org/docs/2.4/mod/core.html#allowoverride may help identify this [11:06] Options -MultiViews <--- [11:06] in /public/.htaccess [11:08] pasting vhost config [11:08] that might help [11:09] "Options -MultiViews" is not an issue in this context [11:11] https://pastebin.ca/3806640 [11:12] this is my vhost config file [11:12] most other than this is out of the box [11:12] hmm... got a little further, syslog had complaints about the only_from and access_times lines so I dropped those. No errors now but no telnet either. [11:12] can you post your updated configurations? [11:13] which updated ones [11:13] this was to TafThorne [11:13] Sorry, I am confusing things. I will do so. [11:13] DirectoryIndex explicit mention also doesn't help in making it work [11:13] Haris: i can't access the pastebin: [11:13] orry, an error has occurred. Reason: That is an invalid ID, or the post has expired. [11:13] https://pastebin.ca/raw/3806640 ? [11:14] this one works, interesting [11:14] https://pastebin.com/zz9QKz0P [11:15] need more conf [11:15] which part ? [11:15] /etc/apache2/apache2.conf probably [11:15] that's the default one. no chagnes from my end in it [11:15] changes+ [11:16] oh well [11:16] i tried [11:16] I was surprised not have found directoryindex on it [11:16] on=it [11:16] on=in [11:16] tomreyn: here is my updated set of configs http://pastebin.ubuntu.com/24504607/ [11:16] Haris: and there's nothing in /var/log/apache2/devwebapp-error_log and /var/log/apache2/devwebapp-access_log ? [11:16] nope [11:17] its a conf problem [11:17] that's also surprising [11:17] it should at least say / was accessed [11:17] apachectl -t says OK [11:17] apachectl -S also says ok [11:17] AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message <--- just this msg. but this is inconsequential [11:18] but this won't detect conflicts [11:18] TafThorne: /etc/init.d/telnet is not /etc/inetd.conf [11:19] apache is not even logging when I access /index.html or / specifically [11:20] Haris: unless you have much traffic on this server, run tail -f across all apache log file and use it to find out which vhost your requests are hitting [11:20] already doing that [11:20] =) [11:20] your requests seem to end up on a different vhost or the default vhost [11:21] the index.html file only 3 lines of html code, for redirecting to /public [11:22] hmm [11:22] i'm suggesting that this file is never read or returned [11:22] because your requests hit a different vhost [11:23] tomreyn: moved the file. [11:23] (but it's really just a guess) [11:23] its like links has cached the pages [11:23] :@ [11:24] Haris: use curl or wget -O- to debug this [11:25] TafThorne: any change? [11:25] wget is getting the 3 liner html code i.e., [11:25] Haris: "curl -I " that is [11:26] perhaps its the links text browser which is not yet capable of going through html redirects ? [11:26] okay so your index.html IS returned [11:26] yep [11:26] links is just not parsing it correctly [11:26] or not giving the "user friendly" parsing [11:26] still a conf problem [11:26] http redicrections with javascript are ugly, why do you do this? [11:26] I just have the