Nagios agent for SLES 12 SP5

Does anyone use Nagios on their SLES servers? We are currently using SNMP to report up to Nagios but it is somewhat lacking. Chris The information contained in this communication is highly confidential and is intended solely for the use of the individual(s) to whom this communication is

Re: Sles 12 with ibm Flashsystem 9500

27Gb Master... Looks Like a big memory leak :-( Em qui., 11 de mai. de 2023 20:19, Mark Post escreveu: > On 5/11/2023 5:46 PM, Rogério Soares wrote: > > I see a lot of oom-killer when dd > > runs.. > > This sounds like you need to increase the amount of memory defined for > this system. > > >

Re: Sles 12 with ibm Flashsystem 9500

On 5/11/2023 5:46 PM, Rogério Soares wrote: I see a lot of oom-killer when dd runs.. This sounds like you need to increase the amount of memory defined for this system. PMR opened with IBM Glad to hear it. Mark Post

Re: Sles 12 with ibm Flashsystem 9500

ote: > > Hello folks, anyone is using ibm Flashsystem 9500 with Sles 12? I'm > facing > > strange behavior after Mount disks Sles stay very very slow, when try > > copy any data, Sles crash.. > > What version of SLES12? Are you up to date on maintenance? Have you >

Re: Sles 12 with ibm Flashsystem 9500

On 5/11/2023 9:19 AM, Rogério Soares wrote: Hello folks, anyone is using ibm Flashsystem 9500 with Sles 12? I'm facing strange behavior after Mount disks Sles stay very very slow, when try copy any data, Sles crash.. What version of SLES12? Are you up to date on maintenance? Have you

Sles 12 with ibm Flashsystem 9500

Hello folks, anyone is using ibm Flashsystem 9500 with Sles 12? I'm facing strange behavior after Mount disks Sles stay very very slow, when try copy any data, Sles crash.. I have adjusted multipath.conf as suggested by ibm, but no luck yet

Re: GRUB - DRACUT error on SLES 12 SP5

On 10/15/21 11:12 AM, Victor Echavarry wrote: dracut-initqueue[418]: Warning: Could not boot. Starting Dracut Emergency Shell... Warning: /dev/swapvg/swap01lv does not exist Generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit the shell to continue. Type

GRUB - DRACUT error on SLES 12 SP5

After patching a guest and reboot it, we find the following error: Booting default (grub2) dracut-initqueue[418]: Warning: dracut-initqueue timeout - starting timeout scri pts dracut-initqueue[418]: Warning: dracut-initqueue timeout - starting timeout scri pts dracut-initqueue[418]: Warning:

Re: unstable LVM on SLES 12

On 4/14/20 8:17 AM, Csaba Polgar wrote: > Hello, > > In the past, there was an attempt to upgrade a Linux system from SLES11 SP4 > to SLES 12 SP4, but it was not successful because of the missing disks > after OS upgrade. > We saw the below error messages in the SLES11 SP4: >

Re: unstable LVM on SLES 12

are not used by the system.   Once this is done then I would try an offline upgrade from 11 SP4 to 12 SP4.  BTW - SLES 12 SP5 is released and I strongly encourage upgrading  11 SP4 to this version. Have you on the customer's behalf or the customer opened a support request to get ideas

unstable LVM on SLES 12

Hello, In the past, there was an attempt to upgrade a Linux system from SLES11 SP4 to SLES 12 SP4, but it was not successful because of the missing disks after OS upgrade. We saw the below error messages in the SLES11 SP4: hostname:~ # lvs | grep "Attr\|ao--p&

Re: NSS not possible in SLES 12

Port To: LINUX-390@VM.MARIST.EDU Subject: Re: NSS not possible in SLES 12 ++1 You guys are going backwards DJ --- DAVID JONES | MANAGING DIRECTOR FOR ZSYSTEMS SERVICES | z/VM, Linux, and Cloud 703.237.7370 (Office) | 281.578.7544 (CELL) INFORMATION TECHNOLOGY COMPANY On 09.04.2019 12:03 PM

Re: NSS not possible in SLES 12

On Thursday, 09/05/2019 at 06:35 GMT, Scott Rohling wrote: > I think the implications extend beyond NSS though... is SLES going to > divorce itself from embedded systems in general? Are they all in on self > patching kernels and that's that? Or can it simply be an option to > exploit when

Re: NSS not possible in SLES 12

On 9/5/19 2:35 PM, Scott Rohling wrote: > I think the implications extend beyond NSS though... is SLES going to > divorce itself from embedded systems in general? Are they all in on self > patching kernels and that's that? Or can it simply be an option to > exploit when desirable? I don't

Re: NSS not possible in SLES 12

I think the implications extend beyond NSS though... is SLES going to divorce itself from embedded systems in general? Are they all in on self patching kernels and that's that? Or can it simply be an option to exploit when desirable? Scott Rohling On Thu, Sep 5, 2019 at 9:57 AM Alan

Re: NSS not possible in SLES 12

: Thursday, September 5, 2019 9:51 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] NSS not possible in SLES 12 On Wednesday, 09/04/2019 at 08:16 GMT, Dave Jones wrote: > ++1 > You guys are going backwards I haven't seen much traction with the NSS in the field. Within an organization,

