Re: Trying to use TRCINT to look at PASE processes

In the case of a git repository I'm going to need to remember not to

journal that from now on, although I don't have any customers doing
'chroot' at this point.

This same issue can happen outside of chroot (aka base of PASE).

Further, IBM is releasing Git as part of 5733OPS in the coming weeks**.
I'd guess many will have Git repos in the base of PASE and will be subject
to this issue.

** Announced at WMCPA keynote.

Aaron Bartell
litmis.com - Services for open source on IBM i


On Thu, Mar 24, 2016 at 3:30 PM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:

Aaron in the posts with Tony you asked: " Does PowerHA for IBM i have this
problem?" (For those that did not read the entire thing, it turns out a
journal on the IFS used for an OEM HA product was called out as part of the
problem)

The answer is NO, PowerHA does not use journaling to do replication. It is
storage level replication meaning that if the 4K page of memory changes
then
PHA pushes it across to the target.

That said, because journaling aids in starting up a partition that has been
taken down hard, we almost always journal everything we can with system
managed journals to aid the system in its start up. In the case of a git
repository I'm going to need to remember not to journal that from now on,
although I don't have any customers doing 'chroot' at this point.

--
Jim Oberholtzer
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Aaron
Bartell
Sent: Thursday, March 24, 2016 2:44 PM
To: Midrange Systems Technical Discussion
Subject: Re: Trying to use TRCINT to look at PASE processes

Since you said "sshd" instead of "STRTCPSVR *SSHD", am I safe to assume you
are actually using the sshd command in PASE from a shell? If so, I
recently
went through an extensive PASE debugging experience** that gave me more
insight concerning how to debug PASE issues using dbx***.

**Special thanks to Tony Cairns for taking the time. The entire experience
is documented here: http://bit.ly/ibmi-git-mmap-failed
*** http://bit.ly/aix-dbx

Aaron Bartell
litmis.com - Services for open source on IBM i


On Thu, Mar 24, 2016 at 2:15 PM, Justin Dearing <zippy1981@xxxxxxxxx>
wrote:

First of all, I'm probably using the wrong tool for this job. What do
I really want to do:
I'm debugging an error when sshd starts up
/QOpenSys/usr/bin/X11/xauth. I want to know whats being piped to it
from stdin. If I could know the job name of any given dead PASE
process and do a WRKJOB on it, that will likely give me what I need.

Now, what I tried to do is this: TRCINT SET(*ON) TRCTYPE(*PASE)
TRCTBL(PASETRC)

I then typed a few unix command in a ssh session

Unfortunately, I don't see the table get created with this SQL:
SELECT TABLE_SCHEMA || '.' || TABLE_NAME FROM QSYS2.SYSTABLES
WHERE NAME ='PASETRC'

Luckily, I was able to create a spool file with TRCINT SET(*OFF)
TRCTBL(PASETRC)

However, searching for the spool file did not turn up either the
commands I ran or anything like exec/execv/shell/cmd, which would be
what I would expect the API calls to be to start a process.

So my two questions are:

1. Would this trace even record all the started processes in PASE, and
if not how do I capture them?
2. How do I query the trace information with SQL instead of looking at
spool files.

Justin
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.