Quick links to this page: 

• Powering The Unit
• Connecting The Appliance Through the Serial Port
• Connecting The Appliance Through Ethernet
• NFS
• SSH
• make
• Run From Flash
• Asterisk
• Warploader
• Call Progress
• Logging
• Logging to Persistent

Powering the Unit

Symptom	LCD Display is blank or displays 'Please wait ... Loading'  for a very long time when applying power to the unit
Cause	The software image that is running is invalid.
Action	You will need to download a new image, follow instructions from (Com port).

 

Symptom	When I power the Appliance, the LED is RED.
Cause	The Appliance is running "HOT"!
Action	Turn it off, right away. Verify that the fan is working properly. Report the problem to PIKA mailto:support@pikatech.com.

 

Connecting Appliance through The Serial Port

Symptom	When plugging the serial cable into the Appliance, the Appliance does not respond from the host's serial port application (mincom).
Cause(1)	Serial port settings are not set properly
Action(1)	Refer to to the section 'Development System Setup and Configuration > Configuring Serial Access' in the 'PIKA Warp PADS User Manual' to set them properly
Cause(2)	Defective Serial cable.
Action(2)	Disconnect the serial cable from Appliance. Loopback pin 2/3 and pin 7/8.  Try to type with the serial application.

Connecting Appliance through Ethernet 

Symptom	Can't login remotely using ssh
Initial Testing	Try to ping to the Appliance, if it fails then it could be one of the following causes.
Cause(1)	The Appliance's IP address is not setup properly
Action(1)	Use the Serial port to set the IP address
Cause(2)	The Appliance's Gateway addess is not set properly
Action(2)	Use the Serial port to set the Gateway address

NFS

Symptom	cuImage.warp does not load from host's tftp-server You might see the following message : TFTP from server 192.168.1.1; our IP address is 192.168.1.2 Filename 'cuImage.warp'. Load address: 0x200000 Loading: ###T #T ##T T ##T #######T #######T ########T ###T #########T ### Retry count exceeded; starting again
Cause(1)	tftp-server is not setup properly
Action(1)	Verify that if you are using the xinet for tftp, the /etc/xinet.d/tftp file is configured properly.
Cause(2)	tftp-server is not accessible
Action(2)	Verify that the tftp-server on the host can actually be accessible locally through tftp-client.  Verify that the Security-Enhanced-Linux on the host is disabled (SELinux).  Verify that the Firewall on the host is disabled.
Cause(3)	Appliance settings are not setup properly
Action(3)	Verify that that the environment variables of the Appliance are configured properly.

Symptom	NFS error -5
Cause	Indicates that the nfsd service is not started on your development computer.
Action	Check that the service is running and configured to start when your development computer is booted.

Symptom	NFS error -13
Cause	Indicates that your NFS path cannot be found.
Action	Check that the path in /etc/exports matches the rootpath environment variable in U-Boot and that the path specified contains a valid mount point. If you changed any information in /etc/exports, run "exportfs -a" on your development computer.

Symptom	When attempting to start the NFS service, the following error appears: Starting NFS quotas: Cannot register service: RPC: Unable to receive; errno = Connection refused
Cause	Check if the portmap service is running: #ps ax | grep portmap
Action	If not, start the portmap service using the appropriate command for your Linux distribution (e.g. "service portmap start"). Ensure that it is configured to start when the system is booted.

SSH

Symptom	The message "dbclient: exited: string too long" when passing an RSA key file to the SSH client
Cause	dbclient, included with the dropbear package indicates that the authentication keys used are not compatible with dropbear. Dropbear is a subset of the full SSH functionality. When the SSH client on the appliance is used to access another system running a fully featured SSH server, the private authentication keys supplied by the server require a conversion step to be compatible with dropbear.
Action	Execute the following command on the appliance:  #dropbearconvert openssh dropbear /path/to/keyFile ~/.ssh/id_rsa.db