Re: NSS not possible in SLES 12

On Wednesday, 09/04/2019 at 08:16 GMT, Dave Jones wrote: > ++1 > You guys are going backwards I haven't seen much traction with the NSS in the field. Within an organization, Linux servers are maintained in a common way across platforms, with different servers on different schedules. NSS

Re: NSS not possible in SLES 12

I’m really curious how the embedded systems folks took this latest “improvement”. By this argument, Intel and ARM systems running from EPROM are no longer viable, or at least will require a forklift upgrade - are they expecting to always copy the entire kernel into RAM and allow it to modify

Re: NSS not possible in SLES 12

On 04.09.19 21:03, Rick Troth wrote: > On 9/4/19 11:39 AM, Christian Borntraeger wrote: >> On 04.09.19 16:41, Scott Rohling wrote: >>> Let's start with who or what said it wasn't possible ? >> [...] Just to be sure, by "nss" I meant Named Saved System. >> [...] > what is the

Re: NSS not possible in SLES 12

Jones Sent: Wednesday, September 4, 2019 3:31 PM To: LINUX-390@VM.MARIST.EDU Subject: [EXT] Re: NSS not possible in SLES 12 [Actual Sender is owner-linux-...@vm.marist.edu] ++1 You guys are going backwards DJ --- DAVID JONES | MANAGING DIRECTOR FOR ZSYSTEMS SERVICES | z/VM, Linux, and Cloud

Re: NSS not possible in SLES 12

++1 You guys are going backwards DJ --- DAVID JONES | MANAGING DIRECTOR FOR ZSYSTEMS SERVICES | z/VM, Linux, and Cloud 703.237.7370 (Office) | 281.578.7544 (CELL) INFORMATION TECHNOLOGY COMPANY On 09.04.2019 12:03 PM, Rick Troth wrote: On 9/4/19 11:39 AM, Christian Borntraeger wrote: On

Re: NSS not possible in SLES 12

On 9/4/19 11:39 AM, Christian Borntraeger wrote: > On 04.09.19 16:41, Scott Rohling wrote: >> Let's start with who or what said it wasn't possible ? > [...] >>> Just to be sure, by "nss" I meant Named Saved System. > [...] what is the reason for nss not being possible with SLES from

Re: NSS not possible in SLES 12

On 04.09.19 16:41, Scott Rohling wrote: > Let's start with who or what said it wasn't possible ? [...] >> Just to be sure, by "nss" I meant Named Saved System. [...] >>> what is the reason for nss not being possible with SLES from version 12? [...] The Linux kernel now makes use of

Re: NSS not possible in SLES 12

on may be. Regards, András BEKE From: Scott Rohling To: LINUX-390@VM.MARIST.EDU Date: 04/09/2019 16:42 Subject:[EXTERNAL] Re: NSS not possible in SLES 12 Sent by:Linux on 390 Port Let's start with who or what said it wasn't possible ? In my experience - most

Re: NSS not possible in SLES 12

Let's start with who or what said it wasn't possible ? In my experience - most things are possible ... though there maybe roadblocks. Scott Rohling On Wed, Sep 4, 2019 at 5:51 AM Andras Beke wrote: > Just to be sure, by "nss" I meant Named Saved System. > > Regards, > > András BEKE

