Appendix C : Microservice trouble shooting

SOAP Log File Location

The path to the main log file can be configured in the listeners config.xml file. This log file is used by both the listener and soap server. Information and recoverable errors are logged here. Lowlevel Errors generated by the listener will be logged to a file called error.log in the current working directory of the listener. Lowlevel errors generated by the soap server will be logged apache/php error log.

Common Errors

• Listeners receive messages from Fedora and send the correct workflow to Taverna but the services don't seem to get called
  • make sure the apache user can write to your listener.log file as configured in the listeners config.xml. This file is written to by both the listener and the services. The services will be running as the apache user.
• Occasional and seemingly random failures of the services
  • If you have a workflow that creates or updates multiple data streams in one object you can get conflicts where two services are trying to update the same object at the same time. You can enable looping to tell Taverna to try this service again or you can design your workflow so that services run after other services are complete.

Tips

• is the listener running?

  • ps -ef | grep php If the listeners are running you should see something like

  microservices   11662 13395  2 15:48 ?        00:00:00 /usr/bin/php connect.php
  microservices   11666 13395  3 15:48 ?        00:00:00 /usr/bin/php connect.php
  microservices   11688 11614  0 15:48 pts/0    00:00:00 grep php
  microservices   13395     1  0 Sep11 ?        00:00:01 php listener.php
  

< previous page