filePro 5.8 bombing

[Jean-Pierre Radley]

Kenneth Brody via Filepro-list averred (on Sat, Dec 26, 2015 at
06:05:29PM -0500):

| On 12/26/2015 5:16 PM, Jean-Pierre Radley via Filepro-list wrote:
|
| >After the fire I had in May, jpr.com was created as a virtual machine
| >on a VMware host in the facilities of Paul McNary in Missouri.
| >
| >I now have a new server (SuperMicro 5028D-TN4T) running OpenServer
| >6.0.0 Definitive.  All is fine except filePro.  I have no problems
| >running version 4.5 of filePro, but not the current 5.8.  If I hit
| >'p', or directly call 'runmenu' or 'dclerk', I immediately get a
| >blank screen with a blinking cursor in the upper left corner.  I
| >cannot get out of that screen, no key does anything.  I have to kill
| >the session from another login.
| >
| >I had rsync'd fP 5.8 from the Missouri machine; now I thought a
| >reinstall from scratch might be in order.  But that craps out in the
| >same way when the first binary (not shell script) is called: blank
| >screen, can't delete or escape back to a shell prompt.
|
| Is it possible that you have PFLMHOST pointed to your old IP address,
| and it's sitting there waiting until the socket connection times out?

I came back to one session where I was installing afresh; it had the
blank screen which I had NOT killed since my root message; the 'finish'
procedure had not finished, nevertheless fP 5.8 did get installed. :-)

I don't see any file where PFLMHOST is set.  Should I put my current IP
(or localhost) in /appl/fp/lib/config?

| Are you running with or without the license manager?

I have a licfp.dat in /appl/fp/lib. Still the blank screen.

| If without, perhaps "something" happened to either the semaphores
| and/or shared memory segment used by filePro, and it now locks up
| connecting to it?  (You can use "ipcs -m" and "ipcs -s", as I recall,
| to check the status. Try removing them via "ipcrm" anything owned by
| user "filepro" and see what happens then.)

Tried that, no difference.

| If with, can you turn up the fplmserver logging to "debug", and
| restart it, to see what's happening on the lm side of things?

Remind me how to run startfplmserver to include debugging?

-- 
JP