[Spacewalk-list] osa-dispatcher and osad

[Sander Grendelman]

On Mon, Feb 28, 2011 at 11:14:04AM +0100, Baptiste AGASSE wrote:
> I've applied the patch attached at https://bugzilla.redhat.com/show_bug.cgi?id=662593, but now, sm don't start (sm dead but subsys locked)

I had the same problem ( I'm guessing that you applied the patch to
sm.xml ?).

What worked for me was removing the roster-lines from sm.xml instead of
commenting them out:

iff -ut /tmp/sm.xml jabberd/sm.xml
--- /tmp/sm.xml	2011-02-28 13:02:06.000000000 +0100
+++ jabberd/sm.xml	2011-02-16 10:39:17.000000000 +0100
@@ -365,9 +365,7 @@
       <module>validate</module>         <!-- validate packet type -->
       <module>status</module>           <!-- update status information
-->
       <module>privacy</module>          <!-- manage privacy lists -->
-      <module>roster</module>           <!-- handle roster get/sets and
       s10ns -->
       <module>vacation</module>         <!-- manage vacation settings
-->
-      <!-- <module>pep</module>         <!- - personal eventing -->
       <module>iq-vcard</module>         <!-- store and retrieve the
user's vcard -->
       <module>iq-ping</module>          <!-- return the server ping -->
       <module>iq-private</module>       <!-- manage the user's private
data store -->
@@ -428,7 +426,6 @@
          sessions as appropriate - this is usually handled by the
          "deliver" module. -->
     <chain id="pkt-user">
-      <module>roster</module>           <!-- handle s10n responses -->
       <module>presence</module>         <!-- process and distribute
incoming presence from external entities -->
       <module>iq-vcard</module>         <!-- grab user vcards -->
       <module>amp</module>              <!-- advanced message
processing -->
@@ -451,8 +448,6 @@
          before a session is created). -->
     <chain id="user-load">
       <module>active</module>           <!-- get active status -->
-      <module>roster</module>           <!-- load the roster and trust
       list -->
-      <module>roster-publish</module>   <!-- load the published roster
       -->
       <module>privacy</module>          <!-- load privacy lists -->
       <module>vacation</module>         <!-- load vacation settings -->
     </chain>
@@ -462,7 +457,6 @@
          registration request). This initialises any per-user data. -->
     <chain id="user-create">
       <module>active</module>           <!-- activate new users -->
-      <module>template-roster</module>  <!-- populate roster from
       template -->
     </chain>
 
     <!-- user-delete. The modules in this chain are called when a user
@@ -475,7 +469,6 @@
       <module>announce</module>         <!-- delete motd data -->
       <module>offline</module>          <!-- bounce queued messages -->
       <module>privacy</module>          <!-- delete privacy lists -->
-      <module>roster</module>           <!-- delete roster -->
       <module>vacation</module>         <!-- delete vacation settings
-->
       <module>status</module>           <!-- delete status information
-->
       <module>iq-last</module>          <!-- delete last logout time
-->


I also removed the pep-module that was already commented out.

So:

service osa-dispatcher stop
service jabberd stop
### remove all "roster" lines from /etc/jabberd/sm.xml> ###
service jabberd start
### Check if sm is running
service osa-dispatcher start