<Fault 10000: 'Unknown error. Module did not load'>
Bug #342812 reported by
bernhard
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Satega |
Fix Released
|
Medium
|
bernhard | ||
Bug Description
The backend is stopped if ONE none CORE module failed to start.
The question is why?
this is to restriktive and should be changed
2009-03-14 16:16:49 ERROR DynDNS configuration file does not exist. Is inadyn installed? Config file:/etc/
2009-03-14 16:16:49 ERROR Module DynDNS did not initialize
2009-03-14 16:16:49 ERROR faultCode: 10000 faultString: Unknown error. Module did not load
Traceback (most recent call last):
| Changed in satega: | |
| importance: | Undecided → Medium |
| milestone: | none → milestone0.1 |
Revision history for this message
| bernhard (bernhardredl) wrote | #1 |
| Changed in satega: | |
| assignee: | nobody → bernhardredl |
| status: | New → Fix Released |
To post a comment you must log in.
i fixed this by creating an iditional if that checks if the module is a primary module
http://