Re: Getting verbose output during boot

On Wed, 16 May 2018, Neale Ferguson wrote: > The problem appears to be related to this message during the > build of the initramfs: > > error: Failed to initialize NSS library > > This left initrd.img in a less than stellar state. The initrd [Initial Ram Disk] is generated into an appropriately

Re: Getting verbose output during boot

The problem appears to be related to this message during the build of the initramfs: error: Failed to initialize NSS library This left initrd.img in a less than stellar state. -- For LINUX-390 subscribe / signoff / archive

Re: Getting verbose output during boot

>>> On 5/16/2018 at 02:01 PM, Neale Ferguson wrote: > Unfortunately, this is the boot that is associated with installing the > product. If I could just get the boot to fail and drop into the shell I might > be able to discern what's happening. Unfortunately, systemd just

Re: single user mode under z/VM

On Wednesday, 05/16/2018 at 07:16 GMT, Rick Troth wrote: > If you're on bare metal, you can use *SYSASCII*. Never done that. (Wish > z/VM would support it for remote access.) I have envisioned a VM telnet <-> guest virtual SYSACII connection to bypass TN3270E. No need for

Re: Getting verbose output during boot

There are thousands who hope you're taking copious notes whenever SystemD is cause of or contributor to the problem. -- R; <>< On 05/16/2018 02:01 PM, Neale Ferguson wrote: > Unfortunately, this is the boot that is associated with installing the > product. If I could just get the boot to fail

Re: single user mode under z/VM

On 05/16/2018 02:23 PM, Terri C. Glowaniak wrote: > Just wondering what 'console' people use to access their Linux systems when > using 'single user mode' ... 3270, IUCV, or ? "yes" *IUCV* is best, if you have an IUCV terminal server running. You can SSH into the terminal server, hop to the

single user mode under z/VM

Just wondering what 'console' people use to access their Linux systems when using 'single user mode' ... 3270, IUCV, or ? Thanks, Terri Glowaniak -- For LINUX-390 subscribe / signoff / archive access instructions, send

Re: Getting verbose output during boot

Unfortunately, this is the boot that is associated with installing the product. If I could just get the boot to fail and drop into the shell I might be able to discern what's happening. Unfortunately, systemd just ends up spitting out an endless stream of messages. On 5/16/18, 13:08, "Linux

Re: Getting verbose output during boot

Greetings, I know this may sound odd, but I would start by setting the grub environment to boot this instance into single user mode if you can. Be aware that "systemd" is new and quite controversial, and in many ways is likely buggy. So the approach I would take once I was on the system as

Re: Getting verbose output during boot

So the log is filling with: systemd-udevd[468]: unable to receive ctrl connection: Function not implemented On 5/16/18, 12:23, "Neale Ferguson" wrote: Thanks Mark. Using debug=1 I see a number of these messages appearing every 30-60 seconds or so: [

Re: Getting verbose output during boot

On 16.05.2018 17:02, Neale Ferguson wrote: I have built a new image to boot our 7.5.1804 system and it is behaving strangely. After booting it goes through the normal startup but then no messages appears for about 6 minutes. No I/O but lots of syscalls (#CP TR SVC) but no console messages. I

Re: Getting verbose output during boot

Thanks Mark. Using debug=1 I see a number of these messages appearing every 30-60 seconds or so: [ 57.090377] systemd-journald[65]: /run/log/journal/43be8124b31c43fe9edc24238dc923cb/system.journal: Allocation limit reached, rotating. [ 57.090394] systemd-journald[65]: Rotating... [

Re: Getting verbose output during boot

>>> On 5/16/2018 at 11:02 AM, Neale Ferguson wrote: > I have built a new image to boot our 7.5.1804 system and it is behaving > strangely. After booting it goes through the normal startup but then no > messages appears for about 6 minutes. No I/O but lots of syscalls (#CP

Getting verbose output during boot

I have built a new image to boot our 7.5.1804 system and it is behaving strangely. After booting it goes through the normal startup but then no messages appears for about 6 minutes. No I/O but lots of syscalls (#CP TR SVC) but no console messages. I am wondering if there is a boot parameter to

Re: [EXTERNAL] Re: zLinux tools and toys site for Developers

On 15 May 2018 at 19:31, Chu, Raymond wrote: We do use it extensively on our development environment to clean things up > after the evening compliance scanning and backups that are memory > intensive. It runs at a random minute in the 4am hour to avoid running it > on all