Technical article 100029

The AFPS server is not starting, how can I troubleshoot this problem?

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6

Written · Last revised

Problem

The AFPS server is not starting.  What steps can I take to
troubleshoot the problem?

Solution

To troubleshoot the problem it is best to break the problem into steps:

(1) Determine the status of the server.

(2) Determine whether it is a network problem or an AFPS problem.

(3) Determine whether it is an external influence or a server problem.

*******************************************************************************

(1) Determine the status of the server:

Start the AFPS server with the command "/etc/asusrv start".

Next, run the command "ps -ef | grep lmx" and check for the existence of the
AFPS server's "lmx." processes:
lmx.ctrl
lmx.srv -s 1
lmx.dmn
lmx.browser

If these processes are all present, then the AFPS server is actually running. If they are not present, then the AFPS server did not start; go to (2).

(2) Determine whether it is a network problem or an AFPS problem:

The most common reason for the AFPS server not starting is that the underlying network protocols are not running. The first thing to do is make sure the appropriate processes are running for your chosen network protocol.

For NetBEUI:
Run "ps -ef | grep link" and check for the following processes:
dllink [network device]
nbelink

If they are not all present then NetBEUI is not running.

For NetBios:
Run "ps -ef | grep nbd" and check for the following process:
/etc/nbd

If it is not present then NetBios is not running.

If your protocols are fine, then go to step (3).

If it is a network protocol problem, then the next step is to check the status of your network protocols:

For NetBios:

Run "nbstatus -d /dev/nbcots" and check for the appropriate sessions, make sure packets are being sent and received, and so on.

You should also check the /etc/default/nbconf file and make sure the HOST, ADDR, and BROADCAST entries are correct for your system. The following are examples of possible /etc/default/nbconf entries:

NB_HOST=FLIGHT
NB_ADDR=132.110.121.200
NB_BROADCAST=132.110.121.255

From the Windows 95 client, you can also run the following commands to see if it is a name NetBios issue or a name server issue:

nbtstat -A [afps ip address]  (if fails, then NetBios issue)
nbtstat -a [AFPS server name]  (if fails, then name server issue)
For NetBEUI:

Run "nbstatus" and check for the appropriate sessions, make sure packets are being sent and received, and so on.

(3) Determine whether it is an external influence or a server problem:

When the AFPS server starts, it broadcasts its name to the network so other machines will know of its existence. If another machine on the network has the same name, then AFPS will not start.

The best way to determine if there is an outside influence is to simply temporarily disconnect the AFPS machine from the network and then try starting the AFPS server again. If it starts up correctly, then there is probably another machine on the network with the same name and the name conflict must be resolved.

If the AFPS server still does not start, then it is a local problem and you should go through the following steps:

(a) Check for licensing issues:

The AFPS server will not start if the policy manager has died.

Run the command "ps -ef | grep ifor" and check for the following
processes:
/etc/ifor_pmd (2 processes)
/etc/ifor_sld

If they are not all present then the policy manager is not running; try rebooting the system and check streams resources with "netstat -m".

(b) Check /etc/asusrv error messages:

Run /etc/asusrv to try to start the AFPS server; make note of the error number and run the command "net helpmsg [number]" to get the full error message.

(c) Check error log (elfread)

There is a log of all AFPS errors that can be read with the following commands:

cd /usr/net/servers/lanman/bin
elfread -d system | more

This will print a list of the error messages that were generated when AFPS was started. Make sure to check the time stamps for the relevant messages.

See also

nbstatus(AS), elfread(AS), netstat(TC)

From the Xinuos technical article database, record 100029. Reproduced with permission. The original is at www.sco.com/ta/100029, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.