=== ErichEickmeyer is now known as Eickmeyer
=== ramon_g_ is now known as ramon_g
=== coreycb_ is now known as coreycb
=== fyx_ is now known as fyx
=== peltre_ is now known as peltre
=== altmasteroman is now known as masteroman
=== lotuspsychje__ is now known as lotuspsychje
[06:16] <lordievader> Good morning
=== Xbert is now known as Guest11415
[09:25] <cpaelzer> jamespage: coreycb: can you do me a favor and check a few openstacks we have deployed and check if openstack ends up constructing the cpu out of features
[09:25] <cpaelzer> meaning a CPU name and a long list of feature enable/disable in libvirt
[09:26] <cpaelzer> I think we talked about that in the past and it was that way (trying to create the common denominator for migration)
[09:26] <cpaelzer> and if so could you please check if the openstacks we have defined the feature "osxsave" or "ospke" ?
[09:26] <cpaelzer> (this is a re-ping from yesterday)
[09:45] <cpaelzer> jamespage: coreycb: the above is most likely if you every used cpu type host-model on x86
[10:39] <axino> cpaelzer: https://pastebin.canonical.com/p/vyfG2mfgR8/ random instance I'm wokring on
[10:40] <axino> cpaelzer: https://pastebin.canonical.com/p/5K5GDfTpWR/
[10:41] <cpaelzer> thanks axino
=== amurray` is now known as amurray
[11:20] <cpaelzer> axino: that matches what I found on other systems - thanks!
[11:40] <geodb27> People : hi ! I wanted to try out nova-lxd on a brand new vm with ubuntu-18.04 LTS server, so I followed what I found over here : https://javacruft.wordpress.com/2019/04/17/openstack-stein-for-ubuntu-18-04-lts/ (installed the repository and did a apt update). However, "apt-get install -y nova-lxd" fails with : "E: Unable to locate package nova-lxd" . What am I doing wrong ?
[11:44] <cpaelzer> geodb27: I think it is called nova-compute-lxd
[11:46] <geodb27> Thanks for your answer cpaelzer. I'll give it a try. However, I thought I had understood that nova-lxd was a meta package to ensure that, as stated on the page I linked to : "The 'nova-lxd' package ensures that the nova-compute daemon is started with the correct hypervisor driver for LXD;"
[11:48] <cpaelzer> geodb27: src:nova-lxd builds binary nova-compute-lxd (and others)
[11:48] <cpaelzer> maybe there was a rename at some point - I don't know details
[11:48] <geodb27> oh, great ! Then I'll see how it works when it is all installed !
=== inteus_ is now known as inteus
=== gislaved15 is now known as gislaved
=== tinwood_ is now known as tinwood
[17:25] <neildugan> I am having trouble with a remote login using Remmina ... I can log into various account on the server but one gives me trouble... when I give the correct username & password. After a while I get the a "Connection Log" dialog with the message "login successful for display 10" "starting connecting" "connection problem, giving up" ... anyone know what is wrong with this account
[17:30] <tomreyn> neildugan: which protocol are you using for the remote connection?
[17:30] <tomreyn> remmina supports several, so this can make quite the difference
[17:32] <neildugan> tomreyn, RDP
[17:40] <tomreyn> neildugan: so the remote system runs which OS?
[17:40] <neildugan> tomreyn, Ubuntu 18.04
[17:41] <tomreyn> neildugan: and the client runs ubuntu, too?
[17:41] <neildugan> tomreyn, yes
[17:41] <tomreyn> and you use RDP rather than VNC there because?
[17:42] <tomreyn> maybe Windows / OS X clients also access this remote system?
[17:42] <neildugan> tomreyn, it works (at least for the other accounts)
[17:43] <tomreyn> have you tried to connect from a command line rdp client such as freerdp?
[17:43] <tomreyn> i think this is what remmina actually uses, too
[17:43] <neildugan> tomreyn, I am using Ubuntu exclusively
[17:44] <tomreyn> personally i'd prefer VNC then, but surely the protocol choice is up to you.
[17:45] <tomreyn> so using freerdp may provide better info on what is failing, and surely you should also inspect the server side RDP server logs.
[17:45] <neildugan> tomreyn, any ideas on why only one account doesn't allow login... all the others do, there are 5 or 6 of them
[17:47] <tomreyn> neildugan: sorry, my crystal ball is currently in repair.
[17:49] <tomreyn> neildugan: check the rdp server and system logs (the latter about authentication), try logging in from the remote system to itself.
[17:50] <neildugan> tomreyn, ha ha ... ok ... do you know where the rdp server logs are
[17:51] <maeud> for Windows neildugan ?
[17:51] <sarnold> lsof on the server may show the log file locations
[17:51] <sarnold> maybe they go through journalctl?
[18:01] <tomreyn> neildugan: there is no rdp serve rinstalled by default, so one of your admins must have installed it. maybe start with    dpkg -l | grep rdp
[18:02] <tomreyn> rdp is tcp 5390 isn't it?
[18:02] <tomreyn> ah no 3389
[18:02] <tomreyn> so     lsof -i:3389    will also tell you the process accepting those connections
[18:03] <tomreyn> and once you have the process you find its installation path using "which processname". and once you got this, you can "dpkg -S installationpath" to get the package providing this command.
[20:44] <greyboop> just noticed live-installer/net-image as an option for preseeding. I tried it out using the hwe-netboot kernel/initrd to pxe boot it but its not downloading the squashfs file. Any ideas what I need to do to get the live-installer running?
[21:05] <null_r3f> Does server 18.10 come with fail2ban or a firewall on by default? Scanning this server with nmap is leading to a lot of no responses on live services.
[21:27] <RoyK> null_r3f: apt install fail2ban ufw
[21:27] <RoyK> ufw allow ssh ; ufw enable
[21:27] <RoyK> take it from there
[21:27] <RoyK> then configure fail2ban
[21:28] <RoyK> null_r3f: very few distros come with these things enabled by default, for good reasons - they make it harder for newbies to setup things and make them work
[21:28] <RoyK> and it can be enabled in seconds
[21:28] <null_r3f> RoyK, just trying to do some troubleshooting. Wanted to make sure these features weren't enabled out of the box