Bug 223811

Summary: zmd will not start
Product: [openSUSE] SUSE Linux 10.1 Reporter: Jim Henderson <jhenderson>
Component: ZenworksAssignee: E-mail List <zlm-code10-bugs>
Status: RESOLVED INVALID QA Contact: Forgotten User YrvzK78Vmi <forgotten_YrvzK78Vmi>
Severity: Normal    
Priority: P5 - None    
Version: Final   
Target Milestone: ---   
Hardware: i686   
OS: SuSE Linux 10.1   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Jim Henderson 2006-11-26 23:11:57 UTC 
I am unsure how long my system has been doing this, but I noticed today that the zen-updater was not running, and upon further investigation discovered that zmd refuses to start.

When I try to start zmd, I see:

[jhenderson@jshlaptop zmd]# /etc/init.d/novell-zmd start
Starting ZENworks Management Daemon                                   done
[jhenderson@jshlaptop zmd]# /etc/init.d/novell-zmd status
Checking for ZENworks Management Daemon:                              dead

The only logfile created is /var/log/zmd-messages.log.  It contains the following information:

** (/usr/lib/zmd/zmd.exe:8394): WARNING **: thread_attach: error creating thread handle

** (/usr/lib/zmd/zmd.exe:8394): WARNING **: thread_attach: error creating thread handle

** (/usr/lib/zmd/zmd.exe:8394): WARNING **: thread_attach: error creating thread handle

** (/usr/lib/zmd/zmd.exe:8394): WARNING **: thread_attach: error creating thread handle

** (/usr/lib/zmd/zmd.exe:8394): WARNING **: thread_attach: error creating thread handle

** (/usr/lib/zmd/zmd.exe:8394): WARNING **: thread_attach: error creating thread handle

** (/usr/lib/zmd/zmd.exe:8394): WARNING **: process_set_current: error creating process handle

** (/usr/lib/zmd/zmd.exe:8394): WARNING **: thread_attach: error creating thread handle

** ERROR **: file threads.c: line 415 (mono_thread_attach): assertion failed: (thread_handle)
aborting...

I've tried removing the zmd.db and installed-packages-stamp files, but this has not corrected the problem - it doesn't seem to get that far, as the backend isn't logging anything.
Comment 1 Jim Henderson 2006-11-29 19:36:40 UTC 
Closing this bug as a restart of the system has resulted in the issue being resolved - not sure why, but I can no longer reproduce the problem.