ifor_pmd dies on new installation of 5.0.7
- From: "Steve M. Fabac, Jr." <smfabac@xxxxxxx>
- Date: Mon, 18 Aug 2008 01:00:17 -0500
I just upgraded a client from 5.0.5 to 5.0.7 and several times
each day they get the message "ifor_pmd died" no one can login
over the network and the system has to be rebooted.
When I say upgraded, I mean installed new quad-core Xeon system,
performed a fresh install, and restored the users and application
software and data from BackupEdge backup.
The installation of 5.0.7 was to boot the 5.0.7 CD with
"defbootstr link=aacraid", install the OS, reboot, run custom
and install SMP (defer license), install MP5 and reboot.
Run custom and install supplemental graphics and network drivers to
enable auto detection of deferred network card. Run netconfig and
set up the network. Create /etc/resolv.conf to point to ISP's
DNS servers.
Install SAMBA from the 5.0.7 media kit.
Install patchck and run it to install:
INSTALLED currently on real.XXXX.com
--------------------------------------------------------------------
oss656b oss656b - OpenServer Supplement oss656b
oss667b oss667b - OpenServer Supplement oss667b
oss672a oss672a - OpenServer Supplement oss672a
oss674a oss674a - OpenServer Supplement oss674a
rs507d Maintenance Pack 5 for OSR5.0.7
j2jre131 Java 2 JRE 1.3.1_22
25-user upgrade license was installed and system tuned for the
additional users.
Stune looks like this:
NODE "real"
EVDEVS 160
EVQUEUES 152
NSPTTYS 128
NUMSP 320
NSTREAM 8192
NHINODE 1024
GPGSLO 2000
GPGSHI 6000
NSTRPAGES 6256
TTHOG 5120
NCLIST 712
NSTREVENT 8448
NUMTIM 1040
NUMTRW 1040
SECLUID 0
SECSTOPIO 1
SECCLEARID 1
SHMMAX 10485760
SHMMNI 200
SEMMAP 256
SEMMNI 384
SEMMNS 512
SEMMNU 150
SEMMSL 50
NMUXLINK 448
NBUF 300000 <- I tuned these paramaters
NHBUF 524288 <-
SDSKOUT 16 <-
TBLNK 360 <-
Everything else was default or tuned by adding the 25-user upgrade license
and the 25-user license from the old 5.0.5 system.
I searched the SCO knowledge base for ifor_pmd but all the posts are pre 5.0.7
Anyone seen the same problem on 5.0.7?
I remember a problem with startx on 5.0.6 and Bela provided this information:
On OSR506, those nodes are created by /etc/conf/node.d/Xsco (well, by `idmknod` according to instructions in that file); relating to the STREAMS pipe driver "sp".
Is that driver enabled?
# cat /etc/conf/sdevice.d/sp sp Y 0 0 0 0 0 0 0 0
If it isn't enabled, I would be worried about the rest of the STREAMS subsystem. Run `mkdev streams` and tell it to go about its business. Defer any kernel relink.
Next, is "sp" configured for 256 units? The nodes refer to minor numbers 254 & 255, i.e. the 255 & 256th units. This is so regular use of "sp" via /dev/spx can automatically allocate units 0 through (256 - 2 * (# active X servers)) without clashing with the preallocated X server nodes.
# grep NUMSP /etc/conf/cf.d/stune /etc/conf/cf.d/stune:NUMSP 256
If not, run /etc/conf/cf.d/configure, go through the Streams section, set NUMSP to 256. No more, no less.
I did not question the "No more, no less." at the time. But I see that
NUMSP on 5.0.7 is set to 320. Can this be a problem?
If you've changed anything, relink (/etc/conf/cf.d/link_unix -y) and reboot...
--
Steve Fabac
S.M. Fabac & Associates
816/765-1670
.
- Follow-Ups:
- Re: ifor_pmd dies on new installation of 5.0.7
- From: bonixsas
- Re: ifor_pmd dies on new installation of 5.0.7
- From: Stephen M. Dunn
- Re: ifor_pmd dies on new installation of 5.0.7
- Prev by Date: Re: Haven't seen this lp problem before
- Next by Date: Re: Password History
- Previous by thread: Password History
- Next by thread: Re: ifor_pmd dies on new installation of 5.0.7
- Index(es):
Relevant Pages
|