[00:31] <gunix> guys, any idea how i can change boot order from maas ?
[00:31] <gunix> i just rebooted the servers and they all defaulted to pxe boot
[00:31] <gunix> i just want them to boot the OS
[00:32] <bradm> well, the boot order is a computer thing
[00:33] <bradm> if you boot them and it pxe boots, maas should have nothing for it, so it should then boot from disk
[01:05] <gunix> bradm: well booting from disk is failing which is strange
[01:05] <gunix> and no idea why maas set the boot order for pxe first
[01:06] <bradm> gunix: if its failing to boot from disk I'd say that has nothing to do with maas, but more with whats on the disk
[01:11] <RoyK> gunix: trying to dual-boot?
[01:11] <sarnold> RoyK: I think gunix is just trying to deploy a machine with maas, nothing fancy
[07:07] <lordievader> Good morning
[08:37] <adac> Hmm I created /var/log/journal directory and my servera gain crashed tonight. There is a file in it now that I wanted to check on what has happened
[08:37] <adac> but the file seems be pretty much binary
[08:38] <adac> ah i need to read it with journalctl -b
[08:38] <adac> 1
[08:39] <adac> hmm but still again there are no old messages in there
[08:39] <adac> only from the last boot If I do:
[08:39] <adac> journalctl -b 1
[08:39] <adac>  /var/log/journal/35a754864d1e47469f9af2c0262f700e/system.journal
[10:23] <blackflow> adac: did you check the standard syslog? journald is forwarding to it by default.
[10:25] <adac> blackflow, yes in syslog I see the time before the machine stopped/was not reachable
[10:25] <adac> but I cannot see what happened
[10:25] <adac> only when the machine is rebooted there are entries again
[10:25] <adac> before there is no error indicating what is happening
[10:40] <blackflow> adac: sounds like a hard crash reboot, and when those happens it's usually due to faulty hardware like memory
[11:47] <gunix> bradm: RoyK: sarnold: The first deployment was ok but something happened after that. Now all deployments are failing. I noticed there was an issue when I tryed to reboot the servers and all failed to boot.
[11:47] <gunix> this is highly confusing
[12:34] <mojtaba> Hello, If I want to keep a process running on the remote machine, even after exiting ssh, should I run screen on my local machine and ssh in screen to the remote machine and run my command? Is there any other way?
[12:35] <ahasenack> mojtaba: nohup
[12:35] <ahasenack> ssh machine
[12:35] <ahasenack> nohup <start-your-process>
[12:35] <ahasenack> logout
[12:35] <mojtaba> ahasenack: Is it like screen?
[12:36] <ahasenack> no, it will just prevent the process from getting the HUP signal when you logout
[12:36] <ahasenack> if it's something interactive, or something that prints stuff to the console that you want to see later,
[12:36] <ahasenack> then I recommend to use screen/byobu on the remote machine
[12:36] <ahasenack> ssh machine
[12:36] <ahasenack> byobu
[12:36] <ahasenack> start process
[12:36] <ahasenack> ctrl-a d
[12:36] <ahasenack> logout
[12:36] <mojtaba> ahasenack: thanks
[12:48] <gunix> ahasenack: do you have any idea why machines that got previously deployed by MAAS are now failing deployment ?
[12:50] <ahasenack> gunix: not without more data, no
[12:51] <gunix> ahasenack: what data would you need?
[12:51] <ahasenack> start by clicking on such a machine in the maas gui, inspect the data you get there. Notably installation logs
[12:51] <gunix> there are not installation logs.
[12:51] <ahasenack> if that's empty, try watching the machine's console while it deploys until it fails
[12:52] <ahasenack> and the events tab in maas
[12:52] <ahasenack> you might also want to hangout in the #maas irc channel, that's more specific than ubuntu server
[12:52] <ahasenack> I idle there as well
[12:52] <gunix> ahasenack: events: https://bpaste.net/show/811673766cfc
[12:53] <gunix> nobody on #maas is answering
[12:53] <gunix> i think they have no idea how the software works cause when i ask a more complex questions it's silence
[12:53] <gunix> but they are answering questions to easy questions :D
[12:54] <ahasenack> watch the console then
[12:54] <ahasenack> it's usually what I do when debugging such a problem with my nodes
[12:54] <gunix> ahasenack: this si the console: https://ibb.co/nc9q9n
[12:55] <gunix> it's stuck there .
[12:55] <ahasenack> it doesn't tell me if that's the first boot or second boot
[12:55] <ahasenack> during deployment there is a first boot, where the installer comes up and installs the ubuntu release on the disk
[12:55] <ahasenack> then it reboots into the newly installed system
[12:56] <ahasenack> do you see evidence in the console, as messages scroll by, that it was able to reach the network to install packages and download stuff?
[12:58] <gunix> https://bpaste.net/show/00edf81fcd8b
[12:58] <gunix> aaand it faield.
[12:59] <TJ-> middle of that photo is a line that reads 'object XXXX from LD_PRELOAD cannot be preloaded (cannot open shared object file). ignored'
[12:59] <adac> blackflow, thanks for the hint, I will contact my hosting provider!
[13:00] <gunix> TJ-: i saw that line but i have no idea how to interpret that
[13:00] <ahasenack> rbasak: if I could pick your brain for a minute wrt a packaging question
[13:00] <TJ-> gunix: nor me, but it was the only anomaly visible
[13:01] <gunix> TJ-: yea and it doesn't tell me anything
[13:01] <gunix> ahasenack: from my point of view it seems like it is getting the image since that is the only way cloudinit could be obtained .
[13:01] <ahasenack> rbasak: package contents: https://pastebin.ubuntu.com/p/vnKrkqNczH/
[13:01] <ahasenack> rbasak: the files under nvml_dbg are triggering an ldconfig call, flagged by the lintian as undesirable
[13:01] <ahasenack> rbasak: upstream told me this about those files:
[13:01] <ahasenack> "Files under nvml_dbg are builds with debugging symbols, logging, asserts
[13:01] <ahasenack> and expensive checks that we normally don't want users to run with."
[13:02] <ahasenack> rbasak: I'm wondering if they should be shipped in another package then, and what its name could be
[13:02] <ahasenack> libfoo-extra-debugging? Is there a precedence for this?
[13:02] <ahasenack> gunix: hm, no, cloudinit data is passed down via another way
[13:02] <ahasenack> gunix: do you see it reboot once, after doing a bunch of stuff?
[13:03] <ahasenack> gnuoy: anyway, in general, the debugging of such failures is either around the actual image installation on disk (that's the first boot), or networking problems
[13:03] <ahasenack> it does run apt-get at some point, so it needs to be able to reach the internet or a mirror
[13:03] <gunix> ahasenack: no, i don't see it reboot
[13:04] <ahasenack> try to ssh to the node while it's stuck in that powered-on state
[13:04] <gnuoy> ahasenack, I think gunix and I are different people
[13:04] <ahasenack> if you added your key to maas, you should be able to ssh in as ubuntu
[13:04] <ahasenack> gnuoy: hah
[13:04] <gnuoy> :)
[13:04] <gunix> ahasenack: i will recheck network config but that is ok afaik
[13:05] <ahasenack> try ssh in and poking around
[13:05] <ahasenack> also make sure you selected the right disk for your root partition in the node in maas
[13:05] <ahasenack> if there is more than one
[13:05] <ahasenack> it also pays to check the partitioning in general, and network config, in the node's page
[13:06] <gunix> ahasenack: network is ok
[13:06] <rbasak> ahasenack: looking
[13:08] <gunix> ahasenack: this is the exact config that was working a few days ago
[13:08] <gunix> that's why this is highly confusing
[13:09] <gunix> the server is still stuck there btw ... at deleting temporary files
[13:09] <ahasenack> gunix: if it was commissioned, then the hardware view maas has of the node changed to reflect the current state
[13:09] <ahasenack> did you ssh in?
[13:09] <rbasak> ahasenack: for a first iteration I'd remove them from the build. I think it's incorrect to ship them in the -dev package.
[13:10] <ahasenack> was your maas installed as a snap?
[13:10] <ahasenack> rbasak: they are more than just debugging symbols
[13:10] <rbasak> ahasenack: the package can be fully functional without them, right?
[13:10] <rbasak> You don't have to provide every development feature upstream provides in a package build.
[13:10] <ahasenack> rbasak: yes, but supposedly upstream would want them somewhere when debugging sometihng. They are installed by "make install"
[13:11] <rbasak> Upstream wouldn't use the distribution package build to debug though, would they?
[13:11] <gunix> ahasenack: i installed using "apt instal maas" on ubuntu 16.04
[13:12] <ahasenack> rbasak: it's a new package, they might ask users to do stuff
[13:12] <ahasenack> I'll propose we remove those files, but wanted to get another opinion
[13:12] <ahasenack> specially if there was precedence for this in ubuntu, an extra-debugging package
[13:12] <rbasak> I imagine the right way to package both, if you really want to package both, would be to provide an alternate libfooX binary package with some other name that conflicts and provides it, so they could ask users to switch to that one instead.
[13:12] <ahasenack> there is no need to conflict
[13:13] <ahasenack> and those extra libs are not used since they are not in the linker's path. I suppose upstream would ask users to set LD_LIBRARY_PATH before some debugging task
[13:13] <rbasak> I don't think that's appropriate for a distribution package.
[13:13] <ahasenack> but, their placement is enough to trigger debhelper's automatic ldconfig call
[13:13] <rbasak> But this is perhaps a discussion from #ubuntu-devel.
[13:20] <rbasak> ahasenack: I think my issue with weird things like this is that the package isn't a special snowflake and users shouldn't have to know about special per-package snowflakes before being able to do things like this. The (reasonable) desire to have a debugging version with extra assertions but lower performance is a generic one. The distribution should provide a generic solution. And the mechanism we
[13:20] <rbasak> have for that is drop in replacement packages via conflicts/provides. Not weird stuff to do with getting the user to override paths.
[13:20] <rbasak> The point of a distribution is to unify these things.
[13:21] <ahasenack> so there is a precedence with special builds that are drop-in replacements and have more logging/debugging/checks?
[13:22] <rbasak> I'm not sure about specifically for libraries.
[13:22] <rbasak> But there are plenty of packages that provide varying functionality depending on the user's package selection.
[13:22] <rbasak> exim for example.
[13:22] <rbasak> People in #ubuntu-devel may know more
[13:23] <rbasak> I'm also unsure about simultaneously providing a concrete package and a virtual package that conflicts with it.
[13:24] <rbasak> I'd want to read and/or test a bit more before committing to that.
[13:24] <rbasak> In the meantime, IMHO it's not worth blocking to figure this out.
[13:24] <ahasenack> I asked them how they would expect end users to use these files, and if we can drop them
[13:25] <ahasenack> in the meantime, a test build confirmed the lintian ldconfig warning is gone when I remove them
[13:25] <rbasak> This kind of thing is very common.
[13:25] <rbasak> Upstreams need to understand that the point of a distribution is to unify things, and they shouldn't expect to be able to do every weird thing that they do in a distribution package.
[13:26] <ahasenack> also that nvml_dbg dir mixes devel and runtime builds of the library
[13:26] <ahasenack> I assume you could link to a debugging version of the library and get more info in your app
[13:26] <ahasenack> so that means two extra packages per library: dev and runtime
[13:26] <ahasenack> if we go down that route
[13:27] <rbasak> dev, normal runtime, normal runtime with debugging symbols, debugging runtime, debugging runtime with debugging symbols.
[13:27] <rbasak> It might be possible to collapse the last two down, as debugging runtime without debugging symbols makes no sense.
[13:28] <ahasenack> it might if it's just about exrta logging
[13:28] <rbasak> If you want to do any of this, I would speak to an archive admin now on how you plan to arrange everything to save any wasted effort.
[13:28] <ahasenack> I also asked to confirm if this extra logging cannot be enabled via env vars
[13:29] <ahasenack> I'm hoping I can just drop that dir
[14:12] <pgaxatte> hello
[14:13] <pgaxatte> coreycb: I tested the changes you submitted on mistral (https://bugs.launchpad.net/cloud-archive/+bug/1757433) and it works for me on Xenial for both pike and queens version
[14:14] <pgaxatte> coreycb: however I'm not familiar with launchpad and I don't get how I am supposed to "change the tag from verification-pike-needed to verification-pike-done"
[14:51] <TJ-> pgaxatte: edit the tags (below the description box)
[14:54] <pgaxatte> TJ-: ah yes on the original comment :)
[14:55] <pgaxatte> TJ-:  i mean the first one which is the description :)
[14:56] <pgaxatte> TJ-, coreycb: done!
[15:09] <ahasenack> hm, I have this lintian warning that I'm trying to override:
[15:09] <ahasenack> W: libpmemlog-dev: manpage-has-errors-from-man usr/share/man/man3/libpmemlog.3.gz 235: warning: macro `..,' not defined
[15:09] <ahasenack> I created debian/source/lintian-overrides
[15:09] <ahasenack> with
[15:09] <ahasenack> libpmemlog-dev binary: manpage-has-errors-from-man
[15:09] <ahasenack> reubilt
[15:09] <ahasenack> but the warning is still there
[15:09] <ahasenack> when I run "lintian" from the build directory
[15:09] <ahasenack> do I need to install the package?
[15:22] <lolek> hello
[15:27] <lolek> maybe you guy will have some idea.  I've got two machines, ubuntu 12.04 and ubuntu 16.04 both have exact same sudoers config file, on both machines the users have almost identical groups (with one eception of one group the one for the virtualmachine), now when I try to run this command: /usr/bin/sudo -k -u lolek /bin/true   on U16.04 I don't get pw prompt while on U12.04 the prompt is there
[15:28] <lolek> *guys
[15:38] <rbasak> lolek: have you looked in /etc/sudoers.d/?
[15:38] <rbasak> lolek: also, remember that sudo caches the fact that you entered the password. There's some default expiry time set.
[15:39] <lolek> rbasak: yes, but in both cases the sudoers file has got commented out that include for sudoers.d
[15:39] <lolek> rbasak: also for the cache is not a problem here as I'm using the -k switch
[15:39] <rbasak> I don't know then, sorry.
[15:40] <TJ-> lolek: how about /etc/pam.d/sudo  ?
[15:41] <lolek> TJ-: checked, the same :/
[15:41] <TJ-> lolek: check /var/log/auth.log on both machines for differences/clues
[15:42] <lolek> right ... hmm let me find it
[15:42] <lolek> I should also mention that u12.04 has got sudo 1.8.3p1 while 16.04 has got version 1.8.16
[15:43] <TJ-> lolek: I cannot reproduce your issue here on 12.04 and 16.04 I see password prompt
[15:45] <lolek> TJ-: you've used your current user right?
[15:46] <TJ-> lolek: I've tried several user accounts
[15:46] <lolek> :/
[15:46] <lolek> you've got original sudoers file?
[15:50] <lolek> TJ-: ok that's interesting .. in auth.log somehow on 12.04 the user is represented in the auth.log having id 1000 but on u16.04 the id is 0
[15:50] <lolek> o.O
[15:50] <TJ-> lolek: well that'd do it!
[15:51] <lolek> TJ-: well yeah but why..
[15:51] <TJ-> lolek: well start off with 'getent passwd lolek'
[15:51] <lolek> when I do id lolek on 16.04 and 12.04 the id is not 0
[15:51] <TJ-> lolek: is sudo or /bin/true setuid root ?
[15:52] <lolek> nope
[15:52] <lolek> both machines same rights
[15:55] <lolek> TJ-: do you have 18.04 at hand?
[15:55] <TJ-> lolek: yes
[15:55] <lolek> as I checked clean 18.04 installation and it's the same, it doesn't ask for pw
[15:55] <lolek> and also in the auth.log the user id is...0
[16:00] <TJ-> lolek: as i said earlier, it's /etc/pam.d/sudo -- on 12.04 it's 'auth' but on 16.04+ it's 'session'
[16:01] <lolek> oh
[16:01] <lolek> missed this one
[16:01] <lolek> hmm
[16:04] <lolek> TJ-: well I've changed it to auth on 18.04 and it still doesn't ask for pw :/
[16:07] <lolek> I'm wondering where it's taking that uid = 0
[16:22] <TJ-> lolek: what does the 16.04  /etc/sudoers look like, can you pastebin it?
[16:22] <lolek> TJ-: sure, a sec
[16:23] <lolek> TJ-: http://pasteall.org/889746
[16:23] <lolek> here it's the default one
[16:23] <lolek> tbh it's logical that it won't ask for pw if I want to switch to current user
[16:23] <lolek> but the question is why on 12.04 it asks for it
[16:23] <lolek> a bug?
[16:27] <TJ-> I wonder if it's been added since. I checked the Debian changelog and didn't see mention but there were several upstream releases in between so they may have brought it in
[16:31] <lolek> mhm
[16:32] <TJ-> lolek: is sudo-ldap installed on any of them?
[16:33] <lolek> I don't see any sudo-ldap package so no
[18:04] <mojtaba> Hello, I am going to write a script to make a backup when a specific computer joins the network. I want to repeat the process, until the directory is fully backed up. Could you please let me know how can I improve this code? http://paste.ubuntu.com/p/TbwKWcT5rz/
[18:19] <blackflow> mojtaba: why don't you just ping 192.168.2.17 ?
[18:19] <blackflow> you don't even have to sleep you can set, say, 30 seconds between two pings
[18:20] <mojtaba> blackflow: ping -i 300 ?
[18:20] <blackflow> that's a bit too long
[18:21] <blackflow> one icmp packet every 30 seconds should be more than enough.
[18:21] <mojtaba> blackflow: ping -i 30 ?
[18:23] <mojtaba> blackflow: Do you know how should I check if rsync has been successful?
[18:23] <mojtaba> blackflow: should it be rsync && exit or rsync && break?
[18:23] <blackflow> mojtaba: yes, but actually I think you'll have to put that into a loop and send one packet only, to have ping exit with success or failure
[18:24] <blackflow> so something like ping -c1 -i 30    in a loop and when it exits with success, the host has replied
[18:24] <mojtaba> blackflow: Can I grep the exit of ping?
[18:26] <blackflow> exit code? no, it's available in something like $?  depending on your shell
[18:26] <mojtaba> blackflow: it is bash
[18:27] <blackflow> you can also do things like     while true; do ping -c1 192.168.2.17 > /dev/null && break; done
[18:27] <blackflow> that will wait until ping exits with success.  oh and I forgot -i
[18:28] <mojtaba> So I have to replace this with until statement in my code?
[18:29] <blackflow> yup
[18:29] <mojtaba> blackflow: what about the rsync part? should it be rsync && break?
[18:29] <blackflow> rsync should also return success or failure, so you can test its output
[18:29] <mojtaba> blackflow: How can I test its output?
[18:30] <blackflow> however, note that rsync can report error on things like files changed during transfer, but otherwise having successful transfer
[18:30] <blackflow> mojtaba: $? contains last set exit code
[18:30] <mojtaba> blackflow: Thanks. I will check it.
[18:32] <blackflow> mojtaba: also consider using ~/.ssh/config instead of ssh options on the command line
[18:32] <mojtaba> blackflow: sure, thanks.
[22:31] <boxrick> I am after a minimal ISO installer without needing internet access. Is there any way to achieve that similar to CentOS?
[22:49] <ChmEarl> boxrick, thats what the ubuntu-server ISO is. Its a CD with about 300 packages, enough to do a minimal install
[22:50] <boxrick> I always thought it had a fit when it didn't get any network
[22:50] <boxrick> Perhaps I am wron
[22:50] <boxrick> wrong* then
[22:51] <ChmEarl> boxrick, I admit , I never used it when competely disconnected from internet
[22:52] <ChmEarl> boxrick, perhaps use this ISO as a debootstrap source