Re: informix hang when nfs server is down
In article <CFzw4n.D9F@wetware.com>, cse@wetware.com (Scott Ellard) writes: > In article <CFz67D.19Hq@austin.ibm.com> bruce@austin.ibm.com (Bruce Bramhall) writes: > > > >I am running SE 5.0 on an IBM RS/6000 AIX 3.2 (call it dbmach). There is a > >user on the same system who nfs mounts a directory onto his home directory > >on dbmach (/u/johndoe). We'll call the other machine he is mounting > >from johnsmach. Informix is installed in /usr/informix and the database is > >in /usr/informix/db/mydb.dbs. > > > >The problem is when johnsmach goes down for some reason I cannot run Informix. > >If I start ISQL with isql I get the menus ok, but when I do "DATABASE" "SELECT" > >"mydb" I get the normal "Running...", then a long pause then what seems to > >be an AIX message "NFS server johnsmach not responding". The only way to > >get Informix to run is to either 1) wait for johnsmach to come back or 2) > >kill the informix processes, unmount /u/johndoe and start informix again. > >Why does informix even care about /u/johndoe? I ran a trace and found > >informix (sqlexec I think) looking though all of the /u directories along > >with many more unrelated directories. Does anyone know how to fix this > >or know of a work around? > > > If directories from NFS mounted filesystems are in $PATH and/or $DBPATH, > you will see hangs if the machines providing those filessystems are down. > > Scott There are NFS mounted filesystems in my $PATH but /u/johndoe is not one of them. There are no NFS mounted filesystems in my $DBPATH. This is a trace while I performed the mention commands. Some irrelevant lines have been removed. This is not a trace when the NFS server was hung, but one in which informix started ok. The directories /u/sam, /u/johndoe, and /u/jane are not in any of my PATH variables or any of my environment variables. So why is informix being so nosey. Why is it looking in directories not related to it. Trace Data ... 107 2.773958400* lookuppn: /usr/informix/db/mydb.dbs 107 2.774592768* lookuppn: / --------------------------- 107 2.774940416* lookuppn: ./ what is informix 107 2.775133696* lookuppn: ./../ looking for between 107 2.775620352* lookuppn: ./../ the dashed lines??? 107 2.775929344* lookuppn: ./../. 107 2.777203200* lookuppn: ./../.. 107 2.777481472* lookuppn: ./../lost+found 107 2.777770496* lookuppn: ./../guest 107 2.778070528* lookuppn: ./../bruce 107 2.778476800* lookuppn: ./../../ 107 2.778772992* lookuppn: ./../../ 107 2.779117312* lookuppn: ./../../. 107 2.780204800* lookuppn: ./../../.. 107 2.780482048* lookuppn: ./../../lost+found 107 2.780804864* lookuppn: ./../../usr 107 2.781145600* lookuppn: ./../../tmp 107 2.781477632* lookuppn: ./../../home 107 2.781919232* lookuppn: /usr/informix/db/ 107 2.782335744* lookuppn: / 107 2.782476544* lookuppn: ./ 107 2.782656256* lookuppn: ./../ 107 2.782882048* lookuppn: ./../ 107 2.783346432* lookuppn: ./../. 107 2.784395008* lookuppn: ./../.. 107 2.784667392* lookuppn: ./../lost+found 107 2.784950016* lookuppn: ./../guest 107 2.785246208* lookuppn: ./../bruce 107 2.785540864* lookuppn: ./../john 107 2.785817088* lookuppn: ./../pete 107 2.786098944* lookuppn: ./../bob 107 2.786379008* lookuppn: ./../sally 107 2.787269888* lookuppn: ./../bin 107 2.790910208* lookuppn: ./../jim 107 2.791926272* lookuppn: ./../../ 107 2.791926272* lookuppn: ./../../ 107 2.792893184* lookuppn: ./../../ 107 2.793440512* lookuppn: ./../../. 107 2.794564096* lookuppn: ./../../.. 107 2.794840576* lookuppn: ./../../lost+found 107 2.795175680* lookuppn: ./../../usr 107 2.795526144* lookuppn: ./../../tmp 107 2.795860480* lookuppn: ./../../home 107 2.796318976* lookuppn: /home/bruce ... 107 2.796854528* lookuppn: /u/sam #NFS mounted filesystem 107 2.799598592* lookuppn: /u/johndoe #NFS mounted filesystem 107 2.803324672* lookuppn: /u/jane #NFS mounted filesystem 107 2.806816256* lookuppn: /u/bin #NFS mounted filesystem ... ----------------------------- 107 2.886368768* lookuppn: mydb.dbs/systables.idx ... Bruce Bramhall The Kernel Group, Incorporated email: bruce@tkg.com These are my opinions and not those of IBM or The Kernel Group.