Re: Netplan issues

Hi Dominik,

 > First of all the new packages could not be installed without removing
 > ltsp-docs due to an dependency issue. Was it just me? Then ignore it.

Vagrant merged lts.conf to ltsp-server, so now ltsp-docs is considered 
obsolete and it's ok to have it removed.

About netplan, does it work with either of those commands in lts.conf?

INIT_COMMAND_RM_NETPLAN1="rm -rf /run/netplan"
INIT_COMMAND_RM_NETPLAN2="rm -f /lib/systemd/system-generators/netplan"

Cheers,
Alkis


On 5/28/19 12:29 PM, Dominik Schlöder wrote:
> Hello Everyone
> 
> A week ago I installed ltsp with the greek schools ppa on a new ubuntu 18.04.2
> amd64 server. For the ltsp installation I followed the instructions on the
> ltsp-wiki. I opted out on the installation of epoptes, chose chroot mode,
> DHCPProxy and NBD.
> 
> Now to my problem. I believe the client was working fine, but it stopped
> working the next day (from May 20th to 21st). The client hung on boot with
> several start jobs:
>    - waiting for network
>    - configure keyboard layout
>    - I forgot about the other two
> and throws SQUASHfs errors after some time.
> 
> I believe the problem comes from having no network connection when the
> initramfs switches to the real system. I was glad, when I saw that Alkis fixed
> an Issue on Saturday (May 25th), which is or is similarly to my Problem.
> 
> First of all the new packages could not be installed without removing ltsp-docs
> due to an dependency issue. Was it just me? Then ignore it.
> 
> I installed the packages on the server and it looked like the client boots
> fine. Later, I also upgraded the client packages in the chroot environment and
> now I am back to the aforementioned issue, but with fewer start jobs. I don't
> know if the one time it booted fine was a fluke or is connected to the
> non-updated client image.
> 
> The network configuration finishes, but the boot process still hangs on the
> configuration of the keyboard layout.
> 
> I am using a VM to boot the client. Here is my lts.config:
> [Default]
> #LDM_AUTOLOGIN = True
> # LDM_USERNAME = <<REDACTED>>
> LDM_PASSWORD = <<REDACTED>>
> XKBLAYOUT = de
> XKBVARIANT = basic
> CONSOLE_KEYMAP = de
> LOCALDEV = True
> SOUND = True
> LDM_LIMIT_ONE_SESSION = True
> DNS_SERVER = "192.168.123.254"
> SEARCH_DOMAIN = <<REDACTED>>
> #NETWORK_COMPRESSION = True
> NBD_SWAP = False
> LDM_DIRECTX = True
> LDM_SESSION = "mate-session"
> 
> I tried the following different boot
> parameters:
> NBD:
> label ltsp-NBD
> menu label LTSP, using NBD
> kernel vmlinuz-4.15.0-50-generic
> append ro initrd=initrd.img-4.15.0-50-generic init=/sbin/init-ltsp forcepae root=/dev/nbd0
> ipappend 3
> 
> NFS:
> label ltsp-NFS
> menu label LTSP, using NFS
> kernel vmlinuz-4.15.0-50-generic
> append ro initrd=initrd.img-4.15.0-50-generic init=/sbin/init-ltsp forcepae root=/dev/nfs ip=dhcp boot=nfs
> ipappend 3
> 
> NFS over SQUASHfs (following the instruction of: https://sourceforge.net/p/ltsp/mailman/ltsp-discuss/thread/ffdf8c34-384c-ff56-b61f-82b429e0dd94%40gmail.com/#msg36669125)
> label ltsp-NFS
> menu label LTSP, using NFS
> kernel vmlinuz-4.15.0-50-generic
> append ro initrd=initrd.img-4.15.0-50-generic init=/sbin/init-ltsp forcepae root=/dev/nfs nfsroot=/opt/ltsp/images ltsploop=amd64.img
> ipappend 3
> 
> and NBD to RAM:
> label ltsp-NBD
> menu label LTSP, using NBD
> kernel vmlinuz-4.15.0-50-generic
> append ro initrd=initrd.img-4.15.0-50-generic init=/sbin/init-ltsp forcepae root=/dev/nbd0 LTSP_NBD_TO_RAM=true
> ipappend 3
> 
> Booting with NBD, NFS and SQUASHfs over NFS does not
> change the result, except that NFS hangs after 30 seconds and NBD/SQUASHfs
> over NFS waits forever to finish. Using the option LTSP_NBD_TO_RAM=true with
> NBD boots fine. However, this is only an option for my testing VM, since some
> of our machines only have 2gb of RAM. Addionally with this option I am not able
> to install applications on the client to try things out before I update the
> image due to space constraints on the root fs.
> 
> Lastly I tried configuring netplan in the image. I created following file:
> #/etc/netplan/01-network-manager-all.yaml
> network:
>    version: 2
>    renderer: networkd
>    ethernets:
>      match:
>        name: enp*
>        dhcp4: yes
> #    enp0s3:
> #      dhcp4: yes
> 
> However, this doesn't fix the issue. Any advice or help is appreciated. If all
> fails, maybe someone can tell me how to increase the size of the root fs with
> NBD and LTSP_NBD_TO_RAM, so I can keep testing on the client without always
> building an image. Thank you very much and
> 
> Regards
> Dominik
> 
> On Thu, May 23, 2019 at 2:26 AM Alkis Georgopoulos <alkisg@...> wrote:
>> A few schools reported that after
>> (1) updating Ubuntu 18.04 and
>> (2) running ltsp-update-image,
>> some clients hang on boot and show NBD/squashfs errors, waiting for
>> services to get started etc.
>>
>> This might be due to a recent netplan update:
>> https://bugs.launchpad.net/netplan/+bug/1763608
>> Read my comment #43 there.
>>
>> If this happens to you, put this in lts.conf:
>> INIT_COMMAND_RM_NETPLAN="rm -f /lib/systemd/system-generators/netplan"
>>
>> ...and reply to this mail, so that I upload a new LTSP to the Greek
>> schools PPA.
>>
>>
>> Cheers,
>> Alkis
> 



_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net