1368403713 Q * Ghislain Quit: Leaving.
1368404144 Q * PowerKe Ping timeout: 480 seconds
1368404677 J * PowerKe ~tom@94-227-30-112.access.telenet.be
1368410507 J * treaki_ 85601c43c3@p4FF4A1B4.dip0.t-ipconnect.de
1368410817 Q * treaki__ Ping timeout: 480 seconds
1368412162 N * l0kit Guest5185
1368412167 J * l0kit ~1oxT@0001b54e.user.oftc.net
1368412565 Q * Guest5185 Ping timeout: 480 seconds
1368421663 Q * marcel__ Ping timeout: 480 seconds
1368422163 J * marcel__ ~marcel@pd95c7474.dip0.t-ipconnect.de
1368428376 J * Arach_ ~arach@28IAACN1M.tor-irc.dnsbl.oftc.net
1368428379 J * Ghislain ~aqueos@adsl1.aqueos.com
1368428440 Q * Arach Remote host closed the connection
1368433173 N * Bertl_zZ Bertl_oO
1368435211 M * morfoh Bertl_oO: just fyi patch-3.4.38-vs2.3.3.9.diff also applies on top of 3.4.45
1368437528 J * thierryp ~thierry@home.parmentelat.net
1368437579 M * Ghislain nooo i just compile 3.4.44 yesterday !
1368437710 M * Ghislain bah mostly radeon stuff will wait for 3.4.46+ to restart the process
1368439604 Q * Aiken Remote host closed the connection
1368439964 Q * ser Ping timeout: 480 seconds
1368441048 P * glen 
1368441058 J * ser ~ser@host1.tldp.ibiblio.org
1368443470 Q * ircuser-1 Ping timeout: 480 seconds
1368444529 M * Bertl_oO morfoh: excellent, tx!
1368444766 Q * hparker Quit: I've fallen off the 'net and can't get up
1368444784 J * hparker ~hparker@2001:470:1f0f:32c:beae:c5ff:fe01:b647
1368445944 Q * treaki_ Quit: Verlassend
1368446195 Q * thierryp Remote host closed the connection
1368446212 J * thierryp ~thierry@2a01:e35:2e2b:e2c0:e00c:116:b066:3efc
1368446324 M * morfoh Bertl_oO: yw ;)
1368446912 J * ircuser-1 ~ircuser-1@35.222-62-69.ftth.swbr.surewest.net
1368447693 N * Bertl_oO Bertl_zZ
1368450166 Q * mcp Remote host closed the connection
1368450200 J * mcp ~mcp@wolk-project.de
1368450944 N * Arach_ Arach
1368453252 Q * nkukard Read error: Connection timed out
1368453768 J * nkukard ~nkukard@197.87.148.190
1368454189 J * grembleb ~bengreen@cpc35-aztw23-2-0-cust207.18-1.cable.virginmedia.com
1368454823 M * marcel__ Wo muss der drop hin?
1368455819 Q * grembleb Quit: I Leave
1368456803 J * nlm ~nlm@host211.200-43-249.telecom.net.ar
1368456938 Q * cuba33ci Remote host closed the connection
1368456954 J * cuba33ci ~cuba33ci@114-25-198-70.dynamic.hinet.net
1368456964 J * csh-harmful ~unknown@pulsar.viking.by.vps.neolocation.net
1368456990 M * csh-harmful Hi! Is there any tutorial how to run systemd inside the vserver instance ?
1368457853 J * BenG_ ~bengreen@host-92-27-135-217.static.as13285.net
1368458567 Q * BenG_ Ping timeout: 480 seconds
1368458659 J * BenG_ ~bengreen@host-92-27-135-217.static.as13285.net
1368459344 Q * thierryp Remote host closed the connection
1368459535 J * thierryp ~thierry@home.parmentelat.net
1368460282 N * Bertl_zZ Bertl_oO
1368461375 M * morfoh csh-harmful: maybe Mr.Poetering will invent a special systemd flavour for vserver guests so everyone can benefit from this immense idiocy
1368461771 J * bonbons ~bonbons@2001:a18:20a:9d01:7835:578e:24a0:4576
1368462048 M * Arach :D
1368462321 M * morfoh sorry... but sometimes I cannot resist when it comes to that highly entertaining topic :D
1368462641 M * morfoh now I am asking myself if for example daemontools was even invented before the systemd author was born .oO
1368462647 M * morfoh :p
1368462652 M * morfoh anyway ... enough :)
1368462962 M * Bertl_oO csh-harmful: to answer the question: none that we know of
1368462998 M * Bertl_oO but most likely 90% of the upstart issues have a similar counterpart with systemd and probably a very similar workaround
1368463023 M * Bertl_oO feel free to start a wiki page describing the necessary configuration changes
1368463062 M * Bertl_oO basically you want to get systemd logging (is there such thing?) enabled early, and all hardware/kernel related functions disabled in systemd
1368463104 Q * thierryp Remote host closed the connection
1368463104 M * Bertl_oO from the guest configuration you need 'plain' init style
1368463785 Q * BenG_ Ping timeout: 480 seconds
1368463790 M * Bertl_oO and yes, I agree that it is usually better to avoid systemd (if that's an option) because it has little advantage over sysv runlevel scripts
1368464660 M * csh-harmful It's has all the advantages of sysv still + all daemontools features + it's own advantages
1368464709 M * csh-harmful I'm a heavy daemontools user and find systemd as a good and more feature reach replacement
1368464747 M * csh-harmful Notably it can bring service A down in case system B went down
1368464921 M * Bertl_oO well, my experience with systemd (the distro I use switched some time ago) is that it is hard to debug, not worth the additional resource usage, and usually not doing what I expect it to do, but that's probably the result of the distro maintainers not knowing how to configure it properly
1368464997 M * Bertl_oO but AFAIK, systemd is designed to work in LXC containers, and with such a config, it should work just fine inside a Linux-VServer guest as well
1368465055 J * thierryp ~thierry@2a01:e35:2e2b:e2c0:78e9:eb57:58a9:6a58
1368465595 Q * nkukard Ping timeout: 480 seconds
1368466146 J * nlm_ ~nlm@host211.200-43-249.telecom.net.ar
1368466169 Q * ser Ping timeout: 480 seconds
1368466170 M * csh-harmful Interesting, if I don't have any ipv4 address defined for vserver it won't bring lo up!
1368466204 M * ard csh-harmful : auto loopback interface I guess :-)
1368466244 M * csh-harmful "iface lo inet loopback" I have it there
1368466254 M * csh-harmful inside vserver
1368466267 M * ard in your interfaces file?
1368466272 M * csh-harmful yes
1368466274 M * ard it won't read your interfaces file
1368466282 M * ard a guest is not allowed to fiddle with interfaces
1368466315 M * ard your host should configure it, and your guest will live fine without having the right to change it
1368466319 M * csh-harmful most likely, then how I supose to bring lo up if I have no IPv4 soace there
1368466339 M * ard configure a bogus ip address on lo :-)
1368466341 M * Bertl_oO what kernel/patch/util-vserver version do you use?
1368466341 M * ard or a valid one
1368466391 M * ard It sounds like a new one... If you don't configure interfaces, you won't get any...
1368466394 M * csh-harmful  0.30.216-pre3038-1 and linux-image-vserver-3.2-beng           3.2.42-2.3.2.16+wheezy
1368466425 J * PowerKe_ ~tom@94-227-30-112.access.telenet.be
1368466433 J * jrklein_ ~osx@proxy.dnihost.net
1368466451 M * Bertl_oO please upload the output of /proc/virtnet/<nid>/info somewhere (pastebin)
1368466461 J * michal_ ~michal@168.63.70.79
1368466467 M * Bertl_oO (for that guest, without the 'lo')
1368466477 M * csh-harmful 1 min
1368466484 M * Bertl_oO np, take your time
1368466499 J * nkukard ~nkukard@197.87.148.190
1368466501 J * l0kit_ ~1oxT@ARennes-653-1-297-79.w109-218.abo.wanadoo.fr
1368466541 Q * nlm synthon.oftc.net larich.oftc.net
1368466541 Q * mcp synthon.oftc.net larich.oftc.net
1368466541 Q * marcel__ synthon.oftc.net larich.oftc.net
1368466541 Q * l0kit synthon.oftc.net larich.oftc.net
1368466541 Q * PowerKe synthon.oftc.net larich.oftc.net
1368466541 Q * jrklein synthon.oftc.net larich.oftc.net
1368466541 Q * Kabaka synthon.oftc.net larich.oftc.net
1368466541 Q * michal synthon.oftc.net larich.oftc.net
1368466541 Q * ccxCZ synthon.oftc.net larich.oftc.net
1368466541 N * michal_ michal
1368466584 M * csh-harmful http://pastebin.com/Cp9xAa8M
1368466617 M * ard Bertl_oO : is it not normal behaviour of autoloopback?
1368466646 M * Bertl_oO well, it is a corner case
1368466690 M * ard http://paste.linux-vserver.org/23828
1368466710 M * Bertl_oO csh-harmful: what does 'nattribute --nid 40001 --get' give you?
1368466756 M * ard hide_lback ?
1368466796 M * ard http://paste.linux-vserver.org/23830
1368466813 M * csh-harmful http://pastebin.com/Rhf93Emq
1368466814 A * ard never considered it a bug :-)
1368466819 M * Bertl_oO I presume the HIDE_NETIF removes 'lo'
1368466843 M * ard I can add an ip to it, just to see what happens
1368466863 J * ser ~ser@host1.tldp.ibiblio.org
1368466878 J * mcp ~mcp@wolk-project.de
1368466911 M * Bertl_oO CONFIG_AUTO_LBACK just assures that a context specific IP is automatically assigned to the guest
1368466923 M * ard as soon as I add an ip address, I get to see a working 127.0.0.1
1368466925 J * Kabaka kabaka@equine.vacantminded.com
1368466943 M * Bertl_oO yeah, because the 'guest does have ipv4 assigned kicks in'
1368466961 J * marcel__ ~marcel@pd95c7474.dip0.t-ipconnect.de
1368466973 M * ard http://paste.linux-vserver.org/23831
1368466975 M * Bertl_oO now, if this is a bug, missing feature, or just okay probably depends on the usage pattern
1368467003 M * Bertl_oO a guest using ipv6 only probably should have an ipv6 loopback
1368467015 M * csh-harmful I hope so
1368467022 M * ard let me check that :-)
1368467024 M * Bertl_oO (and no ipv4 loopback address, that is)
1368467045 M * ard I don't see a ::1 on lo...
1368467077 M * ard this is a "very busy" production proxy, but it all seems to just work without the ::1
1368467104 M * ard http://paste.linux-vserver.org/23832
1368467141 M * ard Maybe something wrong with my networknamespaces in this case... I will check it
1368467170 M * Bertl_oO ipv6 loopback was added after 3.2
1368467177 M * ard ah :-)
1368467185 J * ccxCZ ~ccxCZ@156.200.broadband11.iol.cz
1368467192 M * Bertl_oO so neither you nor csh-harmful will have that
1368467205 M * csh-harmful So I need to have newer kernel ?
1368467239 M * Bertl_oO yes and no, if all you need is ipv4 loopback, then simply add an ipv4 address (dummy, unused) to the guest
1368467244 A * ard runs 3.7 :-)
1368467252 M * Bertl_oO the ipv4 loopback will show up and work ...
1368467278 M * ard of course with the patch against the spinlock deadlock ;_)
1368467280 M * Bertl_oO ard: ah, sorry then, in this case, ip isolation should give you an ipv6 loopback
1368467411 M * Bertl_oO note that the ipv6 loopback stuff is not really well tested 
1368467429 M * ard Hmmmm, is it possible there is a bug in ipv6 loopback, ip isolation combined with network namespaces?
1368467429 M * csh-harmful it's a good time to test then
1368467468 M * ard http://paste.linux-vserver.org/pastebin.php
1368467475 M * Bertl_oO ard: maybe, do you use ip isolation in addition to the network namespaces?
1368467476 M * ard doesn't list a loopback for ipv6 :-)
1368467479 M * ard yes
1368467494 M * Bertl_oO csh-harmful: yeah, please test and let us know what works and what doesn't
1368467534 M * ard It works pretty wel for ipv4, and ipv6 seems working too.
1368467537 M * Bertl_oO ard: you probably want to disable the loopback mapping completely, the network namespace should give you a proper device setup
1368467541 M * ard except for the missing ::1
1368467555 Q * nkukard Read error: Connection timed out
1368467574 M * ard well, I have a network namespace per DMZ, but there are multiple vservers per DMZ possible :-)
1368467594 M * Bertl_oO ah, okay, then full ip isolation is fine
1368467595 M * ard so it shares the namespace with another vserver
1368467616 M * ard actually, there is always a vserver that just exists to hold the namespace
1368467622 M * Bertl_oO can you enable debugging on a test kernel?
1368467642 M * ard which debuggin? :-)
1368467650 M * Bertl_oO Linux-VServer debugging
1368467667 M * ard ipv6 is not that common, so it wouldn't hurt in production
1368467702 M * Bertl_oO i.e. CONFIG_VSERVER_DEBUG=y
1368467747 M * csh-harmful I don't see lo UP at all if no IPv4, I see lo UP if I have bogus IPv4 on interface, but no ::1 on lo. Kernel is 3.7.10-vs2.3.5.6+lihas1
1368467750 M * ard oh wait... it is generic this one ... cool
1368467774 M * ard Bertl_oO : the fun part is, that ipv6 is completely turned "off" on the host and other vservers
1368467897 M * ard bah... can't use them because they are  in use. But it shows that most things just work correctly with network namespaces.
1368467908 A * ard thought these servers were experimental
1368467915 M * ard I will turn on debugging at home
1368467944 Q * ser Ping timeout: 480 seconds
1368467952 M * Bertl_oO okay, if you don't figure how to enable the actual debug messages, just let me know, I'll explain it
1368467953 J * nkukard ~nkukard@197.87.148.190
1368467992 M * ard It's not just enabling the kernel option? Or do I have to say what I want debugged?
1368468017 M * Bertl_oO you configure it via kernel command line or simpler via sysctl interface
1368468034 J * hijacker_ ~hijacker@cable-84-43-134-121.mnet.bg
1368468035 Q * thierryp Remote host closed the connection
1368468042 M * Bertl_oO bascially you can enable/disable the messages by subsystem and group
1368468060 M * ard Ah, so it won't say anything until I say so... I can probably fix the development server with that :-)
1368468060 M * Bertl_oO (otherwise the kernel log would be flooded :)
1368468260 J * ser ~ser@host1.tldp.ibiblio.org
1368468321 M * csh-harmful Should I have /sys inside vserver ?
1368468566 M * Bertl_oO you can have it if you mount it, but it isn't required and by default it isn't mounted
1368468776 J * imcsk8 ~ichavero@148.229.1.11
1368469125 J * Aiken ~Aiken@2001:44b8:2168:1000:21f:d0ff:fed6:d63f
1368469840 J * thierryp ~thierry@home.parmentelat.net
1368470619 Q * thierryp Ping timeout: 480 seconds
1368470911 J * FireEgl ~FireEgl@173-25-83-57.client.mchsi.com
1368471074 J * BenG_ ~bengreen@host-92-27-135-217.static.as13285.net
1368471252 Q * BenG_ 
1368472083 J * thierryp ~thierry@2a01:e35:2e2b:e2c0:98ba:1302:d609:2da9
1368475434 M * Bertl_oO off to bed now ... have a good one everyone!
1368475440 N * Bertl_oO Bertl_zZ
1368477249 Q * hijacker_ Quit: Leaving
1368477319 Q * ser Ping timeout: 480 seconds
1368477899 J * ser ~ser@host1.tldp.ibiblio.org
1368479032 Q * bonbons Quit: Leaving
1368479738 Q * thierryp Remote host closed the connection
1368479949 Q * ser Ping timeout: 480 seconds
1368479969 J * thierryp ~thierry@2a01:e35:2e2b:e2c0:1586:634e:bd70:2d1c
1368480262 J * ser ~ser@host1.tldp.ibiblio.org
1368480640 Q * nlm_ Read error: Connection reset by peer
1368480669 J * nlm_ ~nlm@host211.200-43-249.telecom.net.ar
1368480679 Q * thierryp Remote host closed the connection
1368481725 Q * nlm_ Ping timeout: 480 seconds
1368482499 J * thierryp ~thierry@home.parmentelat.net
1368482899 Q * ser Ping timeout: 480 seconds
1368482987 Q * thierryp Ping timeout: 480 seconds
1368483109 J * ser ~ser@host1.tldp.ibiblio.org
1368483695 Q * PowerKe_ Quit: leaving
1368483707 J * nlm ~nlm@host211.200-43-249.telecom.net.ar
1368483929 Q * ser Ping timeout: 480 seconds
1368484106 J * ser ~ser@host1.tldp.ibiblio.org
1368484624 Q * ser Ping timeout: 480 seconds
1368484656 J * ser ~ser@host1.tldp.ibiblio.org
1368485848 J * PowerKe ~tom@94-227-30-112.access.telenet.be
1368486029 Q * ser Ping timeout: 480 seconds
1368486135 J * thierryp ~thierry@home.parmentelat.net
1368486210 Q * nlm Ping timeout: 480 seconds
1368486320 J * ser ~ser@host1.tldp.ibiblio.org
1368486619 Q * thierryp Ping timeout: 480 seconds
1368487471 Q * Ghislain Quit: Leaving.
1368488345 J * nlm ~nlm@host211.200-43-249.telecom.net.ar