Sidebar: Debugging

Some errors that I encountered during the debug process included:

CALLER SCRIPT FAILED

I saw a lot of this while I was debugging my chat script in the /etc/uucp/Systems file. For further information on writing and testing chat scripts see Sun Microsystems Solaris 2.4 System Administration Manual:TCP/IP and PPPManual.

PPP_ERROR_IND Maximum number of configure requests
exceeded

After careful inspection, I noticed that I left out the "ipcp_async_map 0" in the server /etc/asppp.cf. This error causes the server to send packets with characters unescaped. The client system, though, was configured (properly) to expect escaped control characters. The resulting communication mismatch kept the two ends from resolving the negotiations and to reject the packets.

{BAD FCS} NB (A) {Unrecognized protocol: /
.......a bunch of hex numbers......}

This was a tricky one because the error message suggests the problem is something more subtle than it really is.

The problem was a simple chat script error. Because of this error, the PPP daemon can not recognize the stream of incoming data and then finally times out. By sheer timing accident, the tip and cu tests run successfully, but as soon as the PPP daemons are started up, this error appears in the asppp.log file. After following every keystroke of the aforementioned test, I found that there was a space after the login prompt and that it started with a capital "L." I removed the space and modified the /etc/uucp/Systems file to search for ogin instead of login.