 |
|
 |
|
Next: Bug#553570: gpc-doc: usr-share-doc-symlink-to-for..
|
| Author |
Message |
External

Since: Oct 31, 2009 Posts: 3
|
(Msg. 1) Posted: Sat Oct 31, 2009 11:19 pm
Post subject: ERROR: No space left on device /dev/stdout Archived from groups: linux>redhat (more info?)
|
|
|
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 |
|
 |  |
External

Since: Mar 15, 2009 Posts: 6
|
(Msg. 2) Posted: Sun Nov 01, 2009 1:05 am
Post subject: Re: ERROR: No space left on device /dev/stdout [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
In news:2852acac-24f0-45f2-adc5-9e8e0612d35b@k19g2000yqc.googlegroups.com,
maximb <maxim.bakushin.TakeThisOut@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 |
|
| Back to top |
|
 |  |
External

Since: Oct 31, 2009 Posts: 3
|
(Msg. 3) Posted: Sun Nov 01, 2009 10:34 am
Post subject: Re: ERROR: No space left on device /dev/stdout [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
On Nov 1, 10:05 am, "ynotssor" <ynots....TakeThisOut@invalid.org> wrote:
> Innews:2852acac-24f0-45f2-adc5-9e8e0612d35b@k19g2000yqc.googlegroups.com,
> maximb <maxim.bakus....TakeThisOut@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 |
|
 |  |
External

Since: Mar 15, 2009 Posts: 6
|
(Msg. 4) Posted: Tue Nov 03, 2009 10:34 am
Post subject: Re: ERROR: No space left on device /dev/stdout [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
In news:c8afaf22-811f-4b88-afe9-8df330680c57@a21g2000yqc.googlegroups.com,
maximb <maxim.bakushin.TakeThisOut@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. |
|
| Back to top |
|
 |  |
External

Since: Oct 31, 2009 Posts: 3
|
(Msg. 5) Posted: Wed Nov 04, 2009 12:10 am
Post subject: Re: ERROR: No space left on device /dev/stdout [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
On Nov 3, 8:34 pm, "ynotssor" <ynots... DeleteThis @invalid.org> wrote:
> Innews:c8afaf22-811f-4b88-afe9-8df330680c57@a21g2000yqc.googlegroups.com,
> maximb <maxim.bakus... DeleteThis @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 |
|
 |  |
External

Since: Nov 16, 2007 Posts: 4
|
(Msg. 6) Posted: Wed Nov 04, 2009 5:48 am
Post subject: Re: ERROR: No space left on device /dev/stdout [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
On Nov 4, 8:10 am, maximb <maxim.bakus....DeleteThis@gmail.com> wrote:
> On Nov 3, 8:34 pm, "ynotssor" <ynots....DeleteThis@invalid.org> wrote:
>
>
>
> > Innews:c8afaf22-811f-4b88-afe9-8df330680c57@a21g2000yqc.googlegroups.com,
> > maximb <maxim.bakus....DeleteThis@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 |
|
 |  |
|
You can post new topics in this forum You can reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|
 |
|
|