topic Re: command working fine after machine reboot, but it (the command) is hang couple days later. in Operating System - Linux

command working fine after machine reboot, but it (the command) is hang couple days later.

Anh-Thu Tran — Wed, 07 Jun 2006 14:29:35 GMT

I am able to use ps2pdf command after the machine (redhat ES3) is rebooted. After several days working fine, the ps2pdf command is hang and need the machine to reboot to use the command again. Does anybody have any ideas?

Re: command working fine after machine reboot, but it (the command) is hang couple days later.

A. Clay Stephenson — Wed, 07 Jun 2006 14:37:42 GMT

Note that ps2pdf is simply a front-end script for ghostscript (gs). My best guess is that a somewhat corrupt input file can leave gs waiting for more input (on stdin) that it never sees. Rather than rebooting, I suspect you simply need to kill gs. It would probably also be wise to look for any gs patches.

Re: command working fine after machine reboot, but it (the command) is hang couple days later.

Anh-Thu Tran — Wed, 07 Jun 2006 14:43:10 GMT

We have the second box (Older redhat version)with same gs version and it does not have any problem, so I am not sure if the patch can fix the problem.

Re: command working fine after machine reboot, but it (the command) is hang couple days later.

A. Clay Stephenson — Wed, 07 Jun 2006 14:46:50 GMT

The patch could be to one of the many shared libraries that gs uses.

Re: command working fine after machine reboot, but it (the command) is hang couple days later.

melvyn burnard — Wed, 07 Jun 2006 16:27:31 GMT

Posted in wrong forum, moved to correct forum

Re: command working fine after machine reboot, but it (the command) is hang couple days later.

Vitaly Karasik_1 — Thu, 08 Jun 2006 01:07:33 GMT

what about free disk space?

Re: command working fine after machine reboot, but it (the command) is hang couple days later.

dirk dierickx — Mon, 12 Jun 2006 09:44:00 GMT

what about just killing the process, rebooting the whole machine is a bit overkill.

Re: command working fine after machine reboot, but it (the command) is hang couple days later.

Anh-Thu Tran — Wed, 14 Jun 2006 15:19:27 GMT

Yes, I can kill the gs process to get out or control C. However, my question is why the ps2pdf command is working fine after the reboot and stop later (just hang). To use the command, we have to reboot the box, and of course it will hang sometime later. How can I fix it?

Re: command working fine after machine reboot, but it (the command) is hang couple days later.

dirk dierickx — Thu, 15 Jun 2006 01:38:54 GMT

run strace when executing the command, you'll get a lot of stuff on your screen, and it should after a while show you what it is trying to do and is not working.

Re: command working fine after machine reboot, but it (the command) is hang couple days later.

Anh-Thu Tran — Thu, 15 Jun 2006 12:38:54 GMT

The strace anh.ps anh.pdf stopped at:
open("anh.pdf", O_RDWR|O_CREAT|O_TRUNC, 0666) = 8
open("/dev/random", O_RDONLY) = 9
fstat64(9, {st_mode=S_IFCHR|0644, st_rdev=makedev(1, 8), ...}) = 0
ioctl(9, SNDCTL_TMR_TIMEBASE or TCGETS, 0xbfff8098) = -1 EINVAL (Invalid argument)
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb75e5000
read(9,

Any ideas?

Re: command working fine after machine reboot, but it (the command) is hang couple days later.

Marek Podmaka — Wed, 28 Jun 2006 06:13:29 GMT

Please do the strace again and when it stops at the read() syscall, from another console do:
ls -l /proc/PID/fd
This will find out which file/socket is open under this file descriptor. So if this time it hangs on "read(9,", you should find fd 9. If it is file, the symlink will point to the file's original location.

Re: command working fine after machine reboot, but it (the command) is hang couple days later.

Anh-Thu Tran — Fri, 21 Jul 2006 11:00:53 GMT

The command hang again this moring, but I could not anything /proc/PID/fd. Actually, there is no PID under /proc directory. Our machine is Redhat ES3.

Re: command working fine after machine reboot, but it (the command) is hang couple days later.

Stuart Browne — Sun, 23 Jul 2006 18:12:29 GMT

Err he meant the PID of the running process, i.e. /proc/3872/fd (but replace 3872 with the pid of the process you're stracing)