convert "process stopped"

dlublink · 09-28-2006, 09:13 AM

The following command:

vserver-lublink:/var/www/gallery/officer's mess# convert +profile '*' -filter Lanczos -geometry 80x60 'IMG_0157.JPG' 't_IMG_0157.JPG'

Gives the output:

Processus arrêté

Which is french for 'process stopped'.

I don't know why it's doing this, any ideas?

David

haertig · 09-28-2006, 10:22 AM

In the same terminal window where you originally started the process (it's "controlling terminal"), type jobs. See what it tells you. Another way to check is to run ps j -e and see if your process has a "T" in the STAT column of the output. If your job is stopped, you can bring it back into the foreground by typing fg.

How did it get stopped in the first place? You might have accidently hit <ctrl>-z or <ctrl>-y (these are standard job control key combinations). Or you might have done something like this: kill -s STOP <pid> from a different terminal window (pretty hard to do that by accident though!) Root could have done this to you as well, if they didn't like what you were doing.

dlublink · 09-28-2006, 10:28 AM

Quote:

Originally Posted by haertig

In the same terminal window where you originally started the process (it's "controlling terminal"), type jobs. See what it tells you. Another way to check is to run ps j -e and see if your process has a "T" in the STAT column of the output. If your job is stopped, you can bring it back into the foreground by typing fg.

How did it get stopped in the first place? You might have accidently hit <ctrl>-z or <ctrl>-y (these are standard job control key combinations). Or you might have done something like this: kill -s STOP <pid> from a different terminal window (pretty hard to do that by accident though!) Root could have done this to you as well, if they didn't like what you were doing.

ps j -e shows that all processes are S, Ss or R+. There are no converts listed.

I do believe I hit ctrl+y or ctrl+z as I have tried several times in several different ways to run it.

I am root on the vserver in question, perhaps the vserver administrator has CPU throttling, but nothing else has ever been interrupted before...

David

haertig · 09-28-2006, 11:08 AM

Quote:

Originally Posted by dlublink

Which is french for 'process stopped'.

Maybe your "process stopped" is not the job control "stop" I was thinking about. It could be something internal to the convert program.

I just ran a quick test on my computer and stopped a process, but it only says "Stopped", not "process stopped". So maybe we are talking about different things. What does the STAT column of your "ps j" output tell you about your specific convert process? S and R are typical normal running process states, lowercase s indicates a session leader, and + indicates a foreground process. T indicates a stopped process. If convert is not in a T state, then it's not stopped from a job control standpoint.

Code:

$ vi testfile
... at this point I hit ctrl-z ...
[1]+  Stopped                 vi testfile
$ jobs
[1]+  Stopped                 vi testfile
$ ps j
 PPID   PID  PGID   SID TTY      TPGID STAT   UID   TIME COMMAND
 9825  9827  9827  9827 pts/2     9827 Ss+   1000   0:00 bash
 9825 12892 12892 12892 pts/1    12892 Ss+   1000   0:00 bash
 9825 17972 17972 17972 pts/3    19018 Rs    1000   0:00 bash
17972 19009 19009 17972 pts/3    19018 T     1000   0:00 vi testfile
17972 19018 19018 17972 pts/3    19018 R+    1000   0:00 ps j
$ fg
vi testfile
... then I hit :q! to get out of vi
$

dlublink · 09-28-2006, 11:18 AM

Quote:

Originally Posted by haertig

Maybe your "process stopped" is not the job control "stop" I was thinking about. It could be something internal to the convert program.

I agree with you on this, otherwise there would be something more in ps.

I tried running it with verbose and found nothing.

Any ideas as to what in the program might do this?

Thanks,

David

haertig · 09-28-2006, 11:46 AM

Quote:

Originally Posted by dlublink

Any ideas as to what in the program might do this?

Sorry, no. I've never used the program personally. man convert didn't give me any clues, nor did strings /usr/bin/convert. Since you're seeing the message in French, I wouldn't really have expected to find that text string in convert itself. Some language localization library somewhere perhaps.