Re: [U2] Unirpc hunghup (solved)
Hi all. Finally we discovered the problem. It was caused by an IDS located somewhere by the inter-lan provider. So that, after a certain number of connections to the server-IP, the provider blocked any further packet after the first ACK packet with this server-IP destination. Every connection from remote computer "hunged" the unirpc, even after server reboot. The only sollution was to change the server IP addres. Thanks to the u2-list Regards, __ Augusto Alonso Alonso I.T. Manager Quiter Servicios Informaticos S.L. Tel: +34 902 23 33 23 Fax: +34 902 23 42 80 [EMAIL PROTECTED] www.quiter.com __ - Original Message - From: "Augusto Alonso" <[EMAIL PROTECTED]> To: Sent: Friday, May 16, 2008 2:48 AM Subject: Re: [U2] Unirpc hunghup Thanks, Mike. But the field you talk about is temporary, according to Microsoft. The main problem is that unirpcd.exe doesn't understand the "timeout" parameter. You can reproduce this behaviour by telneting any Universe server on port 31438: After that, any new RPC conection (UVADMIN i.e.) will fail. If the Universe server is a unix box, then you can workaround it by starting the unirpcd with the -timeout15 parameter. What I am looking for, is a similar workaround for a Windows server. Does anybody knows? Thanks in advance, Augusto - Original Message - From: "Mike Dallaire" <[EMAIL PROTECTED]> To: Sent: Thursday, May 15, 2008 7:21 PM Subject: RE: [U2] Unirpc hunghup Augusto, I believe you want to go to Administrative Tools\Services and locate the UniRPC service. From there you can stop the service and then right click on it an go to properties. At the bottom you should see a field to enter start parameters. This is where you would put your timeout setting, then start the service. HTH, Mike Michael Dallaire Senior Applications Developer IBM Certified Solutions Expert Mortgage Builder Software, Inc. Phone: (248) 304-0600 x 103 Fax: (248) 304-0601 [EMAIL PROTECTED] www.mortgagebuilder.com Providing Outstanding Support It's more than just a company philosophy; it's a whole corporate culture whose foundation is service. Confidentiality Notice This transmission may contain confidential information which is intended for the exclusive use of the intended recipient. Any disclosure, copying, distribution or use of the contents by anyone other than the intended recipient is strictly prohibited. If received in error, please reply to the sender immediately. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Augusto Alonso Sent: Thursday, May 15, 2008 12:14 PM To: u2-users@listserver.u2ug.org Subject: [U2] Unirpc hunghup Hi all. Is there any way to start the unirpcd daemon with a timeout value, in a Windows box, like in unix "unirpcd -timeout999"? Whe have done it successfully under Linux, that is quite vulnerable under viruses or unstable communications. But is the first time we see this kind of "Denial Of Service" in a Windows server. Is a Win2003 server with UniVerse 10.0.10. The hung occurs usually in the afternoon, and is caused only by some remote users, not the local ones. Could it would be caused by "black hole" routers? Note: we have tried to start the service adding "c:\ibm\uv\bin\unirpcd -timeout15" via REGEDIT, but it doesn't works. Regards, __ Augusto Alonso Alonso I.T. Manager Quiter Servicios Informaticos S.L. Tel: +34 902 23 33 23 Fax: +34 902 23 42 80 [EMAIL PROTECTED] www.quiter.com __ - Original Message - From: "Patricia Wilson" <[EMAIL PROTECTED]> To: Sent: Tuesday, July 25, 2006 10:09 PM Subject: RE: [U2] Unirpc Oh I found my answer in this Technote on IBM's website Is there a way to cause the "unirpcd" to timeout? Problem "unirpcd" requires a series of communication handshakes between the client and server component before a service can be open and closed down. If one of these handshakes is missing then the "unirpcd" will hang in a wait / listening state thereby by "hanging" the "unirpcd" daemon. This problem creates a situation where no new rpc services can be started. A timeout parameter was created to allow unirpcd abandon waiting for the other part of the incoming request after a certain time so that it can accept new requests. This fix is the result of a number of cases where the unirpcd is left hanging waiting for input from the client and the unirpcd daemon never getting it. The addition of this parameter is the result of ECASE 5040 and applies to UniVerse 10.x and UniData 6.x Cause "unirpcd" was hanging due to client session not responding with information for the "unirpcd" to process Solution NOTE: This applies to UNIX and Linux systems. The "unirpcd" daemon can be started "manually" with a timeout value. The syntax is as follows: ./unirpcd -timeout300 There is no space between "-timeout" and the actual value. The time
Re: [U2] Printer errors in the error log
[EMAIL PROTECTED] wrote: We're logging many errors in the UV error log that say "Too many PRINTER channels open." I know the channel numbers themselves are limited to 0-255, but I didn't know there was a limit on how many could be open at one time. What is the limit? Is there a configuration parameter somewhere that I'm missing? You can specify channel 0 thru 254 as the output channel, (SETPTR x, PRINT ON x, PRINTER CLOSE x); but there's a limit on how many you can have open at a single time. Prime Information would allow you to have 255 open, but I remember when converting to Universe that there was a limit of either 15 or 16 and it was unchangeable. I had to do some creative coding to convert a couple apps. -- Allen Egerton aegerton at pobox dot com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Printer errors in the error log
** Comments embedded below. ** On May 24, 2008, at 2:22 PM, Stevenson, Charles wrote: From: [EMAIL PROTECTED] We're logging many errors in the UV error log that say "Too many PRINTER channels open." I know the channel numbers themselves are limited to 0-255, but I didn't know there was a limit on how many could be open at one time. What is the limit? Is there a configuration parameter somewhere that I'm missing? I vaguely remember encountering this about 10 years ago in a Sequoia/UV conversion. I think there is/was a limit of 14 or so that can be open at one time. I believe the number is 16, which includes the default unit 0, so you can use up to 15 with the numbers selected from the range of 1-255. I don't think there is/was a config param work around. There is no parameter that I have ever heard of. It is my understanding that the limit is hardcoded into both the UV run- machine and the external usp spooler daemon. Or Clif Oliver's. I think he sells a print environment handler designed to make up for UniVerse's inadequacies. Unfortunately, my package (ESP) will not help in this situation. It is more of a print job manager. But thanks for thinking of it! Regards, Clif -- W. Clifton Oliver, CCP CLIFTON OLIVER & ASSOCIATES Tel: +1 619 460 5678Web: www.oliver.com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Printer errors in the error log
Hi Brian, I'm just curious. Why are you using so many print channels? Are you issuing that many PRINT ON statements in a BASIC program? I couldn't find any limit stated in the UV documentation either, but I may have missed it. Have you asked your IBM Support Organization? Or how about [EMAIL PROTECTED] Rgds, Dave Dave Taylor Sysmark Information Systems, Inc. Authorized IBM Business Partner 49 Aspen Way Rolling Hills Estates, CA 90274 (O) 800-SYSMARK (800-797-6275) (F) 310-377-3550 (C) 310-561-5200 www.sysmarkinfo.com - Original Message - From: <[EMAIL PROTECTED]> To: Sent: Friday, May 23, 2008 6:46 AM Subject: [U2] Printer errors in the error log We're logging many errors in the UV error log that say "Too many PRINTER channels open." I know the channel numbers themselves are limited to 0-255, but I didn't know there was a limit on how many could be open at one time. What is the limit? Is there a configuration parameter somewhere that I'm missing? TIA Brian _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material not intended for Public use. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is strictly prohibited. If you received this communication in error, please notify the sender and delete the material from any and all computers or devices. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Printer errors in the error log
From: [EMAIL PROTECTED] > We're logging many errors in the UV error log that say > "Too many PRINTER channels open." > I know the channel numbers themselves are limited to 0-255, > but I didn't know there was a limit on how many could be > open at one time. What is the limit? > Is there a configuration parameter somewhere that I'm missing? I vaguely remember encountering this about 10 years ago in a Sequoia/UV conversion. I think there is/was a limit of 14 or so that can be open at one time. I don't think there is/was a config param work around. If you do: SETPTR n,... SETPTR n+1,... SETPTR n+2,... Etc. I think you'll find that error message once you hit about n+14. I don't recall how to explicitly close a particular channel so you can open another. Anyone? In our case, I think we didn't need to actually print to more than 14 printers at once. We converted the pick code so that a program would call a utility subroutine to map the particular printers it needed onto one of the channels 0-14. If you have to print to more than 14 at once, probably writeseq to files & spool later. If you have to print to more than 14 at once, may the Lord's mercy be upon you. Or Clif Oliver's. I think he sells a print environment handler designed to make up for UniVerse's inadequacies. Chuck S --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