Re: NSS not possible in SLES 12

Just to be sure, by "nss" I meant Named Saved System. Regards, András BEKE > Dear List, > > apologies if I'm asking something evident, the reason being I'm a newbie > both on the list and in the speciality, but does any of you happen to know > what is the reason for nss not being possible with

NSS not possible in SLES 12

Dear List, apologies if I'm asking something evident, the reason being I'm a newbie both on the list and in the speciality, but does any of you happen to know what is the reason for nss not being possible with SLES from version 12? Thank you in advance. Regards, András BEKE

Re: iucvconn setup on SLES 12

Still having issues. I have upgraded both the terminal server and test guest to SLES 12 SP4 which gives a s390tools version of 2.1 or so. Our requirements are to be able to view the console log during shutdown and startup since we no longer have access to a 3270 console or HMC. If you have

Re: Devices for dracut in sles 12 SP4

on its way. hopefully openable! thank you! -Original Message- From: Linux on 390 Port On Behalf Of Mark Post Sent: Tuesday, June 11, 2019 10:09 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Devices for dracut in sles 12 SP4 On 6/11/19 1:05 PM, Marcy Cortes wrote: > If

Re: Devices for dracut in sles 12 SP4

On 6/11/19 1:05 PM, Marcy Cortes wrote: > If you can't, I can email you a copy. Please, do. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message:

Re: Devices for dracut in sles 12 SP4

@VM.MARIST.EDU Subject: Re: [LINUX-390] Devices for dracut in sles 12 SP4 On 6/10/19 3:52 PM, Marcy Cortes wrote: > Does anyone know how dracut is really supposed to be told about devices? I > was under the impression that all devices were allowed unless explicity in a > cio_ignore when runnin

Re: Devices for dracut in sles 12 SP4

On 6/11/19 11:51 AM, Cohen, Sam wrote: > I'm going to ask a religious questionif you're running under z/VM and > (ideally) giving the virtual machine only what it needs, why would you use > cio_ignore at all? That's exactly why Ihno and I successfully lobbied to get the default changed for

Re: Devices for dracut in sles 12 SP4

Of Mark Post Sent: Tuesday, June 11, 2019 8:24 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Devices for dracut in sles 12 SP4 On 6/10/19 3:52 PM, Marcy Cortes wrote: > Does anyone know how dracut is really supposed to be told about devices? I > was under the impression that all devices were a

Re: Devices for dracut in sles 12 SP4

On 6/10/19 3:52 PM, Marcy Cortes wrote: > Does anyone know how dracut is really supposed to be told about devices? I > was under the impression that all devices were allowed unless explicity in a > cio_ignore when running under z/VM. That's been the default for new installations on z/VM for a

Devices for dracut in sles 12 SP4

Resending from other ID – maybe have been blocked for many (like me!) -- After some patching this weekend, we had a few servers go into dracut emergency mode. After a lot of pain and rescue system work,  we found it didn't

Devices for dracut in sles 12 SP4

After some patching this weekend, we had a few servers go into dracut emergency mode. After a lot of pain and rescue system work, we found it didn't know about a couple of the devices in the VG group that housed some needed stuff. We found this in the dracut /run/initram/rdsosreport.txt you

Re: iucvconn setup on SLES 12

On 5/30/19 1:15 PM, Will, Chris wrote: > I have this sort of working. It will display a few messages and then close > the connection. I connect again and it will display a few messages, close, > etc. -snip- > # ssh nbxdv392@slxmfdev3 > Password: > Last login: Thu May 30 11:45:26 2019 from

Re: dasd_configure in SLES 12 SP4

for that. -Original Message- From: Linux on 390 Port On Behalf Of Mark Post Sent: Friday, May 31, 2019 10:42 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] dasd_configure in SLES 12 SP4 On 5/31/19 6:47 AM, Michael MacIsaac wrote: > Why? Doing so will break scripts we have ... Beca

Re: dasd_configure in SLES 12 SP4

