Re: syslogd: FSUM1229 syslogd is already active
No Ravi, I made sure there was no address space, neither in the SDSF DA display nor in the PS screen. But I already found out the root cause which you may read in one of my previous posts. Kind regards, Aitor. On Fri, Oct 12, 2012 at 7:09 AM, Ravi Gaur gaur.ravi2...@gmail.com wrote: Did you check if really SYSLOGD address space active or not? it capture log for FTP daemon etc.. D A,SYSLOGD IEE115I 01.08.26 2012.286 ACTIVITY 488 JOBS M/STS USERSSYSASINITS ACTIVE/MAX VTAM OAS 3000181 00033001851/00100 00015 SYSLOGD STEP1OMVSKERN NSW AO A=00E3 PER=NO SMC=000 PGN=N/A DMN=N/A AFF=NONE CT=002.146S ET=00110.13 WUID=STC18964 USERID=OMVSKERN WKL=STC SCL=STCMDP=1 RGP=N/A SRVR=NO QSC=NO ADDR SPACE ASTE=3EE768C0 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
The least I could do was post the solution here. Regards. On Thu, Oct 11, 2012 at 12:10 PM, IT Pro bilit...@gmail.com wrote: I completely agree, Peter. Thanks for your understanding. Aitor. On Wed, Oct 10, 2012 at 10:36 AM, Hunkeler Peter (KIUP 4) peter.hunke...@credit-suisse.com wrote: Seeing that the message is quite misleading, yes it may deserve opening an APAR. I didn't think about it really. I have never opened an APAR before, but my boss won't be in the mood of my getting into the process of creating one. There's always work to be done, and I must not waste time. I just obey (this doesn't mean IBM does not deserve getting warned about this to correct the manual). I perfectly understand your situation, however, you did waste a lot of time just because the message was so misleading... It would be an APAR against the code not the manual. syslogd should differentiate between the different reasons why it cannot proceed. At least one additional (different) message would be appropriate. -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
Did you check if really SYSLOGD address space active or not? it capture log for FTP daemon etc.. D A,SYSLOGD IEE115I 01.08.26 2012.286 ACTIVITY 488 JOBS M/STS USERSSYSASINITS ACTIVE/MAX VTAM OAS 3000181 00033001851/00100 00015 SYSLOGD STEP1OMVSKERN NSW AO A=00E3 PER=NO SMC=000 PGN=N/A DMN=N/A AFF=NONE CT=002.146S ET=00110.13 WUID=STC18964 USERID=OMVSKERN WKL=STC SCL=STCMDP=1 RGP=N/A SRVR=NO QSC=NO ADDR SPACE ASTE=3EE768C0 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
Oh, well, I don't know whether this deserves opening an APAR. The message is indeed quite misleading, but the thing is that once the line in the section PORT of TCPIP's profile was corrected to match the actual procedure name (that is, removing the leading 1), SYSLOG started successfully and stopped complaining that was already active. On Wed, Oct 10, 2012 at 7:32 AM, Hunkeler Peter (KIUP 4) peter.hunke...@credit-suisse.com wrote: Just one more clarifying comment: the cause was really in a line like 514 UDP SYSLOGT1 in the PORT section of TCPIP's profile. Removing the leading 1 (SYSLOGT is the procedure name) made it work. So that leading 1 was the cause. This is probably a reminiscence when SYSLOG used to fork, if it used to. In your initial post, you showed the message you're getting: BPXF024I (USRFWKT) Oct 8 11:27:08 BOLSAWBD/USRFWKT SYSLOGT syslogd: FSUM1229 syslogd is already active TFM explains FSUM1229 as follows: Explanation: Another instance of syslogd, or possibly some other program, is already processing the syslogd AF_UNIX socket. The syslogd AF_UNIX socket is /dev/log, or a different one specified with the -p command-line parameter. This does not correlate to the cause you've found. syslogd should write a message telling it could not open port 514 with the corresponding reason. APAR time? -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
Seeing that the message is quite misleading, yes it may deserve opening an APAR. I didn't think about it really. I have never opened an APAR before, but my boss won't be in the mood of my getting into the process of creating one. There's always work to be done, and I must not waste time. I just obey (this doesn't mean IBM does not deserve getting warned about this to correct the manual). Regards, Aitor. On Wed, Oct 10, 2012 at 9:02 AM, IT Pro bilit...@gmail.com wrote: Oh, well, I don't know whether this deserves opening an APAR. The message is indeed quite misleading, but the thing is that once the line in the section PORT of TCPIP's profile was corrected to match the actual procedure name (that is, removing the leading 1), SYSLOG started successfully and stopped complaining that was already active. On Wed, Oct 10, 2012 at 7:32 AM, Hunkeler Peter (KIUP 4) peter.hunke...@credit-suisse.com wrote: Just one more clarifying comment: the cause was really in a line like 514 UDP SYSLOGT1 in the PORT section of TCPIP's profile. Removing the leading 1 (SYSLOGT is the procedure name) made it work. So that leading 1 was the cause. This is probably a reminiscence when SYSLOG used to fork, if it used to. In your initial post, you showed the message you're getting: BPXF024I (USRFWKT) Oct 8 11:27:08 BOLSAWBD/USRFWKT SYSLOGT syslogd: FSUM1229 syslogd is already active TFM explains FSUM1229 as follows: Explanation: Another instance of syslogd, or possibly some other program, is already processing the syslogd AF_UNIX socket. The syslogd AF_UNIX socket is /dev/log, or a different one specified with the -p command-line parameter. This does not correlate to the cause you've found. syslogd should write a message telling it could not open port 514 with the corresponding reason. APAR time? -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
Seeing that the message is quite misleading, yes it may deserve opening an APAR. I didn't think about it really. I have never opened an APAR before, but my boss won't be in the mood of my getting into the process of creating one. There's always work to be done, and I must not waste time. I just obey (this doesn't mean IBM does not deserve getting warned about this to correct the manual). I perfectly understand your situation, however, you did waste a lot of time just because the message was so misleading... It would be an APAR against the code not the manual. syslogd should differentiate between the different reasons why it cannot proceed. At least one additional (different) message would be appropriate. -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
Hi Mark, I started it from /etc/rc because having it configured from TCPIP's AUTOLOG the result was just the message of the subject, and it ended. So I commented out the AUTOLOG statement regarding SYSLOG, and I subsequently configured SYSLOG to be started from /etc/rc. I am not starting it from two different places. The result is that starting it from /etc/rc works, but letting TCPIP start it using the AUTOLOG feature ends with the message already active. On Mon, Oct 8, 2012 at 5:49 PM, Mark Zelden m...@mzelden.com wrote: On Mon, 8 Oct 2012 16:31:39 +0200, IT Pro bilit...@gmail.com wrote: We have customized /etc/rc to include the start of syslog, very similar to what you say, and it works like that: _BPX_JOBNAME='SYSLOGT' /usr/sbin/syslogd -d -c -u -f /usr/local/etc/syslogd.conf Well then you've answered your own question.If you are starting it via /etc/rc, then when you try to start it from a console START command or AUTOLOG it will have already been active and you will see the message you are seeing. Choose only one method to start it (I prefer /etc/rc). Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
From: IT Pro bilit...@gmail.com To: IBM-MAIN@LISTSERV.UA.EDU The result is that starting it from /etc/rc works, but letting TCPIP start it using the AUTOLOG feature ends with the message already active. but that doesn't make sense, does it ? Just curious . Walter Marguccio z/OS Systems Programmer BELENUS LOB Informatic GmbH Munich - Germany -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
No, it doesn't make any sense. That's why I was asking in this forum. There must be something that I'm missing... I'm racking my brains! :-( On Tue, Oct 9, 2012 at 9:18 AM, Walter Marguccio walter_marguc...@yahoo.com wrote: From: IT Pro bilit...@gmail.com To: IBM-MAIN@LISTSERV.UA.EDU The result is that starting it from /etc/rc works, but letting TCPIP start it using the AUTOLOG feature ends with the message already active. but that doesn't make sense, does it ? Just curious . Walter Marguccio z/OS Systems Programmer BELENUS LOB Informatic GmbH Munich - Germany -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
SOLVED! In the TCPIP profile there was a line in the PORT section that was reserving port number 514 for SYSLOG, so: 1) I removed (commented out) that line reserving port 514, and 2) Commented out the line in /etc/rc that starts SYSLOG from Unix, and 3) Added the line that I'd previously commented out in the AUTOLOG section of TCPIP's profile to automatically start SYSLOG as a started task using a PROC, and 4) Used -i command-line option for SYSLOG to force SYSLOG run in local-mode only I think the main reason was 1) above: it seemed that OMVS was preventing SYSLOG from using that port. I don't know why that line reserving the port was there. Many thanks to all. Best regards, Aitor. On Tue, Oct 9, 2012 at 10:24 AM, IT Pro bilit...@gmail.com wrote: No, it doesn't make any sense. That's why I was asking in this forum. There must be something that I'm missing... I'm racking my brains! :-( On Tue, Oct 9, 2012 at 9:18 AM, Walter Marguccio walter_marguc...@yahoo.com wrote: From: IT Pro bilit...@gmail.com To: IBM-MAIN@LISTSERV.UA.EDU The result is that starting it from /etc/rc works, but letting TCPIP start it using the AUTOLOG feature ends with the message already active. but that doesn't make sense, does it ? Just curious . Walter Marguccio z/OS Systems Programmer BELENUS LOB Informatic GmbH Munich - Germany -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
Just one more clarifying comment: the cause was really in a line like 514 UDP SYSLOGT1 in the PORT section of TCPIP's profile. Removing the leading 1 (SYSLOGT is the procedure name) made it work. So that leading 1 was the cause. This is probably a reminiscence when SYSLOG used to fork, if it used to. Thanks again for your support. Regards, Aitor. On Tue, Oct 9, 2012 at 11:00 AM, IT Pro bilit...@gmail.com wrote: SOLVED! In the TCPIP profile there was a line in the PORT section that was reserving port number 514 for SYSLOG, so: 1) I removed (commented out) that line reserving port 514, and 2) Commented out the line in /etc/rc that starts SYSLOG from Unix, and 3) Added the line that I'd previously commented out in the AUTOLOG section of TCPIP's profile to automatically start SYSLOG as a started task using a PROC, and 4) Used -i command-line option for SYSLOG to force SYSLOG run in local-mode only I think the main reason was 1) above: it seemed that OMVS was preventing SYSLOG from using that port. I don't know why that line reserving the port was there. Many thanks to all. Best regards, Aitor. On Tue, Oct 9, 2012 at 10:24 AM, IT Pro bilit...@gmail.com wrote: No, it doesn't make any sense. That's why I was asking in this forum. There must be something that I'm missing... I'm racking my brains! :-( On Tue, Oct 9, 2012 at 9:18 AM, Walter Marguccio walter_marguc...@yahoo.com wrote: From: IT Pro bilit...@gmail.com To: IBM-MAIN@LISTSERV.UA.EDU The result is that starting it from /etc/rc works, but letting TCPIP start it using the AUTOLOG feature ends with the message already active. but that doesn't make sense, does it ? Just curious . Walter Marguccio z/OS Systems Programmer BELENUS LOB Informatic GmbH Munich - Germany -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
Just one more clarifying comment: the cause was really in a line like 514 UDP SYSLOGT1 in the PORT section of TCPIP's profile. Removing the leading 1 (SYSLOGT is the procedure name) made it work. So that leading 1 was the cause. This is probably a reminiscence when SYSLOG used to fork, if it used to. In your initial post, you showed the message you're getting: BPXF024I (USRFWKT) Oct 8 11:27:08 BOLSAWBD/USRFWKT SYSLOGT syslogd: FSUM1229 syslogd is already active TFM explains FSUM1229 as follows: Explanation: Another instance of syslogd, or possibly some other program, is already processing the syslogd AF_UNIX socket. The syslogd AF_UNIX socket is /dev/log, or a different one specified with the -p command-line parameter. This does not correlate to the cause you've found. syslogd should write a message telling it could not open port 514 with the corresponding reason. APAR time? -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
Hi John, yes I've read there are several ways, but we want the syslog be configured as a PROC so that it's easier for Operations to deal with its management. They don't want anything dealing with Unix. Anyways, I'll give that possibility a try. Thanks a lot. Aitor. On Mon, Oct 8, 2012 at 11:50 AM, Eatherly, John D john.eathe...@centurylink.com wrote: It can also be started from: /etc/inetd.conf John Eatherly -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
What I meant to say is that if you are already showing it as started, it is probably being started in /etc/inetd.conf. You can comment that out by putting a # to the left of the startup line. Thanks. John Eatherly -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of IT Pro Sent: Monday, October 08, 2012 4:59 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: syslogd: FSUM1229 syslogd is already active Hi John, yes I've read there are several ways, but we want the syslog be configured as a PROC so that it's easier for Operations to deal with its management. They don't want anything dealing with Unix. Anyways, I'll give that possibility a try. Thanks a lot. Aitor. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
Ah sorry, I misunderstood you. No, it isn't started neither from /etc/inetd.conf nor /etc/rc. Thanks. On Mon, Oct 8, 2012 at 12:16 PM, Eatherly, John D john.eathe...@centurylink.com wrote: What I meant to say is that if you are already showing it as started, it is probably being started in /etc/inetd.conf. You can comment that out by putting a # to the left of the startup line. Thanks. John Eatherly -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of IT Pro Sent: Monday, October 08, 2012 4:59 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: syslogd: FSUM1229 syslogd is already active Hi John, yes I've read there are several ways, but we want the syslog be configured as a PROC so that it's easier for Operations to deal with its management. They don't want anything dealing with Unix. Anyways, I'll give that possibility a try. Thanks a lot. Aitor. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
Aitor The start of the syslog is specified in the AUTOLOG of the TCPIP configuration. Try reading in z/OS Communications Server IP Configuration Reference what the AUTOLOG statement in the PROFILE of the IP component of z/OS Communications Server does: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1A1B4B1/2.8 quote 2.8 AUTOLOG statement Use the AUTOLOG statement to provide a list of MVS started procedures to be started by the Autolog task when TCP/IP is started. ... /quote Yes I know this is the V1R13 manual but AUTOLOG hasn't changed since its invention in the early 1990s. Incidentally it is likely that the greatest concentration of specialists with in fact both the SNA (VTAM) as well as the IP components of z/OS Communications Server can be found here: For IBMTCP-L subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO IBMTCP-L Chris Mason On Mon, 8 Oct 2012 11:31:17 +0200, IT Pro bilit...@gmail.com wrote: Hello, We upgraded from z/OS 1.9 to z/OS 1.12 a few months ago. We have configured SYSLOGD daemon to be started as a started task from a PROC, but when started we see in the MVS log syslogd: FSUM1229 syslogd is already active, and the procedure ends. The start of the syslog is specified in the AUTOLOG of the TCPIP configuration. S SYSLOGT $HASP100 SYSLOGT ON STCINRDR $HASP373 SYSLOGT STARTED IEF403I SYSLOGT - STARTED - TIME=11.27.08 BPXF024I (USRFWKT) Oct 8 11:27:08 BOLSAWBD/USRFWKT SYSLOGT syslogd: FSUM1229 syslogd is already active IEF404I SYSLOGT - ENDED - TIME=11.27.08 $HASP395 SYSLOGT ENDED Could anybody give me a hint on this? I'm stuck at this. Thanks, Aitor. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
Hi Chris, I read that. I know it's the TCPIP subsystem which starts daemons specified in the AUTOLOG statement every x seconds, but I don't know why SYSLOG complains there is another instance running, that I don't see anywhere in the process list. However, commenting out the line in the AUTOLOG stetament and starting SYSLOG from /etc/rc works like a charm. There must be something I'm missing, but I'm really flabbergasted anyways. On Mon, Oct 8, 2012 at 1:37 PM, Chris Mason chrisma...@belgacom.net wrote: Aitor The start of the syslog is specified in the AUTOLOG of the TCPIP configuration. Try reading in z/OS Communications Server IP Configuration Reference what the AUTOLOG statement in the PROFILE of the IP component of z/OS Communications Server does: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1A1B4B1/2.8 quote 2.8 AUTOLOG statement Use the AUTOLOG statement to provide a list of MVS started procedures to be started by the Autolog task when TCP/IP is started. ... /quote Yes I know this is the V1R13 manual but AUTOLOG hasn't changed since its invention in the early 1990s. Incidentally it is likely that the greatest concentration of specialists with in fact both the SNA (VTAM) as well as the IP components of z/OS Communications Server can be found here: For IBMTCP-L subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO IBMTCP-L Chris Mason On Mon, 8 Oct 2012 11:31:17 +0200, IT Pro bilit...@gmail.com wrote: Hello, We upgraded from z/OS 1.9 to z/OS 1.12 a few months ago. We have configured SYSLOGD daemon to be started as a started task from a PROC, but when started we see in the MVS log syslogd: FSUM1229 syslogd is already active, and the procedure ends. The start of the syslog is specified in the AUTOLOG of the TCPIP configuration. S SYSLOGT $HASP100 SYSLOGT ON STCINRDR $HASP373 SYSLOGT STARTED IEF403I SYSLOGT - STARTED - TIME=11.27.08 BPXF024I (USRFWKT) Oct 8 11:27:08 BOLSAWBD/USRFWKT SYSLOGT syslogd: FSUM1229 syslogd is already active IEF404I SYSLOGT - ENDED - TIME=11.27.08 $HASP395 SYSLOGT ENDED Could anybody give me a hint on this? I'm stuck at this. Thanks, Aitor. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
From: IT Pro bilit...@gmail.com Subject: Re: syslogd: FSUM1229 syslogd is already active but I don't know why SYSLOG complains there is another instance running, that I don't see anywhere in the process list. what does command D A,SYSL* show ? Walter Marguccio z/OS Systems Programmer BELENUS LOB Informatic GmbH Munich - Germany -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
Hi Walter, Your command's output is: D A,SYSL* IEE115I 13.59.06 2012.282 ACTIVITY JOBS M/STS USERSSYSASINITS ACTIVE/MAX VTAM OAS 5000262 00032000212/00010 00024 SYSL* NOT FOUND On Mon, Oct 8, 2012 at 1:56 PM, Walter Marguccio walter_marguc...@yahoo.com wrote: From: IT Pro bilit...@gmail.com Subject: Re: syslogd: FSUM1229 syslogd is already active but I don't know why SYSLOG complains there is another instance running, that I don't see anywhere in the process list. what does command D A,SYSL* show ? Walter Marguccio z/OS Systems Programmer BELENUS LOB Informatic GmbH Munich - Germany -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
Do you have CA Common Services? That fires up SYSLOGD if it isn't already running, but under a taskname of (by default) something like TNGEMSTR. I'd go to the PS panel in SDSF, or do a D OMVS,A=ALL command and look for a command with syslogd in it. It's not necessarily a task called SYSLOGD, but it will have syslogd in the command. Kind regards Patrick Loftus TNT Express ICS Ltd. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
On Mon, 8 Oct 2012 11:31:17 +0200, IT Pro bilit...@gmail.com wrote: Hello, We upgraded from z/OS 1.9 to z/OS 1.12 a few months ago. We have configured SYSLOGD daemon to be started as a started task from a PROC, but when started we see in the MVS log syslogd: FSUM1229 syslogd is already active, and the procedure ends. The start of the syslog is specified in the AUTOLOG of the TCPIP configuration. S SYSLOGT $HASP100 SYSLOGT ON STCINRDR $HASP373 SYSLOGT STARTED IEF403I SYSLOGT - STARTED - TIME=11.27.08 BPXF024I (USRFWKT) Oct 8 11:27:08 BOLSAWBD/USRFWKT SYSLOGT syslogd: FSUM1229 syslogd is already active IEF404I SYSLOGT - ENDED - TIME=11.27.08 $HASP395 SYSLOGT ENDED Could anybody give me a hint on this? I'm stuck at this. Thanks, Aitor. Are you using the same /etc/rc after you upgraded? For example, this is how I start it from /etc/rc: # Start the SYSLOGD daemon which supplies logging functions for programs _BPX_JOBNAME='SYSLOGD' /usr/sbin/syslogd -f /etc/syslog.conf -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
Hi Chris, I read that. I know it's the TCPIP subsystem which starts daemons specified in the AUTOLOG statement every x seconds, but I don't know why SYSLOG complains there is another instance running, that I don't see anywhere in the process list. a) UNIX daemons usually fork() once or twice during startup. I don't know off hand if this applies to syslogd as well but would guess so. b) z/OS will slightly change a process' (MVS) jobname upon fork() (and non-local spawn()) when the original jobname is shorter than 8 characters: a digit between 1 and 9 will be appended. If both a) and b) apply, then the resulting syslogd process will run in a different address space with a *different* jobname than the one started by TCP/IP's autolog feature. It will then think the job died and will restart it. If this turns out to be your problem, try running syslogd with an 8 character jobname (i,e.PROC name). z/OS will then leave the jobname alone upon fork()/spawn(). -- Peter Hunkeler -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of IT Pro Sent: Montag, 8. Oktober 2012 13:43 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: syslogd: FSUM1229 syslogd is already active However, commenting out the line in the AUTOLOG stetament and starting SYSLOG from /etc/rc works like a charm. There must be something I'm missing, but I'm really flabbergasted anyways. On Mon, Oct 8, 2012 at 1:37 PM, Chris Mason chrisma...@belgacom.net wrote: Aitor The start of the syslog is specified in the AUTOLOG of the TCPIP configuration. Try reading in z/OS Communications Server IP Configuration Reference what the AUTOLOG statement in the PROFILE of the IP component of z/OS Communications Server does: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1A1B4B1/2.8 quote 2.8 AUTOLOG statement Use the AUTOLOG statement to provide a list of MVS started procedures to be started by the Autolog task when TCP/IP is started. ... /quote Yes I know this is the V1R13 manual but AUTOLOG hasn't changed since its invention in the early 1990s. Incidentally it is likely that the greatest concentration of specialists with in fact both the SNA (VTAM) as well as the IP components of z/OS Communications Server can be found here: For IBMTCP-L subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO IBMTCP-L Chris Mason On Mon, 8 Oct 2012 11:31:17 +0200, IT Pro bilit...@gmail.com wrote: Hello, We upgraded from z/OS 1.9 to z/OS 1.12 a few months ago. We have configured SYSLOGD daemon to be started as a started task from a PROC, but when started we see in the MVS log syslogd: FSUM1229 syslogd is already active, and the procedure ends. The start of the syslog is specified in the AUTOLOG of the TCPIP configuration. S SYSLOGT $HASP100 SYSLOGT ON STCINRDR $HASP373 SYSLOGT STARTED IEF403I SYSLOGT - STARTED - TIME=11.27.08 BPXF024I (USRFWKT) Oct 8 11:27:08 BOLSAWBD/USRFWKT SYSLOGT syslogd: FSUM1229 syslogd is already active IEF404I SYSLOGT - ENDED - TIME=11.27.08 $HASP395 SYSLOGT ENDED Could anybody give me a hint on this? I'm stuck at this. Thanks, Aitor. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
Curiously, on our z/OS 1.12 system, when I start SYSLOGD using /etc/rc via the line: # Start the syslog daemon _BPX_JOBNAME='SYSLOGD' /usr/sbin/syslogd -c -u I see the name SYSLOGD in the SDSF DA OSTC. This is in contrast to the CROND daemon which does indeed have a number appended to it. Apparently the SYSLOGD daemon on z/OS does not do a fork(). -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Hunkeler Peter (KIUP 4) Sent: Monday, October 08, 2012 9:04 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: syslogd: FSUM1229 syslogd is already active Hi Chris, I read that. I know it's the TCPIP subsystem which starts daemons specified in the AUTOLOG statement every x seconds, but I don't know why SYSLOG complains there is another instance running, that I don't see anywhere in the process list. a) UNIX daemons usually fork() once or twice during startup. I don't know off hand if this applies to syslogd as well but would guess so. b) z/OS will slightly change a process' (MVS) jobname upon fork() (and non-local spawn()) when the original jobname is shorter than 8 characters: a digit between 1 and 9 will be appended. If both a) and b) apply, then the resulting syslogd process will run in a different address space with a *different* jobname than the one started by TCP/IP's autolog feature. It will then think the job died and will restart it. If this turns out to be your problem, try running syslogd with an 8 character jobname (i,e.PROC name). z/OS will then leave the jobname alone upon fork()/spawn(). -- Peter Hunkeler -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of IT Pro Sent: Montag, 8. Oktober 2012 13:43 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: syslogd: FSUM1229 syslogd is already active However, commenting out the line in the AUTOLOG stetament and starting SYSLOG from /etc/rc works like a charm. There must be something I'm missing, but I'm really flabbergasted anyways. On Mon, Oct 8, 2012 at 1:37 PM, Chris Mason chrisma...@belgacom.net wrote: Aitor The start of the syslog is specified in the AUTOLOG of the TCPIP configuration. Try reading in z/OS Communications Server IP Configuration Reference what the AUTOLOG statement in the PROFILE of the IP component of z/OS Communications Server does: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1A1B4B1/2.8 quote 2.8 AUTOLOG statement Use the AUTOLOG statement to provide a list of MVS started procedures to be started by the Autolog task when TCP/IP is started. ... /quote Yes I know this is the V1R13 manual but AUTOLOG hasn't changed since its invention in the early 1990s. Incidentally it is likely that the greatest concentration of specialists with in fact both the SNA (VTAM) as well as the IP components of z/OS Communications Server can be found here: For IBMTCP-L subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO IBMTCP-L Chris Mason On Mon, 8 Oct 2012 11:31:17 +0200, IT Pro bilit...@gmail.com wrote: Hello, We upgraded from z/OS 1.9 to z/OS 1.12 a few months ago. We have configured SYSLOGD daemon to be started as a started task from a PROC, but when started we see in the MVS log syslogd: FSUM1229 syslogd is already active, and the procedure ends. The start of the syslog is specified in the AUTOLOG of the TCPIP configuration. S SYSLOGT $HASP100 SYSLOGT ON STCINRDR $HASP373 SYSLOGT STARTED IEF403I SYSLOGT - STARTED - TIME=11.27.08 BPXF024I (USRFWKT) Oct 8 11:27:08 BOLSAWBD/USRFWKT SYSLOGT syslogd: FSUM1229 syslogd is already active IEF404I SYSLOGT - ENDED - TIME=11.27.08 $HASP395 SYSLOGT ENDED Could anybody give me a hint on this? I'm stuck at this. Thanks, Aitor. - - For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM- MAIN -- For IBM-MAIN subscribe / signoff / archive access
Re: syslogd: FSUM1229 syslogd is already active
Patrick, in the output of D OMVS,A=ALL does not appear anywhere syslogd On Mon, Oct 8, 2012 at 2:55 PM, Patrick Loftus patrick.lof...@tnt.com wrote: Do you have CA Common Services? That fires up SYSLOGD if it isn't already running, but under a taskname of (by default) something like TNGEMSTR. I'd go to the PS panel in SDSF, or do a D OMVS,A=ALL command and look for a command with syslogd in it. It's not necessarily a task called SYSLOGD, but it will have syslogd in the command. Kind regards Patrick Loftus TNT Express ICS Ltd. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
We have customized /etc/rc to include the start of syslog, very similar to what you say, and it works like that: _BPX_JOBNAME='SYSLOGT' /usr/sbin/syslogd -d -c -u -f /usr/local/etc/syslogd.conf On Mon, Oct 8, 2012 at 3:12 PM, Mark Zelden m...@mzelden.com wrote: On Mon, 8 Oct 2012 11:31:17 +0200, IT Pro bilit...@gmail.com wrote: Hello, We upgraded from z/OS 1.9 to z/OS 1.12 a few months ago. We have configured SYSLOGD daemon to be started as a started task from a PROC, but when started we see in the MVS log syslogd: FSUM1229 syslogd is already active, and the procedure ends. The start of the syslog is specified in the AUTOLOG of the TCPIP configuration. S SYSLOGT $HASP100 SYSLOGT ON STCINRDR $HASP373 SYSLOGT STARTED IEF403I SYSLOGT - STARTED - TIME=11.27.08 BPXF024I (USRFWKT) Oct 8 11:27:08 BOLSAWBD/USRFWKT SYSLOGT syslogd: FSUM1229 syslogd is already active IEF404I SYSLOGT - ENDED - TIME=11.27.08 $HASP395 SYSLOGT ENDED Could anybody give me a hint on this? I'm stuck at this. Thanks, Aitor. Are you using the same /etc/rc after you upgraded? For example, this is how I start it from /etc/rc: # Start the SYSLOGD daemon which supplies logging functions for programs _BPX_JOBNAME='SYSLOGD' /usr/sbin/syslogd -f /etc/syslog.conf -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: syslogd: FSUM1229 syslogd is already active
Exactly what you say John: in SDSF DA, CRON appears with a number appended, where as SYSLOG does not, just the exact JOBNAME as specified in _BPX_JOBNAME On Mon, Oct 8, 2012 at 4:22 PM, McKown, John john.mck...@healthmarkets.com wrote: Curiously, on our z/OS 1.12 system, when I start SYSLOGD using /etc/rc via the line: # Start the syslog daemon _BPX_JOBNAME='SYSLOGD' /usr/sbin/syslogd -c -u I see the name SYSLOGD in the SDSF DA OSTC. This is in contrast to the CROND daemon which does indeed have a number appended to it. Apparently the SYSLOGD daemon on z/OS does not do a fork(). -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Hunkeler Peter (KIUP 4) Sent: Monday, October 08, 2012 9:04 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: syslogd: FSUM1229 syslogd is already active Hi Chris, I read that. I know it's the TCPIP subsystem which starts daemons specified in the AUTOLOG statement every x seconds, but I don't know why SYSLOG complains there is another instance running, that I don't see anywhere in the process list. a) UNIX daemons usually fork() once or twice during startup. I don't know off hand if this applies to syslogd as well but would guess so. b) z/OS will slightly change a process' (MVS) jobname upon fork() (and non-local spawn()) when the original jobname is shorter than 8 characters: a digit between 1 and 9 will be appended. If both a) and b) apply, then the resulting syslogd process will run in a different address space with a *different* jobname than the one started by TCP/IP's autolog feature. It will then think the job died and will restart it. If this turns out to be your problem, try running syslogd with an 8 character jobname (i,e.PROC name). z/OS will then leave the jobname alone upon fork()/spawn(). -- Peter Hunkeler -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of IT Pro Sent: Montag, 8. Oktober 2012 13:43 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: syslogd: FSUM1229 syslogd is already active However, commenting out the line in the AUTOLOG stetament and starting SYSLOG from /etc/rc works like a charm. There must be something I'm missing, but I'm really flabbergasted anyways. On Mon, Oct 8, 2012 at 1:37 PM, Chris Mason chrisma...@belgacom.net wrote: Aitor The start of the syslog is specified in the AUTOLOG of the TCPIP configuration. Try reading in z/OS Communications Server IP Configuration Reference what the AUTOLOG statement in the PROFILE of the IP component of z/OS Communications Server does: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1A1B4B1/2.8 quote 2.8 AUTOLOG statement Use the AUTOLOG statement to provide a list of MVS started procedures to be started by the Autolog task when TCP/IP is started. ... /quote Yes I know this is the V1R13 manual but AUTOLOG hasn't changed since its invention in the early 1990s. Incidentally it is likely that the greatest concentration of specialists with in fact both the SNA (VTAM) as well as the IP components of z/OS Communications Server can be found here: For IBMTCP-L subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO IBMTCP-L Chris Mason On Mon, 8 Oct 2012 11:31:17 +0200, IT Pro bilit...@gmail.com wrote: Hello, We upgraded from z/OS 1.9 to z/OS 1.12 a few months ago. We have configured SYSLOGD daemon to be started as a started task from a PROC, but when started we see in the MVS log syslogd: FSUM1229 syslogd is already active, and the procedure ends. The start of the syslog is specified in the AUTOLOG of the TCPIP configuration. S SYSLOGT $HASP100 SYSLOGT ON STCINRDR $HASP373 SYSLOGT STARTED IEF403I SYSLOGT - STARTED - TIME=11.27.08 BPXF024I (USRFWKT) Oct 8 11:27:08 BOLSAWBD/USRFWKT SYSLOGT syslogd: FSUM1229 syslogd is already active IEF404I SYSLOGT - ENDED - TIME=11.27.08 $HASP395 SYSLOGT ENDED Could anybody give me a hint on this? I'm stuck at this. Thanks, Aitor. - - For IBM-MAIN subscribe
Re: syslogd: FSUM1229 syslogd is already active
On Mon, 8 Oct 2012 16:31:39 +0200, IT Pro bilit...@gmail.com wrote: We have customized /etc/rc to include the start of syslog, very similar to what you say, and it works like that: _BPX_JOBNAME='SYSLOGT' /usr/sbin/syslogd -d -c -u -f /usr/local/etc/syslogd.conf Well then you've answered your own question.If you are starting it via /etc/rc, then when you try to start it from a console START command or AUTOLOG it will have already been active and you will see the message you are seeing. Choose only one method to start it (I prefer /etc/rc). Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
