Error Writing To Pipe Interrupted System Call
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Named pipe getting “clogged” up vote 1 down vote favorite for elem in {1..99} ; do echo $elem> mypipe ; done This piece of bash code should pass 99 ints through the pipe, which previously, in another terminal had this set: cat
Interrupted system call View next topic View previous topic Add To Favorites This topic has been marked "Resolved." This topic is not resolved, but there is a WORKAROUND. Post new topic Reply to topic DSXchange Forum Index » IBM® Infosphere DataStage Server Edition Author Message kausmone Participant Joined: 21 Sep 2007 Posts: 39 Location: Prague Points: 392 Posted: Thu Apr 10, 2008 12:53 am Reply with quote Back to top DataStage Release: 7x Job Type: Server OS: Unix Hello, I have a server job performing a Teradata Multiload using TDMLoad stage. Source data is in a flat file. The job has been running fine for months, scheduled at a frequencey of every 10 minutes. Recently however, every once in a while it aborts with the below message Code: Could not http://askubuntu.com/questions/101996/named-pipe-getting-clogged write row to data file in stage
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing https://www.veritas.com/support/en_US/article.000026185 Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English ä¸æ–‡(简体) English Français Deutsch Italiano 日本語 í•œêµì–´ Português Español USA Site: Veritas Veritas PartnerNet Network data management protocol backups failing with status 13, file read failed errors Article:000026185 Publish: Article URL:http://www.veritas.com/docs/000026185 Support / Article Sign In error writing Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Network data management protocol error writing to backups failing with status 13, file read failed errors Error Message bpfsmap: flush_flist: can't send imagedb recs err=41 Solution The problem is bptm is timing out after 10 minutes when bpdbm is busy updating the .f file. This should be a very large catalog.Some errors gathered from the logs:From bpdbm -23:39:35.195 [18854] <2> add_files: updating /usr/openv/netbackup/db/images/prost/1054000000/prost_users_1054608799_INCR.f......23:49:49.027 [18854] <2> add_files: 5000 files added to /usr/openv/netbackup/db/images/prost/1054000000/prost_users_1054608799_INCR.fThus bpdbm took more than 10 minutes to do this update.Later in the bpdbm log -23:49:49.028 [18854] <2> sighdl: pipe signal23:49:49.029 [18854] <2> put_string: cannot write data to network:  Broken pipe (32)23:49:49.029 [18854] <2> db_senddata: put_string(): connection dropped or not connected, Broken pipe, (32)23:49:49.030 [18854] <2> bpdbm: request complete: exit status 0From the bptm log -23:49:34.878 [10776] <2> sighdl: timed out23:49:34.879 [10776] <2> get_long: (1) cannot read (byte 1) from network: Interrupted system call (4)23:49:34.879 [10776] <2> db_getdata: get_string() failed: Interrupted system call (4) connection timed out (-2)23:49:34.879 [10776] <2> db_end: no DONE from db_