My Favorites

Close

Please to see your favorites.

  • Bookmark
  • Email Document
  • Printer Friendly
  • Favorite
  • Rating:

All appliance builds fail with "An internal build error occurred."

This document (7018251) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Studio Onsite 1.3

Situation

Building appliances worked fine just a day before, but now attempting to build any appliance from any version of the OS fails.  The following message is displayed on the web user interface for the build result:

An internal build error occurred.

Clicking on the build log to the right brings up the logs but they are empty.

/srv/studio/runner/log/production.log shows the following:

2016-11-07 17:07:43 #4817 [INFO]: Starting job a123-0.0.5-oem-x86_64 simple for image 724
2016-11-07 17:07:43 #4817 [INFO]: 10:07:43.068984 PID 04817: Waiting for lock KiwiJob-get_containment_id...
2016-11-07 17:07:43 #4817 [INFO]: 10:07:43.069126 PID 04817: Acquired lock tmp/lock/KiwiJob-get_containment_id
2016-11-07 17:07:43 #4817 [INFO]: IDs used: 16 8 2 7 18 9 0 12 17 1 14 10 11 6 5 13 4 15 19 3
2016-11-07 17:07:43 #4817 [INFO]: 10:07:43.069568 PID 04817: Released lock KiwiJob-get_containment_id
2016-11-07 17:07:43 #4817 [ERROR]: Error starting job a123-0.0.5-oem-x86_64 simple for image 724
2016-11-07 17:07:43 #4817 [ERROR]: No containment id available!, Please try again later


Resolution

Go to the directory /srv/studio/runner/tmp/kiwi_pids/

If the system thinks that any builds are in process there will be a *.yml file that matches the "pid" of the process.  If no builds are currently happening then these files can be safely removed (or moved to another location if preferred).

After removing the files try to build again and it should work correctly.

Cause

There is a hard limit of 20 simultaneous build ID's that can be processing at any given time.  The files created in /srv/studio/runner/tmp/kiwi_pids/ identify the active builds.  If something unexpectedly terminates a build, such as a server reboot or manual termination of a build, then these files can be left behind.  Once all 20 build ID's have the appearance of being in use then no new builds can be launched.  Removing the files clears up the problem.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7018251
  • Creation Date:07-NOV-16
  • Modified Date:07-NOV-16
    • SUSESUSE Studio
< Back to Support Search

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center