[00:00] prefconfig ubuntu-server.seed cannot be found [00:59] had to mount to /cdrom myfault [00:59] entropygain: is there a specific reason that you're trying to install this (very unusual) way? [00:59] ease of disk encryption on a remote system [01:00] hmm i don't think i can follow [01:00] disk encryption + LVM is super easy using the alternative installer [01:00] this worked though I am very happyu [01:00] I only have Finnix [01:00] why don't you just boot the system you want to install on from the iso (written to a bootable storage) and use the intstallers' partitioning tool to setup the encryption? [01:01] what is "finnix"? [01:01] so I made a raw drive and pulled the .iso image in [01:01] but then it was not recognizing the cdrom past the keyboard setup [01:01] so i had to open the shell [01:01] and mount the disk to /cdrom [01:01] and all is well now [01:01] maybe if I somehow wrote to /cdrom in the first place this would have been easier [01:01] I wrote to /dev/sda [01:02] Finnix is some sort of system that my provider allows me to use as a rescue [01:02] so its like an outside system that has bash and internet where I can mount the disks alottet to my account [01:02] so you can't boot this system off the iso? [01:03] i can boot the system off of the raw disk where I wrote the ISO [01:03] but in the process after setting up keyboard it does not recognize my cd [01:04] which hosting provider is this, if you don't mind disclosing this? [01:05] linode [01:05] ok, i have no first hand experience with them. what you can probably do is to use debootrap to install ubuntu from the running finnix system [01:06] however, the latet finnix release seems to be from 4 years ago, probably not an ideal installation environment. but it will liekely still work. [01:09] linode provides an imaging function where you can just have them create an ubuntu installation for you. it won't be encrypted and adding the full disk encryption later is, while possible, not that easy. but if you had them setup a bootable ubuntu for you this way, then added a second empty volume, and used ubuntu to install to the other volume, that should work out fine. [01:11] here's another approach, looks even easier: https://www.linode.com/docs/security/encryption/use-luks-for-full-disk-encryption/ [07:14] <[rg]> is password login is disabled by ubuntu server on default? [08:28] <_KaszpiR_> for root? yes [08:29] <_KaszpiR_> but it really depends on what preseed configig was used when creating that server [08:29] _KaszpiR_: he left [08:29] <_KaszpiR_> ah, the joy of hidden join/part/quit [10:10] Hi. I'm looking for tricky software. I want it to read STDOUT and STDERR of application and if something appears in STDERR then get last N strings from STDOUT and send to remote server so I can see source of problem. I can't find it in google. Anyone know something like this? [10:21] this is built in to linux bash - do want a way to extract the data? or something else - basically, it's a one line thing [10:21] Azlligia: ^ [10:27] weedmic, my idea is that I launch my code on multiple servers and my code logs errors to STDERR. If error occurs then I want to receive last 1000 lines of STDOUT on my central server/email/messenger. So I can debug it. [10:30] Azlligia: I cannot tell if you are asking or telling something - here is an example of how to dump errors to a file - the imporant part is 2> - rsync -aprv root@172.20.1.25:/DATA/ACTIVE/ /mnt/weekly/01-MON/ 2>> /home/weedmic/CRONs/MONbackuplog.txt [10:32] weedmic, I will try to explain. I want to receive last 1000 lines of log ONLY if error occurs. I need not only error, but last 1000 lines of STDOUT too. [10:37] weedmic, Something like "reporterrors myapp" which will run "myapp" and listen for STDERR and remember last 1000 lines of STDOUT. If something appears in STDERR then send 1000 lines of STDOUT and STDERR to my server. I hope you understand what my idea is. [10:37] i just don't grep what you mean. You can dump all errors to a file, then grep out the lines you want 1000 or whatever. Although I can't imagine have that many errors. [10:41] weedmic, 1000 lines of STDOUT, not STDERR. So STDOUT will will be like "user joined", "user sent message: hell'o" and STDERR will be like "Server crashed due to syntax error". If I will receive only STDERR without seeing STDOUT I will not know what happened. What did user sent to server. [10:43] And I will be unable to reproduce error without seeing STDOUT. [15:33] Azlligia: you shouldn't log to STDOUT; just send everything to STDERR [15:33] or use proper logs (journald and/or syslog) [15:34] STDERR is *NOT* meant for error messages only [15:36] STDERR is meant for “printing diagnostic or error messages” [15:38] but really, you should be logging to a proper logging facility, which has timestamps etc., and then get whatever you need from there [15:38] Azlligia: like others have suggested, use journal or syslog. you can set severity to messages and thus have more than just two levels. === svetlana is now known as Sveta