Troubleshooting

Single most important tip for troubleshooting config server components is inspect log files by searching of running tail -f command while servers are running. Unless specified, all log files go into one of these two locations

Profile Generator

Analyze the log
${JBOSS_HOME}/jboss/log/server.log - Web page error, EJB errors. Log file for 90% of configuration system operations
Change log level
edit file: ${JBOSS_HOME}/server/sipx/conf/log4j.xml and change the debug flag: param name="Threshold" value="DEBUG" or "INFO" and restart processes.
Replication to Commservers
User information is sent to services like the sipXproxy. To ensure infomation has been recieved, run this command:
      sipdbtest display credential
You should see your basic user edits in this list.
sipXregistry will not authorize my phone
Assuming you've configured the phone line correctly, it's possible the information did not get sent to appropriate sipX servers. Check log file for error in communication. Java VM needs to have correct certificate authority imported, see install-cert.sh file. Lastly, check the timestamp of the credentials.xml file to see if time is after your change.
Check for server's CA
If you've installed a Certificate Authority(CA) into java, you can check the CA by running this command.
        cd `sipx-config --jdk`
bin/keytool -list -keystore jre/lib/security/cacerts -storepass changeit | grep mykey
Start server from console
You can run Profile Generator by itself after RMI Registry is started by running
   su - SIPXPBXUSER profilegenerator.sh
where SIPXPBXUSER is the daemon sipX user account (default is 'sipx')
Resetting superadmin password
Run this command from the console, superadmin password will be blank until you reset it from the web ui.
		psql -U postgres PDS -c "update users set password='' where display_id = 'superadmin';"

Profile Publisher

Analyze the logs
sds.log for SIP and SIP stack level messages to phone devices. This log contains SIP messages so you can use the sipviewer to display graphically the SIP messages.
      syslog2siptrace < sds.log > sds-siptrace.xml
sipviewer sds-siptrace.xml
PDSMessages.log for communication of user, permission and credential datasets to other sipX servers.
Change log level
edit file: bin/profilepublisher.sh and change the debug flag: PDS_DEBUG=-Dpds.debug=true and restart processses.
Start server from console
You can run Profile Publisher by itself after RMI Registry is started by running
   su - SIPXPBXUSER profilepublisher.sh
where SIPXPBXUSER is the daemon sipX user account (default is 'sipx')

Profile Writer

Analyze the log
profilewriter.log
Change log level
edit file: bin/profilewriter.sh and change the debug flag: PDS_DEBUG=-Dpds.debug=true and restart processses
Start server from console
You can run Profile Publisher by itself after RMI Registry is started by running:
   su - SIPXPBXUSER profilewriter.sh
where SIPXPBXUSER is the daemon sipX user account (default is 'sipx')

RMI registry

Start server from console
RMI registry does not have a console, but you analyze what's getting written to stdout or stderr by running rmi from the console:
      su - SIPXPBXUSER startrmireg.sh
where SIPXPBXUSER is the daemon sipX user account (default is 'sipx'). Personally, I've never seen an error here, but it's worth noting.