ERROR: No space left on device /dev/stdout
maximb
It is my first post to this group, so please be patient if I do not
follow an accepted format. Also, if this group is not the right place
to ask such a questions, please say so and kindly suggest an
alternative.
I have a legacy software application running on Red Hat 6.1. Yes, it
is pretty old. Known, that the filesystem in use is the ext2fs.
Sometimes, after a few days of running without a problem, the system
throws the following error messages as a response to an attempt to
save or display the curently running configuration:
awk: write failure (No space left on device)
awk: close failed on file /dev/stdout (No space left on device)
echo: error writing to the standard output: No space left on device
Somewhere I had read an opinion, that such kind of errors can be
related to size or avalability of free memory in /tmp directory. Is
that correct ?
Thanks in advance.
maximb
lapisdecor
maximb
As far as I understand, the filesystem is RAM-mounted.
I still not quite understand how /dev/stdout file can suffer from lack
of free space... May be the problem arises when the stdout is
redirected to another file.
Thanks for your time.
maximb
Jeremiah Bess
Jeremiah E. Bess
Network Ninja, Penguin Geek, Father of four
Robert Citek
On Sun, Nov 1, 2009 at 1:19 AM, maximb <maxim.b...@gmail.com> wrote:
> Somewhere I had read an opinion, that such kind of errors can be
> related to size or avalability of free memory in /tmp directory. Is
> that correct ?
Depending on how /tmp is set up, it could be a ramdisk, a separate
partition, or just another folder in the filesystem.
Can you run the following script and post the contents of output.txt:
true && ( set -x
head /etc/issue*
df -hT /tmp
df -hTl
) >& output.txt
Also, have you tried booting up the machine with a LiveCD, e.g.
Knoppix, and running an fsck on the filesystem
Regards,
- Robert
maximb
it's a good question. I'd like to know it, but the issue is that the
legacy application I had mentioned in the original post replaces the
native Linux shell with its own. Thus, the Linux native shell commands
are not interpreted by the application's shell.
Thanks for your time.
maximb
>
> - Show quoted text -
maximb
I will use your suggestion and run the script as soon as I 'enhance'
the application's shell with native Linux shell commands.
Can you, please, post some examples of a good- and-bad looking outputs
of the script ?
Thanks in advance.
maximb
Robert Citek
> I will use your suggestion and run the script as soon as I 'enhance'
> the application's shell with native Linux shell commands.
Can you elaborate on what that means? Are you able to run a bash or
sh shell? Are you able to boot into runlevel 1 or single?
> Can you, please, post some examples of a good- and-bad looking outputs
> of the script ?
Here's the output when run on my Ubuntu machine:
$ cat output.txt
+ head /etc/issue /etc/issue.net
==> /etc/issue <==
Ubuntu 8.04.3 LTS \n \l
==> /etc/issue.net <==
Ubuntu 8.04.3 LTS
+ df -hT /tmp
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda3 ext3 20G 16G 2.4G 87% /
+ df -hTl
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda3 ext3 20G 16G 2.4G 87% /
varrun tmpfs 220M 116K 220M 1% /var/run
varlock tmpfs 220M 0 220M 0% /var/lock
udev tmpfs 220M 52K 220M 1% /dev
devshm tmpfs 220M 12K 220M 1% /dev/shm
lrm tmpfs 220M 40M 181M 18%
/lib/modules/2.6.24-25-generic/volatile
gvfs-fuse-daemon
fuse.gvfs-fuse-daemon 20G 16G 2.4G 87% /home/rwcitek/.gvfs
The output you get from RedHat should look similar. Although I don't
remember if RH6.1 has /etc/issue or if the df command has the -T
option.
As for bad-looking output, it could be anything, for example an error
with "command not found".
Regards,
- Robert
maximb
The whole machine I work with is not a general purpose machine, but
some kind of embedded HDD-less product. When powered up, the machine
runs the OS, which in turn 'wired' to perform numerous manipulations
in order to run what we call Application. As I've said before, the
Application replaces the native Linux shell (sh, bash, etc) with its
own so, that I cannot login as a root, for example, and use the Linux
native CLI interface. Considering the option to 'un-wire' the OS from
the Application and manually perform all the manipulations appears to
lead to huge overhead and, possibly, change in runtime behaviour.
That's why I'm giving very serious thought to implementing a backdoor
in the Application's shell, which will allow me to use Linux CLI
commands.
What you say ?
Thanks.
maximb
On Nov 4, 2:53 am, Robert Citek <robert.ci...@gmail.com> wrote:
Robert Citek
> The whole machine I work with is not a general purpose machine, but
> some kind of embedded HDD-less product.
> What you say ?
What product is this? Can you get access to the filesystem by booting
a LiveCD, e.g. Knoppix?
Regards,
- Robert
maximb
No, I cannot do it. There is no CD-ROM device and no PATA slots on the
MB.
Fortunally, I've got the sources of the whole system.
Thanks, again.
maximb
On Nov 4, 3:33 pm, Robert Citek <robert.ci...@gmail.com> wrote:
spokeman
You've answered your own question, although you may not realize it.
Your computer has no hard drive. Therefore the file system HAS to be
in RAM (unless it's really really old, and running from floppies!).
Since the file system is running as a RAM disk, then you are most
likely running out of RAM. Since this machine has been around a while,
either your RAM has developed bad spots, or the machine has
accumulated "stuff" that is filling the RAM.
Given the hardware setup you have described, you are most likely
dealing with a proprietary device and application. The company that
the machine came from will be your best resource for a solution, given
that they know the hardware and application parameters.