On Wed, Mar 27, 2013 at 3:29 PM, G Jones <[email protected]> wrote: > Hi,
Hello > We're experiencing some intermittent failures where it appears the > FPGA is spontaneously deprogramming on the ROACH II. We'd like to try > to track this down by turning on logging in tcpborphserver3. Has > anyone done this for a network mounted ROACH II? Should we mount an > extra directory as r+w to store the logs? Looking for advice on best > practices or at least something that works. As per other mails: Remote syslog for kernel level messages. To log katcp messages: - Check out github.com/ska-sa/katcp_devel/ - Remove/comment out KATCP_STRICT_CONFORMANCE in Makefile.inc - Compile on your logging server, not the roach. - use the utility log/kcplog to connect to a remote roach and save katcp log messages to local file. kcplog understands SIGHUP and thus can be used under logrotate, while SIGUSR? can be used to de/increase the log verbosity. use ./kcplog -h for more information. You can also monitor individual hardware sensors with commands like this (echo "?sensor-sampling raw.voltage.3v3 event" ; cat ) | nc roach_host 7147 regards marc
