jabberd initialization fails with "db: couldn't open environment: Resource temporarily unavailable"
This document (7015878) is provided subject to the disclaimer at the end of this document.
SUSE Manager 2.1
SUSE Manager 1.7
Nov 11 10:05:12 suma1 jabberd/sm: db: couldn't open environment: Resource temporarily unavailable
Nov 11 10:05:12 suma1 jabberd/sm: initialisation of storage driver 'db' failed
Nov 11 10:05:12 suma1 jabberd/sm: failed to initialise one or more storage drivers, aborting
Nov 11 10:05:14 suma1 jabberd/c2s: db: couldn't open environment: Resource temporarily unavailable
Nov 11 10:05:14 suma1 jabberd/c2s: failed to initialize auth module 'db'
rcosa-dispatcher stopAfter removing the database, jabberd should start without issue.
SUSE has seen reports where customers ran a cronjob with the above commands frequently.
If the db already is deleted (file is created with 0 bytes) and OSAD/Jabberd misbehave, run:
/usr/share/spacewalk/setup/jabberd/create_sqlite3_databaseto recreate the database with the correct content, then restart osad-dispatcher and jabberd.
This Support Knowledgebase provides a valuable tool for 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:7015878
- Creation Date: 11-Nov-2014
- Modified Date:03-Mar-2020
- SUSE Manager
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com