 |
|
| Linux Forum Index » Linux - Red Hat Forum » ERROR: No space left on device /dev/stdout... |
|
Page 1 of 1 |
|
| Author |
Message |
| maximb... |
 Posted: Sat Oct 31, 2009 8:19 pm |
|
|
|
Guest
|
Hi, all.
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 |
|
|
| Back to top |
|
|
|
| ynotssor... |
| Posted: Sun Nov 01, 2009 2:05 am |
|
|
|
Guest
|
In news:2852acac-24f0-45f2-adc5-9e8e0612d35b at (no spam) k19g2000yqc.googlegroups.com,
maximb <maxim.bakushin at (no spam) gmail.com> typed:
Quote: 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
$ ls -l /dev/stdout
lrwxrwxrwx 1 root root 15 Oct 3 17:27 /dev/stdout -> /proc/self/fd/1
I'd be willing to bet that your listing is different, that /dev/stdout has
somehow been corrupted by something that's happened into an ordinary file
rather than a symbolic link |
|
|
| Back to top |
|
|
|
| maximb... |
| Posted: Sun Nov 01, 2009 8:34 am |
|
|
|
Guest
|
On Nov 1, 10:05 am, "ynotssor" <ynots... at (no spam) invalid.org> wrote:
Quote: Innews:2852acac-24f0-45f2-adc5-9e8e0612d35b at (no spam) k19g2000yqc.googlegroups.com,
maximb <maxim.bakus... at (no spam) gmail.com> typed:
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
$ ls -l /dev/stdout
lrwxrwxrwx 1 root root 15 Oct 3 17:27 /dev/stdout -> /proc/self/fd/1
I'd be willing to bet that your listing is different, that /dev/stdout has
somehow been corrupted by something that's happened into an ordinary file
rather than a symbolic link
Hi.
Thank you for response.
The legacy application I had mentioned in the original post replaces
the native Linux shell with its own, so I do not have access to Linux
CLI commands.
Its seems like I have to 'enhance' the application's shell by Linux
CLI commands in order to see the status of the stdout descriptor and
trace the problem.
Also, as other experts noticed, possibly I have to double-check all
the standard output re-directions to filesystem directories.
Again, thanks for your time.
maximb |
|
|
| Back to top |
|
|
|
| ynotssor... |
| Posted: Tue Nov 03, 2009 1:34 pm |
|
|
|
Guest
|
In news:c8afaf22-811f-4b88-afe9-8df330680c57 at (no spam) a21g2000yqc.googlegroups.com,
maximb <maxim.bakushin at (no spam) gmail.com> typed:
Quote: $ ls -l /dev/stdout
lrwxrwxrwx 1 root root 15 Oct 3 17:27 /dev/stdout -> /proc/self/fd/1
I'd be willing to bet that your listing is different, that
/dev/stdout has somehow been corrupted by something that's happened
into an ordinary file rather than a symbolic link
....
The legacy application I had mentioned in the original post replaces
the native Linux shell with its own, so I do not have access to Linux
CLI commands.
....
Log in as a different user that uses bash, csh, etc as its $SHELL. |
|
|
| Back to top |
|
|
|
| maximb... |
| Posted: Tue Nov 03, 2009 10:10 pm |
|
|
|
Guest
|
On Nov 3, 8:34 pm, "ynotssor" <ynots... at (no spam) invalid.org> wrote:
Quote: Innews:c8afaf22-811f-4b88-afe9-8df330680c57 at (no spam) a21g2000yqc.googlegroups.com,
maximb <maxim.bakus... at (no spam) gmail.com> typed:
$ ls -l /dev/stdout
lrwxrwxrwx 1 root root 15 Oct 3 17:27 /dev/stdout -> /proc/self/fd/1
I'd be willing to bet that your listing is different, that
/dev/stdout has somehow been corrupted by something that's happened
into an ordinary file rather than a symbolic link
...
The legacy application I had mentioned in the original post replaces
the native Linux shell with its own, so I do not have access to Linux
CLI commands.
...
Log in as a different user that uses bash, csh, etc as its $SHELL.
Hi.
The login procedure is replaced too.
Thanks.
maximb |
|
|
| Back to top |
|
|
|
| C. (http://symcbean.blogspot.com/)... |
| Posted: Wed Nov 04, 2009 3:48 am |
|
|
|
Guest
|
On Nov 4, 8:10 am, maximb <maxim.bakus... at (no spam) gmail.com> wrote:
Quote: On Nov 3, 8:34 pm, "ynotssor" <ynots... at (no spam) invalid.org> wrote:
Innews:c8afaf22-811f-4b88-afe9-8df330680c57 at (no spam) a21g2000yqc.googlegroups.com,
maximb <maxim.bakus... at (no spam) gmail.com> typed:
$ ls -l /dev/stdout
lrwxrwxrwx 1 root root 15 Oct 3 17:27 /dev/stdout -> /proc/self/fd/1
I'd be willing to bet that your listing is different, that
/dev/stdout has somehow been corrupted by something that's happened
into an ordinary file rather than a symbolic link
...
The legacy application I had mentioned in the original post replaces
the native Linux shell with its own, so I do not have access to Linux
CLI commands.
...
Log in as a different user that uses bash, csh, etc as its $SHELL.
Hi.
The login procedure is replaced too.
Thanks.
maximb
So if it uses a custom login and a custom shell and doesn't allow you
proper access to the operating system then you're stuffed unless you
can get in touch with the supplier.
(P.S. stdout may be redirected to a device - on a normal system you
could try 'df' or looking for files over 2Gb)
C. |
|
|
| Back to top |
|
|
|
|
|
All times are GMT - 5 Hours
The time now is Tue Dec 08, 2009 7:15 pm
|
|