Symptom	The dropbear daemon starts without complaining. If I try to login with ssh from an other computer, authentication (password) works, but then dropbear hangs and spits out this error:  failed to open any /dev/pty?? devices no pty was allocated, couldn't execute
Cause	Something was modified in the busybox package
Action	On the Warp applicance: #mkdir /dev/pts #mount -t devpts /dev/pts /dev/pts

make

Symptom	'make image' fails with the following error: genext2fs -U \ -d build_warp/root \ -b 130000 \ -i 2048 images/rootfs.img genext2fs: invalid option -- U make: *** [image] Error 1
Cause	This may occur if you have more than one version of genext2fs on your development computer. The version in /bin should be used.
Action	The following entries in the top level Makefile may need to be adjusted if any of the directories listed in PATH contain the executable genext2fs. PATH:= /usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin PATH:= $(PATH):$(TOOLS_BIN)

 

Symptom	make Fails with the following error: /warp_appliance/dl/skeleton-1.0.0-16.tgz -C /warp_appliance/build_warp/root tar: ./dev/ptyp7: Cannot mknod: Operation not permitted tar: ./dev/mtd14: Cannot mknod: Operation not permitted tar: ./dev/ptyp2: Cannot mknod: Operation not permitted tar: ./dev/ttyp5: Cannot mknod: Operation not permitted tar: ./dev/mtdblock14: Cannot mknod: Operation not permitted ... br> ... ... ... tar: Error exit delayed from previous errors make: *** [/warp_appliance/build_warp/root/.unpacked] Error 2
Cause	mknod can only be run by root user
Action	Recompile as root user

 

Symptom	make fails with the following error: > make image > genext2fs -U \ > -d build_warp/root \ > -b 130000 \ > -i 2048 \ > images/rootfs.img > number of inodes too low, increasing to 2680 > genext2fs: group descr 16. free blocks count == 0 (corrupted fs?) > make: *** [image] Error 1
Cause	This is most-likely due to the fact that the image is getting too big for the parameters that are passed to the genext2fs executable.
Action	There are 2 alternatives: 1) increase the -b <block size> parameter, so that the image can fit on the file system (eg 1320000).  This is a good alternative if the image marginally increases. 2) Move some of the files to other persistent storage locations.  The instructions on how to achieve this can be found in How-To : Use the other persistent storage partitions.

Symptom	Applications are installed in wrong location on Warp
Cause	If you see that your application is being installed in the wrong location on the appliance while building a package check whether you have DESTDIR variable set. Some applications use both DESTDIR and --prefix values when setting install locations. So if you set your --prefix=$(TARGET_DIR)/usr during the configure but see that your application is being installed to $(TARGET_DIR)/$(TARGET_DIR)/usr then a previous package probably exported DESTDIR:=$(TARGET_DIR) .
Action	In order to protect against this you can use the following at the top of the .mk file of packages that use DESTDIR. ifeq ($(DESTDIR), "") CONFIGURE_OPTS+=--prefix=$(TARGET_DIR)/usr else CONFIGURE_OPTS+=--prefix=/usr endif

Symptom	Make shows error about Makefile being created in the future
Cause	If you are running gcc on the appliance to create natively compiled applications you may sometimes see errors about * make[2]: Warning: File 'filename' has modification time ##s in the future * make[2]: warning: Clock skew detected. Your build may be incomplete.
Action	This will happen if you are running from an NFS mount and the time on your PC is ahead of the time on your appliance. In order to get rid of these errors sync the time of the PC and appliance.

 

Symptom	/usr/lib/libpikagpapi.so: could not read symbols: File in wrong format
Cause	Incompatibility with library file format.  For example, x86 compiled libraries are being pointed to instead of power pc compiled libraries.
Action	Make sure the you are pointing to the correct library.

Run from Flash

 

