Re: Upgrade sles 12sp4 - sles 15

[Mark Pace]

The way I calculate the number of orphans was flawed.  It's only 371 -
still seems like a whole bunch.

On Wed, Mar 20, 2019 at 9:56 AM Mark Pace  wrote:

> Recommended as part of the upgrade is to look for Orphaned packages.
>
> zypper packages --orphaned
>
> Frankly I'm amazed/terrified at the number of Orphaned Packages!  700+
> Can this be right?  And how do I know they aren't really being used?
>
>
>
> On Tue, Mar 19, 2019 at 9:02 AM Mark Pace  wrote:
>
>> So this morning - I tried the following.
>> Added - media_upgrade=1  to the parmfile.
>>
>> Then when asked I pointed the installed to the Packages dvd1 source.
>> Currently the installer is happily running installing packages.
>>
>> There was some message about the registration may now be incomplete, but
>> I think I can deal with that afterwards.
>>
>> On Mon, Mar 18, 2019 at 1:48 PM Lori Grimaldi 
>> wrote:
>>
>>> Maybe this will help:
>>>
>>>https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12-SP3/
>>>
>>> Additionally, there are the following extensions which are not covered by
>>> SUSE support agreements, available at no additional cost and without an
>>> extra registration key:
>>>   SUSE Package Hub: https://packagehub.suse.com/
>>>   SUSE Linux Enterprise Software Development Kit
>>>
>>> Lori Grimaldi
>>> Linux on zSeries Americas Team, Team Lead - Senior
>>> IBM Services
>>> Notes:  leter...@us.ibm.com
>>> Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666
>>> Email Address: leter...@us.ibm.com
>>> IBM
>>>
>>>
>>>
>>>
>>>
>>> From:   Paul Dembry 
>>> To: LINUX-390@VM.MARIST.EDU
>>> Date:   03/18/2019 01:36 PM
>>> Subject:Re: Upgrade sles 12sp4 - sles 15
>>> Sent by:Linux on 390 Port 
>>>
>>>
>>>
>>> > Any progress is good progress.
>>> Unless you are a lemming :-)
>>> Paul
>>>
>>> -Original Message-
>>> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
>>> Mark
>>> Pace
>>> Sent: Monday, March 18, 2019 10:11 AM
>>> To: LINUX-390@VM.MARIST.EDU
>>> Subject: Re: Upgrade sles 12sp4 - sles 15
>>>
>>> Thank you, Lori -
>>> I tried the SUSEConnect --clean  and then register again - and now I
>>> have a
>>> different error message.
>>>
>>> The requested products 'Suse Package Hub 12 SP4 s390x' have not been
>>> activated on the system.
>>>
>>> So I need to go figure out what this means.
>>>
>>> Thank you again.  Any progress is good progress.
>>>
>>> On Mon, Mar 18, 2019 at 12:36 PM Lori Grimaldi 
>>> wrote:
>>>
>>> > I had a problem opened with Microfocus and here is what we did to
>>> resolve:
>>> >
>>> > - Ran SUSEConnect --cleanup
>>> > - Re-Registered system into SCC
>>> > - Upgraded SLES12SP3 to SP4 via zypper migration
>>> > - Upgraded SLES12SP4 to SLES15 via off-line mode
>>> > - Cleaned up gpg key V# warning according
>>> >
>>>
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.suse.com_releasenotes_x86-5F64_SUSE-2DSLES_15_=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4=Hqe7wtWVuyxouUKULbOQJQARQXQCGj0jhZvI_V86APA=tMAUzCDn-1yIZemens8r9HwK0cSyEf1A8pMtOLVAbmk=
>>>
>>> >
>>> > Lori Grimaldi
>>> > Linux on zSeries Americas Team, Team Lead - Senior IBM Services
>>> > Notes:  leter...@us.ibm.com
>>> > Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666 Email Address:
>>> > leter...@us.ibm.com IBM
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > From:   Mark Pace 
>>> > To: LINUX-390@VM.MARIST.EDU
>>> > Date:   03/18/2019 10:00 AM
>>> > Subject:Re: Upgrade sles 12sp4 - sles 15
>>> > Sent by:Linux on 390 Port 
>>> >
>>> >
>>> >
>>> > Thanks, Mark.  Unfortunately that was not the issue.  I used Yast
>>> > Product Registration.  It came back as already registered.  I then
>>> > used Register Again to make sure it was registered.
>>> >
>>> > I may either create a local SMT server, or just build a new SLES 15
>>> > and manually migrate.
>>> >
>>> > O

Re: Upgrade sles 12sp4 - sles 15

[Mark Pace]

Recommended as part of the upgrade is to look for Orphaned packages.

zypper packages --orphaned

Frankly I'm amazed/terrified at the number of Orphaned Packages!  700+
Can this be right?  And how do I know they aren't really being used?



On Tue, Mar 19, 2019 at 9:02 AM Mark Pace  wrote:

> So this morning - I tried the following.
> Added - media_upgrade=1  to the parmfile.
>
> Then when asked I pointed the installed to the Packages dvd1 source.
> Currently the installer is happily running installing packages.
>
> There was some message about the registration may now be incomplete, but I
> think I can deal with that afterwards.
>
> On Mon, Mar 18, 2019 at 1:48 PM Lori Grimaldi  wrote:
>
>> Maybe this will help:
>>
>>https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12-SP3/
>>
>> Additionally, there are the following extensions which are not covered by
>> SUSE support agreements, available at no additional cost and without an
>> extra registration key:
>>   SUSE Package Hub: https://packagehub.suse.com/
>>   SUSE Linux Enterprise Software Development Kit
>>
>> Lori Grimaldi
>> Linux on zSeries Americas Team, Team Lead - Senior
>> IBM Services
>> Notes:  leter...@us.ibm.com
>> Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666
>> Email Address: leter...@us.ibm.com
>> IBM
>>
>>
>>
>>
>>
>> From:   Paul Dembry 
>> To: LINUX-390@VM.MARIST.EDU
>> Date:   03/18/2019 01:36 PM
>> Subject:Re: Upgrade sles 12sp4 - sles 15
>> Sent by:Linux on 390 Port 
>>
>>
>>
>> > Any progress is good progress.
>> Unless you are a lemming :-)
>> Paul
>>
>> -Original Message-
>> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
>> Mark
>> Pace
>> Sent: Monday, March 18, 2019 10:11 AM
>> To: LINUX-390@VM.MARIST.EDU
>> Subject: Re: Upgrade sles 12sp4 - sles 15
>>
>> Thank you, Lori -
>> I tried the SUSEConnect --clean  and then register again - and now I have
>> a
>> different error message.
>>
>> The requested products 'Suse Package Hub 12 SP4 s390x' have not been
>> activated on the system.
>>
>> So I need to go figure out what this means.
>>
>> Thank you again.  Any progress is good progress.
>>
>> On Mon, Mar 18, 2019 at 12:36 PM Lori Grimaldi 
>> wrote:
>>
>> > I had a problem opened with Microfocus and here is what we did to
>> resolve:
>> >
>> > - Ran SUSEConnect --cleanup
>> > - Re-Registered system into SCC
>> > - Upgraded SLES12SP3 to SP4 via zypper migration
>> > - Upgraded SLES12SP4 to SLES15 via off-line mode
>> > - Cleaned up gpg key V# warning according
>> >
>>
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.suse.com_releasenotes_x86-5F64_SUSE-2DSLES_15_=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4=Hqe7wtWVuyxouUKULbOQJQARQXQCGj0jhZvI_V86APA=tMAUzCDn-1yIZemens8r9HwK0cSyEf1A8pMtOLVAbmk=
>>
>> >
>> > Lori Grimaldi
>> > Linux on zSeries Americas Team, Team Lead - Senior IBM Services
>> > Notes:  leter...@us.ibm.com
>> > Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666 Email Address:
>> > leter...@us.ibm.com IBM
>> >
>> >
>> >
>> >
>> >
>> > From:   Mark Pace 
>> > To: LINUX-390@VM.MARIST.EDU
>> > Date:   03/18/2019 10:00 AM
>> > Subject:Re: Upgrade sles 12sp4 - sles 15
>> > Sent by:Linux on 390 Port 
>> >
>> >
>> >
>> > Thanks, Mark.  Unfortunately that was not the issue.  I used Yast
>> > Product Registration.  It came back as already registered.  I then
>> > used Register Again to make sure it was registered.
>> >
>> > I may either create a local SMT server, or just build a new SLES 15
>> > and manually migrate.
>> >
>> > On Fri, Mar 15, 2019 at 7:15 PM Mark Post  wrote:
>> >
>> > > On 3/15/19 4:25 PM, Mark Pace wrote:
>> > > > This is then end - the lines before this are the panel being
>> displayed.
>> > >
>> > > I think there are a number of lines before then that would be
>> > > useful, but given what you're showing, I have to ask if this system
>> > > is registered, with either SCC or a local SMT server? The sense I'm
>> > > getting is that YaST is asking the registration server what
>> > > migration products are available for the currently installed

Re: Upgrade sles 12sp4 - sles 15

[Mark Pace]

So this morning - I tried the following.
Added - media_upgrade=1  to the parmfile.

Then when asked I pointed the installed to the Packages dvd1 source.
Currently the installer is happily running installing packages.

There was some message about the registration may now be incomplete, but I
think I can deal with that afterwards.

On Mon, Mar 18, 2019 at 1:48 PM Lori Grimaldi  wrote:

> Maybe this will help:
>
>https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12-SP3/
>
> Additionally, there are the following extensions which are not covered by
> SUSE support agreements, available at no additional cost and without an
> extra registration key:
>   SUSE Package Hub: https://packagehub.suse.com/
>   SUSE Linux Enterprise Software Development Kit
>
> Lori Grimaldi
> Linux on zSeries Americas Team, Team Lead - Senior
> IBM Services
> Notes:  leter...@us.ibm.com
> Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666
> Email Address: leter...@us.ibm.com
> IBM
>
>
>
>
>
> From:   Paul Dembry 
> To: LINUX-390@VM.MARIST.EDU
> Date:   03/18/2019 01:36 PM
> Subject:Re: Upgrade sles 12sp4 - sles 15
> Sent by:Linux on 390 Port 
>
>
>
> > Any progress is good progress.
> Unless you are a lemming :-)
> Paul
>
> -----Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark
> Pace
> Sent: Monday, March 18, 2019 10:11 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Upgrade sles 12sp4 - sles 15
>
> Thank you, Lori -
> I tried the SUSEConnect --clean  and then register again - and now I have a
> different error message.
>
> The requested products 'Suse Package Hub 12 SP4 s390x' have not been
> activated on the system.
>
> So I need to go figure out what this means.
>
> Thank you again.  Any progress is good progress.
>
> On Mon, Mar 18, 2019 at 12:36 PM Lori Grimaldi 
> wrote:
>
> > I had a problem opened with Microfocus and here is what we did to
> resolve:
> >
> > - Ran SUSEConnect --cleanup
> > - Re-Registered system into SCC
> > - Upgraded SLES12SP3 to SP4 via zypper migration
> > - Upgraded SLES12SP4 to SLES15 via off-line mode
> > - Cleaned up gpg key V# warning according
> >
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.suse.com_releasenotes_x86-5F64_SUSE-2DSLES_15_=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4=Hqe7wtWVuyxouUKULbOQJQARQXQCGj0jhZvI_V86APA=tMAUzCDn-1yIZemens8r9HwK0cSyEf1A8pMtOLVAbmk=
>
> >
> > Lori Grimaldi
> > Linux on zSeries Americas Team, Team Lead - Senior IBM Services
> > Notes:  leter...@us.ibm.com
> > Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666 Email Address:
> > leter...@us.ibm.com IBM
> >
> >
> >
> >
> >
> > From:   Mark Pace 
> > To: LINUX-390@VM.MARIST.EDU
> > Date:   03/18/2019 10:00 AM
> > Subject:Re: Upgrade sles 12sp4 - sles 15
> > Sent by:Linux on 390 Port 
> >
> >
> >
> > Thanks, Mark.  Unfortunately that was not the issue.  I used Yast
> > Product Registration.  It came back as already registered.  I then
> > used Register Again to make sure it was registered.
> >
> > I may either create a local SMT server, or just build a new SLES 15
> > and manually migrate.
> >
> > On Fri, Mar 15, 2019 at 7:15 PM Mark Post  wrote:
> >
> > > On 3/15/19 4:25 PM, Mark Pace wrote:
> > > > This is then end - the lines before this are the panel being
> displayed.
> > >
> > > I think there are a number of lines before then that would be
> > > useful, but given what you're showing, I have to ask if this system
> > > is registered, with either SCC or a local SMT server? The sense I'm
> > > getting is that YaST is asking the registration server what
> > > migration products are available for the currently installed
> > > product(s), and is getting a null answer, possibly because it's not
> registered:
> > > *2019-03-15 16:23:16 <1> sles003.s390.mainline.com <
> >
> > https://urldefense.proofpoint.com/v2/url?u=http-3A__sles003.s390.mainl
> > ine.com=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=0O2Q0N3bhw8wToDxvSVQtC4OUF
> > vEgeKgNzzJ7wh_xG4=UeUdErz6SEwDmmv1KCoDqn6gCwC1beUjX1EFnrwpo5s=tUid
> > 9VAs-uO5lMrs4DZMC2_yCwFqva2y_KKH03uf51Y=
> > >(31420) [Ruby]
> > > registration/registration.rb:182 Received possible migrations paths:
> > >[]*
> > >
> > >
> > > Mark Post
> > >
> > > 
> > > -- For LINUX-390 subscribe 

Re: Upgrade sles 12sp4 - sles 15

[Mark Pace]

I'm doing this upgrade from 12sp4, not sp3.

On Mon, Mar 18, 2019 at 1:48 PM Lori Grimaldi  wrote:

> Maybe this will help:
>
>https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12-SP3/
>
> Additionally, there are the following extensions which are not covered by
> SUSE support agreements, available at no additional cost and without an
> extra registration key:
>   SUSE Package Hub: https://packagehub.suse.com/
>   SUSE Linux Enterprise Software Development Kit
>
> Lori Grimaldi
> Linux on zSeries Americas Team, Team Lead - Senior
> IBM Services
> Notes:  leter...@us.ibm.com
> Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666
> Email Address: leter...@us.ibm.com
> IBM
>
>
>
>
>
> From:   Paul Dembry 
> To: LINUX-390@VM.MARIST.EDU
> Date:   03/18/2019 01:36 PM
> Subject:Re: Upgrade sles 12sp4 - sles 15
> Sent by:Linux on 390 Port 
>
>
>
> > Any progress is good progress.
> Unless you are a lemming :-)
> Paul
>
> -----Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark
> Pace
> Sent: Monday, March 18, 2019 10:11 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Upgrade sles 12sp4 - sles 15
>
> Thank you, Lori -
> I tried the SUSEConnect --clean  and then register again - and now I have a
> different error message.
>
> The requested products 'Suse Package Hub 12 SP4 s390x' have not been
> activated on the system.
>
> So I need to go figure out what this means.
>
> Thank you again.  Any progress is good progress.
>
> On Mon, Mar 18, 2019 at 12:36 PM Lori Grimaldi 
> wrote:
>
> > I had a problem opened with Microfocus and here is what we did to
> resolve:
> >
> > - Ran SUSEConnect --cleanup
> > - Re-Registered system into SCC
> > - Upgraded SLES12SP3 to SP4 via zypper migration
> > - Upgraded SLES12SP4 to SLES15 via off-line mode
> > - Cleaned up gpg key V# warning according
> >
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.suse.com_releasenotes_x86-5F64_SUSE-2DSLES_15_=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4=Hqe7wtWVuyxouUKULbOQJQARQXQCGj0jhZvI_V86APA=tMAUzCDn-1yIZemens8r9HwK0cSyEf1A8pMtOLVAbmk=
>
> >
> > Lori Grimaldi
> > Linux on zSeries Americas Team, Team Lead - Senior IBM Services
> > Notes:  leter...@us.ibm.com
> > Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666 Email Address:
> > leter...@us.ibm.com IBM
> >
> >
> >
> >
> >
> > From:   Mark Pace 
> > To: LINUX-390@VM.MARIST.EDU
> > Date:   03/18/2019 10:00 AM
> > Subject:Re: Upgrade sles 12sp4 - sles 15
> > Sent by:Linux on 390 Port 
> >
> >
> >
> > Thanks, Mark.  Unfortunately that was not the issue.  I used Yast
> > Product Registration.  It came back as already registered.  I then
> > used Register Again to make sure it was registered.
> >
> > I may either create a local SMT server, or just build a new SLES 15
> > and manually migrate.
> >
> > On Fri, Mar 15, 2019 at 7:15 PM Mark Post  wrote:
> >
> > > On 3/15/19 4:25 PM, Mark Pace wrote:
> > > > This is then end - the lines before this are the panel being
> displayed.
> > >
> > > I think there are a number of lines before then that would be
> > > useful, but given what you're showing, I have to ask if this system
> > > is registered, with either SCC or a local SMT server? The sense I'm
> > > getting is that YaST is asking the registration server what
> > > migration products are available for the currently installed
> > > product(s), and is getting a null answer, possibly because it's not
> registered:
> > > *2019-03-15 16:23:16 <1> sles003.s390.mainline.com <
> >
> > https://urldefense.proofpoint.com/v2/url?u=http-3A__sles003.s390.mainl
> > ine.com=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=0O2Q0N3bhw8wToDxvSVQtC4OUF
> > vEgeKgNzzJ7wh_xG4=UeUdErz6SEwDmmv1KCoDqn6gCwC1beUjX1EFnrwpo5s=tUid
> > 9VAs-uO5lMrs4DZMC2_yCwFqva2y_KKH03uf51Y=
> > >(31420) [Ruby]
> > > registration/registration.rb:182 Received possible migrations paths:
> > >[]*
> > >
> > >
> > > Mark Post
> > >
> > > 
> > > -- For LINUX-390 subscribe / signoff / archive access instructions,
> > > send email to lists...@vm.marist.edu with the message: INFO
> > > LINUX-390 or visit
> > >
> >
> > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htb
> > in_

Re: Upgrade sles 12sp4 - sles 15

[Mark Pace]

Thank you, Lori -
I tried the SUSEConnect --clean  and then register again - and now I have a
different error message.

The requested products 'Suse Package Hub 12 SP4 s390x' have not been
activated on the system.

So I need to go figure out what this means.

Thank you again.  Any progress is good progress.

On Mon, Mar 18, 2019 at 12:36 PM Lori Grimaldi  wrote:

> I had a problem opened with Microfocus and here is what we did to resolve:
>
> - Ran SUSEConnect --cleanup
> - Re-Registered system into SCC
> - Upgraded SLES12SP3 to SP4 via zypper migration
> - Upgraded SLES12SP4 to SLES15 via off-line mode
> - Cleaned up gpg key V# warning according
> https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15/
>
> Lori Grimaldi
> Linux on zSeries Americas Team, Team Lead - Senior
> IBM Services
> Notes:  leter...@us.ibm.com
> Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666
> Email Address: leter...@us.ibm.com
> IBM
>
>
>
>
>
> From:   Mark Pace 
> To: LINUX-390@VM.MARIST.EDU
> Date:   03/18/2019 10:00 AM
> Subject:Re: Upgrade sles 12sp4 - sles 15
> Sent by:Linux on 390 Port 
>
>
>
> Thanks, Mark.  Unfortunately that was not the issue.  I used Yast Product
> Registration.  It came back as already registered.  I then used Register
> Again to make sure it was registered.
>
> I may either create a local SMT server, or just build a new SLES 15 and
> manually migrate.
>
> On Fri, Mar 15, 2019 at 7:15 PM Mark Post  wrote:
>
> > On 3/15/19 4:25 PM, Mark Pace wrote:
> > > This is then end - the lines before this are the panel being displayed.
> >
> > I think there are a number of lines before then that would be useful,
> > but given what you're showing, I have to ask if this system is
> > registered, with either SCC or a local SMT server? The sense I'm getting
> > is that YaST is asking the registration server what migration products
> > are available for the currently installed product(s), and is getting a
> > null answer, possibly because it's not registered:
> > *2019-03-15 16:23:16 <1> sles003.s390.mainline.com
> > <
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__sles003.s390.mainline.com=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4=UeUdErz6SEwDmmv1KCoDqn6gCwC1beUjX1EFnrwpo5s=tUid9VAs-uO5lMrs4DZMC2_yCwFqva2y_KKH03uf51Y=
> >(31420) [Ruby]
> > registration/registration.rb:182 Received possible migrations paths: []*
> >
> >
> > Mark Post
> >
> > --
> > For LINUX-390 subscribe / signoff / archive access instructions,
> > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> > visit
> >
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htbin_wlvindex-3FLINUX-2D390=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4=UeUdErz6SEwDmmv1KCoDqn6gCwC1beUjX1EFnrwpo5s=RDeB4YyOhULyuKMQKad_mcJ0VtMW6Ie5AzVj01arbR4=
>
> >
>
>
> --
> The postings on this site are my own and don’t necessarily represent
> Mainline’s positions or opinions
>
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htbin_wlvindex-3FLINUX-2D390=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4=UeUdErz6SEwDmmv1KCoDqn6gCwC1beUjX1EFnrwpo5s=RDeB4YyOhULyuKMQKad_mcJ0VtMW6Ie5AzVj01arbR4=
>
>
>
>
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Upgrade sles 12sp4 - sles 15

[Mark Pace]

Thanks, Mark.  Unfortunately that was not the issue.  I used Yast Product
Registration.  It came back as already registered.  I then used Register
Again to make sure it was registered.

I may either create a local SMT server, or just build a new SLES 15 and
manually migrate.

On Fri, Mar 15, 2019 at 7:15 PM Mark Post  wrote:

> On 3/15/19 4:25 PM, Mark Pace wrote:
> > This is then end - the lines before this are the panel being displayed.
>
> I think there are a number of lines before then that would be useful,
> but given what you're showing, I have to ask if this system is
> registered, with either SCC or a local SMT server? The sense I'm getting
> is that YaST is asking the registration server what migration products
> are available for the currently installed product(s), and is getting a
> null answer, possibly because it's not registered:
> *2019-03-15 16:23:16 <1> sles003.s390.mainline.com
> <http://sles003.s390.mainline.com>(31420) [Ruby]
> registration/registration.rb:182 Received possible migrations paths: []*
>
>
> Mark Post
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Upgrade sles 12sp4 - sles 15

[Mark Pace]

This is then end - the lines before this are the panel being displayed.