Mark, Thanks for a thorough reply. We have been warned :)) -Mike M On Fri, May 31, 2019 at 1:43 PM Mark Post wrote: > On 5/31/19 6:47 AM, Michael MacIsaac wrote: > > Why? Doing so will break scripts we have ... > > Because they require maintenance, cause bug reports (such as Marcy's), >

Re: dasd_configure in SLES 12 SP4

On 5/31/19 6:47 AM, Michael MacIsaac wrote: > Why? Doing so will break scripts we have ... Because they require maintenance, cause bug reports (such as Marcy's), etc., etc. They're not going away tomorrow, but please plan ahead. One of the complaints we hear is that "doing X on SLES for the

Re: dasd_configure in SLES 12 SP4

On Fri, May 31, 2019 at 12:48 PM Michael MacIsaac wrote: > Mark, > > > The wrappers will be removed at some point in the future. > Why? Doing so will break scripts we have ... > > Same here. I would urge SuSE to keep them. --

Re: dasd_configure in SLES 12 SP4

Mark, > The wrappers will be removed at some point in the future. Why? Doing so will break scripts we have ... -Mike On Thu, May 30, 2019 at 5:06 PM Mark Post wrote: > On 5/30/19 4:54 PM, Marcy Cortes wrote: > > Should I just be using that chzdev command now? > > Yes. Starting with

Re: dasd_configure in SLES 12 SP4

|", "r|/dev/fd.*|", "r|/dev/cdrom|", "a/.*/" ] So not sure what is up with that... -Original Message- From: Linux on 390 Port On Behalf Of Mark Post Sent: Thursday, May 30, 2019 2:04 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] dasd_c

Re: dasd_configure in SLES 12 SP4

On 5/30/19 4:54 PM, Marcy Cortes wrote: > Should I just be using that chzdev command now? Yes. Starting with SLES12 SP4, the following SUSE-provided scripts: ctc_configure dasd_configure qeth_configure zfcp_disk_configure zfcp_host_configure are simply wrappers for the chzdev command. The

dasd_configure in SLES 12 SP4

So it seems to return an 8 now on SP4 , which messes up my scripting :( myhost:~ # export DEBUG=yes myhost:~ # dasd_configure 0.0.8002 1 0 All the parms passed were -- '0.0.8002' '1' '0' Found the end of parms indicator: -- chzdev -e dasd --no-root-update 0.0.8002 use_diag=0 ECKD DASD 0.0.8002

Re: iucvconn setup on SLES 12

: iucvconn setup on SLES 12 ALERT This email was sent from a source external to BCBSM/BCN. DO NOT CLICK links or attachments unless you recognize the sender and trust the content. On 5/30/19 1:15 PM, Will, Chris wrote: > I have this sort of working. It will display a few messages and then cl

Re: iucvconn setup on SLES 12

We are at SLES 12 SP3 ~ sept 2018 patch level Information for package s390-tools: --- Repository : SLES12-SP3-Updates:testing Name : s390-tools Version: 1.34.0-65.20.1 Chris Will Enterprise Linux/UNIX (ELU) (313) 549-9729 Cell cw...@bcbsm.com

Re: iucvconn setup on SLES 12

On 5/30/19 1:15 PM, Will, Chris wrote: > I have this sort of working. It will display a few messages and then close > the connection. I connect again and it will display a few messages, close, > etc. That sounds vaguely familiar to me. Let me ask the obligatory question: are you up to date on

Re: iucvconn setup on SLES 12

...@bcbsm.com -Original Message- From: Linux on 390 Port On Behalf Of David Boyes Sent: Saturday, May 25, 2019 3:01 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: iucvconn setup on SLES 12 ALERT This email was sent from a source external to BCBSM/BCN. DO NOT CLICK links or attachments

Re: iucvconn setup on SLES 12

On 5/24/19, 9:16 AM, "Linux on 390 Port on behalf of Alan Altmark" wrote: >While I've always wanted to see it virtualized and the VM telnet server >given a way to connect to it (meaning no client/host translations or >conversions) Amen to both. Constructing an analogue to a

Re: iucvconn setup on SLES 12

On Thursday, 05/23/2019 at 07:38 GMT, David Boyes wrote: > IBM tried to introduce an HMC feature to provide a character-mode > console, but it never worked the way most people wanted it to work, so this is > the result. While I've always wanted to see it virtualized and the VM telnet server

Re: iucvconn setup on SLES 12

On 5/23/19, 11:18 AM, "Linux on 390 Port on behalf of Will, Chris" wrote: >Is there any advantage to setting up a terminal server Yes. Think of it as analogous to attaching the console ports of your discrete servers without built-in management processors to a hardware terminal server so you

iucvconn setup on SLES 12

Currently we have had good success using iucvconn on our SLES 11 SP4 servers. We use it mostly for a server that goes into emergency repair mode and we need a console. Based on some one of the newer z/VM cookbooks, I thought this was already setup for SLES 12 and there are hvc terminals

SLES 12 "Tuning/Optimization Guide" for s390x?

As many sites are upgrading from SLES 11 to SLES 12, I was curious if there were any specific references or known standards regarding "tunable parameters" related to s390x? Outside of the obvious things like setting the vm.swappiness to something other than the default of "60&

Re: SUSE SLES 12 missing PHP extensions

Hi Mark, Thank you for your reply. It turns out that I just downloaded the source from a PHP branch closes to the version delivered by SLES 12 and compiled the Tidy module and used it in my system. I reported this as a bug but it took months to get any answer so I moved on. Tidy was one

Re: SUSE SLES 12 missing PHP extensions

>>> On 1/2/2018 at 02:42 PM, Aria Bamdad wrote: > Hi, > > > > I have an application that requires the PHP-Tidy extension among others. > Previously with SLES 11, this extension, among others was provided by SUSE > for PHP 5.2 that came with SLES 11. N

Documentation about upgrading from SLES 11 SP4 to SLES 12 SP3 with "silent mode"?

Could somebody provide a link, documentation or a draft about upgrading from SLES 11 SP4 to SLES 12 SP3 with "silent mode" (without interaction)? Kind Regards, Csaba Polgar -- For LINUX-390 subscribe / signoff / arch

Re: Problems with perl after sles 11 sp4 to sles 12 sp2 upgrade

, 2018 7:04 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Problems with perl after sles 11 sp4 to sles 12 sp2 upgrade >>> On 3/19/2018 at 03:03 PM, "Will, Chris" <cw...@bcbsm.com> wrote: > I ran the upgrade and everything seemed ok until I ran a perl job (in > this case

Re: Problems with perl after sles 11 sp4 to sles 12 sp2 upgrade

>>> On 3/19/2018 at 03:03 PM, "Will, Chris" <cw...@bcbsm.com> wrote: > I ran the upgrade and everything seemed ok until I ran a perl job (in this > case smt-agent). It seems the @INC variable is still pointing to the older > 5.10 version and not 5.18 that com

Re: Problems with perl after sles 11 sp4 to sles 12 sp2 upgrade

- From: te...@wellsfargo.com [mailto:te...@wellsfargo.com] Sent: Tuesday, March 20, 2018 12:34 PM To: LINUX-390@VM.MARIST.EDU Cc: marcy.d.cor...@wellsfargo.com; Will, Chris <cw...@bcbsm.com> Subject: RE: Problems with perl after sles 11 sp4 to sles 12 sp2 upgrade Check your environment too.

Re: Problems with perl after sles 11 sp4 to sles 12 sp2 upgrade

ase advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Marcy Cortes [mailto:marcy.d.cor...@wellsfargo.com] Sent: Monday, March 19, 2018 12:34 PM Subject: Re: Problems with perl after sles 11 sp4 to sles 12 sp2 upgr

Re: Problems with perl after sles 11 sp4 to sles 12 sp2 upgrade

old stuff that will never get patched. Marcy -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Will, Chris Sent: Monday, March 19, 2018 12:04 PM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Problems with perl after sles 11 sp4 to sles 12 sp2 upgr

Problems with perl after sles 11 sp4 to sles 12 sp2 upgrade

I ran the upgrade and everything seemed ok until I ran a perl job (in this case smt-agent). It seems the @INC variable is still pointing to the older 5.10 version and not 5.18 that comes with SLES 12. Is there any way to refresh this or reinstall perl to correct this? # smt-agent Can't

Re: SLES 12 upgrade fails

om > To: LINUX-390@VM.MARIST.EDU > Cc: > Date: Mar 16, 2018, 11:55:58 PM > Subject: Re: [LINUX-390] SLES 12 upgrade fails > > > So someone needs to reply and include my comments so all can see but it > appears that various mail providers are attempting to protect you from

Re: SLES 12 upgrade fails

For those who didn't see this Alan On Mar 16, 2018, 11:55:58 PM, marcy.d.cor...@wellsfargo.com wrote: From: marcy.d.cor...@wellsfargo.com To: LINUX-390@VM.MARIST.EDU Cc: Date: Mar 16, 2018, 11:55:58 PM Subject: Re: [LINUX-390] SLES 12 upgrade fails So someone needs to reply and include

Re: SLES 12 upgrade fails

DU<mailto:LINUX-390@VM.MARIST.EDU>> Subject: Re: [LINUX-390] SLES 12 upgrade fails Marcy's posts have been going to my spam folder. That just started happening recently. Tom Duerbusch THD Consulting On Wed, Mar 14, 2018 at 9:56 PM, Alan Ackerman <alan.ackerma...@gmail.com> wrote:

Re: SLES 12 upgrade fails

ything about SLES 12 upgrade fails on the web page. > > Sent from my iPhone > > On Mar 14, 2018, at 5:15 PM, Gregg Levine <gregg.drw...@gmail.com> wrote: > > Hello! > > Mark as interesting as our discussions are, there is a more > interesting problem, I'm not se

Re: SLES 12 upgrade fails

pam folder. It happens to a few other >> posts as well, but not often or consistently enough to diagnose. >> >> Mike Walter >> >> From: Alan Ackerman >> Sent: Wednesday, March 14, 9:58 PM >> Subject: Re: SLES 12 upgrade fails >> To: linux-390@vm.marist.ed

Re: SLES 12 upgrade fails

...@ventura.org -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mike Riggs Sent: Thursday, March 15, 2018 5:33 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES 12 upgrade fails Whew.. I thought it was just me. It would be great to get this resolved as her

Re: SLES 12 upgrade fails

, 2018 8:24 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES 12 upgrade fails This happens consistently for my mail system - her posts are put in the spam folder with this explanation: This message has a from address in wellsfargo.com but has failed wellsfargo.com's required tests

Re: SLES 12 upgrade fails

t; > From: Alan Ackerman > Sent: Wednesday, March 14, 9:58 PM > Subject: Re: SLES 12 upgrade fails > To: linux-390@vm.marist.edu > > > I have the same problem — I am not seeing Marcy’s posts. I also don’t see > anything about SLES 12 upgrade fails on the web page. Sent from my iP

Re: SLES 12 upgrade fails

: SLES 12 upgrade fails To: linux-390@vm.marist.edu I have the same problem — I am not seeing Marcy’s posts. I also don’t see anything about SLES 12 upgrade fails on the web page. Sent from my iPhone On Mar 14, 2018, at 5:15 PM, Gregg Levine wrote: Hello! Mark as interesting as our discussions

Re: SLES 12 upgrade fails

I have the same problem — I am not seeing Marcy’s posts. I also don’t see anything about SLES 12 upgrade fails on the web page. Sent from my iPhone On Mar 14, 2018, at 5:15 PM, Gregg Levine <gregg.drw...@gmail.com> wrote: Hello! Mark as interesting as our discussions are, there is

Re: SLES 12 upgrade fails

Hello! Mark as interesting as our discussions are, there is a more interesting problem, I'm not seeing anything by Marcy except as a response. That is when someone responds to something that Marcy posted. - Gregg C Levine gregg.drw...@gmail.com "This signature fought the Time Wars, time and

Re: SLES 12 upgrade fails

>>> On 3/14/2018 at 06:20 PM, Marcy Cortes >>> wrote: > Victor has already gotten the networking part to work since the VNC portion > came up and and enough of the media was loaded to put up the license > acceptance and the disk activated Hi, Marcy, Yes, I

Re: SLES 12 upgrade fails

gt;> Date: Wednesday, Mar 14, 2018, 3:13 PM To: LINUX-390@VM.MARIST.EDU <LINUX-390@VM.MARIST.EDU<mailto:LINUX-390@VM.MARIST.EDU>> Subject: Re: [LINUX-390] SLES 12 upgrade fails >>> On 3/13/2018 at 04:02 PM, Victor Echavarry <victor.echava...@evertecinc.com> wrote: >

Re: SLES 12 upgrade fails

>>> On 3/13/2018 at 04:02 PM, Victor Echavarry wrote: > PARMFILE > > ramdisk_size=65536 root=/dev/ram1 ro init=/linuxrc TERM=dumb For SLES12 you can delete everything on this line except for "TERM=dumb". > hostip=10.23.11.246 netmask=255.255.248.0

Re: SLES 12 upgrade fails

, 2018 12:29 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES 12 upgrade fails The problem is the .iso file. You will need to mount that -o loop on the webserver and serve out the content. From: Victor Echavarry <victor.echava...@evertecinc.com<mailto:victor.echava...@evertecinc.com&

Re: SLES 12 upgrade fails

<LINUX-390@VM.MARIST.EDU<mailto:LINUX-390@VM.MARIST.EDU>> Subject: [LINUX-390] SLES 12 upgrade fails We are planning a upgrade of all our z/Linux guest from SLES 11 SP4 to SLES 12 SP3. When executing the upgrade we receive the following message: Failed to execute /init (error -2) Ke

Re: SLES 12 upgrade fails

Victor, Does the virtual machine have at least 1G of memory? -Mike On Tue, Mar 13, 2018 at 4:02 PM, Victor Echavarry < victor.echava...@evertecinc.com> wrote: > We are planning a upgrade of all our z/Linux guest from SLES 11 SP4 to > SLES 12 SP3. When executing the upgrad

SLES 12 upgrade fails

We are planning a upgrade of all our z/Linux guest from SLES 11 SP4 to SLES 12 SP3. When executing the upgrade we receive the following message: Failed to execute /init (error -2) Kernel panic - not syncing: Requested init /linuxrc failed (error -2). CPU: 0 PID: 1 Comm: swapper/0 Not tainted

Re: Upgrade from SLES 11 to SLES 12

For 16 the command is "zypper packages --orphaned" -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Marcy Cortes Sent: Friday, February 9, 2018 4:37 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Upgrade from SLES 11 to S

Re: Upgrade from SLES 11 to SLES 12

My preferred method is to replace the servers! First read all of this (never mind that x86 is in the URL, it does apply to both). https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12-SP3/ Don't forget to check that all of your SW supports it. While you can upgrade, new servers are less risky

Upgrade from SLES 11 to SLES 12

We have 88 guests with SLES 11SP4 on z/VM 6.4, the majority with oracle 11 and 12. The cookbook only show how to made a new installation. We want to know is there a way to upgrade those servers to SLES12. If true: 1. How can we achieved it. DVD, NFS, FTP. 2. How many servers can upgrade

SUSE SLES 12 missing PHP extensions

Hi, I have an application that requires the PHP-Tidy extension among others. Previously with SLES 11, this extension, among others was provided by SUSE for PHP 5.2 that came with SLES 11. Now with SLES 12, PHP 5.5 and 7 are available but for some unknown reason, this extension and other were

Process to clone SLES 12 guest installed on LUN?

omplishing the same using a LUN? Install gold copy image on a LUN (SLES 12 w/LVM). Shut the gold copy server down, clone the FCP LUN, create a new zVM guest and use the cloned FCP LUN instead of doing a new installation again? Also not sure if there are "tools" out there that accomplish this,

Re: Upgrade of SLES 11 SP4 to SLES 12 SP2 on System z

>>> On 8/24/2017 at 01:17 PM, Harley Linker <harley.lin...@ensono.com> wrote: > The deployment guide I refenced is the one I obtained from the SLES 12 SP2 > DVD1 iso file. I did find the parameter in > https://www.suse.com/documentation/sles-12/singlehtml

Re: Upgrade of SLES 11 SP4 to SLES 12 SP2 on System z

>>> On 8/24/2017 at 12:23 PM, Harley Linker wrote: > I am using a PARMFILE containing the following (sanitized): > ramdisk_size=131072 root=/dev/ram1 ro init=/linuxrc term=dumb > vmpoff=logoff hostname= mf-syssoft1 hostip=10.17.1.xxx > gateway=10.17.1.129

Re: Upgrade of SLES 11 SP4 to SLES 12 SP2 on System z

Yes, thanks. The one on the DVD is perhaps outdated. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Harley Linker Sent: Thursday, August 24, 2017 1:17 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Upgrade of SLES 11 SP4 to SLES 12 SP2 on System z

Re: Upgrade of SLES 11 SP4 to SLES 12 SP2 on System z

Aria, The deployment guide I refenced is the one I obtained from the SLES 12 SP2 DVD1 iso file. I did find the parameter in https://www.suse.com/documentation/sles-12/singlehtml/book_sle_deployment/book_sle_deployment.html#sec.appdendix.parm.general. Thanks again! Harley -Original

Re: Upgrade of SLES 11 SP4 to SLES 12 SP2 on System z

. Harley -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Aria Bamdad Sent: Thursday, August 24, 2017 11:37 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Upgrade of SLES 11 SP4 to SLES 12 SP2 on System z Hi Harley, My environment is not the same

Re: Upgrade of SLES 11 SP4 to SLES 12 SP2 on System z

To: LINUX-390@VM.MARIST.EDU Subject: Upgrade of SLES 11 SP4 to SLES 12 SP2 on System z Hi, I am looking to upgrade some of my z/VM based servers from SLES 11 SP4 to SLES 12 SP2 and am wondering if this is possible on System z. My guest is defined as: PROFILE LNXDFLT LOGONBY ... IPL CMS PARM

Upgrade of SLES 11 SP4 to SLES 12 SP2 on System z

Hi, I am looking to upgrade some of my z/VM based servers from SLES 11 SP4 to SLES 12 SP2 and am wondering if this is possible on System z. My guest is defined as: PROFILE LNXDFLT LOGONBY ... IPL CMS PARM AUTOCR CONSOLE 009 3215 T SPOOL 00C 2540 READER A SPOOL 00D 2540 PUNCH A SPOOL 00E

Re: Single user (rescue target) in SLES 12

>>> On 7/5/2017 at 09:29 AM, Steffen Maier wrote: -snip- > Doesn't this take you to single user mode of the "auxiliary" > kernel, i.e. the one of grub2-s390x-emu, rather than your > "target" / production kernel which can be quite different? No, it doesn't. It takes

Re: Single user (rescue target) in SLES 12

(rescue target) in SLES 12 On 6/26/2017 at 03:26 PM, Marcy Cortes <marcy.d.cor...@wellsfargo.com> wrote: One thing I haven't figured out in SLES 12 systemd system is how to boot into single user mode (rescue.target)? On sles 11, I just did a #cp vi vmsg 1 1 Anyone know? You should be able

Re: Single user (rescue target) in SLES 12

>>> On 6/27/2017 at 09:33 AM, Dave Jones <djo...@itconline.com> wrote: > Hi, Mark. > > Is there a list or doc someplace that has all of the valid PARM values > for IPL-ing SLES 12 in addition to the "PARM S" for getting into single > user mode? Mostly

Re: Single user (rescue target) in SLES 12

command correctly before restarting the virtual machine. I'm sure this is old news to many of you, but I thought it worth mentioning. Ray On 2017-06-26 15:26, Marcy Cortes wrote: > One thing I haven't figured out in SLES 12 systemd system is how to boot into > single user mode (rescue.

Re: Single user (rescue target) in SLES 12

Hi, Mark. Is there a list or doc someplace that has all of the valid PARM values for IPL-ing SLES 12 in addition to the "PARM S" for getting into single user mode? Thanks. DJ On 06/26/2017 05:14 PM, Mark Post wrote: > PARM S -- ITC-email-sig *David Jones **|**Managing Director

Re: Single user (rescue target) in SLES 12

Thanks! That is easy to remember! -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: Monday, June 26, 2017 3:15 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Single user (rescue target) in SLES 12 >>> On 6/26/2017

Re: Single user (rescue target) in SLES 12

>>> On 6/26/2017 at 03:26 PM, Marcy Cortes <marcy.d.cor...@wellsfargo.com> >>> wrote: > One thing I haven't figured out in SLES 12 systemd system is how to boot into > single user mode (rescue.target)? > On sles 11, I just did a #cp vi vmsg 1 1 > >

  1   2   3   >