Symptom	After loading a new image with warploader, the console displays the following: ## Loading RAMDisk Image at 02200000 ... Image Name: PIKA Warp 1.0.0-222 Image Type: PowerPC Linux RAMDisk Image (gzip compressed) Data Size: 44368879 Bytes = 42.3 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... Bad Data CRC
Cause	Uncompression size is most-likely too small
Action	Connect to COM port using your favourite Com utility program a. Reboot (power off/on) b. Hit any key to stop autoboot c. = = > setenv load_nand_ramdisk nand read.jffs2 2200000 200000 2600000 d. = = > saveenv e. Reboot where 2600000 is the new size in Hexadecimal.

Asterisk

Symptom	SIP phone does not register to Asterisk Warp. The file /var/log/asterisk contains the following line  00:03:41] WARNING[236] chan_sip.c: Unable to get own IP address, SIP disabled
Cause	Asterisk cannot resolve the IP address
Action	Replace the entry of file /etc/HOSTNAME with the IP address of the unit.

Symptom	SIP phones between to Asterisk proxies terminate call prematurely. Reviewing the SIP messages outlines a 491 Request Pending SIP message
Cause	Re-invites are allowed from both Asterisk proxies.
Action	For each SIP user in sip.conf, add: canreinvite=no

 

 

Symptom	Updating pika.conf does not seem to take effect when the "reload" command is issued in Asterisk.
Cause	This is a defect that will be fixed in the next release.
Action	A workaround it to stop and restart asterisk.  Ultimately rebooting the Appliance will also remedy the problem.

Symptom	Multilog: warning: unable to write to /var/log/asterisk/current, pausing: out of disk space
Cause(1)	Typically the cause of this is that Asterisk is failing to start properly. Open the /var/log/asterisk/current file to determine the reason. This error will eventually fill up RAM because Asterisk tries to re-start every second.
Cause(2)	If daemontools is disabled, then check that if an autorun script is failing.

Warploader

Symptom	Error: /tmp # warploader -p persistent image.jffs2 That paritition is currently mounted. Please `umount /dev/mtdblock6' /tmp # umount /dev/mtdblock6 umount: cannot umount /persistent: Device or resource busy
Cause	An application is using that particular partition.
Action	Kill any application currently using the persistent partition. This is typically the httpd webserver. ('ps'/'kill')

Call Progress

Symptom	The PIKA Warp is connected to a third party PBX FXO and the Caller ID is not detected from the expected FSK_BELLCORE signal.
Cause	The PIKA Warp starts decoding after the 2nd ring instead of the expected 1st ring.
Action	In pikagp_aoh.cfg, set the ringcount >1 for the [TRUNK_xxxx], for example:  [TRUNK_xxxx] ringcount=2

 

Logging

Changing configuration parameters related to PIKA logging and debugging at run-time can alter the location of PIKA log files. For example, turning on the PIKA Channel Driver logs and restarting Asterisk will cause PIKA logs to be directed to /var/log/pika instead of syslog. When the system is rebooted, the logs will once again be directed to syslog. If you change any configuration information for PIKA software that affects log generation (e.g. turning on debugging flags), be aware that logs may subsequently be generated to /var/log/pika.

Symptom	No aoh logs written
Cause	/var/log might be full
Action	df to check if there is enough memory available in ram.

 Logging to Persistent

 

Symptom	Logs are wrapping around
Cause	Logs have reached their maximim size.
Action	Log to persistent storage

 Pika Logs

These changes will provide a more detailed cyclical log to help debugging the Pika software.

To update the Grandprix logging, in /persistent/etc/pika/pikagp.cfg look for the header [logs], modify the file to contain

[logs]
level=debug
files=5
size=5

this will make 5 log files each 5 mb large

To update the AoH logs, in /persistent/etc/pika/pikagp_aoh.cfg again look for the header [logs] and modify the file to contain

[logs]
level=debug
api=0xffffcffb ; disable api message from the queue, play and record
object.mediastream=0x3 ; disable all mediastream logging other than errors or warnings
files=5
size=5

In /persistent/etc/localenv change

export PKH_LOGS_DIR=SYSLOG
export PKX_LOGS_DIR=SYSLOG

to read

export PKH_LOGS_DIR=/mnt/sd/
export PKX_LOGS_DIR=/mnt/sd/