Cat Write Error Resource Temporarily Unavailable
Contents |
linux (Ubuntu) Edit Invalid Undecided Unassigned Edit You need to log in to change this bug's status. Affecting: linux (Ubuntu) Filed here by: Daniel Gonzalez When: 2007-10-10 Completed: 2008-11-02 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex
Cat Read Error Resource Temporarily Unavailable
Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build bash read error 0 resource temporarily unavailable Ubuntu RTM Package (Find…) Project (Find…) Status Importance Invalid Undecided Assigned to Nobody Me Comment on this change (optional) Email me
Tee Standard Output Resource Temporarily Unavailable
about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description I am running Gutsy, upgraded on the 9 October 2007. The current kernel is: Linux version 2.6.22-14-generic socket error resource temporarily unavailable (buildd@palmer) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Tue Oct 9 09:51:52 GMT 2007 I have an amd x2, but I am running the 32 bit OS (or so I think). Currently I have KSysguard, Firefox, emacs and Rhythmbox running. I am developing using tcl scripting. I run my tcl script from an xterm, with output teed to a log file in the form: ./tcl_script | tee log_file socket error resource temporarily unavailable python The script produces a lot of output, quite fast. Around 50% of the times the script stops and I get the message: "tee: write error" Sometimes I see also: "tee: standard output: Resource temporarily unavailable" I get the following message The error seems to disappear if I redirect the output of tee to a file in the way: ./tcl_script | tee log_file > file This same script is working fine in other machines (Solaris). I do not attach the script since it is actually a very big test suite. more information lspci 00:00.0 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a1) 00:01.0 ISA bridge: nVidia Corporation MCP61 LPC Bridge (rev a2) 00:01.1 SMBus: nVidia Corporation MCP61 SMBus (rev a2) 00:01.2 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a2) 00:02.0 USB Controller: nVidia Corporation MCP61 USB Controller (rev a2) 00:02.1 USB Controller: nVidia Corporation MCP61 USB Controller (rev a2) 00:04.0 PCI bridge: nVidia Corporation MCP61 PCI bridge (rev a1) 00:05.0 Audio device: nVidia Corporation MCP61 High Definition Audio (rev a2) 00:06.0 IDE interface: nVidia Corporation MCP61 IDE (rev a2) 00:07.0 Bridge: nVidia Corporation MCP61 Ethernet (rev a2) 00:08.0 IDE interface: nVidia Corporation MCP61 SATA Controller (rev a2) 00:08.1 IDE interface: nVidia Corporation MCP61 SATA Controller (rev a
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
Fork Error Resource Temporarily Unavailable
more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered error 35 resource temporarily unavailable Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:
Error 11 Resource Temporarily Unavailable
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 Why is this tee losing stdout? up vote 3 down vote favorite Simple script: https://bugs.launchpad.net/bugs/151440 #!/bin/bash remote_ssh_account="depesz@localhost" directory_to_tar=pgdata exec nice tar cf - "$directory_to_tar" | \ tee >( md5sum - | \ ssh "$remote_ssh_account" 'cat - > /tmp/h3po4-MD5-2012-03-13.tar' ) | \ ssh "$remote_ssh_account" 'cat - > /tmp/h3po4-data-2012-03-13.tar' Theoretically it should deliver the data and checksum, to remote machine. But somehow the tee fails with: tee: standard output: Resource temporarily unavailable Did strace, but nothing came out of it. I see both ssh started, and tee writing to both of them, but only http://serverfault.com/questions/369757/why-is-this-tee-losing-stdout the pipe to ( md5sum | ssh ) gets data - strace of the ssh "data" doesn't get any data, and after 5 seconds tee shows the error. Aside from this all works. 2 connections are established, tar works, md5sum and its delivery works. linux ssh bash pipe tee share|improve this question asked Mar 14 '12 at 19:21 user13185 On the strace front, try strace -fF. Works like a champ for me. –BMDan Mar 14 '12 at 20:14 -fF is not in manual, but there is -f, -F and -ff. I used strace -ff -o strace.log -s 512 ./z.sh –user13185 Mar 14 '12 at 20:25 -fF is the same as -f -F. The -F is actually unneeded on most of the systems I work on, but it (tries to) follow vforks on older versions of strace, and has no effect on newer ones, but it doesn't hurt. -ff ends up writing a bunch of files (one per PID) that you then have to collate back into a sensible timeline, so I avoid it in the vast majority of situations. That said, -ff should work, but the output files will be oddly-named. –BMDan Mar 15 '12 at 12:55 add a comment| 2 Answers 2 active oldest votes up vote 3 down vote accepted Try this, an alternative way of doing the pipe that breaks: #!/bin/bash remote_ssh_account="dep
here for a quick overview of the site Help Center Detailed answers to http://stackoverflow.com/questions/28096337/reading-fifos-resource-temporary-unavailable any questions you might have Meta Discuss the workings and http://unix.stackexchange.com/questions/253903/creating-threads-fails-with-resource-temporarily-unavailable-with-4-3-kernel policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community resource temporarily Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Reading FIFOs, resource temporary unavailable up vote 1 down vote favorite I have a problem with a multithreaded program. Basically I'm using fifos to pass messages between threads resource temporarily unavailable This is the thread that read from the pipe: thread_args args = (thread_args) *arguments; char* fifo_buffer = calloc (FIFO_SIZE, sizeof(char)); int flag; int fifo_win_to_send = open(args.fifo_names[FIFO_WTS], O_RDONLY); if (fifo_win_to_send < 0) { perror("fifo: error opening fifo"); exit(1); } flag = fcntl(fifo_win_to_send, F_GETFL); fcntl(fifo_win_to_send, F_SETFL, flag | O_NONBLOCK | O_NDELAY); if (read( fifo_win_to_send, fifo_buffer, FIFO_SIZE) <= 0) { perror("fifo: error reading window to sender fifo"); exit(1); } if (VERBOSE_SENDER) { printf("Read %s from fifo window_to_sender", fifo_buffer); fflush(stdout); } and the "writing thread": char * fifo_buffer = calloc(FIFO_SIZE, sizeof(char)); thread_args args = (thread_args) *arguments; int fifo_win_to_send = open(args.fifo_names[FIFO_WTS], O_WRONLY); if (fifo_win_to_send < 0) { perror("fifo: error opening fifo"); exit(1); } *fifo_buffer = 'A'; memcpy(fifo_buffer+1, &sequence_number, sizeof(int)); write( fifo_win_to_send, fifo_buffer, FIFO_SIZE); if (VERBOSE_FIFO) { printf("From window to send:%s\n", fifo_buffer); fflush(stdout); } The fifo files are created in the main() before threads are spawned: mkdir("temp",0777); char * fifo_id[6]; for(i=0;i<6;i++) { fifo_id[i]=calloc(100,sizeof(char)); } fifo_id[FIFO_WTS] = strcpy(fifo_id[FIFO_WTS], "tem
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 Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. 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 Creating threads fails with “Resource temporarily unavailable” with 4.3 kernel up vote 13 down vote favorite 5 I am running a docker server on Arch Linux (kernel 4.3.3-2) with several containers. Since my last reboot, both the docker server and random programs within the containers crash with a message about not being able to create a thread, or (less often) to fork. The specific error message is different depending on the program, but most of them seem to mention the specific error Resource temporarily unavailable. See at the end of this post for some example error messages. Now there are plenty of people who have had this error message, and plenty of responses to them. What’s really frustrating is that everyone seems to be speculating how the issue could be resolved, but no one seems to point out how to identify which of the many possible causes for the problem is present. I have collected these 5 possible causes for the error and how to verify that they are not present on my system: There is a system-wide limit on the number of threads configured in /proc/sys/kernel/threads-max (source). In my case this is set to 60613. Every thread takes some space in the stack. The stack size limit is configured using ulimit -s (source). The limit for my shell used to be 8192, but I have increased it by putting * soft stack 32768 into /etc/security/limits.conf, so it ulimit -s now returns 32768. I have also increased it for the docker process by putting LimitSTACK=33554432 into /etc/systemd/system/docker.service (source, and I verified that the limit applies by looking into /proc/