How to Obtain Debugging Information for Chat Scripts

Use the following procedure for obtaining debugging information from chat and suggestions for clearing common problems. For more information, refer to Common Chat Script Problems.

1. Become superuser on the dial-out machine or assume an equivalent role.

   Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services. To configure a role with the Primary Administrator profile, see Chapter 2, Working With the Solaris Management Console (Tasks), in System Administration Guide: Basic Administration.

2. Edit the /etc/ppp/peers/peer-name file for the peer to be called.

3. Add -v as an argument to the chat command that is specified in connect option.

   connect "/usr/bin/chat -v -f /etc/ppp/chat-script-name"

4. View chat script errors in the file /etc/ppp/connect-errors.

   The following is the main error that occurs with chat.

   Oct 31 08:57:13 deino chat[107294]: [ID 702911 local2.info] expect (CONNECT) Oct 31 08:57:58 deino chat[107294]: [ID 702911 local2.info] alarm Oct 31 08:57:58 deino chat[107294]: [ID 702911 local2.info] Failed

   The example shows timeout while waiting for a (CONNECT)string. When chat fails, you get the following message from pppd:

   Connect script failed