Hi.

Yesterday, I installed the patches

PHSS_32928 PHSS_32864 PHNE_23289 PHNE_23288 PHKL_23316 PHKL_23315
PHKL_23314 PHKL_23313 PHKL_23312 PHKL_23311 PHKL_23310 PHKL_23309
PHKL_23308 PHKL_23307 PHKL_23306 PHKL_23305 PHKL_23304 PHKL_23303
PHKL_23302 PHKL_23301 PHKL_23300 PHKL_23299 PHKL_23298 PHKL_23297
PHKL_23296 PHKL_23295 PHKL_23294 PHKL_23293 PHKL_23292 PHKL_23291
PHKL_23290 PHCO_28160 PHCO_23340

Since then, I cannot start /usr/bin/ksh anymore. I cleared the $HOME
directory (moved it away and did a mkdir $HOME). I also
moved /etc/profile out of the way.

When I run /usr/bin/ksh with tusc (http://hpux.connect.org.uk/hppd/hpux/Sysadmin/tusc-7.7/)
and get the following output. Command I ran:

/usr/local/bin/tusc /usr/bin/ksh

open(".sh_history", O_RDWR|O_APPEND|O_CREAT, 0600) .................................................. . = 3
lseek(3, 0, SEEK_END) .................................................. .............................. = 0
close(2047) .................................................. ........................................ ERR#9 EBADF
fcntl(3, F_DUPFD, 2047) .................................................. ............................ = 2047
close(3) .................................................. ........................................... = 0
fcntl(2047, F_SETFD, 1) .................................................. ............................ = 0
sigprocmask(SIG_BLOCK, 0x7f7f1100, 0x7f7f10e0) .................................................. ..... = 0
sigprocmask(SIG_BLOCK, 0x7f7f1180, 0x7f7f1160) .................................................. ..... = 0
sigprocmask(SIG_BLOCK, 0x7f7f1200, 0x7f7f11e0) .................................................. ..... = 0
brk(0x4001b860) .................................................. .................................... = 0
sigprocmask(SIG_SETMASK, 0x7f7f11e0, NULL) .................................................. ......... = 0
sigprocmask(SIG_SETMASK, 0x7f7f1160, NULL) .................................................. ......... = 0
sigprocmask(SIG_SETMASK, 0x7f7f10e0, NULL) .................................................. ......... = 0
sigprocmask(SIG_BLOCK, 0x7f7f1140, 0x7f7f1120) .................................................. ..... = 0
sigprocmask(SIG_SETMASK, 0x7f7f1120, NULL) .................................................. ......... = 0
fcntl(2047, F_GETFL, 0) .................................................. ............................ = 10
lseek(2047, 0, SEEK_CUR) .................................................. ........................... = 0
ioctl(2047, TCGETATTR, 0x400040a8) .................................................. ................. ERR#25 ENOTTY
sigprocmask(SIG_BLOCK, 0x7f7f1140, 0x7f7f1120) .................................................. ..... = 0
sigprocmask(SIG_SETMASK, 0x7f7f1120, NULL) .................................................. ......... = 0
write(2047, "0101", 2) .................................................. ............................. = 2
fcntl(2047, F_SETLK, 0x40003868) .................................................. ................... [sleeping]

Any ideas, why it's hanging/sleeping?

Thanks a lot,

Alexander Skwar
--
The core is not frozen, but slushy.
-- Larry Wall in <199705101952.MAA00756@wall.org>

Hi Alexander
>
> Since then, I cannot start /usr/bin/ksh anymore. I cleared the $HOME
> directory (moved it away and did a mkdir $HOME). I also
> moved /etc/profile out of the way.
home directory on NFS mount or local?


If NFS try:
rm $HOME/.sh_history
ln /tmp/bla $HOME/.sh_history

If it works then ->looks like a hanging file lock.

Florian

Florian Anwander <spam.interessiert.nicht@mnet-online.de>:

> Hi Alexander
>>
>> Since then, I cannot start /usr/bin/ksh anymore. I cleared the $HOME
>> directory (moved it away and did a mkdir $HOME). I also
>> moved /etc/profile out of the way.
> home directory on NFS mount or local?

NFS

> If NFS try:
> rm $HOME/.sh_history

I did: "rm -rf $HOME /etc/profile". ksh still doesn't start.

I installed PHCO_33169, GoldApps11i and GoldBase11i from June '05 and
also all the patches, that cpm_collect.sh from ITRC has
shown. This also required a reboot of the machine.

ksh still hangs

Any further ideas?

Have a look at the last line of the tusc output:

fcntl(2047, F_SETLK, 0x40003868) .................................................. ................... [sleeping]

What's it doing there? It's calling fcntl() with F_SETLK, right?
This means, it's trying to set a lock, correct? Why is that
hanging?

Alexander Skwar
--
Even if you do learn to speak correct English, whom are you going to speak
it to?
-- Clarence Darrow

Florian Anwander wrote:
: If NFS try:
: rm $HOME/.sh_history
: ln /tmp/bla $HOME/.sh_history

How will this help? You won't be able to do a hardlink if one was NFS.
If a symlink, won't the lock still have problems? Or does it follow
the symlink to the local FS before trying to lock?

One trick is to export HISTFILE point to a local FS.

Of course I absolutely positively have to have it to work over NFS so
I make sure patches are installed and rpc.statd and rpc.lockd are working.
It's been years since I've had this problem.

Hi Marty


> Florian Anwander wrote:
> : If NFS try:
> : rm $HOME/.sh_history
> : ln /tmp/bla $HOME/.sh_history
>
> How will this help? You won't be able to do a hardlink if one was NFS.
> If a symlink, won't the lock still have problems? Or does it follow
> the symlink to the local FS before trying to lock?
Of course you are right! It should have been a symlink. And yes: first
the link is followed and then the lock is done.

Florian