RE: AF errors after setting up SSH connections with BASH Shell

So with further experimentation I noticed if I disable SSHD with "ENDTCPSVR SERVER(*SSHD)" the AF errors still occur. However if I rename the "/QOpenSys/opt" directory to something else "/QOpenSys/opt-backup" while SSHD is off, the AF errors do not occur (not even for the new path). This leads me to believe IBM Web Administration for i specifically tries to access "/QOpenSys/opt" if it exists upon startup.

What permissions does everyone have set for QTMHHTTP on "/QOpenSys/opt". I'd like to confirm whether or not this is typical behavior before I just set permissions to stop the AF errors.

-----Original Message-----
From: Dan Lanza
Sent: Wednesday, February 03, 2016 12:51 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: AF errors after setting up SSH connections with BASH Shell

Aaron,

As soon as I turned on debugging mode I received this:
syslogd -d
syslogd: bind: errno = 67
off & running....
init
logmsg: pri 56, flags 8, from AS400, msg syslogd: restart
syslogd: restarted
readfds = 0x2018
got a message (-1, 0x2018)
readfds = 0x2018

I then proceeded to restart a web server to recreate the authority failure and I confirmed the errors were triggered, but nothing changed on my QP2TERM session.

However every few minutes I get this displayed to the screen:
got a message (-1, 0x2018)
readfds = 0x2018

I suppose it is just some sort of keep alive, not much comes up on it online.

Where else could I look for more information?