Running guide in a directory with this:

# nohup guide -na -ns -Z8 2>&1​ &

...and it's terminating like this:

[1]+ Segmentation fault (core dumped) nohup guide -na -ns -Z8 . 2>&1

If I select all of the files and run guide individually on them, I don't see any failures.  Is there any way to track down which file is causing the segfault?

------------------------------
Kevin King
President
Precision Solutions, Inc.
Longmont CO US
------------------------------

Kevin,

It could be related to volume rather than an individual file. I suggest checking 'ulimit' and making sure the settings are set to 'unlimited' and if the issue persists then tracing the process is possible but could take a while:

strace -f -p PID  1> strace.out 2>strace.err

where the PID is the PID of the guide process and the last lines output should give a pointer/ On AIX the command is 'truss' and on HP-UX it it 'tusc'.  Optionally you could use the PID of the parent shell process before guide is launched as the -f flag traces child processes. 

Hopefully using a current version of UniData?

Regards

JJ

------------------------------
John Jenkins
Thame, Oxfordshire
------------------------------

---

Kevin,

It could be related to volume rather than an individual file. I suggest checking 'ulimit' and making sure the settings are set to 'unlimited' and if the issue persists then tracing the process is possible but could take a while:

strace -f -p PID  1> strace.out 2>strace.err

where the PID is the PID of the guide process and the last lines output should give a pointer/ On AIX the command is 'truss' and on HP-UX it it 'tusc'.  Optionally you could use the PID of the parent shell process before guide is launched as the -f flag traces child processes. 

Hopefully using a current version of UniData?

Regards

JJ

------------------------------
John Jenkins
Thame, Oxfordshire
------------------------------

ulimit reports 'unlimited'.  Unidata version reported by VERSION is 8.2.1 hf11.  Not bleeding edge, but not ancient either.  I'll try the strace when I have a little more time; been working on this all day and I need some rest.

------------------------------
Kevin King
President
Precision Solutions, Inc.
Longmont CO US
------------------------------

---

Kevin,

It could be related to volume rather than an individual file. I suggest checking 'ulimit' and making sure the settings are set to 'unlimited' and if the issue persists then tracing the process is possible but could take a while:

strace -f -p PID  1> strace.out 2>strace.err

where the PID is the PID of the guide process and the last lines output should give a pointer/ On AIX the command is 'truss' and on HP-UX it it 'tusc'.  Optionally you could use the PID of the parent shell process before guide is launched as the -f flag traces child processes. 

Hopefully using a current version of UniData?

Regards

JJ

------------------------------
John Jenkins
Thame, Oxfordshire
------------------------------

John, you blessed, fantastic wizard!  Strace showed it stumbled on an old rsztemp file.  Removed it and guide is running to completion in that directory.

------------------------------
Kevin King
President
Precision Solutions, Inc.
Longmont CO US
------------------------------

---

John, you blessed, fantastic wizard!  Strace showed it stumbled on an old rsztemp file.  Removed it and guide is running to completion in that directory.

------------------------------
Kevin King
President
Precision Solutions, Inc.
Longmont CO US
------------------------------

Kevin,

Glad it worked - you should open a ticket with Rocket on this as guide should have reported an error for the specific file and moved on - not bombed out completely.

Regards

JJ.

------------------------------
John Jenkins
Thame, Oxfordshire
------------------------------

---