2019-03-15 16:23:15 <1> sles003.s390.mainline.com(31420) [Ruby]
ui/migration_repos_workflow.rb:337 Installed products: [#,
#]
2019-03-15 16:23:15 <2> sles003.s390.mainline.com(31420) [ui-shortcuts]
YShortcutManager.cc(checkShortcuts):85 Not enough widgets with valid
shortcut characters - no check
2019-03-15 16:23:15 <1> sles003.s390.mainline.com(31420) [Ruby]
registration/registration.rb:174 Offline migration for: #.
2019-03-15 16:23:15 <1> sles003.s390.mainline.com(31420) [Ruby]
registration/helpers.rb:55 Current language: en_US
2019-03-15 16:23:15 <1> sles003.s390.mainline.com(31420) [Ruby]
registration/helpers.rb:76 Language for HTTP requests set to "en-US"
2019-03-15 16:23:15 <1> sles003.s390.mainline.com(31420) [Ruby]
registration/registration.rb:308 Using custom registration URL: "
https://scc.suse.com;
2019-03-15 16:23:15 <1> sles003.s390.mainline.com(31420) [Ruby]
registration/helpers.rb:118 Boot reg_ssl_verify option: nil
*2019-03-15 16:23:16 <1> sles003.s390.mainline.com
<http://sles003.s390.mainline.com>(31420) [Ruby]
registration/registration.rb:182 Received possible migrations paths: []*
*2019-03-15 16:23:16 <3> sles003.s390.mainline.com
<http://sles003.s390.mainline.com>(31420) [Ruby]
ui/migration_repos_workflow.rb:342 No migration product found.*
2019-03-15 16:23:16 <1> sles003.s390.mainline.com(31420) [ui]
YPushButton.cc(setFunctionKey):202 Guessing button role YOKButton for
YPushButton "OK" at 0x3ff9c1b2b70 from function key F10


On Fri, Mar 15, 2019 at 4:03 PM Mark Pace  wrote:

> Thanks for the heads up, Mark.
>
> On Fri, Mar 15, 2019 at 2:43 PM Mark Post  wrote:
>
>> On 3/15/19 2:22 PM, Mark Pace wrote:
>> > That log is nearly 2MB.  I think I'll erase it and try again.  Hopefully
>> > the log will be a little smaller.
>>
>> In the case of an upgrade (or any installation for that matter), when
>> you're booting the installer for the new version, those logs won't be
>> the same as what is in the /var/log/ directory on the "real" system.
>>
>> That means that to be able to look at them, you need to have "usessh"
>> and "sshpassword" is your parameter file, even if you're using VNC or
>> some other method to do the actual install/upgrade. Then, when the error
>> comes up, you can look at /var/log/ which will be in the ramdisk, as
>> opposed to /mnt/var/log/ which will be on the "real" system.
>>
>>
>> Mark Post
>>
>> --
>> For LINUX-390 subscribe / signoff / archive access instructions,
>> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
>> visit
>> http://www.marist.edu/htbin/wlvindex?LINUX-390
>>
>
>
> --
> The postings on this site are my own and don’t necessarily represent
> Mainline’s positions or opinions
>
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
>
>
>
>

-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Upgrade sles 12sp4 - sles 15

[Mark Pace]

Thanks for the heads up, Mark.

On Fri, Mar 15, 2019 at 2:43 PM Mark Post  wrote:

> On 3/15/19 2:22 PM, Mark Pace wrote:
> > That log is nearly 2MB.  I think I'll erase it and try again.  Hopefully
> > the log will be a little smaller.
>
> In the case of an upgrade (or any installation for that matter), when
> you're booting the installer for the new version, those logs won't be
> the same as what is in the /var/log/ directory on the "real" system.
>
> That means that to be able to look at them, you need to have "usessh"
> and "sshpassword" is your parameter file, even if you're using VNC or
> some other method to do the actual install/upgrade. Then, when the error
> comes up, you can look at /var/log/ which will be in the ramdisk, as
> opposed to /mnt/var/log/ which will be on the "real" system.
>
>
> Mark Post
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Upgrade sles 12sp4 - sles 15

[Mark Pace]

That log is nearly 2MB.  I think I'll erase it and try again.  Hopefully
the log will be a little smaller.

On Fri, Mar 15, 2019 at 11:31 AM Mark Post  wrote:

> On 3/15/19 9:50 AM, Mark Pace wrote:
> > Has anyone done a successful upgrade from sles12 sp4 to sles 15 via
> > Upgrade=1
> >
> > Doing upgrade via VNC -
> >
> > Everything looks pretty normal at the beginning. But once I select the
> > partition to be upgraded I receive a pop-up - Error No migration product
> > found.
>
> This is the first I've heard of it. One of our customers does a lot of
> testing of just this scenario during the beta testing, so I'm a little
> surprised to hear of problems doing that.
>
> The logs under /var/log/YaST2/ would provide some insight into what YaST
> is trying to do before it gives up and displays that dialog box.
>
>
> Mark Post
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Upgrade sles 12sp4 - sles 15

[Mark Pace]

My boot is on the / filesystem  - there is 3.5GB available

Filesystem  Size  Used Avail Use% Mounted on
/dev/dasda1 6.7G  2.9G  3.5G  45% /

On Fri, Mar 15, 2019 at 11:28 AM Lori Grimaldi  wrote:

> What about increasing the /boot disk?
>
> Lori Grimaldi
> Linux on zSeries Americas Team, Team Lead - Senior
> IBM Services
> Notes:  leter...@us.ibm.com
> Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666
> Email Address: leter...@us.ibm.com
> IBM
>
>
>
>
>
> From:   Mark Pace 
> To: LINUX-390@VM.MARIST.EDU
> Date:   03/15/2019 11:18 AM
> Subject:Re: Upgrade sles 12sp4 - sles 15
> Sent by:Linux on 390 Port 
>
>
>
> Yes, I had done a
> zypper up   before hand, and rebooting to be sure it was up to date.
>
> On Fri, Mar 15, 2019 at 10:39 AM Lori Grimaldi 
> wrote:
>
> > Have you patched SLES 12 SP4 before upgrading?  I had to add a 1500
> > cylinder /boot disk also.
> >
> > Lori Grimaldi
> > Linux on zSeries Americas Team, Team Lead - Senior
> > IBM Services
> > Notes:  leter...@us.ibm.com
> > Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666
> > Email Address: leter...@us.ibm.com
> > IBM
> >
> >
> >
> >
> >
> > From:   Mark Pace 
> > To: LINUX-390@VM.MARIST.EDU
> > Date:   03/15/2019 09:53 AM
> > Subject:Upgrade sles 12sp4 - sles 15
> > Sent by:Linux on 390 Port 
> >
> >
> >
> > Has anyone done a successful upgrade from sles12 sp4 to sles 15 via
> > Upgrade=1
> >
> > Doing upgrade via VNC -
> >
> > Everything looks pretty normal at the beginning. But once I select the
> > partition to be upgraded I receive a pop-up - Error No migration product
> > found.
> >
> > On the CMS console I am also receive message - warning: Unsupported
> version
> > of key: V3
> >
> > Once I click OK it returns to the Select for Update panel.
> >
> > Rinse and repeat.
> >
> >
> > --
> > The postings on this site are my own and don’t necessarily represent
> > Mainline’s positions or opinions
> >
> > Mark D Pace
> > Senior Systems Engineer
> > Mainline Information Systems
> >
> > --
> > For LINUX-390 subscribe / signoff / archive access instructions,
> > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> > visit
> >
> >
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htbin_wlvindex-3FLINUX-2D390=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4=U_1sDo75GuRPuk9FncSLcW9eeFWLSAuslv6VwtHl1Vc=nuKt8NpKQobxZbUG6vADHnV2iOrK-pbFzbNvr1SEuYE=
>
> >
> >
> >
> >
> >
> > --
> > For LINUX-390 subscribe / signoff / archive access instructions,
> > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> > visit
> >
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htbin_wlvindex-3FLINUX-2D390=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4=3cxl5g-G--2vqbnwWSlnZuVYUi3Q7PcNlmXbfvZpIUA=hvJXb4719rzVv1aY5HFGoSTruRo4PIhYuw-BG1WmGTQ=
>
> >
>
>
> --
> The postings on this site are my own and don’t necessarily represent
> Mainline’s positions or opinions
>
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htbin_wlvindex-3FLINUX-2D390=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4=3cxl5g-G--2vqbnwWSlnZuVYUi3Q7PcNlmXbfvZpIUA=hvJXb4719rzVv1aY5HFGoSTruRo4PIhYuw-BG1WmGTQ=
>
>
>
>
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Upgrade sles 12sp4 - sles 15

[Mark Pace]

Yes, I had done a
zypper up   before hand, and rebooting to be sure it was up to date.

On Fri, Mar 15, 2019 at 10:39 AM Lori Grimaldi  wrote:

> Have you patched SLES 12 SP4 before upgrading?  I had to add a 1500
> cylinder /boot disk also.
>
> Lori Grimaldi
> Linux on zSeries Americas Team, Team Lead - Senior
> IBM Services
> Notes:  leter...@us.ibm.com
> Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666
> Email Address: leter...@us.ibm.com
> IBM
>
>
>
>
>
> From:   Mark Pace 
> To: LINUX-390@VM.MARIST.EDU
> Date:   03/15/2019 09:53 AM
> Subject:Upgrade sles 12sp4 - sles 15
> Sent by:Linux on 390 Port 
>
>
>
> Has anyone done a successful upgrade from sles12 sp4 to sles 15 via
> Upgrade=1
>
> Doing upgrade via VNC -
>
> Everything looks pretty normal at the beginning. But once I select the
> partition to be upgraded I receive a pop-up - Error No migration product
> found.
>
> On the CMS console I am also receive message - warning: Unsupported version
> of key: V3
>
> Once I click OK it returns to the Select for Update panel.
>
> Rinse and repeat.
>
>
> --
> The postings on this site are my own and don’t necessarily represent
> Mainline’s positions or opinions
>
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htbin_wlvindex-3FLINUX-2D390=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4=U_1sDo75GuRPuk9FncSLcW9eeFWLSAuslv6VwtHl1Vc=nuKt8NpKQobxZbUG6vADHnV2iOrK-pbFzbNvr1SEuYE=
>
>
>
>
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Upgrade sles 12sp4 - sles 15

[Mark Pace]

Has anyone done a successful upgrade from sles12 sp4 to sles 15 via
Upgrade=1

Doing upgrade via VNC -

Everything looks pretty normal at the beginning. But once I select the
partition to be upgraded I receive a pop-up - Error No migration product
found.

On the CMS console I am also receive message - warning: Unsupported version
of key: V3

Once I click OK it returns to the Select for Update panel.

Rinse and repeat.


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: SLES and pure-ftpd

[Mark Pace]

Bummer.

Thanks for the info, Mark!

On Wed, Feb 27, 2019 at 5:14 PM Mark Post  wrote:

> On 2/27/19 4:27 PM, Mark Pace wrote:
> > Did SuSE stop supporting pure-ftpd after 11sp4?
> > I no longer see it in the sles12 distribution, DVD1 or DVD2.
>
> Yes. SLES12 was the version where Product Management and others did a
> lot of work to pick one tool/package for any particular function. The
> vsftpd package was chosen for the FTP server.
>
>
> Mark Post
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

SLES and pure-ftpd

[Mark Pace]

Did SuSE stop supporting pure-ftpd after 11sp4?
I no longer see it in the sles12 distribution, DVD1 or DVD2.

-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: VSFTPD log file oddity

[Mark Pace]

I'll give the xferlog option a try in my test system.

On Fri, Oct 5, 2018 at 6:40 PM Jeffrey Barnard  wrote:

> For what it may be worth ...
>
> The messages in both cases are a bit different from the normal logged
> messages.
>
> Wed Oct  3 15:25:49 2018 vsftpd [pid 12912]: "" from "10.0.192.124":
> vsf_sysutil_recv_peek*Wed Oct  3 15:38:56 2018 [pid 13254] CONNECT: Client
> "10.0.192.124"*
>
> Mon Oct  1 15:55:48 2018 vsftpd [pid 10431]: "jcb" from "192.168.1.238":
> priv_sock_get_cmdMon Oct  1 15:55:49 2018 [pid 10587] CONNECT: Client
> "192.168.1.238"
>
> In the case of the error, the literal "vsftpd" (program name, command
> name?) is present. Normal logged messages do not have this.
>
> Turns out these error messages are issued from various routines using the
> die() function call. The thread is terminated. Note the different pid in
> the lines for both samples.
>
> For example, the error I see comes from privsock.c
>
> char
> priv_sock_get_cmd(int fd)
> {
>char res;
>int retval = vsf_sysutil_read_loop(fd, , sizeof(res));
>if (retval != sizeof(res))
>{
>  die("priv_sock_get_cmd");
>}
>return res;
> }
>
> Marks error is similar.
>
> This results in a "500 OOPS: priv_sock_get_cmd" sent on the command
> connection, which is already closed or being closed.
>
> The "priv_sock_get_cmd" is then send to the vsftpd.log file. This
> execution
> follows a chain of calls leading to logging.c and vsf_log_commom() which
> calls vsf_log_do_log_to_file() which adds a '\n' to each string before
> writting it to the log. So, just by looking at the code (3.0.3) I don't
> see
> the error.
>
> If I get in the mood, I might compile the source and trace down the error.
>
> In Mark Pace's case, I suspect he could use the xferlog option instead of
> the vsftpd.log. This would allow him to catch the transfers without all
> the
> rest of the messages.
>
> LOL. Don't know if this helps or if anyone really cares.
>
> Regards,
> Jeff
>


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: VSFTPD log file oddity

[Mark Pace]

Hey, Mark -

 cat /etc/os-release
NAME="SLES"
VERSION="12-SP3"
VERSION_ID="12.3"
PRETTY_NAME="SUSE Linux Enterprise Server 12 SP3"

vsftpd - Version: 3.0.2-40.8.1 Installed: 3.0.2-40.8.1

On Thu, Oct 4, 2018 at 10:47 PM Mark Post  wrote:

> >>> On 10/3/2018 at 04:45 PM, Mark Pace  wrote:
> > Thanks, Jeff for the confirmation that you see this error also.   Yes the
> > server runs fine.  But I have some scripts that reads the log file and
> > sends an email out when a new file arrives.  Sometimes the message that
> > shows a new file was written is the one appended to the end of the
> SSL/TLS
> > message and my script never sees it and no email is sent.  :(
>
> Hi, Mark,
>
> What distribution are you running this on?
>
>
> Mark Post
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: VSFTPD log file oddity

[Mark Pace]

incron looks very interesting.  Wish I had know about when I was first
starting to write these scripts/execs.  I really don't want to replace what
I have now just for one bug.

On Wed, Oct 3, 2018 at 7:43 PM Frank M. Ramaekers 
wrote:

> Ever use incron?  (like crontab, but for various file updates).
> https://linux.die.net/man/5/incrontab
>
> I use it to trigger events when a file arrives.
>
> Frank M. Ramaekers Jr.
>
>
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
> Mark Pace
> Sent: Wednesday, October 3, 2018 3:46 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: VSFTPD log file oddity
>
> Thanks, Jeff for the confirmation that you see this error also.   Yes the
> server runs fine.  But I have some scripts that reads the log file and
> sends an email out when a new file arrives.  Sometimes the message that
> shows a new file was written is the one appended to the end of the SSL/TLS
> message and my script never sees it and no email is sent.  :(
>
> On Wed, Oct 3, 2018 at 4:32 PM Jeffrey Barnard  wrote:
>
> > Mark,
> >
> > On my vsftpd it is this line ...
> >
> > Mon Oct  1 15:55:48 2018 vsftpd [pid 10431]: "jcb" from "192.168.1.238":
> > priv_sock_get_cmdMon Oct  1 15:55:49 2018 [pid 10587] CONNECT: Client
> > "192.168.1.238"
> >
> > The error message from the sandbox security is there even though we
> > have seccomp_sandbox=NO specified. Not enough of a problem to try and
> > fix? And, vsftpd runs fine anyway.
> >
> > We are at 3.0.3-lp150.5.6.1 on Leap 15. Which is pretty current. You
> > can always open a PMR for support.
> >
> > Jeff
> >
> > --
> > For LINUX-390 subscribe / signoff / archive access instructions, send
> > email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> > visit
> > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htb
> > in_wlvindex-3FLINUX-2D390=DwIFaQ=laxeQK7vPmHfouIIPNyCfbQd49eK3u00U
> > 8Jdo0RFvts=EOaM1MkMLG24_TOy4m7EdDoX0CP9-c0YJ2kTdeagcqQ=V_nzSYhLc4f
> > YxwhDQW5ZimCQgKdCuzMj-UZc9SB5_j8=qzZdCLonyUf2wP9DDVj3t5hU7b4uX4FZFyY
> > EhKEIQyw=
> > --
> > For more information on Linux on System z, visit
> > https://urldefense.proofpoint.com/v2/url?u=http-3A__wiki.linuxvm.org_;
> > d=DwIFaQ=laxeQK7vPmHfouIIPNyCfbQd49eK3u00U8Jdo0RFvts=EOaM1MkMLG24_
> > TOy4m7EdDoX0CP9-c0YJ2kTdeagcqQ=V_nzSYhLc4fYxwhDQW5ZimCQgKdCuzMj-UZc9
> > SB5_j8=ZbgfUmE5z0jaGc2wNtSfmllIc8CBDJ1xRuJ5aRrSCxI=
> >
>
>
> --
> The postings on this site are my own and don’t necessarily represent
> Mainline’s positions or opinions
>
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions, send
> email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htbin_wlvindex-3FLINUX-2D390=DwIFaQ=laxeQK7vPmHfouIIPNyCfbQd49eK3u00U8Jdo0RFvts=EOaM1MkMLG24_TOy4m7EdDoX0CP9-c0YJ2kTdeagcqQ=V_nzSYhLc4fYxwhDQW5ZimCQgKdCuzMj-UZc9SB5_j8=qzZdCLonyUf2wP9DDVj3t5hU7b4uX4FZFyYEhKEIQyw=
> --
> For more information on Linux on System z, visit
> https://urldefense.proofpoint.com/v2/url?u=http-3A__wiki.linuxvm.org_=DwIFaQ=laxeQK7vPmHfouIIPNyCfbQd49eK3u00U8Jdo0RFvts=EOaM1MkMLG24_TOy4m7EdDoX0CP9-c0YJ2kTdeagcqQ=V_nzSYhLc4fYxwhDQW5ZimCQgKdCuzMj-UZc9SB5_j8=ZbgfUmE5z0jaGc2wNtSfmllIc8CBDJ1xRuJ5aRrSCxI=
>
> --
> This message contains information which is privileged and confidential and
> is solely for the use of the intended recipient. If you are not the
> intended recipient, be aware that any review, disclosure, copying,
> distribution, or use of the contents of this message is strictly
> prohibited. If you have received this in error, please destroy it
> immediately and notify us at privacy...@torchmarkcorp.com.
>
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>


-- 
The postings on this site

Re: VSFTPD log file oddity

[Mark Pace]

Thanks, Jeff for the confirmation that you see this error also.   Yes the
server runs fine.  But I have some scripts that reads the log file and
sends an email out when a new file arrives.  Sometimes the message that
shows a new file was written is the one appended to the end of the SSL/TLS
message and my script never sees it and no email is sent.  :(

On Wed, Oct 3, 2018 at 4:32 PM Jeffrey Barnard  wrote:

> Mark,
>
> On my vsftpd it is this line ...
>
> Mon Oct  1 15:55:48 2018 vsftpd [pid 10431]: "jcb" from "192.168.1.238":
> priv_sock_get_cmdMon Oct  1 15:55:49 2018 [pid 10587] CONNECT: Client
> "192.168.1.238"
>
> The error message from the sandbox security is there even though we have
> seccomp_sandbox=NO specified. Not enough of a problem to try and fix? And,
> vsftpd runs fine anyway.
>
> We are at 3.0.3-lp150.5.6.1 on Leap 15. Which is pretty current. You can
> always open a PMR for support.
>
> Jeff
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

VSFTPD log file oddity

[Mark Pace]

I recently setup SSL/TLS on our VSFTPD server.

The problem is anytime someone connects with SSL/TLS any messages written
to the log file do not have a LF or CRLF at the end.  Example.

Wed Oct  3 15:25:49 2018 vsftpd [pid 12912]: "" from "10.0.192.124":
vsf_sysutil_recv_peek*Wed Oct  3 15:38:56 2018 [pid 13254] CONNECT: Client
"10.0.192.124"*

The bold and underlined piece should have been a new line, but it was
appended to the end of the SSL/TLS message.

I have done a lot of searching with google and can't find an answer.  So I
hope that someone here may have seen this before.

TIA

-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Bug with XFS and SLES 12SP3 kernel-default-4.4.131-94.29-default

[Mark Pace]

After a long process I have the filesystem converted to EXT3 and the new
kernel running.

On Thu, May 24, 2018 at 1:59 PM, Mike Walter  wrote:

> I'm just supposing here, that you put and it's on a test bed server first,
> at which point you would have found the problem with the xfs file system
> and been able to back it out. Only after maintenance has been thoroughly
> vetted on the test bed server wood shove it down the throats of the other
> servers.
>
> But, I never was responsible for Linux on Z systems servers, so I may have
> missed out on all the fun.
>
> Mike Walter
> -Retired-
> 
> From: Linux on 390 Port  on behalf of Marcy
> Cortes 
> Sent: Thursday, May 24, 2018 11:00:12 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Bug with XFS and SLES 12SP3 kernel-default-4.4.131-94.29-
> default
>
> Nice idea, but when you have a thousand servers, that isn't very
> practical.  And one your server has been up a few minutes its data has
> changed and regressing it that way may be a problem.   The multi kernel
> support works well for things like backing out the kernel.
>
>
>
>
> -Original Message-
> From: Linux on 390 Port  On Behalf Of John McKown
> Sent: Thursday, May 24, 2018 7:51 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: [LINUX-390] Bug with XFS and SLES 12SP3
> kernel-default-4.4.131-94.29-default
>
> On Thu, May 24, 2018 at 9:29 AM Mike Walter  com>
> wrote:
>
> > When I was a young man learning the art of systems programming sooo
> > long ago, I was taught that the first step of applying maintenance is
> > to make a physical backup of the target volumes.  That way you have a
> > validated source with which to return if/when the maintenance fails.
> Just sayin'.
> > :-)
> >
>
> ​Total agreement. I'm having a problem with a sandox system right now with
> some maintenance (but it's z/OS, not Linux). But that's what I did --
> physical back of all the volumes before doing _anything_. I do the same
> sort of thing when I install a never version of a product. I do a "tar"
> backup of the various files (it they're in /etc or /var or ...) &
> filesystems.​
>
>
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> https://eur03.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-
> 390=02%7C01%7C%7C74815a2d96a04a6abef508d5c18fc160%
> 7C84df9e7fe9f640afb435%7C1%7C0%7C636627745517533603=
> T6se4MfGCrQKhEoLAl1GSZdahtAXs2ZZd4gZiuAwgjU%3D=0
> --
> For more information on Linux on System z, visit
> https://eur03.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwiki.linuxvm.org%2F=02%7C01%7C%
> 7C74815a2d96a04a6abef508d5c18fc160%7C84df9e7fe9f640afb435
> %7C1%7C0%7C636627745517533603=84ePrZlYwZTFJpCrEaMBxk9u2g%
> 2FiN1kja9rARzKuHl0%3D=0
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>



-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Bug with XFS and SLES 12SP3 kernel-default-4.4.131-94.29-default

[Mark Pace]

I found in yast a way to update the boot loader to point to the older
version of the kernel.  That allowed me to reboot and mount the XFS file
system. Yay.

But i still need to figure out if there is a way to remove the patches from
the new kernel.  As it is, it appears to me, that the maintenance(patches)
are now out of sync. Yast/zypper now think I am running the new kernel when
in fact I am using an older kernel.

On Thu, May 24, 2018 at 9:34 AM, Mark Pace <pacemainl...@gmail.com> wrote:

> In /boot I still have the previous kernel files,  just not sure how to
> make them the kernel used at boot.
>
> .image-4.4.126-94.22-default.hmac  image-4.4.126-94.22-default
> symvers-4.4.126-94.22-default.gz
> .image-4.4.131-94.29-default.hmac  image-4.4.131-94.29-default
> symvers-4.4.131-94.29-default.gz
> System.map-4.4.126-94.22-default   initrd
> sysctl.conf-4.4.126-94.22-default
> System.map-4.4.131-94.29-default   initrd-4.4.126-94.22-default
> sysctl.conf-4.4.131-94.29-default
> boot.readmeinitrd-4.4.126-94.22-default-kdump
> vmlinux-4.4.126-94.22-default.gz
> config-4.4.126-94.22-default   initrd-4.4.131-94.29-default
> vmlinux-4.4.131-94.29-default.gz
> config-4.4.131-94.29-default   initrd-4.4.131-94.29-default-kdump
> zipl
> grub2  symtypes-4.4.126-94.22-default.gz
> image  symtypes-4.4.131-94.29-default.gz
>
>
> On Thu, May 24, 2018 at 9:27 AM, Alan Altmark <alan_altm...@us.ibm.com>
> wrote:
>
>> On Thursday, 05/24/2018 at 12:45 GMT, Rick Troth <r...@casita.net> wrote:
>> > On 05/23/2018 07:25 PM, R P Herrold wrote:
>> > >> Suse just released a new kernel-default-4.4.131-94.29-1
>> > >> package for SLES 12SP3 with some kernel security fixes.  If
>> > >> you use XFS, don't install it!
>> > > My condolences
>> > >
>> > > There has been an (at least) four way finger pointing contest
>> > > raging for the last couple of months (on the Fedoraproject
>> > > front) between:
>> > > - xfs developers
>> > > - systemd developers
>> > > - dracut developers
>> > > - innocent victims of XFS
>> >
>> > - snip -
>> >
>> > Explain to me how a KERNEL update relates to a finger-pointing fest
>> > among three user-space packages and the users?
>> >
>> > I DO use XFS on some systems. I prolly fall into the fourth group, but
>> > was already pointing my digits at that second bullet.
>>
>> Explain to me why a distro would release an update that knowingly breaks
>> a
>> file system?  Unless they don't support xfs?
>>
>> Alan Altmark
>>
>> Senior Managing z/VM and Linux Consultant
>> IBM Systems Lab Services
>> IBM Z Delivery Practice
>> ibm.com/systems/services/labservices
>> office: 607.429.3323
>> mobile; 607.321.7556
>> alan_altm...@us.ibm.com
>> IBM Endicott
>>
>>
>> --
>> For LINUX-390 subscribe / signoff / archive access instructions,
>> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
>> visit
>> http://www.marist.edu/htbin/wlvindex?LINUX-390
>> --
>> For more information on Linux on System z, visit
>> http://wiki.linuxvm.org/
>>
>
>
>
> --
> The postings on this site are my own and don’t necessarily represent
> Mainline’s positions or opinions
>
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
>
>
>
>


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Bug with XFS and SLES 12SP3 kernel-default-4.4.131-94.29-default

[Mark Pace]

In /boot I still have the previous kernel files,  just not sure how to make
them the kernel used at boot.

.image-4.4.126-94.22-default.hmac  image-4.4.126-94.22-default
symvers-4.4.126-94.22-default.gz
.image-4.4.131-94.29-default.hmac  image-4.4.131-94.29-default
symvers-4.4.131-94.29-default.gz
System.map-4.4.126-94.22-default   initrd
sysctl.conf-4.4.126-94.22-default
System.map-4.4.131-94.29-default   initrd-4.4.126-94.22-default
sysctl.conf-4.4.131-94.29-default
boot.readmeinitrd-4.4.126-94.22-default-kdump
vmlinux-4.4.126-94.22-default.gz
config-4.4.126-94.22-default   initrd-4.4.131-94.29-default
vmlinux-4.4.131-94.29-default.gz
config-4.4.131-94.29-default   initrd-4.4.131-94.29-default-kdump  zipl
grub2  symtypes-4.4.126-94.22-default.gz
image  symtypes-4.4.131-94.29-default.gz


On Thu, May 24, 2018 at 9:27 AM, Alan Altmark 
wrote:

> On Thursday, 05/24/2018 at 12:45 GMT, Rick Troth  wrote:
> > On 05/23/2018 07:25 PM, R P Herrold wrote:
> > >> Suse just released a new kernel-default-4.4.131-94.29-1
> > >> package for SLES 12SP3 with some kernel security fixes.  If
> > >> you use XFS, don't install it!
> > > My condolences
> > >
> > > There has been an (at least) four way finger pointing contest
> > > raging for the last couple of months (on the Fedoraproject
> > > front) between:
> > > - xfs developers
> > > - systemd developers
> > > - dracut developers
> > > - innocent victims of XFS
> >
> > - snip -
> >
> > Explain to me how a KERNEL update relates to a finger-pointing fest
> > among three user-space packages and the users?
> >
> > I DO use XFS on some systems. I prolly fall into the fourth group, but
> > was already pointing my digits at that second bullet.
>
> Explain to me why a distro would release an update that knowingly breaks a
> file system?  Unless they don't support xfs?
>
> Alan Altmark
>
> Senior Managing z/VM and Linux Consultant
> IBM Systems Lab Services
> IBM Z Delivery Practice
> ibm.com/systems/services/labservices
> office: 607.429.3323
> mobile; 607.321.7556
> alan_altm...@us.ibm.com
> IBM Endicott
>
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>



-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Bug with XFS and SLES 12SP3 kernel-default-4.4.131-94.29-default

[Mark Pace]

I was able to edit my fstab and remove the mount for the XFS filesystem and
reboot the system.
Is there a way to roll back the maintenance for the kernel?  Still
struggling trying to figure out how to fix this.

On Thu, May 24, 2018 at 8:43 AM, Rick Troth  wrote:

> On 05/23/2018 07:25 PM, R P Herrold wrote:
> >> Suse just released a new kernel-default-4.4.131-94.29-1
> >> package for SLES 12SP3 with some kernel security fixes.  If
> >> you use XFS, don't install it!
> > My condolences
> >
> > There has been an (at least) four way finger pointing contest
> > raging for the last couple of months (on the Fedoraproject
> > front) between:
> >   - xfs developers
> >   - systemd developers
> >   - dracut developers
> >   - innocent victims of XFS
>
> - snip -
>
> Explain to me how a KERNEL update relates to a finger-pointing fest
> among three user-space packages and the users?
>
> I DO use XFS on some systems. I prolly fall into the fourth group, but
> was already pointing my digits at that second bullet.
>
> -- R; <><
>
>
>
>
>
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>



-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Bug with XFS and SLES 12SP3 kernel-default-4.4.131-94.29-default

[Mark Pace]

I just got hit by this, this morning.  Updated SLES12 SP3 and now my XFS
filesystem will not mount.  I truly have no idea how to fix this.  I tried
xfs_repair on the device.  It ran to completion, but I get the same error
when I reboot.
Any suggestions?

Ý  OK  ¨ Found device
/dev/mapper/36005076307ffd4da003c-part1.

 Starting File System Check on
/dev/...7ffd4da003c-part1...
Ý  OK  ¨ Started File System Check on
/dev/m...307ffd4da003c-part1.
 Mounting
/srv/ftp/pub...

SGI XFS with ACLs, security attributes, realtime, no debug
enabled
XFS (dm-4): Mounting V5
Filesystem

XFS (dm-4): Torn write (CRC failure) detected at log block 0x231d3.
Truncating head block from 0x231d7.
XFS (dm-4): failed to locate log
tail
XFS (dm-4): log mount/recovery failed: error
-74
XFS (dm-4): log mount
failed

ÝFAILED¨ Failed to mount
/srv/ftp/pub.

See 'systemctl status srv-ftp-pub.mount' for
details.

On Wed, May 23, 2018 at 7:25 PM, R P Herrold  wrote:

> On Wed, 23 May 2018, Ted Rodriguez-Bell wrote:
>
> > Suse just released a new kernel-default-4.4.131-94.29-1
> > package for SLES 12SP3 with some kernel security fixes.  If
> > you use XFS, don't install it!
>
> My condolences
>
> There has been an (at least) four way finger pointing contest
> raging for the last couple of months (on the Fedoraproject
> front) between:
> - xfs developers
> - systemd developers
> - dracut developers
> - innocent victims of XFS
>
> Here is a trailhead to read back and forth from:
> http://tinyurl.com/y7d2a4he
>
> I have a number of Red Hat Bugzilla reports I track, I have
> corresponded twice privately with the Fedoraproject lead about
> applying dynamite to at least get the innocent victims out of
> XFS' harm's way, and ... bupkis.  I have to say the problem
> looks well and truly wedged, and XFS and data I care about
> will never meet
>
> In response, I went into our local deployment SOP's and added
> a general prohibition on using XFS, absent explicit prior
> approval from an admin or greater level authority.  The ONLY
> exception I can see being sought relates to extremely large
> filesystems
>
> -- Russ herrold
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>



-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: High Level Assembler for Linux on Z

[Mark Pace]

Really hate to dredge up this old thread - but - I'm trying to find the
HLASM RPM to install in Linux.  I just installed HLASM on my z/VM system
from an electronic SDO.  I can not find the RPM that is supposedly
included.  I've checked every minidisk on the installation ID.  Has anyone
successfully found the ASMA90.RPM file?

Crosspost VM
TIA

On Thu, Feb 6, 2014 at 1:17 PM, Davis, Larry (National VM Capability) <
larry.dav...@hp.com> wrote:

> Then just order the VM HLASM and that should give you access to the Linux
> RPM.
> Later you will have to convert the CP HLASM license to an PRPQ per IFL
> License if IBM is nice they should convert it straight over.
>
>
>
>
> Larry Davis,
> VM Capability
>
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
> Michel Beaulieu
> Sent: Thursday, February 06, 2014 1:12 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: High Level Assembler for Linux on Z
>
> Thanks Larry,
>
>
> At this time, Linux is running under z/VM 5.4 on CP processors.
>
>
>
> Do we need the PRPQ anyway?
>
>
> Later when IFL are added, do we need to re-install a new RPM?   with the
> PRPQ?
>
>
> Regards,
>
>
> Michel Beaulieu
>  IBM SO-Delivery, Canada
> |*| Opinions expressed are my own and do not represent my employer in any
> way.
> --
>  > Date: Thu, 6 Feb 2014 17:55:59 +
> > From: larry.dav...@hp.com
> > Subject: Re: High Level Assembler for Linux on Z
> > To: LINUX-390@VM.MARIST.EDU
> >
> > HLASM for Linux on an IFL has a separate Feature code for the OTC and
> > the S
> >
> > IBM High Level Assembler for Linux on System z intending to execute High
> Level Assembler on IFL processors should order PRPQs 5799-TCQ and 5799-TCR
> for each IFL.
> > 5799-TCQ (OTC)and
> > 5799-TCR (S)
> >
> >
> >
> > Larry Davis,
> > VM Capability
> >
> > -Original Message-
> > From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
> > Michel Beaulieu
> > Sent: Thursday, February 06, 2014 12:25 PM
> > To: LINUX-390@VM.MARIST.EDU
> > Subject: High Level Assembler for Linux on Z
> >
> > Hello,
> >
> > For an installation with no z/OS.
> >
> >
> >
> > How do I get the High Level Assembler RPM to install on Linux?
> >
> >
> > Thanks!
> >
> > Michel Beaulieu
> > IBM SO-Delivery, Canada
> > * Opinions expressed are my own and do not represent my employer in any
> way.
> >
> >
> >
> >
> > --
> > For LINUX-390 subscribe / signoff / archive access instructions, send
> > email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> > visit
> > http://www.marist.edu/htbin/wlvindex?LINUX-390
> > --
> > For more information on Linux on System z, visit
> > http://wiki.linuxvm.org/
> >
> > --
> > For LINUX-390 subscribe / signoff / archive access instructions, send
> > email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> > visit
> > http://www.marist.edu/htbin/wlvindex?LINUX-390
> > --
> > For more information on Linux on System z, visit
> > http://wiki.linuxvm.org/
>
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions, send
> email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit http://wiki.linuxvm.org/
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>



-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: SYSTEMD and autostarting VSE VTAPE (SUSE 12)

[Mark Pace]

This worked for me.  I'm certain someone will point out the flaws.

[Unit]
Description=VSE vtape daemon
After=network.target

[Service]
ExecStart=/usr/bin/su - vtape -c "nohup ./run.sh >/var/log/vtape.log" &
ExecStop=/usr/bin/pkill -f VirtualTapeServer$

[Install]
WantedBy=multi-user.target


I also had to create the /var/log/vtape.log
touch /var/log/vtape
chown vtape /var/log/vtape.log



On Tue, Dec 19, 2017 at 4:18 PM, Mark Pace <pacemainl...@gmail.com> wrote:

> Thanks for the update.  I'm going on vacation until the end of the year.
> I'll pick it back up then.  Hopefully one of use will figure out soon.
>
> Have a great day.
>
> On Tue, Dec 19, 2017 at 4:16 PM, Duerbusch, Tom <duerbus...@stlouis-mo.gov
> > wrote:
>
>> I'm just getting back to it (I was out last week).
>>
>> Currently, my notes from two weeks ago, don't make a lot of sense.
>> But, once everything gets paged back into my brain, they will make sense.
>>
>> Tom Duerbusch
>> THD Consulting
>>
>> On Tue, Dec 19, 2017 at 3:07 PM, Mark Pace <pacemainl...@gmail.com>
>> wrote:
>>
>> > Tom -
>> > What did you finally end up doing to get vtape started on you SLES12?
>> I'm
>> > about to go down the same path and don't to have to reinvent the wheel.
>> >
>> > Thanks
>> >
>> > On Wed, Dec 6, 2017 at 3:09 PM, Duerbusch, Tom <
>> duerbus...@stlouis-mo.gov>
>> > wrote:
>> >
>> > > With SUSE 12 SP3, I found that I needed to start converting my startup
>> > > scripts from using INIT.D to SYSTEMD.
>> > >
>> > > While SYSTEMD looks a lot cleaner, INIT.D was working.  But it's time
>> to
>> > > convert.
>> > >
>> > >
>> > > The script to startup VTAPE, as delivered by IBM is:
>> > >
>> > > linux91:/opt/IBM/VSEVTAPE # cat run.sh
>> > > #!/bin/sh
>> > > # ---
>> > > # Startup file for VSE VTAPE Server
>> > > # ---
>> > > if [ -e "$JAVA_HOME/bin/java" ]; then
>> > >   JAVA_EXEC="$JAVA_HOME/bin/java"
>> > > else
>> > >   JAVA_EXEC=java
>> > > fi
>> > > export CLASSPATH=".:VirtualTape.jar:$CLASSPATH"
>> > > "$JAVA_EXEC" com.ibm.vse.vtape.VirtualTapeServer "$@"
>> > >
>> > > And can be run from the command line without any problem.
>> > >
>> > > The service file is:
>> > >
>> > > linux91:/etc/systemd/system # cat vtape.service
>> > > [Unit]
>> > > Description=VSE VTAPE daemon
>> > > After=graphical.target
>> > >
>> > > [Service]
>> > > ExecStart=/opt/IBM/VSEVTAPE/run.sh
>> > >
>> > > [Install]
>> > > WantedBy=graphical-user.target
>> > >
>> > >
>> > > When I try to start it, I get the following logged in the journal
>> file:
>> > >
>> > > Dec 06 14:03:36 linux91 systemd[1]: Started VSE VTAPE daemon.
>> > > Dec 06 14:03:36 linux91 run.sh[17403]: Error: Could not find or load
>> main
>> > > class com.ibm.vse.vtape.VirtualTapeServer
>> > > Dec 06 14:03:36 linux91 systemd[1]: vtape.service: Main process
>> exited,
>> > > code=exited, status=1/FAILURE
>> > > Dec 06 14:03:36 linux91 systemd[1]: vtape.service: Unit entered failed
>> > > state.
>> > > Dec 06 14:03:36 linux91 systemd[1]: vtape.service: Failed with result
>> > > 'exit-code'.
>> > >
>> > > When I run it manually, it starts up fine:
>> > >
>> > > linux91:/opt/IBM/VSEVTAPE # ./run.sh
>> > > Licensed Materials - Property of IBM
>> > > (C) Copyright IBM Corp. 1998, 2010. All Rights Reserved.
>> > >
>> > > US Government Users Restricted Rights -
>> > > Use, duplication or disclosure restricted by
>> > > GSA ADP Schedule Contract with IBM Corp.
>> > >
>> > > VirtualTapeServer starting...
>> > > VirtualTapeServer listening on port 2386
>> > > Enter 'quit' to stop the server
>> > >
>> > > I take it that SYSTEMCTL is running in a different environment than I
>> am.
>> > > Is there something in the service file where I can set the correct
>> > > environment?
>> > >
>> > > Thanks
>> > >
>>

Re: SYSTEMD and autostarting VSE VTAPE (SUSE 12)

[Mark Pace]

Thanks for the update.  I'm going on vacation until the end of the year.
I'll pick it back up then.  Hopefully one of use will figure out soon.

Have a great day.

On Tue, Dec 19, 2017 at 4:16 PM, Duerbusch, Tom <duerbus...@stlouis-mo.gov>
wrote:

> I'm just getting back to it (I was out last week).
>
> Currently, my notes from two weeks ago, don't make a lot of sense.
> But, once everything gets paged back into my brain, they will make sense.
>
> Tom Duerbusch
> THD Consulting
>
> On Tue, Dec 19, 2017 at 3:07 PM, Mark Pace <pacemainl...@gmail.com> wrote:
>
> > Tom -
> > What did you finally end up doing to get vtape started on you SLES12?
> I'm
> > about to go down the same path and don't to have to reinvent the wheel.
> >
> > Thanks
> >
> > On Wed, Dec 6, 2017 at 3:09 PM, Duerbusch, Tom <
> duerbus...@stlouis-mo.gov>
> > wrote:
> >
> > > With SUSE 12 SP3, I found that I needed to start converting my startup
> > > scripts from using INIT.D to SYSTEMD.
> > >
> > > While SYSTEMD looks a lot cleaner, INIT.D was working.  But it's time
> to
> > > convert.
> > >
> > >
> > > The script to startup VTAPE, as delivered by IBM is:
> > >
> > > linux91:/opt/IBM/VSEVTAPE # cat run.sh
> > > #!/bin/sh
> > > # ---
> > > # Startup file for VSE VTAPE Server
> > > # ---
> > > if [ -e "$JAVA_HOME/bin/java" ]; then
> > >   JAVA_EXEC="$JAVA_HOME/bin/java"
> > > else
> > >   JAVA_EXEC=java
> > > fi
> > > export CLASSPATH=".:VirtualTape.jar:$CLASSPATH"
> > > "$JAVA_EXEC" com.ibm.vse.vtape.VirtualTapeServer "$@"
> > >
> > > And can be run from the command line without any problem.
> > >
> > > The service file is:
> > >
> > > linux91:/etc/systemd/system # cat vtape.service
> > > [Unit]
> > > Description=VSE VTAPE daemon
> > > After=graphical.target
> > >
> > > [Service]
> > > ExecStart=/opt/IBM/VSEVTAPE/run.sh
> > >
> > > [Install]
> > > WantedBy=graphical-user.target
> > >
> > >
> > > When I try to start it, I get the following logged in the journal file:
> > >
> > > Dec 06 14:03:36 linux91 systemd[1]: Started VSE VTAPE daemon.
> > > Dec 06 14:03:36 linux91 run.sh[17403]: Error: Could not find or load
> main
> > > class com.ibm.vse.vtape.VirtualTapeServer
> > > Dec 06 14:03:36 linux91 systemd[1]: vtape.service: Main process exited,
> > > code=exited, status=1/FAILURE
> > > Dec 06 14:03:36 linux91 systemd[1]: vtape.service: Unit entered failed
> > > state.
> > > Dec 06 14:03:36 linux91 systemd[1]: vtape.service: Failed with result
> > > 'exit-code'.
> > >
> > > When I run it manually, it starts up fine:
> > >
> > > linux91:/opt/IBM/VSEVTAPE # ./run.sh
> > > Licensed Materials - Property of IBM
> > > (C) Copyright IBM Corp. 1998, 2010. All Rights Reserved.
> > >
> > > US Government Users Restricted Rights -
> > > Use, duplication or disclosure restricted by
> > > GSA ADP Schedule Contract with IBM Corp.
> > >
> > > VirtualTapeServer starting...
> > > VirtualTapeServer listening on port 2386
> > > Enter 'quit' to stop the server
> > >
> > > I take it that SYSTEMCTL is running in a different environment than I
> am.
> > > Is there something in the service file where I can set the correct
> > > environment?
> > >
> > > Thanks
> > >
> > > Tom Duerbusch
> > > THD Consulting
> > >
> > > --
> > >
> > > --
> > > For LINUX-390 subscribe / signoff / archive access instructions,
> > > send email to lists...@vm.marist.edu with the message: INFO LINUX-390
> or
> > > visit
> > > http://www.marist.edu/htbin/wlvindex?LINUX-390
> > > --
> > > For more information on Linux on System z, visit
> > > http://wiki.linuxvm.org/
> > >
> >
> >
> >
> > --
> > The postings on this site are my own and don’t necessarily represent
> > Mainline’s positions or opinions
> >
> > Mark D Pace
> > Senior Systems Engineer
> > Mainline Information Systems
> >
> > 

Re: SYSTEMD and autostarting VSE VTAPE (SUSE 12)

[Mark Pace]

Tom -
What did you finally end up doing to get vtape started on you SLES12?  I'm
about to go down the same path and don't to have to reinvent the wheel.

Thanks

On Wed, Dec 6, 2017 at 3:09 PM, Duerbusch, Tom 
wrote:

> With SUSE 12 SP3, I found that I needed to start converting my startup
> scripts from using INIT.D to SYSTEMD.
>
> While SYSTEMD looks a lot cleaner, INIT.D was working.  But it's time to
> convert.
>
>
> The script to startup VTAPE, as delivered by IBM is:
>
> linux91:/opt/IBM/VSEVTAPE # cat run.sh
> #!/bin/sh
> # ---
> # Startup file for VSE VTAPE Server
> # ---
> if [ -e "$JAVA_HOME/bin/java" ]; then
>   JAVA_EXEC="$JAVA_HOME/bin/java"
> else
>   JAVA_EXEC=java
> fi
> export CLASSPATH=".:VirtualTape.jar:$CLASSPATH"
> "$JAVA_EXEC" com.ibm.vse.vtape.VirtualTapeServer "$@"
>
> And can be run from the command line without any problem.
>
> The service file is:
>
> linux91:/etc/systemd/system # cat vtape.service
> [Unit]
> Description=VSE VTAPE daemon
> After=graphical.target
>
> [Service]
> ExecStart=/opt/IBM/VSEVTAPE/run.sh
>
> [Install]
> WantedBy=graphical-user.target
>
>
> When I try to start it, I get the following logged in the journal file:
>
> Dec 06 14:03:36 linux91 systemd[1]: Started VSE VTAPE daemon.
> Dec 06 14:03:36 linux91 run.sh[17403]: Error: Could not find or load main
> class com.ibm.vse.vtape.VirtualTapeServer
> Dec 06 14:03:36 linux91 systemd[1]: vtape.service: Main process exited,
> code=exited, status=1/FAILURE
> Dec 06 14:03:36 linux91 systemd[1]: vtape.service: Unit entered failed
> state.
> Dec 06 14:03:36 linux91 systemd[1]: vtape.service: Failed with result
> 'exit-code'.
>
> When I run it manually, it starts up fine:
>
> linux91:/opt/IBM/VSEVTAPE # ./run.sh
> Licensed Materials - Property of IBM
> (C) Copyright IBM Corp. 1998, 2010. All Rights Reserved.
>
> US Government Users Restricted Rights -
> Use, duplication or disclosure restricted by
> GSA ADP Schedule Contract with IBM Corp.
>
> VirtualTapeServer starting...
> VirtualTapeServer listening on port 2386
> Enter 'quit' to stop the server
>
> I take it that SYSTEMCTL is running in a different environment than I am.
> Is there something in the service file where I can set the correct
> environment?
>
> Thanks
>
> Tom Duerbusch
> THD Consulting
>
> --
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>



-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Regina and THE (the hessling editor)

[Mark Pace]

Thank you, Mark!

On Wed, Dec 13, 2017 at 1:30 PM, Mark Post mpost <mp...@suse.com> wrote:

> Regina, or oorexx, could be reinstated, but not THE. THE has a non-OSS
> license for a couple of its source files.
> I f
> Have been building packages for both of them in OBS (openSUSE Build
> Service) for a while now. I just now added SLES12 SP3 to the list of
> versions I build. If you go to https://download.opensuse.org/
> repositories/home:/markkp:/THE/ after a while, you should see packages
> for SLES12 SP3.
>
> Mark PostMark Pace <pacemainl...@gmail.com> wrote:
> >>> "Mark Pace" <pacemainl...@gmail.com> 12/13/2017 10:42 >>>
> These used to be on the SDK.  I can't find them on the SLES12 SP3 SDK.
>
> Have they been removed?  Is there some where I can them?
>
> Thank you
>
> --
> The postings on this site are my own and don’t necessarily represent
> Mainline’s positions or opinions
>
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>
>
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>



-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Regina and THE (the hessling editor)

[Mark Pace]

These used to be on the SDK.  I can't find them on the SLES12 SP3 SDK.

Have they been removed?  Is there some where I can them?

Thank you

-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: OOREXX install on RHEL 7

[Mark Pace]

What is the difference between OOREXX and Regina? If I recall Regina is in
included in the distributions.

On Wed, Oct 4, 2017 at 11:30 AM, Neale Ferguson 
wrote:

> The EPEL repo now has OORexx:
>
> http://download.sinenomine.net/epel/epel7/s390x/oorexx-4.
> 2.0-3.el7.s390x.rp
> m
> http://download.sinenomine.net/epel/epel7/s390x/oorexx-
> devel-4.2.0-3.el7.s3
> 90x.rpm
> http://download.sinenomine.net/epel/epel7/s390x/oorexx-
> docs-4.2.0-3.el7.s39
> 0x.rpm
> http://download.sinenomine.net/epel/epel7/s390x/oorexx-
> libs-4.2.0-3.el7.s39
> 0x.rpm
>
> For those interested in the openJDK with the s390x JIT:
>
> http://download.sinenomine.net/epel/oss/s390x/java-9-
> openjdk-9.0.0.181-3.el
> 7.s390x.rpm
>
> Slightly older releases exist in EPEL as well. The newer release is in
> this separate repo as it required a higher level of rpm to build (along
> with co-reqs). This repo also contains a heap of python2/python3 packages.
>
> On 10/3/17, 4:43 PM, "Linux on 390 Port on behalf of Davis, Larry
> (National VM Capability)"  larry.dav...@dxc.com> wrote:
>
> >Thanks Neale
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>



-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: udevadm question

[Mark Pace]

Thank you, both.  I learned a lot today.
I got my multipath.conf setup, and I installed and got locate working.

Locate is SO much better than the find command.  Other than needing the
database to be updated.

On Thu, Aug 25, 2016 at 1:37 PM, Mark Post <mp...@suse.com> wrote:

> >>> On 8/25/2016 at 01:25 PM, Mark Pace <pacemainl...@gmail.com> wrote:
>
> > But I don't have a multipath.conf file.  I don't have anything to use as
> a
> > template to create this file.
>
> Look under /usr/share/doc/packages/multipath-tools/ for
> multipath.conf.annotated
> multipath.conf.defaults
>
> Or, man multipath.conf
>
> As a side note, if you don't have the findutils-locate package installed,
> it can help with things like this.
>
> # locate multipath.conf
> /usr/share/doc/packages/multipath-tools/multipath.conf.annotated
> /usr/share/doc/packages/multipath-tools/multipath.conf.defaults
> /usr/share/doc/packages/multipath-tools/multipath.conf.synthetic
> /usr/share/man/man5/multipath.conf.5.gz
>
>
> Mark Post
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>



-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: udevadm question

[Mark Pace]

On Thu, Aug 25, 2016 at 1:10 PM, Steffen Maier <ma...@linux.vnet.ibm.com>
wrote:

> On 08/25/2016 06:53 PM, Mark Pace wrote:
>
>> I'm having issues with that link also.
>>
>> *To enable user-friendly names or to specify aliases:*
>>
>> *In a terminal console, log in as the root user.*
>>
>> *Open the /etc/multipath.conf file in a text editor.*
>>
>> *(Optional) Modify the location of the /var/lib/multipath/bindings file. *
>>
>> *The alternate path must be available on the system root device where
>> multipath can find it. *
>>
>
> Does your multipath volume contain your root-fs?
> If not, you can definitely skip this optional step.
>

No this new multipath is going to be used as a data devive


>
> *Move the /var/lib/multipath/bindings file to /etc/multipath/bindings.*
>>
>> *Set the bindings_file option in the defaults section of
>> /etc/multipath.conf to this new location. For example:*
>> On my system I don't have any of those files.
>> /etc/multipath.conf
>> /var/lib/multipath <-- that subdirectory does exist in /var/lib
>>
>
> The only relevant step for simple data volumes is
> "5. (Optional) Specify your own names for devices by using the alias
> option in the multipath section."
> (and 6 to save the changes)
>

But I don't have a multipath.conf file.  I don't have anything to use as a
template to create this file.


>
> On Thu, Aug 25, 2016 at 12:33 PM, Mark Pace <pacemainl...@gmail.com>
>> wrote:
>>
>> Thank you for the comments and the link.  I'll go looking there.
>>>
>>> The manual I refer to is - SC33-8413-08 - How to use FC-attached SCSI
>>> devices with Linux on z Systems
>>>
>>
> OK, thanks for letting me know.
>
> Parts of this book are superseded by the more often updated
> "Device Drivers, Features, and Commands" book
> or respective distro documentation (for the case here).
>
>
>
> --
> Mit freundlichen Grüßen / Kind regards
> Steffen Maier
>
> Linux on z Systems Development
>
> IBM Deutschland Research & Development GmbH
> Vorsitzende des Aufsichtsrats: Martina Koederitz
> Geschaeftsfuehrung: Dirk Wittkopp
> Sitz der Gesellschaft: Boeblingen
> Registergericht: Amtsgericht Stuttgart, HRB 243294
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>



-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: udevadm question

[Mark Pace]

I'm having issues with that link also.

*To enable user-friendly names or to specify aliases:*
-

*In a terminal console, log in as the root user.*
-

*Open the /etc/multipath.conf file in a text editor.*

*(Optional) Modify the location of the /var/lib/multipath/bindings file. *

*The alternate path must be available on the system root device where
multipath can find it. *
-

*Move the /var/lib/multipath/bindings file to /etc/multipath/bindings.*

*Set the bindings_file option in the defaults section of
/etc/multipath.conf to this new location. For example:*
On my system I don't have any of those files.
/etc/multipath.conf
/var/lib/multipath <-- that subdirectory does exist in /var/lib



On Thu, Aug 25, 2016 at 12:33 PM, Mark Pace <pacemainl...@gmail.com> wrote:

> Thank you for the comments and the link.  I'll go looking there.
>
> The manual I refer to is - SC33-8413-08 - How to use FC-attached SCSI
> devices with
> Linux on z Systems
>
>
> On Thu, Aug 25, 2016 at 12:27 PM, Steffen Maier <ma...@linux.vnet.ibm.com>
> wrote:
>
>> Hi Mark,
>>
>> On 08/25/2016 06:20 PM, Mark Pace wrote:
>>
>>> sles 11sp3
>>>
>>> Working with FCP devices for the first time.
>>> I have 2 devices that I am using to multipath.
>>> I've followed the manual pretty well to multipath these devices.
>>>
>>>  multipath -ll
>>>
>>
>> multipathd -k'show topo'
>> is preferred because
>> - it only works if multipathd runs which is a requirement
>> - it does not cause unnecessary load due to extra path checks
>>
>> 36005076307ffd4da0028 dm-1 IBM,2107900
>>> size=100G features='1 queue_if_no_path' hwhandler='0' wp=rw
>>> `-+- policy='service-time 0' prio=1 status=active
>>>   |- 0:0:0:1076379648 sda 8:0  active ready running
>>>   `- 1:0:0:1076379648 sdb 8:16 active ready running
>>>
>>> So now I have this device with the really long name -
>>> /dev/mapper/36005076307ffd4da0028
>>> /dev/mapper/36005076307ffd4da0028_part1
>>>
>>> In the manual it talks about using udev to map it to a more friendly
>>> name,
>>> there it goes wrong. The manual talks about udevinfo, which doesn't
>>> exist,
>>> it's part of udevadm, but that output doesn't look like the manual.
>>>
>>> I'm looking for example of udevadm to add a rule to rename those to
>>> something short and easy to remember.
>>>
>>
>> Which manual do you refer to?
>>
>> While udev can be used in general to rename devices,
>> for multipath devices there is a much easier common way to do this via
>> alias names in multipath.conf:
>> https://www.suse.com/documentation/sles11/stor_admin/data/mpionames.html
>>
>> --
>> Mit freundlichen Grüßen / Kind regards
>> Steffen Maier
>>
>> Linux on z Systems Development
>>
>> IBM Deutschland Research & Development GmbH
>> Vorsitzende des Aufsichtsrats: Martina Koederitz
>> Geschaeftsfuehrung: Dirk Wittkopp
>> Sitz der Gesellschaft: Boeblingen
>> Registergericht: Amtsgericht Stuttgart, HRB 243294
>>
>> --
>> For LINUX-390 subscribe / signoff / archive access instructions,
>> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
>> visit
>> http://www.marist.edu/htbin/wlvindex?LINUX-390
>> --
>> For more information on Linux on System z, visit
>> http://wiki.linuxvm.org/
>>
>
>
>
> --
> The postings on this site are my own and don’t necessarily represent
> Mainline’s positions or opinions
>
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
>
>
>
>


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: udevadm question

[Mark Pace]

Thank you for the comments and the link.  I'll go looking there.

The manual I refer to is - SC33-8413-08 - How to use FC-attached SCSI
devices with
Linux on z Systems


On Thu, Aug 25, 2016 at 12:27 PM, Steffen Maier <ma...@linux.vnet.ibm.com>
wrote:

> Hi Mark,
>
> On 08/25/2016 06:20 PM, Mark Pace wrote:
>
>> sles 11sp3
>>
>> Working with FCP devices for the first time.
>> I have 2 devices that I am using to multipath.
>> I've followed the manual pretty well to multipath these devices.
>>
>>  multipath -ll
>>
>
> multipathd -k'show topo'
> is preferred because
> - it only works if multipathd runs which is a requirement
> - it does not cause unnecessary load due to extra path checks
>
> 36005076307ffd4da0028 dm-1 IBM,2107900
>> size=100G features='1 queue_if_no_path' hwhandler='0' wp=rw
>> `-+- policy='service-time 0' prio=1 status=active
>>   |- 0:0:0:1076379648 sda 8:0  active ready running
>>   `- 1:0:0:1076379648 sdb 8:16 active ready running
>>
>> So now I have this device with the really long name -
>> /dev/mapper/36005076307ffd4da0028
>> /dev/mapper/36005076307ffd4da0028_part1
>>
>> In the manual it talks about using udev to map it to a more friendly name,
>> there it goes wrong. The manual talks about udevinfo, which doesn't exist,
>> it's part of udevadm, but that output doesn't look like the manual.
>>
>> I'm looking for example of udevadm to add a rule to rename those to
>> something short and easy to remember.
>>
>
> Which manual do you refer to?
>
> While udev can be used in general to rename devices,
> for multipath devices there is a much easier common way to do this via
> alias names in multipath.conf:
> https://www.suse.com/documentation/sles11/stor_admin/data/mpionames.html
>
> --
> Mit freundlichen Grüßen / Kind regards
> Steffen Maier
>
> Linux on z Systems Development
>
> IBM Deutschland Research & Development GmbH
> Vorsitzende des Aufsichtsrats: Martina Koederitz
> Geschaeftsfuehrung: Dirk Wittkopp
> Sitz der Gesellschaft: Boeblingen
> Registergericht: Amtsgericht Stuttgart, HRB 243294
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>



-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

udevadm question

[Mark Pace]

sles 11sp3

Working with FCP devices for the first time.
I have 2 devices that I am using to multipath.
I've followed the manual pretty well to multipath these devices.

 multipath -ll
36005076307ffd4da0028 dm-1 IBM,2107900
size=100G features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=1 status=active
  |- 0:0:0:1076379648 sda 8:0  active ready running
  `- 1:0:0:1076379648 sdb 8:16 active ready running

So now I have this device with the really long name -
/dev/mapper/36005076307ffd4da0028
/dev/mapper/36005076307ffd4da0028_part1

In the manual it talks about using udev to map it to a more friendly name,
there it goes wrong. The manual talks about udevinfo, which doesn't exist,
it's part of udevadm, but that output doesn't look like the manual.

I'm looking for example of udevadm to add a rule to rename those to
something short and easy to remember.


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Dynamically add a network port

[Mark Pace]

That did the trick.

qeth_configure 0.0.3d00 0.0.3d01 0.0.3d02 1

Thank you, all.  Have a great weekend.

On Fri, Aug 19, 2016 at 11:14 AM, Mark Post <mp...@suse.com> wrote:

> >>> On 8/19/2016 at 10:59 AM, Mark Pace <pacemainl...@gmail.com> wrote:
> > Trying to dynamically add a network port.
> > Granted linux access to the vswitch
> >
> > set vswitch vswbpic grant sles001
> > Command complete
> >
> > Then defined the virtual nic to linux
> > sles001:~ # vmcp define nic 3d00 type qdio dev 3
> > NIC 3D00 is created; devices 3D00-3D02 defined
> > sles001:~ # vmcp couple 3d00 system vswbpic
> > NIC 3D00 is connected to VSWITCH SYSTEM VSWBPIC
> >
> > When I try to bring the nic online.
> > sles001:~ # chccwdev -e 0.0.3d00-0.0.3d02
> > Setting device 0.0.3d00 online
> > Failed (Invalid argument)
> > Failed
> >
> > Not sure what I am missing, or what the Invalid argument is.
>
> Try using qeth_configure:
> qeth_configure 0.0.3d00 0.0.3d01 0.0.3d02 1
>
> This has the added benefit of writing out the udev rules to make the NIC
> persistent across reboots.
>
>
> Mark Post
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>



-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Dynamically add a network port

[Mark Pace]

Pedro - sles11 sp3

I'm not sure what Sebastian means by grouping them.

On Fri, Aug 19, 2016 at 11:13 AM, Pedro Henrique dos Santos Principeza <
pedro...@br.ibm.com> wrote:

> Mark,
>
> If that's SLES12, you need to take them out of the cio_ignore list, with:
>
> # cio_ignore -r 
>
> Hope that helps.
>
> Regards,
> --
> Pedro Principeza
> Senior SW Support Engineer - IBM Brazil Linux Support
>
>
>
> From:   Mark Pace <pacemainl...@gmail.com>
> To: LINUX-390@VM.MARIST.EDU
> Date:   08/19/2016 12:01 PM
> Subject:Dynamically add a network port
> Sent by:Linux on 390 Port <LINUX-390@VM.MARIST.EDU>
>
>
>
> Trying to dynamically add a network port.
> Granted linux access to the vswitch
>
> set vswitch vswbpic grant sles001
> Command complete
>
> Then defined the virtual nic to linux
> sles001:~ # vmcp define nic 3d00 type qdio dev 3
> NIC 3D00 is created; devices 3D00-3D02 defined
> sles001:~ # vmcp couple 3d00 system vswbpic
> NIC 3D00 is connected to VSWITCH SYSTEM VSWBPIC
>
> When I try to bring the nic online.
> sles001:~ # chccwdev -e 0.0.3d00-0.0.3d02
> Setting device 0.0.3d00 online
> Failed (Invalid argument)
> Failed
>
> Not sure what I am missing, or what the Invalid argument is.
>
> --
> The postings on this site are my own and don’t necessarily represent
> Mainline’s positions or opinions
>
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>
>
>
>
>
>


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Dynamically add a network port

[Mark Pace]

Trying to dynamically add a network port.
Granted linux access to the vswitch

set vswitch vswbpic grant sles001
Command complete

Then defined the virtual nic to linux
sles001:~ # vmcp define nic 3d00 type qdio dev 3
NIC 3D00 is created; devices 3D00-3D02 defined
sles001:~ # vmcp couple 3d00 system vswbpic
NIC 3D00 is connected to VSWITCH SYSTEM VSWBPIC

When I try to bring the nic online.
sles001:~ # chccwdev -e 0.0.3d00-0.0.3d02
Setting device 0.0.3d00 online
Failed (Invalid argument)
Failed

Not sure what I am missing, or what the Invalid argument is.

-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Simple DASD question

[Mark Pace]

You could try.

sles003:~> /sbin/lsdasd
Bus-ID Status  Name  Device  Type  BlkSz  Size  Blocks
==
0.0.0201   active  dasda 94:0ECKD  ???7042MB???


On Tue, Apr 19, 2016 at 2:51 PM, Tom Huegel  wrote:

> I am sure the answer must be simple.
> How can I tell if a disk (3390-9) is actually being used?
>
> Background:
> I just installed SUSE 12 specifying 2 3390-9 on the installation panel.
> I tried to add a package and I get 'no space on DASD' condition.
> I am guessing the installation only used the first disk, but how can I be
> sure?
> Assuming I can determine the second disk is unused I should be able to
> extend the LVM to it and my problem would be solved. Right?
>
> Thanks
> Tom
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>



-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: SUSE Linux Enterprise Server 12 Service Pack 1 is now available

[Mark Pace]

The linked worked for me also.

Thanks, Mark.

On Thu, Dec 17, 2015 at 11:16 AM, Mark Post  wrote:

> >>> On 12/17/2015 at 04:09 AM, Christer Solskogen <
> christer.solsko...@gmail.com>
> wrote:
> > I cant seem to download it. Invalid token.
> > And if I go the suse.com and download it from there, the System Z page
> > will send me to ppc64le isos.
>
> The link I gave works for me.  Perhaps clearing your browser cookies,
> etc., will help.
>
> I've reported the problem with the other page getting routed to the PPCle
> page.
>
>
> Mark Post
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>



-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Are weekly z/VM IPLs necessary?

[Mark Pace]

I IPL z/VM only when CP maintenance is applied.  I used to reboot/IPL my
Linux guests at the same time.  I no longer do that.  I simply move them to
another z/VM with LGR and after the z/VM IPL I move them back again.  I
can't think of the last time I had to reboot/IPL my Linux guests.

On Wed, May 27, 2015 at 11:30 PM, Marcy Cortes 
marcy.d.cor...@wellsfargo.com wrote:

 You've gotten a lot of answers and they are worrisome!

 Here's my 5 or 6 cents.

 Yes, z/VM and Linux can go a very long time without being IPL'd/rebooted.
 Your applications may or may not.   I would argue if they cannot, they need
 to solve the problem rather than clean it up with an IPL and/or reboot.
  If they need a reboot every weekend to clean up their memory problems,
 what happens if their volume doubles?  Will they start rebooting every 3.5
 days?  We saw an app that started having very intermittent periods of weird
 delays after 5 or 6 weeks of uptime that was solved by an app recycle so
 they are now searching for a leak. I will add that I don't think I've
 ever seen an app leak problem affect Linux itself or for that matter VM
 itself - cycling the app or pkill -u appuser has been enough to clear up
 any memory issues.   If someone asks your to recycle a server to solve an
 app problem , just say no ( Or more diplomatically, really??can't we try
 just recycling the app first?).   The only ones I've seen that that was
 actually necessary on was when the OOM killer on Linux shot things, visible
 in the console.  At that point reboot is inevitable and probably the server
 was short on memory to start with) .

 If you go more than a couple months on Linux or even on z/VM these days
 (and we all follow IBM ResourceLink Security for z/VM right?) , your patch
 policy is very generous or non-existent.

 I would say that we are at probably 5-6 VM IPLs per year to stay current
 (RSUs, releases, HW ucode), apply fixes we need (we find bugs, we apply
 fixes, we don't wait around to find the bugs that someone else already did)
 , and all security fixes.

 Linux is also averaging every other month for a reboot needed for kernel
 and/or glibc things that of course will require a reboot.   Our challenge
 these days is to just coordinate those to same weekends so that there are
 change-free holiday weekends and system change free weekends so that those
 are available for application changes.

 PS - Our WMB (IIB) doesn't need weekly recycles as far as I've heard and
 we've been running that for probably 4 or 5 years.   Its supporting some
 70+ applications.
 These days when someone brags about uptime I'm not impressed.  Watch the
 youtube from Share Seattle http://www.share.org/p/bl/et/blogaid=343
  Yeah, it was z/OS, but is your tn3270 running encrypted and not subject to
 all the SSL bugs?!


 PPS to Sir Alan,: i need a card for the security weasel club, thanks :)


 Marcy



 -Original Message-
 From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
 Will, Chris
 Sent: Wednesday, May 27, 2015 7:34 AM
 To: LINUX-390@VM.MARIST.EDU
 Subject: [LINUX-390] Are weekly z/VM IPLs necessary?

 We have gotten in the habit of IPLing our z/VM and zLinux guests every
 Sunday during our standalone window.  With the window shrinking and the
 need for 24/7 availability is it really necessary to IPL every week?  If
 not what potential problems could we run into by not doing the IPL (memory
 leaks, logs filling etc.).  This is in comparison to the Intel side of the
 shop (Red Hat, Windows) where they go months between IPLs.  The only
 benefit I see is the opportunity to recycle WMB execution groups.

 Chris Will



 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 directed. If you are not the intended recipient, you are
 hereby notified that any viewing, copying, disclosure or distribution of
 this information is prohibited. Please notify the sender, by electronic
 mail or telephone, of any unintended receipt and delete the original
 message without making any copies.

  Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are
 nonprofit corporations and independent licensees of the Blue Cross and Blue
 Shield Association.

 --
 For LINUX-390 subscribe / signoff / archive access instructions, send
 email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit http://wiki.linuxvm.org/

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 

Re: zVM/Linux Upgrade

[Mark Pace]

Sorry - late to the party.  Is this a 2nd level install?  And is that Q V
CONS from the 2nd level guest?

If so I think you need to be doing a LOADPARM=009

On Thu, May 7, 2015 at 3:01 PM, Dazzo, Matt mda...@pch.com wrote:

 Thanks for all the replies. But I have another question, I get the
 HCPSED6013A msg when I IPL. I used force the first time and then tried warm
 the second time. I am using loadparm=SYSC as that was used with my old
 system. The install guide has SYSG used for install, I tried SYSG but the
 system will not even come up. Any help is appreciated, thanks Matt

 q cons
 CONS 0009 ON LDEV L0003   TERM START HOST TCPIPFROM 10.37.0.102
  0009 CL T NOCONT NOHOLD COPY 001READY FORM STANDARD
  0009 TO MAINT630 RDR DIST SYSPROG   FLASHC 000 DEST OFF
  0009 FLASH   CHAR   MDFY   0 FCB   LPP OFF
  0009 3215   NOEOF OPEN 0015 NOKEEP NOMSG NONAME
  0009 SUBCHANNEL = 

 -Original Message-
 From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
 Alan Altmark
 Sent: Wednesday, May 06, 2015 11:47 AM
 To: LINUX-390@VM.MARIST.EDU
 Subject: Re: zVM/Linux Upgrade

 On Wednesday, 05/06/2015 at 11:30 EDT, Dazzo, Matt mda...@pch.com
 wrote:
  My upgrade/install of 6.3 from 6.1 is complete, first time yea!.
 Checking on
  the service level I noticed that the new 6.3 system is at 1501 but my
 6.3
  install DVD states 6.3 with RSU6304. So I though the 6304 service would
 have
  gone on with the install? Question is, do I try to install the service
 off the
  DVD or pull from shop zseries? I have searched all over for instructions
 on how
  to install the service from the DVD and can't find it anywhere, any help
 there?

 From the Plan your DVD Installation part of the Installation Guide:  
 Installation will install the RSU shipped as part of the z/VM product DVD.
 If additional service is
 required, install the additional service after your initial installation
 is complete.

 And if you look at http://www.vm.ibm.com/service/rsu/stk630.html, you will
 see that RSU6304 contains service level 1501.   RSUs are containers that
 hold service level upgrades.  The various components may be at different
 service levels within the RSU.

 Alan Altmark

 Senior Managing z/VM and Linux Consultant
 Lab Services System z Delivery Practice
 IBM Systems  Technology Group
 ibm.com/systems/services/labservices
 office: 607.429.3323
 mobile; 607.321.7556
 alan_altm...@us.ibm.com
 IBM Endicott

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: zVM/Linux Upgrade

[Mark Pace]

Well I learned something today.

Thanks, Alan.

On Fri, May 8, 2015 at 11:58 AM, Alan Altmark alan_altm...@us.ibm.com
wrote:

 On Thursday, 05/07/2015 at 03:10 EDT, Dazzo, Matt mda...@pch.com
 wrote:
  Thanks for all the replies. But I have another question, I get the
 HCPSED6013A
  msg when I IPL. I used force the first time and then tried warm the
 second
  time. I am using loadparm=SYSC as that was used with my old system. The
 install
  guide has SYSG used for install, I tried SYSG but the system will not
 even come
  up. Any help is appreciated, thanks Matt

 When you use IPL  LOADPARM SYSC, then CP will use the integrated
 Operating System Messages console.  When CP wants a response from it
 (you), the icon will flash.   This support is virtualized, so the flashing
 icon is simulated by HCPSED6013A.

 To respond to the virtual Operating System Messages console, use #CP
 VINPUT VMSG xx, where # is the linend character on your *first
 level* ID.

 If you want CP to use 009, then
 1. TERMINAL  SYS3270 ON
 2. IPL  LOADPARM SYSG
 3. When SAPL comes up, put CONS=SYSG in the IPL parameters

 Some people use TERMINAL CONMODE 3270, and then IPL  LOADPARM 009.
 That's fine, but just know that once you issue TERMINAL CONMODE 3270, CMS
 can no longer write to the terminal.  Disconcerting, perhaps, but it won't
 stop you from IPLing CP.

 Alan Altmark

 Senior Managing z/VM and Linux Consultant
 Lab Services System z Delivery Practice
 IBM Systems  Technology Group
 ibm.com/systems/services/labservices
 office: 607.429.3323
 mobile; 607.321.7556
 alan_altm...@us.ibm.com
 IBM Endicott

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: SUSE FTP Server issue

[Mark Pace]

For giggles you might try running your FTP as a listen server instead of
being started by xinetd.

listen=YES

On Wed, May 6, 2015 at 8:04 AM, Donald J. dona...@4email.net wrote:

 The parameters would go in your vsftpd config file which is probably
 in /etc or /etc/vsftpd.  I no longer have a linux to look at to verify
 that.
 As I said, I don't think increasing timers from 60 or 300 is going to
 fix your problem.  60 seconds is a long timer.  You probably are
 having a total hang at some point, so increasing a timer probably
 won't help, but it won't hurt either.

 You misunderstood what I said about netstat.  Your want to do
 netstat commands while your ftp is going so you can see the port
 numbers in the REMOTE column.  NOTHING is happening at
 the time you did the netstat below.  Would be best to put the
 netstat in a script and put a one second delay between commands.

 Only reason for netstat is to see if you are hanging on one
 particular remote port number.  Your netstat below only shows
 local port numbers because there are no remote connections
 active at that time.
 --
   Donald J.
   dona...@4email.net

 On Wed, May 6, 2015, at 01:03 AM, Mainframe Mainframe wrote:
  Hello Donald,
 Thanks for reply. I checked for my FTP server from
  # netstat -antp |grep listen -i
  tcp0  0 0.0.0.0:32769   0.0.0.0:*
  LISTEN
   -
  tcp0  0 0.0.0.0:20490.0.0.0:*
  LISTEN
   -
  tcp0  0 0.0.0.0:838 0.0.0.0:*
  LISTEN
   4899/rpc.mountd
  tcp0  0 0.0.0.0:15  0.0.0.0:*
  LISTEN
   4994/xinetd
  tcp0  0 0.0.0.0:111 0.0.0.0:*
  LISTEN
   4233/portmap
  tcp0  0 0.0.0.0:21  0.0.0.0:*
  LISTEN
   4994/xinetd
  tcp0  0 0.0.0.0:23  0.0.0.0:*
  LISTEN
   4994/xinetd
  tcp0  0 0.0.0.0:631 0.0.0.0:*
  LISTEN
   4710/cupsd
  tcp0  0 127.0.0.1:250.0.0.0:*
  LISTEN
   4862/master
  tcp0  0 0.0.0.0:667 0.0.0.0:*
  LISTEN
   4726/ypbind
  tcp0  0 :::22   :::*
 LISTEN
   4362/sshd
 
 
  So, in xinetd, we have
 
   # cat /etc/xinetd.d/vsftpd
  # default: off
  # description:
  #   The vsftpd FTP server serves FTP connections. It uses
  #   normal, unencrypted usernames and passwords for authentication.
  # vsftpd is designed to be secure.
  service ftp
  {
  socket_type = stream
  protocol= tcp
  wait= no
  user= root
  server  = /usr/sbin/vsftpd
  #server_args =
  #log_on_success  += DURATION USERID
  #log_on_failure  += USERID
  #nice= 10
  }
 
 
  Now, my query is do I need to add the parameter you mentioned in last
  response in this vsftpd file.
 
  accept_timeout
  The timeout, in seconds, for a remote client to establish connection
 with a
  PASV style data connection.
  Default: 60
 
  connect_timeout
  The timeout, in seconds, for a remote client to respond to our PORT style
  data connection.
  Default: 60
 
  data_connection_timeout
  The timeout, in seconds, which is roughly the maximum time we permit data
  transfers to stall for with no progress. If the timeout triggers, the
  remote client is kicked off.
  Default: 300
 
  idle_session_timeout
  The timeout, in seconds, which is the maximum time a remote client may
  spend between FTP commands. If the timeout triggers, the remote client is
  kicked off.
  Default: 300
 
  We contacted network team as well, But no solution till now. I am really
  not able to find why FTP failing only while coping  MNT190 disk.
 
  IUGIDV8339I  BYPASSING INSTDIR EXEC DUE TO PROGRAM RESTART
  IUGILB8440I NOW LOADING MAINT190 (190) DISK 4 OF 317
  IUGILB8344I FTPGET COMMAND FAILED FOR CKD190
  REISSUING COMMAND.
  CKD190*
  DMSRXS1408W File TCPIP DATA * not found
  PROCESSING CKD19000
  IUGILB8342E THE COMMAND ' PIPE FTPGET CKD190* ' FAILED WITH RC= -111
  IUGIDV8342E THE COMMAND ' EXEC INSTLBMD ' FAILED WITH RC= 100
  IUGIDV8376E INSTDVD EXEC ENDED IN ERROR
  IUGITL8342E THE COMMAND ' EXEC INSTDVD ' FAILED WITH RC=100
  IUGITL8376E INSTALL EXEC ENDED IN ERROR. TO RESTART CORRECT THE PROBLEM
 AND
  REIS
  SUE INSTALL
 
 
  Thanks for help.
 
 
  On Thu, Apr 30, 2015 at 6:37 PM, Donald J. dona...@4email.net wrote:
 
   Are these valid parms on your version of vsftpd?
   But it is unlikely you would exceed 60 or 300 seconds.
  
   accept_timeout
   The timeout, in seconds, for a remote client to establish connection
 with
   a PASV style data connection.
   Default: 60
  
   connect_timeout
   The timeout, in seconds, for a remote client to respond to our PORT
 style
   data connection.
   Default: 60
  
   data_connection_timeout
   The timeout, 

Silly question about SLES

[Mark Pace]

Why is SLES coming out with a SLES 11SP4 when they have already released
SLES 12?


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Silly question about SLES

[Mark Pace]

Thank you, all.  I have never noticed that the new version was released
before the SP4 for the previous version.

On Tue, Apr 28, 2015 at 2:58 PM, Marcy Cortes marcy.d.cor...@wellsfargo.com
 wrote:

 This is good info about what is in SP4.


 https://share.confex.com/share/124/webprogram/Handout/Session16418/SHARE_Seattle_2015_SLES_z_roadmap_16418.pdf


 The release notes say Q3 CY 2015 although the chart in the above link
 looks like Q2.

 https://www.suse.com/releasenotes/x86_64/SUSE-SLES/11-SP4/

 (Ignore the x86 in the URL  - seems they include s390x too in the same doc)

 Given the 6 months to upgrade, i sure hope it is September and not July so
 we don't run into needing to complete it before the holidays and freeze
 periods.



 -Original Message-
 From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
 Dave Jones
 Sent: Tuesday, April 28, 2015 11:08 AM
 To: LINUX-390@VM.MARIST.EDU
 Subject: Re: [LINUX-390] Silly question about SLES

 Does anyone know when SLES 11 SP 4 will be released?

 Have a good one, too.

 DJ

 On 04/28/2015 11:45 AM, Cameron Seader wrote:
  The Short answer.. Its a natural progression. We always do at least 4
  Service Packs per version.
 
  Long answer.. This is to satisfy the 13 year lifecycle that SLES 11 has.
  When SLES 11 SP4 is released you will have 6 months to move to the
  next Service Pack before SP3 is out of support. If you can't meet that
  time frame then you can purchase Long Term Service Pack Support which
  will give you an 18 month window.
 
  More information on our lifecycle here.
 
  https://www.suse.com/lifecycle/
 
  On 04/28/2015 10:25 AM, Mark Pace wrote:
  Why is SLES coming out with a SLES 11SP4 when they have already
  released SLES 12?
 
 
 
  --
  Cameron Seader
  Sr. Systems Engineer
  SUSE
  c...@suse.com
  (W)208-577-6857
  (M)208-420-2167
 
  Register for SUSECon 2015
  www.susecon.com
 
  --
  For LINUX-390 subscribe / signoff / archive access instructions, send
  email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
  visit
  http://www.marist.edu/htbin/wlvindex?LINUX-390
  --
  For more information on Linux on System z, visit
  http://wiki.linuxvm.org/
 

 --
 Dave Jones
 V/Soft Software
 www.vsoft-software.com
 Houston, TX
 281.578.7544

 --
 For LINUX-390 subscribe / signoff / archive access instructions, send
 email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit http://wiki.linuxvm.org/

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Registration Error

[Mark Pace]

Thanks for the quick responses.  Hopefully they will be just as quick in
the SuSE forums and give me a link to this updated
s390-tools-1.24.1-38.17.8188.1.PTF.919293.s390x.rpm

On Fri, Apr 24, 2015 at 4:39 PM, Michael O'Reilly mik...@us.ibm.com wrote:

 Mark,

 Re Validation failed: Uuid should be formatted as UUID ...

 SuSE engineering has determined that the SUSEconnect problem is due to 
 for registration purposes on s390x SUSEConnect requires the uuid to be
 extracted via `read_values -u` SUSEConnect either expects an empty output
 or a properly formatted uuid.

 SuSE provided a s390-tools-1.24.1-38.17.8188.1.PTF.919293.s390x.rpm
 containing:
 * Wed Mar 04 2015 pu...@suse.com
 - update read_values: print error messages to standard error
   (bnc#919293)

 Mike O'Reilly
 IBM Linux Change Team











  Mark Pace
  pacemainline@gma
  il.comTo
  Sent by: Linux on LINUX-390@VM.MARIST.EDU
  390 Port   cc
  linux-...@vm.mar
  IST.EDU  Subject
Registration Error

  04/24/2015 01:28
  PM


  Please respond to
  Linux on 390 Port
  linux-...@vm.mar
  IST.EDU






 I just posted this on the SuSE forums also,  but to see if anyone here has
 had this problem before and knows how to fix it.

 Trying to register a new system for online updates. When I go through Yast
 and enter my code I get an error.
 Error
 Registration server error.
 Retry registration later.
 Details: Validation failed: Uuid should be formatted as UUID

 Well that doesn't make a lot of sense.
 So I went and requested a new registration code for Linux Enterprise Server
 on System z.
 I receive an email saying that my code had been updated. So I copy and
 paste the new registration code into yast and now I get a new error.

 Error
 Registration Failed
 Details: Invalid registration code

 Any ideas what I do now?

 --
 The postings on this site are my own and don’t necessarily represent
 Mainline’s positions or opinions

 Mark D Pace
 Senior Systems Engineer
 Mainline Information Systems

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/





-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Registration Error

[Mark Pace]

I just posted this on the SuSE forums also,  but to see if anyone here has
had this problem before and knows how to fix it.

Trying to register a new system for online updates. When I go through Yast
and enter my code I get an error.
Error
Registration server error.
Retry registration later.
Details: Validation failed: Uuid should be formatted as UUID

Well that doesn't make a lot of sense.
So I went and requested a new registration code for Linux Enterprise Server
on System z.
I receive an email saying that my code had been updated. So I copy and
paste the new registration code into yast and now I get a new error.

Error
Registration Failed
Details: Invalid registration code

Any ideas what I do now?

-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Registration Error

[Mark Pace]

This is for SLES 12 if it makes a difference.

On Fri, Apr 24, 2015 at 4:28 PM, Mark Pace pacemainl...@gmail.com wrote:

 I just posted this on the SuSE forums also,  but to see if anyone here has
 had this problem before and knows how to fix it.

 Trying to register a new system for online updates. When I go through Yast
 and enter my code I get an error.
 Error
 Registration server error.
 Retry registration later.
 Details: Validation failed: Uuid should be formatted as UUID

 Well that doesn't make a lot of sense.
 So I went and requested a new registration code for Linux Enterprise
 Server on System z.
 I receive an email saying that my code had been updated. So I copy and
 paste the new registration code into yast and now I get a new error.

 Error
 Registration Failed
 Details: Invalid registration code

 Any ideas what I do now?

 --
 The postings on this site are my own and don’t necessarily represent
 Mainline’s positions or opinions

 Mark D Pace
 Senior Systems Engineer
 Mainline Information Systems






-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Retiring

[Mark Pace]

Congratulations.  Enjoy your retirement.

On Thu, Feb 26, 2015 at 8:55 AM, Smith, Ann (CTO Service Delivery) 
ann.sm...@thehartford.com wrote:

 Tomorrow is my last day at IBM
 Hit the big 60 and I am retiring
 8 years working in MVS, 22 in VM and 8 with Linux
 I will miss the work and the people I've met along the way

 Annie Smith
 
 This communication, including attachments, is for the exclusive use of
 addressee and may contain proprietary, confidential and/or privileged
 information.  If you are not the intended recipient, any use, copying,
 disclosure, dissemination or distribution is strictly prohibited.  If you
 are not the intended recipient, please notify the sender immediately by
 return e-mail, delete this communication and destroy all copies.
 

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: SLES12 / partitioning

[Mark Pace]

sles003:~ df -Ht
df: option requires an argument -- 't'
Try 'df --help' for more information.
sles003:~ df -H
Filesystem   Size  Used Avail Use% Mounted on
/dev/mapper/system-root  5.7G  2.5G  3.0G  46% /
devtmpfs 460M  8.2k  460M   1% /dev
tmpfs467M 0  467M   0% /dev/shm
tmpfs467M  7.4M  460M   2% /run
tmpfs467M 0  467M   0% /sys/fs/cgroup
/dev/mapper/system-root  5.7G  2.5G  3.0G  46% /.snapshots
/dev/mapper/system-root  5.7G  2.5G  3.0G  46% /var/tmp
/dev/mapper/system-root  5.7G  2.5G  3.0G  46% /var/spool
/dev/dasda1  204M   26M  168M  14% /boot/zipl
/dev/mapper/system-root  5.7G  2.5G  3.0G  46% /var/opt
/dev/mapper/system-root  5.7G  2.5G  3.0G  46% /var/lib/pgsql
/dev/mapper/system-root  5.7G  2.5G  3.0G  46% /var/lib/mailman
/dev/mapper/system-root  5.7G  2.5G  3.0G  46% /opt
/dev/mapper/system-root  5.7G  2.5G  3.0G  46% /var/crash
/dev/mapper/system-root  5.7G  2.5G  3.0G  46% /var/log
/dev/mapper/system-root  5.7G  2.5G  3.0G  46% /usr/local
/dev/mapper/system-root  5.7G  2.5G  3.0G  46% /boot/grub2/s390x-emu
/dev/mapper/system-root  5.7G  2.5G  3.0G  46% /home
/dev/mapper/system-root  5.7G  2.5G  3.0G  46% /var/lib/named
/dev/mapper/system-root  5.7G  2.5G  3.0G  46% /tmp
/dev/mapper/system-root  5.7G  2.5G  3.0G  46% /srv


On Thu, Dec 18, 2014 at 2:24 PM, Mark Post mp...@suse.com wrote:

  On 12/18/2014 at 09:54 AM, Mark Pace pacemainl...@gmail.com wrote:
  Playing around with the Installer and the DASD layout I found the setting
  to use a LVM based btrfs.  This created a partition with ext2 for the
  /boot/zipl and then created a partition for LVM and btrfs for the root.
 I
  then added the rest of the DASD I usually set aside for the LVM and now I
  have a nice big btrfs with everything minus /boot/zipl  .  I'll run this
 in
  a test environment for awhile so I can learn how to grow the LVM and
 btrfs
  as needed,

 I'm having a hard time visualizing this.  Perhaps a df -Ht will help me.


 Mark Post

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: SLES12 / partitioning

[Mark Pace]

I'm going back and putting / in a partition of it's own.
And will then try to add the other 3 disks to a btrfs.

So during install I don't see a way to add 3 disks to btrfs without first
creating an LVM volume group.  I see no way to run this command, btrfs
device add dev1 dev2 /path/to/filesystem during install.

On Fri, Dec 19, 2014 at 12:54 PM, Mark Post mp...@suse.com wrote:

  On 12/19/2014 at 09:46 AM, Mark Pace pacemainl...@gmail.com wrote:
  sles003:~ df -Ht
  df: option requires an argument -- 't'
  Try 'df --help' for more information.
  sles003:~ df -H
  Filesystem   Size  Used Avail Use% Mounted on
  /dev/mapper/system-root  5.7G  2.5G  3.0G  46% /
  devtmpfs 460M  8.2k  460M   1% /dev
  tmpfs467M 0  467M   0% /dev/shm
  tmpfs467M  7.4M  460M   2% /run
  tmpfs467M 0  467M   0% /sys/fs/cgroup
  /dev/mapper/system-root  5.7G  2.5G  3.0G  46% /.snapshots
  /dev/mapper/system-root  5.7G  2.5G  3.0G  46% /var/tmp
  /dev/mapper/system-root  5.7G  2.5G  3.0G  46% /var/spool
  /dev/dasda1  204M   26M  168M  14% /boot/zipl
  /dev/mapper/system-root  5.7G  2.5G  3.0G  46% /var/opt
  /dev/mapper/system-root  5.7G  2.5G  3.0G  46% /var/lib/pgsql
  /dev/mapper/system-root  5.7G  2.5G  3.0G  46% /var/lib/mailman
  /dev/mapper/system-root  5.7G  2.5G  3.0G  46% /opt
 -snip-

 OK, even though I got the switches wrong (should have been -hT) I can see
 what you've done.  First, I'll reiterate my long-standing don't put / on
 an LV recommendation.  Having the ability to boot from a read-only
 snapshot might make that less important, but I don't know that to be true
 yet.

 Since btrfs is new to everyone in an enterprise environment, I'm not sure
 what you've done is of any real benefit.  A btrfs file system can span
 multiple physical (or virtual) volumes.  So, you can do a

 btrfs device add dev1 dev2 /path/to/filesystem

 if extra space is needed.  Having everything in one large btrfs on LVM
 doesn't help with the problem of a runaway process (or user) filling up
 everything, _unless_ you start using quotas.  I suspect most people on this
 mailing list haven't bothered doing that up until now, so this would be one
 more new thing to deal with.

 It will be interesting to see what winds up working best for you and
 anyone else trying things out.  Thanks for helping me understand your setup.


 Mark Post

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Problem to test relocating a Linux image to another z/VM - Device 0592

[Mark Pace]

As part of my linux PROFILE EXEC - if it is going to IPL linux it runs an
exec that detaches all disks that do not belong to that linux guest, in my
case, all R/O disks.

On Fri, Dec 19, 2014 at 1:55 PM, Cohen, Sam sam.co...@lrs.com wrote:

 Ray,

 You should detach the CMS-oriented disks from your Linux guest before
 booting the Linux kernel.  Your kernel should only have disks attached that
 Linux will actually use.  Having disks attached/linked that are dedicated
 to one particular z/VM image will prevent relocation.

 Thanks,


 Sam Cohen
 Levi, Ray  Shoup, Inc.

 -Original Message-
 From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
 Chu, Raymond
 Sent: Friday, December 19, 2014 11:36 AM
 To: LINUX-390@VM.MARIST.EDU
 Subject: Re: Problem to test relocating a Linux image to another z/VM -
 Device 0592

 Hi Alan and all,

 The EQID on VSWITCH was fixed. When I ran the following:

 vmreloc test Lnx004 zvm2
 HCPRLH1940E LNX004 is not relocatable for the following reason (s):
 HCPRLI1996I LNX004: Virtual machine device 0592 is a link to a local
 minidisk

 Below is the definition for LNXDFLT profile for Linux images and TCPMAINT

 IDENTITY TCPMAINT PASSWORD   32M   64M ABCG
  INCLUDE TCPCMSU
  BUILD ON ZVM1 USING SUBCONFIG TCPMNT-1
  BUILD ON ZVM2 USING SUBCONFIG TCPMNT-2
  BUILD ON ZVM3 USING SUBCONFIG TCPMNT-3
  BUILD ON ZVM4 USING SUBCONFIG TCPMNT-4

 SUBCONFIG TCPMNT-1
  LINK 6VMTCP30 491 491 RR
  LINK 6VMTCP30 492 492 RR
  MDISK 591 3390 8558 122 XX12B4 MR RTCPMAIN WTCPMAIN MTCPMAIN
  MDISK 592 3390 8680 140 XX12B4 MR ALL  WTCPMAIN MTCPMAIN
  MDISK 198 3390 8820 009 XX12B4 MR RTCPMAIN WTCPMAIN MTCPMAIN
  MDISK 191 3390 8829 007 XX12B4 MR RTCPMAIN WTCPMAIN MTCPMAIN

 SUBCONFIG TCPMNT-2
  LINK 6VMTCP30 491 491 RR
 LINK 6VMTCP30 492 492 RR
  MDISK 591 3390 8558 122 XX1395 MR RTCPMAIN WTCPMAIN MTCPMAIN
  MDISK 592 3390 8680 140 XX1395 MR ALL  WTCPMAIN MTCPMAIN
  MDISK 198 3390 8820 009 XX1395 MR RTCPMAIN WTCPMAIN MTCPMAIN
  MDISK 191 3390 8829 007 XX1395 MR RTCPMAIN WTCPMAIN MTCPMAIN

 SUBCONFIG TCPMNT-3
 LINK 6VMTCP30 491 491 RR
  LINK 6VMTCP30 492 492 RR
  MDISK 591 3390 8558 122 XX1A06 MR RTCPMAIN WTCPMAIN MTCPMAIN
  MDISK 592 3390 8680 140 XX1A06 MR ALL  WTCPMAIN MTCPMAIN
  MDISK 198 3390 8820 009 XX1A06 MR RTCPMAIN WTCPMAIN MTCPMAIN  MDISK 191
 3390 8829 007 XX1A06 MR RTCPMAIN WTCPMAIN MTCPMAIN

 SUBCONFIG TCPMNT-4
  LINK 6VMTCP30 491 491 RR
  LINK 6VMTCP30 492 492 RR
  MDISK 591 3390 8558 122 XX139F MR RTCPMAIN WTCPMAIN MTCPMAIN
  MDISK 592 3390 8680 140 XX139F MR ALL  WTCPMAIN MTCPMAIN
  MDISK 198 3390 8820 009 XX139F MR RTCPMAIN WTCPMAIN MTCPMAIN  MDISK 191
 3390 8829 007 VX139F MR RTCPMAIN WTCPMAIN MTCPMAIN
 *

 PROFILE LNXDFLT
   COMMAND SET VSWITCH PASSWORD GRANT USERID
   COMMAND DEFINE NIC 600 TYPE QDIO
   COMMAND COUPLE 600 TO SYSTEM VSWPSEG1
  *
   COMMAND SET VSWITCH VSWPSEG2 GRANT USERID
   COMMAND DEFINE NIC 700 TYPE QDIO
   COMMAND COUPLE 700 TO SYSTEM VSWPSEG2
  *
   CPU 00 BASE
   CPU 1
   IPL CMS
   MACHINE ESA 10
   IUCV ALLOW
   OPTION CHPIDV ONE
   CONSOLE 009 3215 T
   SPOOL 000C 2540 READER *
   SPOOL 000D 2540 PUNCH A
   SPOOL 000E 1403 A
   LINK MAINT 0190 0190 RR
   LINK MAINT 019D 019D RR
   LINK MAINT 019E 019E RR
   LINK LNXMAINT 0192 0191 RR
   LINK TCPMAINT 0592 0592 RR


 USER LNX004  PASSWORD 512M 1G G
  INCLUDE LNXDFLT
  COMMAND DEFINE STORAGE 256M STANDBY 768M
  OPTION LNKNOPAS APPLMON
  MDISK 0100 3390 0001 5008  XX1185 MR  PASSWORD PASSWORD
 PASSWORD
  MDISK 0101 3390 5009 5008  XX1185 MR PASSWORD PASSWORD PASSWORD

 As you can see the profile for LNXDFLT has a statement  LINK TCPMAINT
 0592 0592 RR. When I first tested the first zLinux image, it complained
 about the vdisk  592. I realized that this statement existed in z/VM V6.1
 so I added the statement and the first zLinux image came up and so were
 other zLinux images.

 At z/VM V6.3, when I attempted the LGR function, it complained about it.
 Believe the statement is no longer applicable and need to code to address
 to the IDENTITY TCPMAINT statement instead. However I do not what the
 coding is like. Please advise.

 Thanks,
 Ray

 -Original Message-
 From: Chu, Raymond
 Sent: Wednesday, December 17, 2014 4:26 PM
 To: 'Linux on 390 Port'
 Subject: RE: Problem to test relocating a Linux image to another z/VM

 I add the rdev 0E1C EQ myEQID TYPE OSA like this to SYSTEM CONFIG and
 reIPLed. It worked


 -Original Message-
 From: Chu, Raymond
 Sent: Wednesday, December 17, 2014 3:48 PM
 To: 'Linux on 390 Port'
 Subject: RE: Problem to test relocating a Linux image to another z/VM

 Never mind. Please ignore the previous email. It is not even a
 communication controller and it is a special device.


 -Original Message-
 From: Chu, Raymond
 Sent: Wednesday, December 17, 2014 2:44 PM
 To: LINUX-390@VM.MARIST.EDU
 Subject: RE: Problem to test relocating a Linux image to another z/VM

 Alan,

 Understood that the EQID must be assigned to the 

Re: Problem to test relocating a Linux image to another z/VM - Device 0592

[Mark Pace]

Here is the exec/pipe that I run to detach all disks link R/O.

/* * 
*\
   Name:
DETDISK
   Version:
1.0
   Author:   M.
Pace
   Function: Detach all disk linked
R/O
   Comments: Give Linux fewer disks to look
at.

History:

\* * 
*/
Trace
Off

Signal on
novalue
Parse upper source . . myname mytype mymode syn
.


'PIPE (name
DETDISK.EXEC:13)',
   '|cp q v dasd
',
   '| locate w 5 %R/O%
',
   '| spec /DET / 1 w2 nw
',
   '| cp
',
   '|
console'



exit
0



ERREXIT:  /* general errorexit routine
*/
 do i=2 to arg()  /* give errormessages (if any)
*/
say myname':' arg(i)  /* example: call errexit 99,'User
quit' */
 end

 exit
arg(1)


On Fri, Dec 19, 2014 at 3:43 PM, Alan Altmark alan_altm...@us.ibm.com
wrote:

 On Friday, 12/19/2014 at 03:35 EST, Chu, Raymond raymond@pseg.com
 wrote:
  Mark,
 
  I am still a z/VM learner. Based on your comments, my PROFILE LNXDFLT
 for
  TCPMAINT should be changed from
 
  LINK MAINT 0190 0190 RR
  LINK MAINT 019D 019D RR
  LINK MAINT 019E 019E RR
  LINK LNXMAINT 0192 0191 RR
  LINK TCPMAINT 0592 0592 RR
 
  To
  LINK MAINT 0190 0190 R
  LINK MAINT 019D 019D R
  LINK MAINT 019E 019E R
  LINK LNXMAINT 0192 0191 R
  LINK TCPMAINT 0592 0592 R
 
  Shouldn't it?

 No, those disks should linked RR.  The problem is that MAINT and TCPMAINT
 are IDENTITYs with SUBCONFIGs and those MDISKs are defined in the
 SUBCONFIGs.  That means they are local disks.  If you want to relocate the
 guest, you must first CP DETACH any linked minidisks that are defined in a
 SUBCONFIG.


 Alan Altmark

 Senior Managing z/VM and Linux Consultant
 Lab Services System z Delivery Practice
 IBM Systems  Technology Group
 ibm.com/systems/services/labservices
 office: 607.429.3323
 mobile; 607.321.7556
 alan_altm...@us.ibm.com
 IBM Endicott

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: SLES12 / partitioning

[Mark Pace]

Playing around with the Installer and the DASD layout I found the setting
to use a LVM based btrfs.  This created a partition with ext2 for the
/boot/zipl and then created a partition for LVM and btrfs for the root.  I
then added the rest of the DASD I usually set aside for the LVM and now I
have a nice big btrfs with everything minus /boot/zipl  .  I'll run this in
a test environment for awhile so I can learn how to grow the LVM and btrfs
as needed,

On Thu, Dec 18, 2014 at 9:32 AM, Levy, Alan al...@doitt.nyc.gov wrote:

 Does it make sense in just setting up one mod 29 (32000+ cylinders, app
 21G) and let the btrfs use the whole thing instead of breaking it up into
 smaller pieces (var, opt, home, etc) ?

 -Original Message-
 From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
 Mark Post
 Sent: Wednesday, December 17, 2014 6:10 PM
 To: LINUX-390@VM.MARIST.EDU
 Subject: Re: SLES12 / partitioning

  On 12/17/2014 at 09:41 AM, Mark Pace pacemainl...@gmail.com wrote:
  With btrfs now the default file system on sles12, is there a new
  recommended way to layout DASD devices?
  I would think if you had really big 3390 devices that btrfs makes sense.
  But still working with mod-9s it doesn't seem like the right fit.
 
  I'm still putting / on a minidisk and then creating a large LVM and
  breaking out home srv tmp usr var opt

 You need to be aware of how btrfs and subvolumes work so that you don't
 accidentally prevent automatic snapshots being taken of everything that is
 needed to do an operating system rollback in the event of a problem.  Being
 able to boot the system from a prior snapshot is a pretty nice feature to
 have.


 Mark Post

 --
 For LINUX-390 subscribe / signoff / archive access instructions, send
 email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit http://wiki.linuxvm.org/

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/



-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: SLES12 / partitioning

[Mark Pace]

With btrfs now the default file system on sles12, is there a new
recommended way to layout DASD devices?
I would think if you had really big 3390 devices that btrfs makes sense.
But still working with mod-9s it doesn't seem like the right fit.

I'm still putting / on a minidisk and then creating a large LVM and
breaking out
home
srv
tmp
usr
var
opt
into logical volumes in the LVM.

On Wed, Nov 19, 2014 at 4:08 PM, Mark Post mp...@suse.com wrote:

  On 11/19/2014 at 07:43 AM, Levy, Alan al...@doitt.nyc.gov wrote:
  During the install, I removed /var, /opt/ ,tmp and /home from the btrfs
  (dasda). I then created these partitions on their own device (dasdb thru
  dasde). When I log in, via maintenance mode due to the failed dependency
  errors, everything looks fine. I can see the separated partitions. I can
  create files/directories within those mount points. The /etc/fstab looks
 ok
  also. This looks like some kind of timing issue.

 Sounds like a support request is the way to go here.  But, before you do,
 check to see if any maintenance is available.  Bug fixes for SLE12 are
 going out the door all the time.


 Mark Post

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/



-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Need help with LVM in SLES 12 on System z

[Mark Pace]

Odd -  Installed a sles12 with LVM this morning - during install I did not
include the maintenance.  On reboot LVM did not start.

So I reinstalled and this time registered and checked that I wanted
maintenance installed during install.  No issues with LVM starting on the
reboot.

On Wed, Dec 17, 2014 at 1:56 PM, Offer Baruch offerbar...@gmail.com wrote:

 Hi

 I think this should be handled by udev rules...
 I don't have a sles 12 available to look at...
 Can you list your /etc/*udev*/*rules*.d/ directory?
 See if there is any lvm related files...

 Offer Baruch
 On Dec 17, 2014 7:26 PM, Linker Harley - hlinke 
 harley.lin...@acxiom.com
 wrote:

  I spent a few hours this morning manually applying all known patches to
  SLES 12.  My LV still comes up as 'NOT available' after a system reboot.
 
  I just tried the following to no avail:
  vgchange -ay  (LV status changed to available)
  pvscan -v
  vgscan -v
  lvscan -v
 
  I then went to yast | System | Services Manager and Enabled and Started
  both lvm2-activation-early and lvm2-activation.  When I clicked OK to
 save
  the configuration change I again received the pop-up which contained a
  message stating that there were no Volume Groups found.
 
  This is very frustrating.
 
 
  Harley Linker
 
  -Original Message-
  From: Linker Harley - hlinke
  Sent: Tuesday, December 16, 2014 5:52 PM
  To: LINUX-390@VM.MARIST.EDU
  Subject: RE: Need help with LVM in SLES 12 on System z
 
  No, I don't have an easy way to obtain maintenance as my system doesn't
  have internet connectivity.  I checked the available maintenance this
  afternoon but nothing looked like it was related (looking at the package
  names).
 
 
  Harley Linker
 
  -Original Message-
  From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
  Mark Post
  Sent: Tuesday, December 16, 2014 3:57 PM
  To: LINUX-390@VM.MARIST.EDU
  Subject: Re: Need help with LVM in SLES 12 on System z
 
   On 12/16/2014 at 09:19 AM, Linker Harley - hlinke
   harley.lin...@acxiom.com
  wrote:
   Mark,
  
   I used yast to add the mountpoint to fstab as you asked and it had no
   effect on the problem.  Upon reboot the system entered recovery mode
   because the LV was not available.
 
  OK, thanks.  Now, have you installed any of the maintenance that has come
  out since SLES12 went GA?
 
 
  Mark Post
 
  --
  For LINUX-390 subscribe / signoff / archive access instructions, send
  email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
  http://www.marist.edu/htbin/wlvindex?LINUX-390
  --
  For more information on Linux on System z, visit
 http://wiki.linuxvm.org/
 
 ***
  The information contained in this communication is confidential, is
  intended only for the use of the recipient named above, and may be
 legally
  privileged.
 
  If the reader of this message is not the intended recipient, you are
  hereby notified that any dissemination, distribution or copying of this
  communication is strictly prohibited.
 
  If you have received this communication in error, please resend this
  communication to the sender and delete the original message or any copy
  of it from your computer system.
 
  Thank You.
 
 
 
 
  --
  For LINUX-390 subscribe / signoff / archive access instructions,
  send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
  visit
  http://www.marist.edu/htbin/wlvindex?LINUX-390
  --
  For more information on Linux on System z, visit
  http://wiki.linuxvm.org/
 

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/



-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Problem to test relocating a Linux image to another z/VM

[Mark Pace]

Understood that the EQID must be assigned to the VSWITCHes. I searched the
define vswitch command and did not have a parameter for EQID.

Not sure how you keep misreading Alan's note.  The VSWITCH does NOT get the
EQID.  The real devices that you attach to the VSWITCH is where the EQID
belongs.

Here is an example from my system

MISZVM: BEGIN
Define VSWITCH VSWTCH3 RDEV 0600 CONTR * IP nonROUTER
MISZVM:END

BPZVM: BEGIN
Define VSWITCH VSWTCH3 RDEV 0600 CONTR * IP nonROUTER
BPZVM: END


Rdevs that relate to this vswitch.
Rdevice 0600-061F EQID OSA199 Type OSA

On Wed, Dec 17, 2014 at 2:43 PM, Chu, Raymond raymond@pseg.com wrote:

 Alan,

 Understood that the EQID must be assigned to the VSWITCHes. I searched the
 define vswitch command and did not have a parameter for EQID.

 I ran the command q controller command and it showed the follows:

 q controller

 Controller DTCVSW2   Available: YES   VDEV Range: 0600-F000 Level 630
   Capability: IP ETHERNET VLAN_ARP GVRPLINKAGGISOLATION
   NO_ENSEMBLE NO_INMN BRIDGE_CAPABLEVEPA
SYSTEM VSWPSEG1   Active   Controller: * RDEV: 0E1C
SYSTEM VSWPSEG2   Active   Controller: * RDEV: 0F5F

 Controller DTCVSW1   Available: YES   VDEV Range: 0600-F000 Level 630
   Capability: IP ETHERNET VLAN_ARP GVRPLINKAGGISOLATION
   NO_ENSEMBLE NO_INMN BRIDGE_CAPABLEVEPA
SYSTEM VSWPSEG1   Backup   Controller: * RDEV: 0F5C
SYSTEM VSWPSEG2   Backup   Controller: * RDEV: 0E1F

 Those VSWITCHes are within the Communication Controllers There is a set
 rdev command for communication controllers as follows:

 -Set--RDEVice--+-rdev+--++--TYpe--
  '-rdev1-rdev2-'  +-EQid--eqid-+
   '-NOEQid-'

 .-SET_ADDRess--4-.
 --+-+-BSC_ADAPTer---+--++-+---
| +-IBM1_ADAPTer--+  '-SET_ADDRess--n-' |
| '-TELE2_ADAPTer-' |
'-3705--'

 Therefore, I can do the following:

 set rdev 0E1C EQID myEQID

 However the Type parameter is mandatory.

 Could you let me know what it should be?

 Thanks,
 Ray


 -Original Message-
 From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
 Alan Altmark
 Sent: Monday, December 15, 2014 11:32 PM
 To: LINUX-390@VM.MARIST.EDU
 Subject: Re: Problem to test relocating a Linux image to another z/VM

 Email sent from outside of PSEG. Use caution before using
 links/attachments.


 On Monday, 12/15/2014 at 10:19 EST, Chu, Raymond raymond@pseg.com
 wrote:
  Hi,
 
  I had a chance to first test LGR function. This is what I had when I
  ran
 the
  vmrelocate test command
 
  vmrelocate test seal005 airforce
 
  HCPRLH1940E SEAL005 is not relocatable for the following reason(s):
  HCPRLI1996I SEAL005: Virtual machine device 0592 is a link to a local
 minidisk
  HCPRLI1982I SEAL005: Source system simulated network device 0600 is
 coupled to
  a VSWITCH without an assigned EQID
  HCPRLI1982I SEAL005: Source system simulated network device 0700 is
 coupled to
  a VSWITCH without an assigned EQID
 
  The VSWITCH definition in system config do not have definition for
  eqid
 and do
  not how to set it.

 HELP HCP1928I gives you the information you need.  You don't actually
 assign the EQID to VSWITCH, but to the RDEVs that it is using as uplinks.
 Your VSWITCHes are using devices E1C-E21 and 5FC-601 on all 4 LPARs, but
 your RDEVICE statements aren't setting the EQID on those devices.

 For example, note here than you are assigning an EQID to E10-E12 and
 F50-F52, but you aren't using those devices in the DEFINE VSWITCH.

  NAVY:   BEGIN
  rdev 0E10-0E12 eqid PSEGzVM  type osa
  rdev 0F50-0F52 eqid PSEGzVM  type osa
  vmlan macprefix 02000B
  vmlan MACIDRANGE SYSTEM 01-0F USER 0F0001-0F vmlan limit
  transient 0
  NAVY:   END
 :
  define vswitch VSWPSEG1 rdev 0E1C 0F5C ethernet define vswitch
  VSWPSEG2 rdev 0F5F 0E1F ethernet

 Alan Altmark

 Senior Managing z/VM and Linux Consultant Lab Services System z Delivery
 Practice IBM Systems  Technology Group
 ibm.com/systems/services/labservices
 office: 607.429.3323
 mobile; 607.321.7556
 alan_altm...@us.ibm.com
 IBM Endicott

 --
 For LINUX-390 subscribe / signoff / archive access instructions, send
 email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit http://wiki.linuxvm.org/


 -

 The information contained in this e-mail, including any attachment(s), is
 intended solely for use by the named addressee(s).  If you are not the
 intended recipient, or a person designated as 

Re: Upgrading from SLES11 SP2 to SLES11 SP3 via zypper

[Mark Pace]

Is there an updated procedure for updating a SLES11 SPx to SLES 12 using
zypper?

On Tue, Jul 23, 2013 at 2:30 PM, Mark Post mp...@suse.com wrote:

  On 7/22/2013 at 07:10 AM, Will, Chris cw...@bcbsm.com wrote:
  We use smt for our repositories.  I went through the procedure and the
 test
  server was upgraded successfully.  I deleted/removerepo the old SP1 and
 SP2
  repositories, however any subsequent suse_register (say moving from
 full to
  testing) brings back the old SP1 and SP2 repositories (they are
 disabled
  however).

 I contacted out Product Manager for maintenance about this and was told
 this is by design.

 I have always tried to use adapt the repo model and not roll back...

 The idea behind this adapted model, was to enable customers to easily
 access
 the old repo if they need to stay on older versions of specific packages.

 So, for the lifetime of SP3 and SP4, this channel model will remain in
 place.

 So, again, apologies for my incomplete understanding of how things were
 going to work with SP3.


 Mark Post

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Upgrading from SLES11 SP2 to SLES11 SP3 via zypper

[Mark Pace]

Thanks, Mark.

On Mon, Dec 1, 2014 at 3:49 PM, Mark Post mp...@suse.com wrote:

  On 12/1/2014 at 01:48 PM, Mark Pace pacemainl...@gmail.com wrote:
  Is there an updated procedure for updating a SLES11 SPx to SLES 12 using
  zypper?

 The supported upgrade methods are documented in the Deployment Guide.  See
 https://www.suse.com/documentation/sles-12/book_sle_deployment/data/sec_update_sle12.html


 Mark Post

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Adding memory dynamically to a RHEL6.5 guest running under z/VM 6.3

[Mark Pace]

It is not possible to change the memory allocated to a guest without
logging off and logging on again.

On Thu, Oct 2, 2014 at 9:36 AM, Martin, Terry Contractor 
terry.mar...@ssa.gov wrote:

 Hi

 I have a couple of guests that I need to add memory to without recycling
 the guests. What are the steps and commands to accomplish this?

 Thanks,

 Terry


 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Adding memory dynamically to a RHEL6.5 guest running under z/VM 6.3

[Mark Pace]

My apologies for being wrong about this.

On Thu, Oct 2, 2014 at 9:46 AM, Mark Pace pacemainl...@gmail.com wrote:

 It is not possible to change the memory allocated to a guest without
 logging off and logging on again.

 On Thu, Oct 2, 2014 at 9:36 AM, Martin, Terry Contractor 
 terry.mar...@ssa.gov wrote:

 Hi

 I have a couple of guests that I need to add memory to without recycling
 the guests. What are the steps and commands to accomplish this?

 Thanks,

 Terry


 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




 --
 The postings on this site are my own and don’t necessarily represent
 Mainline’s positions or opinions

 Mark D Pace
 Senior Systems Engineer
 Mainline Information Systems






-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Error when load z/Linux for first time

[Mark Pace]

Is there an MD5 chksum routine for z/VM?


On Mon, Aug 25, 2014 at 10:33 AM, Alan Altmark alan_altm...@us.ibm.com
wrote:

 On Monday, 08/25/2014 at 10:21 EDT, Martin, Terry Contractor
 terry.mar...@ssa.gov wrote:
  Could the INITRD corrupted at the ISO level ? Or is it the Kernel Image
 that is
  the problem? We have been concentrating on the INITRD file up to this
 point.

 It isn't the kernel since you can't see the kernel running.  As I said
 previously, I think the ramdisk (INITRD) is corrupted.  Note the
 incomplete write.  Whether is was corrupted on upload to VM, to your
 workstation, or at the source is TBD.  If it were at the source, then
 everyone would have the same issue.

 Alan Altmark

 Senior Managing z/VM and Linux Consultant
 IBM System Lab Services and Training
 ibm.com/systems/services/labservices
 office: 607.429.3323
 mobile; 607.321.7556
 alan_altm...@us.ibm.com
 IBM Endicott

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Error when load z/Linux for first time

[Mark Pace]

The way to tell if the ISO is corrupted is with MD5 checksums.  All the ISO
files I've seen made available by SuSE and RH have the MD5 checksum values
so that you can verify them.


On Mon, Aug 25, 2014 at 10:48 AM, Martin, Terry Contractor 
terry.mar...@ssa.gov wrote:

 Thanks Alan.
  If it were at the source, then everyone would have the same issue.

 I don't think this was tried anywhere else other than at the z/VM level.
 The x86 REDHAT folks loaded the ISO files to a HTTP server for us and we
 downloaded it from there. We used the PCOMM SEND/REC protocol first and
 then FTP to download to z/VM to no avail . So not sure how to tell if the
 source (At the ISO level) is corrupted or not?

 Terry martin - Contractor
 Cell - 443 854-2452
 Office (NCC) - 410 965-8682
 Email - terry.mar...@ssa.gov


 -Original Message-
 From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of
 Alan Altmark
 Sent: Monday, August 25, 2014 10:33 AM
 To: LINUX-390@vm.marist.edu
 Subject: Re: Error when load z/Linux for first time

 On Monday, 08/25/2014 at 10:21 EDT, Martin, Terry Contractor
 terry.mar...@ssa.gov wrote:
  Could the INITRD corrupted at the ISO level ? Or is it the Kernel
  Image
 that is
  the problem? We have been concentrating on the INITRD file up to this
 point.

 It isn't the kernel since you can't see the kernel running.  As I said
 previously, I think the ramdisk (INITRD) is corrupted.  Note the
 incomplete write.  Whether is was corrupted on upload to VM, to your
 workstation, or at the source is TBD.  If it were at the source, then
 everyone would have the same issue.

 Alan Altmark

 Senior Managing z/VM and Linux Consultant IBM System Lab Services and
 Training ibm.com/systems/services/labservices
 office: 607.429.3323
 mobile; 607.321.7556
 alan_altm...@us.ibm.com
 IBM Endicott

 --
 For LINUX-390 subscribe / signoff / archive access instructions, send
 email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit http://wiki.linuxvm.org/

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Setting Address Space to Unlimited

[Mark Pace]

Or try the IBM-MAIN listserv.


On Tue, Aug 19, 2014 at 2:21 PM, Mark Post mp...@suse.com wrote:

  On 8/14/2014 at 10:28 AM, Jake anderson justmainfra...@gmail.com
 wrote:
  Hi Group,
 
  I am looking for a syntax to change Address space to unlimited.
 
  I tried with ulimit -A unlimited but it is not taking in OMVS(z/os).
 
  Can i change it permanently to unlimited ?

 You might want to ask this question on the MVS-OE listserv.  This mailing
 list deals with Linux, not z/OS.  We have a few z/OS people that hang out
 here, but not a lot.


 Mark Post

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Suspending and starting a Linux server

[Mark Pace]

No, because you have to IPL CMS.  You can issue CP commands via vmcp
without stopping linux.


On Thu, Jul 24, 2014 at 11:56 AM, Cameron Seay cws...@gmail.com wrote:

 I have what I think is a simple question.  Maybe I'm not clear about how to
 stop and restart a Linux server, but I was under the impressing that if I
 have a running Linux server in a guest I could suspend it and then return
 to the state that the server was in when I suspended it.  My question comes
 from a need to go into a guest that has a running Linux server, switch over
 to CMS to do something, and then resume the server's work.  I know how to
 #cp stop or #cp begin, but the only way I know to get back to the server is
 to ipl it again.  Is there a way I can go back to the processing point I
 was on the Linux server before I stopped it?

 Thanks.

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

vsftpd

[Mark Pace]

I'm trying to add SSL to my vsftpd server.   From else where on the web I
found the following to add to the config.
# enable FTPS
ssl_enable=YES
allow_anon_ssl=NO
force_local_data_ssl=NO
force_local_logins_ssl=NO
ssl_tlsv1=YES
ssl_sslv2=YES
ssl_sslv3=YES
ssl_request_cert=NO
rsa_cert_file=/etc/vsftpd/vsftpd.pem

I copied out cert file to /etc/vsftpd/
sles001:/etc # ls -al /etc/vsftpd/
total 28
drwxr-xr-x  2 root root  4096 May  6 11:33 .
drwxr-xr-x 99 root root 12288 May  6 11:39 ..
-rw-r--r--  1 root root  1920 May  6 10:35 mainline.pem
-rw-r--r--  1 root root  2136 May  6 11:31 sscert.pem
-rw-r--r--  1 root root  1920 May  6 11:33 vsftpd.pem


Starting vsftpd startproc:  exit status of parent of /usr/sbin/vsftpd: 1

So I'm trying to find out what that message is trying to tell me.  So I
look in the start script figure out where the messages should be.
/etc/rc.d/vsftpd

case $1 in
start)
echo -n Starting vsftpd 
/sbin/startproc -l /var/log/rcvsftp.log $VSFTPD_BIN
rc_status -v
;;

Look for the log
sles001:/etc # ls -al /var/log/rcvsftp.log
-rw-r--r-- 1 root root 0 Jul  2  2010 /var/log/rcvsftp.log

And it has nothing in it and hasn't been touched since 2010.
There is also nothing in /var/log/messages or /var/log/vsftpd.log  about
this failure.

Any idea why I don't have a log  or what could be causing this error?

-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: EXTERNAL: vsftpd

[Mark Pace]

Yes I do.  I didn't include the entire conf for brevity.   Complete conf -
minus the comments.

listen=YES
max_clients=20
use_localtime=YES
# enable FTPS
ssl_enable=YES
allow_anon_ssl=NO
force_local_data_ssl=NO
force_local_logins_ssl=NO
ssl_tlsv1=YES
ssl_sslv2=YES
ssl_sslv3=YES
ssl_request_cert=NO
rsa_cert_file=/etc/vsftpd/vsftpd.pem

anonymous_enable=NO
local_enable=YES
write_enable=YES
local_umask=022
anon_umask=666
dirmessage_enable=YES
message_file=.message
xferlog_enable=YES
connect_from_port_20=YES
xferlog_file=/var/log/vsftpd.log
banner_file=/etc/vsftpd.banner
deny_email_enable=YES
banned_email_file=/etc/vsftpd.banned_emails
chroot_local_user=YES
pasv_enable=YES
listen_ipv6=NO



On Tue, May 6, 2014 at 11:54 AM, Hodge, Robert L robert.l.ho...@lmco.comwrote:

 Mark,
 Do you have listen=YES in the vsftpd.conf ?

 -Original Message-
 From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
 Mark Pace
 Sent: Tuesday, May 06, 2014 9:45 AM
 To: LINUX-390@VM.MARIST.EDU
 Subject: EXTERNAL: vsftpd

 I'm trying to add SSL to my vsftpd server.   From else where on the web I
 found the following to add to the config.
 # enable FTPS
 ssl_enable=YES
 allow_anon_ssl=NO
 force_local_data_ssl=NO
 force_local_logins_ssl=NO
 ssl_tlsv1=YES
 ssl_sslv2=YES
 ssl_sslv3=YES
 ssl_request_cert=NO
 rsa_cert_file=/etc/vsftpd/vsftpd.pem

 I copied out cert file to /etc/vsftpd/
 sles001:/etc # ls -al /etc/vsftpd/
 total 28
 drwxr-xr-x  2 root root  4096 May  6 11:33 .
 drwxr-xr-x 99 root root 12288 May  6 11:39 ..
 -rw-r--r--  1 root root  1920 May  6 10:35 mainline.pem
 -rw-r--r--  1 root root  2136 May  6 11:31 sscert.pem
 -rw-r--r--  1 root root  1920 May  6 11:33 vsftpd.pem


 Starting vsftpd startproc:  exit status of parent of /usr/sbin/vsftpd: 1

 So I'm trying to find out what that message is trying to tell me.  So I
 look in the start script figure out where the messages should be.
 /etc/rc.d/vsftpd

 case $1 in
 start)
 echo -n Starting vsftpd 
 /sbin/startproc -l /var/log/rcvsftp.log $VSFTPD_BIN
 rc_status -v
 ;;

 Look for the log
 sles001:/etc # ls -al /var/log/rcvsftp.log
 -rw-r--r-- 1 root root 0 Jul  2  2010 /var/log/rcvsftp.log

 And it has nothing in it and hasn't been touched since 2010.
 There is also nothing in /var/log/messages or /var/log/vsftpd.log  about
 this failure.

 Any idea why I don't have a log  or what could be causing this error?

 --
 The postings on this site are my own and don’t necessarily represent
 Mainline’s positions or opinions

 Mark D Pace
 Senior Systems Engineer
 Mainline Information Systems

 --
 For LINUX-390 subscribe / signoff / archive access instructions, send
 email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: vsftpd

[Mark Pace]

I know how it starts.  It's a Listen server that is started at IPL.


On Tue, May 6, 2014 at 12:07 PM, Mark Post mp...@suse.com wrote:

  On 5/6/2014 at 11:45 AM, Mark Pace pacemainl...@gmail.com wrote:
  I
  look in the start script figure out where the messages should be.
  /etc/rc.d/vsftpd
 
  case $1 in
  start)
  echo -n Starting vsftpd 
  /sbin/startproc -l /var/log/rcvsftp.log $VSFTPD_BIN
  rc_status -v
  ;;
 
  Look for the log
  sles001:/etc # ls -al /var/log/rcvsftp.log
  -rw-r--r-- 1 root root 0 Jul  2  2010 /var/log/rcvsftp.log
 
  And it has nothing in it and hasn't been touched since 2010.
  There is also nothing in /var/log/messages or /var/log/vsftpd.log  about
  this failure.
 
  Any idea why I don't have a log  or what could be causing this error?

 First, make sure that you know how vsftpd is getting invoked.  It could be
 via the script in /etc/rc.d, or it could be via xinetd.  On my system, it's
 not started at all at the moment.
 # chkconfig --list vsftpd
 vsftpd0:off  1:off  2:off  3:off  4:off  5:off  6:off
 xinetd based services:
 vsftpd: off

 There are several logging related options in the configuration file.  By
 default, /etc/vsftpd.conf has:
 # Log to the syslog daemon instead of using an logfile.
 #
 syslog_enable=YES

 I would change that to NO.  I would also uncomment
 log_ftp_protocol=YES
 xferlog_enable=YES

 But, it would likely be a better idea to use yast ftp-server to turn on
 SSL/TLS and see what changes get made to the configuration file.


 Mark Post

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: vsftpd

[Mark Pace]

I tried pointing to both cert  key separately and I tried combing each
into 1 file.  Same results.
Using the sh -x   didn't help resolve the error.

So Mark how did you use this strace?   Did you add it to the script - or
did you just run from the command line?  I wish I knew why nothing was
being written to the rcvsftpd.log



On Tue, May 6, 2014 at 12:30 PM, Mark Pace pacemainl...@gmail.com wrote:

 I know how it starts.  It's a Listen server that is started at IPL.


 On Tue, May 6, 2014 at 12:07 PM, Mark Post mp...@suse.com wrote:

  On 5/6/2014 at 11:45 AM, Mark Pace pacemainl...@gmail.com wrote:
  I
  look in the start script figure out where the messages should be.
  /etc/rc.d/vsftpd
 
  case $1 in
  start)
  echo -n Starting vsftpd 
  /sbin/startproc -l /var/log/rcvsftp.log $VSFTPD_BIN
  rc_status -v
  ;;
 
  Look for the log
  sles001:/etc # ls -al /var/log/rcvsftp.log
  -rw-r--r-- 1 root root 0 Jul  2  2010 /var/log/rcvsftp.log
 
  And it has nothing in it and hasn't been touched since 2010.
  There is also nothing in /var/log/messages or /var/log/vsftpd.log  about
  this failure.
 
  Any idea why I don't have a log  or what could be causing this error?

 First, make sure that you know how vsftpd is getting invoked.  It could
 be via the script in /etc/rc.d, or it could be via xinetd.  On my system,
 it's not started at all at the moment.
 # chkconfig --list vsftpd
 vsftpd0:off  1:off  2:off  3:off  4:off  5:off  6:off
 xinetd based services:
 vsftpd: off

 There are several logging related options in the configuration file.  By
 default, /etc/vsftpd.conf has:
 # Log to the syslog daemon instead of using an logfile.
 #
 syslog_enable=YES

 I would change that to NO.  I would also uncomment
 log_ftp_protocol=YES
 xferlog_enable=YES

 But, it would likely be a better idea to use yast ftp-server to turn on
 SSL/TLS and see what changes get made to the configuration file.


 Mark Post

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




 --
 The postings on this site are my own and don’t necessarily represent
 Mainline’s positions or opinions

 Mark D Pace
 Senior Systems Engineer
 Mainline Information Systems






-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: vsftpd

[Mark Pace]

I should also mention that I also tried creating a self-signed cert as it
shows in multiple examples to be sure that it wasn't my cert/key that was
the problem.


On Tue, May 6, 2014 at 12:45 PM, Mark Pace pacemainl...@gmail.com wrote:

 I tried pointing to both cert  key separately and I tried combing each
 into 1 file.  Same results.
 Using the sh -x   didn't help resolve the error.

 So Mark how did you use this strace?   Did you add it to the script - or
 did you just run from the command line?  I wish I knew why nothing was
 being written to the rcvsftpd.log



 On Tue, May 6, 2014 at 12:30 PM, Mark Pace pacemainl...@gmail.com wrote:

 I know how it starts.  It's a Listen server that is started at IPL.


 On Tue, May 6, 2014 at 12:07 PM, Mark Post mp...@suse.com wrote:

  On 5/6/2014 at 11:45 AM, Mark Pace pacemainl...@gmail.com wrote:
  I
  look in the start script figure out where the messages should be.
  /etc/rc.d/vsftpd
 
  case $1 in
  start)
  echo -n Starting vsftpd 
  /sbin/startproc -l /var/log/rcvsftp.log $VSFTPD_BIN
  rc_status -v
  ;;
 
  Look for the log
  sles001:/etc # ls -al /var/log/rcvsftp.log
  -rw-r--r-- 1 root root 0 Jul  2  2010 /var/log/rcvsftp.log
 
  And it has nothing in it and hasn't been touched since 2010.
  There is also nothing in /var/log/messages or /var/log/vsftpd.log
  about
  this failure.
 
  Any idea why I don't have a log  or what could be causing this error?

 First, make sure that you know how vsftpd is getting invoked.  It could
 be via the script in /etc/rc.d, or it could be via xinetd.  On my system,
 it's not started at all at the moment.
 # chkconfig --list vsftpd
 vsftpd0:off  1:off  2:off  3:off  4:off  5:off  6:off
 xinetd based services:
 vsftpd: off

 There are several logging related options in the configuration file.  By
 default, /etc/vsftpd.conf has:
 # Log to the syslog daemon instead of using an logfile.
 #
 syslog_enable=YES

 I would change that to NO.  I would also uncomment
 log_ftp_protocol=YES
 xferlog_enable=YES

 But, it would likely be a better idea to use yast ftp-server to turn
 on SSL/TLS and see what changes get made to the configuration file.


 Mark Post

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390
 or visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




 --
 The postings on this site are my own and don’t necessarily represent
 Mainline’s positions or opinions

 Mark D Pace
 Senior Systems Engineer
 Mainline Information Systems






 --
 The postings on this site are my own and don’t necessarily represent
 Mainline’s positions or opinions

 Mark D Pace
 Senior Systems Engineer
 Mainline Information Systems






-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: vsftpd

[Mark Pace]

Thanks, Mark!

Using the strace I was able to get it to work using the 2 separate files.
I'm unsure what caused the error the first time I tried separate files,
possibly a typo, but when I tried it this time it worked.


On Tue, May 6, 2014 at 12:50 PM, Mark Post mp...@suse.com wrote:

  On 5/6/2014 at 12:45 PM, Mark Pace pacemainl...@gmail.com wrote:
  So Mark how did you use this strace?   Did you add it to the script - or
  did you just run from the command line?  I wish I knew why nothing was
  being written to the rcvsftpd.log

 I just ran it from the command line.  There doesn't appear to be anything
 special happening in the init script.  You're not getting anything in the
 log, I'm guessing, because the daemon is not really up yet when it dies.


 Mark Post

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Yast - x app

[Mark Pace]

During installation I get these really nice X app to do installation.
After the first boot I still have the X apps.  But as soon as I log off I
can't seem to get the X Yast back again.  /sbin/yast /sbin/YaST2
/sbin/YaST  all start the ncurses version.  How can I get the X Yast so I
can show some people, that yes we can do GUI if we need to.  Just running
xclock doesn't show much.

-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Yast - x app

[Mark Pace]

I always use sudo - first thing I do when setting up a new server is set
ssh PermitRootLogin no

Copying the .Xauthority to root allowed me to su  and then run yast2.
Using sudo /sbin/yast2   still brought up the ncurses.

Thank you, Rick, that is a step forward.




On Thu, Dec 19, 2013 at 4:56 PM, Richard Troth
ri...@velocitysoftware.comwrote:

 If you're able to run 'xclock' then you have an X server on the
 workstation end, so that's good.

 YaST runs as root, and it's often tricky to convey X authority from
 non-root. (This is assuming that you 'su' or 'sudo' which I truly hope
 you're doing.)

 If you connect as root, then SSH, and you requested to forward X
 traffic on the client end, will do the right thing. But ... really ...
 don't sign on directly as root. Best practice is to disallow root
 login and require everyone to use 'sudo'.

 The *proper* way to do it is with a sort of export and import via
 'xauth'. And you'll need to set your DISPLAY variable correctly in the
 root shell in any case. But you can short-cut the details by copying
 .Xauthority from your home directory to root's home directory.
 Verify with an 'xterm' or with 'xclock'. Then try 'yast2'.



 On Thu, Dec 19, 2013 at 4:47 PM, Mark Pace pacemainl...@gmail.com wrote:
  During installation I get these really nice X app to do installation.
  After the first boot I still have the X apps.  But as soon as I log off I
  can't seem to get the X Yast back again.  /sbin/yast /sbin/YaST2
  /sbin/YaST  all start the ncurses version.  How can I get the X Yast so I
  can show some people, that yes we can do GUI if we need to.  Just running
  xclock doesn't show much.
 
  --
  The postings on this site are my own and don’t necessarily represent
  Mainline’s positions or opinions
 
  Mark D Pace
  Senior Systems Engineer
  Mainline Information Systems
 
  --
  For LINUX-390 subscribe / signoff / archive access instructions,
  send email to lists...@vm.marist.edu with the message: INFO LINUX-390
 or visit
  http://www.marist.edu/htbin/wlvindex?LINUX-390
  --
  For more information on Linux on System z, visit
  http://wiki.linuxvm.org/



 --
 -- R;
 Rick Troth
 Velocity Software
 http://www.velocitysoftware.com/

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: After upgrading from SLES11 SP2 to SLES11 SP3 via zypper getting register status message.

[Mark Pace]

I did an update on one of my servers this morning.  No problems at all.


On Fri, Aug 2, 2013 at 12:45 PM, Tom Morris tmor...@wcfgroup.com wrote:

 HI,  Has any one experienced this problem?  After upgrading from SLES11 SP2
 to SLES11 SP3 via zypper and trying to re-register the server
 I get the following message:

 Registration status is not available

 You get this after I running the  zypper dup --from SLES11-SP3-Pool --from
 SLES11-SP3-Updates zypper dup  command and
 try to register the server for the last time.

 Thanks

 Tom  Morris
 WCF

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Server memory adjustments

[Mark Pace]

Once you change the USER DIRECTORY you have to logoff and logon again.  If
you are doing that, check to be sure that your USER DIRECTORY is being
placed online immediately when you do the update.


On Thu, Aug 1, 2013 at 9:10 AM, Dean, David (I/S) david_d...@bcbst.comwrote:

 Sometimes when I add memory in the User Dir it does not show up on the
 first reboot and I have to reboot again.  This has been no killer issue,
 just curious as to what I might be doing wrong.
 -
 Please see the following link for the BlueCross BlueShield of Tennessee
 E-mail disclaimer:  http://www.bcbst.com/email_disclaimer.shtm

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

What version am I running?

[Mark Pace]

I know I've read how to do this in the past, but I can not find it anywhere
in my archives.

How do I determine what version of SLES I am running?

-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: What version am I running?

[Mark Pace]

Thank you both.  I knew it was simple, but I just couldn't find it.
Now I need a better memory, because my main FTP server says it's SP2 and I
do NOT remember upgrading it.  :(

Oh well, one less step to get it to SP3.  :)


On Thu, Jul 25, 2013 at 2:43 PM, Mauro Souza thoriu...@gmail.com wrote:

 I usually run
 # cat /etc/*release

 So wherever it's SuSE, RedHat, Ubuntu, Fedora or almost anything, I can get
 the distro version.

 And to get the kernel version:
 # uname -a




 Mauro
 http://mauro.limeiratem.com - registered Linux User: 294521
 Scripture is both history, and a love letter from God.


 2013/7/25 Pedro Principeza pedro...@br.ibm.com

  Hi Mark.
 
  Run:
 
  # cat /etc/SuSE-release
  # uname -a
 
  That'll tell you the version of SuSE and the kernel version + patches.
 
  --
  Pedro Principeza
 
 
 
  From:   Mark Pace pacemainl...@gmail.com
  To: LINUX-390@vm.marist.edu,
  Date:   25/07/2013 15:30
  Subject:What version am I running?
  Sent by:Linux on 390 Port LINUX-390@vm.marist.edu
 
 
 
  I know I've read how to do this in the past, but I can not find it
  anywhere
  in my archives.
 
  How do I determine what version of SLES I am running?
 
  --
  The postings on this site are my own and don’t necessarily represent
  Mainline’s positions or opinions
 
  Mark D Pace
  Senior Systems Engineer
  Mainline Information Systems
 
  --
  For LINUX-390 subscribe / signoff / archive access instructions,
  send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
  visit
  http://www.marist.edu/htbin/wlvindex?LINUX-390
  --
  For more information on Linux on System z, visit
  http://wiki.linuxvm.org/
 
 
 
 

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Passwords on Repository source

[Mark Pace]

I'm testing doing an upgrade of 11sp1 to 11sp2.
In YAST I added 2 software repositories.  They are access via FTP and I
added to userid and password in the definition.  Yast successfully
connected to the repository and added to the list of repositories.
However ever time I try to access the new repositories I am prompted for
the ftp password.  I also tried to modify the complete URL that had the
userid@ftpserver  to userid:password@ftpserver   that did not fix the
problem either.  How do I make yast remember the passwords for ftp server
userid?  I know it's possible as the original repositories are on the same
ftp server and it does not prompt me for the password.

-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Passwords on Repository source

[Mark Pace]

Thanks, Mark.  And that is how I did it, via YaST - Software - Software
Repositories. Click on the name of the repository, and then Edit.  I fill
in the userid and password and click OK.

But when I go to use it, it prompts me for the password again.  The correct
userid is there, but not the password.


On Thu, Jul 11, 2013 at 2:51 PM, Mark Post mp...@suse.com wrote:

  On 7/11/2013 at 10:27 AM, Mark Pace pacemainl...@gmail.com wrote:
  How do I make yast remember the passwords for ftp server
  userid?  I know it's possible as the original repositories are on the
 same
  ftp server and it does not prompt me for the password.

 The official method should be YaST - Software - Software Repositories.
  Click on the name of the repository, and then Edit.  You should be able
 to specify the authentication information there.


 Mark Post

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: REXX mod

[Mark Pace]

In the directory entry for the guest you can specify the CPUID.  See the CP
Planning and Administration Guide



 CPU cpuaddr BASE CPUID bb

CPUID bb
provides the processor identification number to be stored in bits 8 through
31 of
the CPU ID that is returned in response to the store processor ID (STIDP)
instruction. If the guest is relocated, these bits do not change as a
result of the
relocation, even if the FORCE ARCHITECTURE or FORCE DOMAIN options
were used on the VMRELOCATE command.
The variable bb is a 6-digit hexadecimal number. (No checking is done to
ensure that this number is unique in the virtual configuration.) For base
processors, this option overrides the CPUID operand on the OPTION
statement. For nonbase processors, it overrides the CPU ID of the base CPU.


On Wed, Jun 26, 2013 at 3:41 PM, Ron Wells ron.we...@slfs.com wrote:

 Do not know if this is place to ask
 Is there a way to tell VM that I am going to run a image(Linux or zos)
 under a different machine/serial/model # than what I am really on??

 looking at doing it for a DR possibility where it is a PAIN to get auth
 codes..

 --
 Email Disclaimer
 This  E-mail  contains  confidential  information  belonging to the
 sender, which  may be legally privileged information.  This information is
 intended only  for  the use of the individual or entity addressed above.
  If you are not  the  intended  recipient, or  an  employee  or  agent
 responsible for delivering it to the intended recipient, you are hereby
 notified that any disclosure,  copying, distribution, or the taking of any
 action in reliance on the contents of the E-mail or attached files is
 strictly prohibited.

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Seeing a -4010 on install

[Mark Pace]

For SuSE I use 150 cyl minidisk for /boot and then LVM together however
minidisks I need for the total disk space required.  That incudes
everything except swap space which I put on VDISK.

Example.
* Swap
  MDISK 0200 FB-512 V-DISK 1048576
  MDISK 0201 FB-512 V-DISK 4194296
* /boot
  MDISK 0202 3390 776 150 VMUSR1 MR READ WRITE MULTI
* /  root fs
  MDISK 0203 3390 1 10016 LNX017 MW READ WRITE MULTI
  MDISK 0204 3390 1 10016 LNX018 MW READ WRITE MULTI
  MDISK 0205 3390 1 10016 LNX019 MW READ WRITE MULTI


On Fri, Jun 21, 2013 at 11:35 AM, Pesce, Andy andy.pe...@autozone.comwrote:

 I know I have seen some articles about getting this error during install
 dealing with LVM's.
 So, if I define a /boot with 200mb on a real disk, then can I put the
 other mountpoints
 like /tmp, /home, etc into an LVM?  It looks like this is being caused by
 stating to format
 the disk in the LVM and automatically mount them.  Any other thoughts?

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

disable autocleanup of /tmp

[Mark Pace]

Is there a way to disable autocleanup of /tmp at boot?  I've found
/etc/rc.d/boot.cleanup  but I'm unsure of what to change to make it not
cleanup.

Thanks.

-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: disable autocleanup of /tmp

[Mark Pace]

Did I miss something in this post?  I don't see anything.


On Fri, Jan 18, 2013 at 4:30 PM, Veencamp, Jonathon D. 
jdveenc...@fedins.com wrote:

 This is for SLES, and is the opposite of what you want, but it shows where
 it is configured (at least on SLES)



 2013/1/18 Mark Pace pacemainl...@gmail.com

  Is there a way to disable autocleanup of /tmp at boot?  I've found
  /etc/rc.d/boot.cleanup  but I'm unsure of what to change to make it not
  cleanup.
 
  Thanks.
 
  --
  The postings on this site are my own and don't necessarily represent
  Mainline's positions or opinions
 
  Mark D Pace
  Senior Systems Engineer
  Mainline Information Systems
 
  --
  For LINUX-390 subscribe / signoff / archive access instructions,
  send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
  visit
  http://www.marist.edu/htbin/wlvindex?LINUX-390
  --
  For more information on Linux on System z, visit
  http://wiki.linuxvm.org/
 

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/

 

 The information contained in this e-mail message is intended only for the
 personal and confidential use of the designated recipient(s) named above.
 This message may be an attorney-client or work product communication which
 is privileged and confidential. It may also contain protected health
 information that is protected by federal law. If you have received this
 communication in error, please notify us immediately by telephone and
 destroy (shred) the original message and all attachments. Any review,
 dissemination, distribution or copying of this message by any person other
 than the intended recipient(s) or their authorized agents is strictly
 prohibited. Thank you.

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: disable autocleanup of /tmp

[Mark Pace]

Probably should have mentioned that it is SLES 11.

Doing chkconfig without parameters it doesn't list a boot.cleanup to turn
off.


On Fri, Jan 18, 2013 at 4:10 PM, Mauro Souza thoriu...@gmail.com wrote:

 On my Ubuntu, it's on /etc/default/rcS... There's a TMPTIME var there. If
 it's 0, it will clear /tmp on every boot. I kept it on 30...

 Mauro
 http://mauro.limeiratem.com - registered Linux User: 294521
 Scripture is both history, and a love letter from God.


 2013/1/18 Mark Pace pacemainl...@gmail.com

  Is there a way to disable autocleanup of /tmp at boot?  I've found
  /etc/rc.d/boot.cleanup  but I'm unsure of what to change to make it not
  cleanup.
 
  Thanks.
 
  --
  The postings on this site are my own and don’t necessarily represent
  Mainline’s positions or opinions
 
  Mark D Pace
  Senior Systems Engineer
  Mainline Information Systems
 
  --
  For LINUX-390 subscribe / signoff / archive access instructions,
  send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
  visit
  http://www.marist.edu/htbin/wlvindex?LINUX-390
  --
  For more information on Linux on System z, visit
  http://wiki.linuxvm.org/
 

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: disable autocleanup of /tmp

[Mark Pace]

Hmm -

slestpm:/etc/rc.d # chkconfig boot.cleanup off
insserv: Service boot.cleanup has to be enabled to start service
boot.localnet
insserv: exiting now!
/sbin/insserv failed, exit code 1

Finally googled up something.  Apparently controlled through system
config.  Went to yast, system config editor, cron, verified
CLEAR_TMP_DIRS_AT_BOOT was set to no.  It appears that the default is to
NOT cleanup /tmp at boot.  Just another thing the IBM prereqchecker fibbed
to me about. :(



On Fri, Jan 18, 2013 at 4:25 PM, Mark Post mp...@suse.com wrote:

  On 1/18/2013 at 03:42 PM, Mark Pace pacemainl...@gmail.com wrote:
  Is there a way to disable autocleanup of /tmp at boot?  I've found
  /etc/rc.d/boot.cleanup  but I'm unsure of what to change to make it not
  cleanup.

 chkconfig boot.cleanup off


 Mark Post

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Linux ZVM command help ....

[Mark Pace]

sudo /sbin/vmcp q userid
SLES001  AT MISZVM


On Wed, Oct 31, 2012 at 8:52 AM, Ben Duncan b...@linux4ms.net wrote:

 Is there a command on the zlinux (SuSe 11.1) instance to tell you what
 the assigned name
 in the ZVM file that instance is ?

 For example - server called database01.ms.gov in all the local
 hosts/naming file(s) might
 be referenced as server0009 in the ZVM console list. We want to be able
 to what the server is referenced as from inside the instance. i.e.

 database01$ zvmyname
  server009
 database01$

 As always, thanks 

 Ben Duncan - Business Network Solutions, Inc. 336 Elton Road  Jackson
 MS, 39212
 Never attribute to malice, that which can be adequately explained by
 stupidity
 - Hanlon's Razor



 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: LGR guest quiesce

[Mark Pace]

No, the freeze does not cause the buffers to be written to disk.  It
wouldn't be any different than taking a point-in-time copy of the disks.

On Thu, Aug 30, 2012 at 11:11 AM, Aria Bamdad a...@bsc.gwu.edu wrote:

 Just curious, could this functionality be used somehow to allow for a
 **consistent** disk snapshot using flashcopy for a live Linux guest?  What
 I
 mean is that currently, we have to shutdown the guest, do the flashcopy and
 then restart the guest.  Is there a way we can tell the Linux guest to
 freeze, take a snapshot of the disks and then resume?

 -Original Message-
 From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Rob
 van der Heij
 Sent: Thursday, August 30, 2012 7:47 AM
 To: LINUX-390@VM.MARIST.EDU
 Subject: Re: LGR guest quiesce

 On 30 August 2012 11:43, Lu GL Gao lu...@cn.ibm.com wrote:

 Linux guest move its memory to target z/VM member during relocating. Then
  it quiesce and resume on target z/VM.
  How to understand quiesce? What state of linux when it is in quiesce
  time? Is idling? shutdown? or something?
 

 See it as frozen while running -  as long as Linux is actually running,
 it may change memory that z/VM already copied over, so z/VM will copy it
 again, and again...  To stop that, finally the guest is frozen for a very
 short period, not making any further changes. That gives z/VM time to copy
 the last bits and the guest then continues to run on the other side, at the
 very instruction where it was frozen before.
 Linux will observe that some time passed where it did not run, but that's
 normal in time sharing.

 Rob

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: LGR IPL CMS

[Mark Pace]

Detaching all the minidisks was the answer to my problem.

I must say it is pretty amazing the 1st time that LGR works.  You know that
it should work, but actually seeing it happen the 1st time is pretty cool.

On Wed, Jun 13, 2012 at 2:23 PM, Robert J Brenneman bren...@gmail.comwrote:

 I relocate my Linux systems and I IPL CMS by default so I can use
 SWAPGEN too - what is the actual error message you're getting when you
 attempt to relocate ?

 --
 Jay Brenneman

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

LGR IPL CMS

[Mark Pace]

Currently all of my linux guests IPL CMS to create VDISK swap disks and
signatures.  For a linux to work with LGR it must IPL from a device or NSS
so no CMS if I want to LGR.  I've been doing it this way for so long I'm
unsure of how I would create the swap signature in my VDISKs without IPLing
CMS first.

Suggestions would greatly be appreciated.

-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: LGR IPL CMS

[Mark Pace]

Thanks, Alan. I guess for simplicities sake just detaching all the
minidisks associated with CMS just before IPLing the Liunx system is the
easiest solution.

On Wed, Jun 13, 2012 at 2:18 PM, Alan Altmark alan_altm...@us.ibm.comwrote:

 On Wednesday, 06/13/2012 at 02:09 EDT, Mark Pace pacemainl...@gmail.com
 wrote:
  Currently all of my linux guests IPL CMS to create VDISK swap disks and
  signatures.  For a linux to work with LGR it must IPL from a device or
 NSS
  so no CMS if I want to LGR.  I've been doing it this way for so long I'm
  unsure of how I would create the swap signature in my VDISKs without
 IPLing
  CMS first.
 
  Suggestions would greatly be appreciated.

 I think it's been discussed here or on IBMVM before, but you have two
 options if you want to IPL CMS first:
 1. Create another CMS that uses a cross-system shared S-disk, e.g.
 LINUXCMS with a shared 1190 S-disk.
 2. Have Linux detach the CMS disks when it starts.

 Alan Altmark

 Senior Managing z/VM and Linux Consultant
 IBM System Lab Services and Training
 ibm.com/systems/services/labservices
 office: 607.429.3323
 mobile; 607.321.7556
 alan_altm...@us.ibm.com
 IBM Endicott

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: LGR IPL CMS

[Mark Pace]

Thanks, Marcy - that was the kick in the head i needed to recall that was
how I did it before SWAPGEN.

On Wed, Jun 13, 2012 at 2:57 PM, Marcy Cortes marcy.d.cor...@wellsfargo.com
 wrote:

 We've always done it in /etc/init.d/boot.local.   That way we are safe
 from whatever changes Linux might make...

 Like this

 /sbin/mkswap /dev/disk/by-path/ccw-0.0.ff00-part1
 /sbin/mkswap /dev/disk/by-path/ccw-0.0.ff01-part1
 /sbin/mkswap /dev/disk/by-path/ccw-0.0.ff02-part1
 /sbin/mkswap /dev/disk/by-path/ccw-0.0.ff03-part1
 /sbin/swapon /dev/disk/by-path/ccw-0.0.ff00-part1 -p 4
 /sbin/swapon /dev/disk/by-path/ccw-0.0.ff01-part1 -p 3
 /sbin/swapon /dev/disk/by-path/ccw-0.0.ff02-part1 -p 2
 /sbin/swapon /dev/disk/by-path/ccw-0.0.ff03-part1 -p 1



 Marcy

 -Original Message-
 From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
 Mark Post
 Sent: Wednesday, June 13, 2012 11:41 AM
 To: LINUX-390@VM.MARIST.EDU
 Subject: Re: [LINUX-390] LGR  IPL CMS

  On 6/13/2012 at 01:59 PM, Mark Pace pacemainl...@gmail.com wrote:
  Currently all of my linux guests IPL CMS to create VDISK swap disks and
  signatures.  For a linux to work with LGR it must IPL from a device or
 NSS
  so no CMS if I want to LGR.

 That doesn't sound right to me.  After the Linux guest IPLs itself (from
 where ever) there shouldn't be any traces of CMS left in the guest.  Where
 is that restriction documented?

  I've been doing it this way for so long I'm
  unsure of how I would create the swap signature in my VDISKs without
 IPLing
  CMS first.

 You would need to put something in /etc/rc.d/rc.local to do the mkswap at
 boot time.


 Mark Post

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: LGR IPL CMS

[Mark Pace]

I was being stupid, overlooking the fact that I could DETACH all the CMS
minidisks in my EXEC.  I work on to many OSes at once. I can't keep
straight what I am working on 1 min to the next.  It's like starting to
write code in one language and mid-way through start writing in a different
language, in the same program, because it works better.  The great
programming overlap as I call it.

On Wed, Jun 13, 2012 at 2:41 PM, Mark Post mp...@suse.com wrote:

  On 6/13/2012 at 01:59 PM, Mark Pace pacemainl...@gmail.com wrote:
  Currently all of my linux guests IPL CMS to create VDISK swap disks and
  signatures.  For a linux to work with LGR it must IPL from a device or
 NSS
  so no CMS if I want to LGR.

 That doesn't sound right to me.  After the Linux guest IPLs itself (from
 where ever) there shouldn't be any traces of CMS left in the guest.  Where
 is that restriction documented?

  I've been doing it this way for so long I'm
  unsure of how I would create the swap signature in my VDISKs without
 IPLing
  CMS first.

 You would need to put something in /etc/rc.d/rc.local to do the mkswap at
 boot time.


 Mark Post

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Router/routing issues

[Mark Pace]

I don't know why I am having such a hard time making linux be a router.  I
made it work years ago.

[ guest1 -   eth0 - 172.16.1.2/24 - GW 172.16.1.1]
.
.
[ vswitch - prirouter]
.
.
[guest2 - eth1 - 172.16.1.1/24]
[guest2 - eth0 - 199.xx.xx.xx/25  - GW - 199.xx.xx.1]
.
.
[vswitch - nonrouter] Connected to OSA connected to the internet.


Within guest2 I have turned on IP_FORWARD and added 2 IPTABLES rules
# iptables --table nat --append POSTROUTING --out-interface eth0 -j
MASQUERADE
# iptables --append FORWARD --in-interface eth1 -j ACCEPT

I am obviously forgetting something, but it sure doesn't seem obvious to me.

-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Router/routing issues

[Mark Pace]

Within Guest2 - the router - Yes
misvpn:~ # sudo cat /proc/sys/net/ipv4/ip_forward
1


On Thu, Jun 7, 2012 at 9:55 AM, Rich Smrcina r...@velocitysoftware.comwrote:

 Is ip_forwarding turned on?


 On 06/07/2012 08:43 AM, Mark Pace wrote:

 I don't know why I am having such a hard time making linux be a router.  I
 made it work years ago.

 [ guest1 -   eth0 - 172.16.1.2/24 - GW 172.16.1.1]
 .
 .
 [ vswitch - prirouter]
 .
 .
 [guest2 - eth1 - 172.16.1.1/24]
 [guest2 - eth0 - 199.xx.xx.xx/25  - GW - 199.xx.xx.1]
 .
 .
 [vswitch - nonrouter] Connected to OSA connected to the internet.


 Within guest2 I have turned on IP_FORWARD and added 2 IPTABLES rules
 # iptables --table nat --append POSTROUTING --out-interface eth0 -j
 MASQUERADE
 # iptables --append FORWARD --in-interface eth1 -j ACCEPT

 I am obviously forgetting something, but it sure doesn't seem obvious to
 me.



 --
 Rich Smrcina
 Velocity Software, Inc.
 http://www.velocitysoftware.**com http://www.velocitysoftware.com

 --**--**--
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/**wlvindex?LINUX-390http://www.marist.edu/htbin/wlvindex?LINUX-390
 --**--**--
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Router/routing issues

[Mark Pace]

Wasn't aware of that one.

misvpn:~ # cat /proc/sys/net/ipv4/conf/all/rp_filter
1

misvpn:~ # echo 0  /proc/sys/net/ipv4/conf/all/rp_filter
misvpn:~ # cat /proc/sys/net/ipv4/conf/all/rp_filter
0

Stll unable to ping outward.

On Thu, Jun 7, 2012 at 10:22 AM, Rob van der Heij rvdh...@gmail.com wrote:

 On Thu, Jun 7, 2012 at 4:10 PM, Mark Pace pacemainl...@gmail.com wrote:
  Within Guest2 - the router - Yes
  misvpn:~ # sudo cat /proc/sys/net/ipv4/ip_forward
  1
 

 There's also the  conf/if/rp_filter that by default not to accept
 traffic on the interface that you would not have sent that way

 Rob

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Router/routing issues

[Mark Pace]

On the internal guest2
sles003:~ # netstat -nr
Kernel IP routing table
Destination Gateway Genmask Flags   MSS Window  irtt
Iface
0.0.0.0 172.16.1.1  0.0.0.0 UG0 0  0
eth0
10.6.0.00.0.0.0 255.255.255.0   U 0 0  0
hsi0
127.0.0.0   0.0.0.0 255.0.0.0   U 0 0  0 lo
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0
eth0
172.16.1.0  0.0.0.0 255.255.255.0   U 0 0  0
eth0


And on the router guest1
misvpn:~ # netstat -nr
Kernel IP routing table
Destination Gateway Genmask Flags   MSS Window  irtt
Iface
199.44.167.00.0.0.0 255.255.255.128 U 0 0  0
eth0
10.6.0.00.0.0.0 255.255.255.0   U 0 0  0
hsi0
172.16.1.0  0.0.0.0 255.255.255.0   U 0 0  0
eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0
eth0
127.0.0.0   0.0.0.0 255.0.0.0   U 0 0  0 lo
0.0.0.0 199.44.167.10.0.0.0 UG0 0  0
eth0

I've never done a tcpdump before, something new to learn.  :-)

Mark

On Thu, Jun 7, 2012 at 11:04 AM, Mauro Souza thoriu...@gmail.com wrote:

 A couple tcpdumps could help know where your pings are getting killed.
 You can run tcpdump -i eth0 icmp on your guest, on the gateway, and
 on the external machine.

 A netstat -nr would help know if your routing table is pointing to the
 wrong destination...

 Mauro
 http://mauro.limeiratem.com - registered Linux User: 294521
 Scripture is both history, and a love letter from God.


 2012/6/7 Mark Pace pacemainl...@gmail.com:
  Wasn't aware of that one.
 
  misvpn:~ # cat /proc/sys/net/ipv4/conf/all/rp_filter
  1
 
  misvpn:~ # echo 0  /proc/sys/net/ipv4/conf/all/rp_filter
  misvpn:~ # cat /proc/sys/net/ipv4/conf/all/rp_filter
  0
 
  Stll unable to ping outward.
 
  On Thu, Jun 7, 2012 at 10:22 AM, Rob van der Heij rvdh...@gmail.com
 wrote:
 
  On Thu, Jun 7, 2012 at 4:10 PM, Mark Pace pacemainl...@gmail.com
 wrote:
   Within Guest2 - the router - Yes
   misvpn:~ # sudo cat /proc/sys/net/ipv4/ip_forward
   1
  
 
  There's also the  conf/if/rp_filter that by default not to accept
  traffic on the interface that you would not have sent that way
 
  Rob
 
  --
  For LINUX-390 subscribe / signoff / archive access instructions,
  send email to lists...@vm.marist.edu with the message: INFO LINUX-390
 or
  visit
  http://www.marist.edu/htbin/wlvindex?LINUX-390
  --
  For more information on Linux on System z, visit
  http://wiki.linuxvm.org/
 
 
 
 
  --
  The postings on this site are my own and don’t necessarily represent
  Mainline’s positions or opinions
 
  Mark D Pace
  Senior Systems Engineer
  Mainline Information Systems
 
  --
  For LINUX-390 subscribe / signoff / archive access instructions,
  send email to lists...@vm.marist.edu with the message: INFO LINUX-390
 or visit
  http://www.marist.edu/htbin/wlvindex?LINUX-390
  --
  For more information on Linux on System z, visit
  http://wiki.linuxvm.org/

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Router/routing issues

[Mark Pace]

So I'm not real sure what I am looking at.
Doing a ping from the internal guest to a internet address.
Not seeing anything received on the tcdump on the router.

*sles003:~ # tcpdump -i eth0 icmp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
11:16:07.644089 IP sles003  miszvm.s390.mainline.com: ICMP echo request,
id 15023, seq 1, length 64
*

On Thu, Jun 7, 2012 at 11:13 AM, Mark Pace pacemainl...@gmail.com wrote:

 On the internal guest2
 sles003:~ # netstat -nr
 Kernel IP routing table
 Destination Gateway Genmask Flags   MSS Window  irtt
 Iface
 0.0.0.0 172.16.1.1  0.0.0.0 UG0 0  0
 eth0
 10.6.0.00.0.0.0 255.255.255.0   U 0 0  0
 hsi0
 127.0.0.0   0.0.0.0 255.0.0.0   U 0 0  0 lo
 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0
 eth0
 172.16.1.0  0.0.0.0 255.255.255.0   U 0 0  0
 eth0


 And on the router guest1
 misvpn:~ # netstat -nr
 Kernel IP routing table
 Destination Gateway Genmask Flags   MSS Window  irtt
 Iface
 199.44.167.00.0.0.0 255.255.255.128 U 0 0  0
 eth0
 10.6.0.00.0.0.0 255.255.255.0   U 0 0  0
 hsi0
 172.16.1.0  0.0.0.0 255.255.255.0   U 0 0  0
 eth1
 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0
 eth0
 127.0.0.0   0.0.0.0 255.0.0.0   U 0 0  0 lo
 0.0.0.0 199.44.167.10.0.0.0 UG0 0  0
 eth0

 I've never done a tcpdump before, something new to learn.  :-)

 Mark


 On Thu, Jun 7, 2012 at 11:04 AM, Mauro Souza thoriu...@gmail.com wrote:

 A couple tcpdumps could help know where your pings are getting killed.
 You can run tcpdump -i eth0 icmp on your guest, on the gateway, and
 on the external machine.

 A netstat -nr would help know if your routing table is pointing to the
 wrong destination...

 Mauro
 http://mauro.limeiratem.com - registered Linux User: 294521
 Scripture is both history, and a love letter from God.


 2012/6/7 Mark Pace pacemainl...@gmail.com:
  Wasn't aware of that one.
 
  misvpn:~ # cat /proc/sys/net/ipv4/conf/all/rp_filter
  1
 
  misvpn:~ # echo 0  /proc/sys/net/ipv4/conf/all/rp_filter
  misvpn:~ # cat /proc/sys/net/ipv4/conf/all/rp_filter
  0
 
  Stll unable to ping outward.
 
  On Thu, Jun 7, 2012 at 10:22 AM, Rob van der Heij rvdh...@gmail.com
 wrote:
 
  On Thu, Jun 7, 2012 at 4:10 PM, Mark Pace pacemainl...@gmail.com
 wrote:
   Within Guest2 - the router - Yes
   misvpn:~ # sudo cat /proc/sys/net/ipv4/ip_forward
   1
  
 
  There's also the  conf/if/rp_filter that by default not to accept
  traffic on the interface that you would not have sent that way
 
  Rob
 
  --
  For LINUX-390 subscribe / signoff / archive access instructions,
  send email to lists...@vm.marist.edu with the message: INFO LINUX-390
 or
  visit
  http://www.marist.edu/htbin/wlvindex?LINUX-390
  --
  For more information on Linux on System z, visit
  http://wiki.linuxvm.org/
 
 
 
 
  --
  The postings on this site are my own and don’t necessarily represent
  Mainline’s positions or opinions
 
  Mark D Pace
  Senior Systems Engineer
  Mainline Information Systems
 
  --
  For LINUX-390 subscribe / signoff / archive access instructions,
  send email to lists...@vm.marist.edu with the message: INFO LINUX-390
 or visit
  http://www.marist.edu/htbin/wlvindex?LINUX-390
  --
  For more information on Linux on System z, visit
  http://wiki.linuxvm.org/

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




 --
 The postings on this site are my own and don’t necessarily represent
 Mainline’s positions or opinions

 Mark D Pace
 Senior Systems Engineer
 Mainline Information Systems







-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex

Re: Router/routing issues

[Mark Pace]

Well I was pretty certain that I had tried switching the PRIROUTER -
NONROUTER previously.  But that was also before I had turned off the
rp_filter.  A college suggested changing the internal network vswitch  to a
hipersocket connection. So with the vswitch for the internal network
replaced with hipersockets, and PRIROUTER set on the external network
vswitch I can route just fine.

Thanks very much for all the hints and tips.

On Thu, Jun 7, 2012 at 3:23 PM, Mark Post mp...@suse.com wrote:

  On 6/7/2012 at 09:43 AM, Mark Pace pacemainl...@gmail.com wrote:
  [ vswitch - prirouter]
  .
  .
  [guest2 - eth1 - 172.16.1.1/24]
  [guest2 - eth0 - 199.xx.xx.xx/25  - GW - 199.xx.xx.1]
  .
  .
  [vswitch - nonrouter] Connected to OSA connected to the internet.

 I think you have the nonrouter prirouter attributes reversed.  The virtual
 router needs to pick up addresses that wouldn't normally be otherwise
 delivered to it: the 172.16.1.0/24 subnet.


 Mark Post

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/




-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/