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?

-----Original Message-----
From: Aaron Bartell [mailto:aaronbartell@xxxxxxxxx]
Sent: Wednesday, February 03, 2016 12:25 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: AF errors after setting up SSH connections with BASH Shell

Hi Dan,

In this case you aren't changing any settings. The reason for creating /QOpenSys/etc/syslog.conf is to get past an error message when starting syslogd.

To run syslogd you need to be in PASE: CALL QP2TERM

Then type `syslogd -d` and hit enter. This will lock the session and wait for ssh things to happen and log them to your screen when they do happen.
To end the process just exist (F3) QP2TERM.

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


On Wed, Feb 3, 2016 at 11:19 AM, Dan Lanza <DLanza@xxxxxxxxxxxxxxx> wrote:

I'm sorry, I'm unfamiliar with Syslogd and read about different
priority and debug levels here:

http://www-01.ibm.com/support/knowledgecenter/ssw_aix_61/com.ibm.aix.c
mds5/syslogd.htm

Maybe it isn't applicable when just turning debugging mode on or off,
but I just wanted to make note of any settings before I changed them.
I suppose if /QOpenSys/etc/syslog.conf didn't exist yet, syslogd had
no prior settings and was not being used.

I also did not see a way to turn off debugging mode or stop syslogd.
Would I just run the command `$ syslogd -d` again in order to turn it off?

Thank you again for your assistance.

Also, how can I determine the current settings of Syslogd before I
elevate

the logging level?

I am not sure what you are asking. What log level?

Aaron Bartell
litmis.com - Services for open source on IBM i
--
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.