|
Bugzilla – Full Text Bug Listing |
| Summary: | suse_register fails to run, Checking for ZENworks Management Daemon .. dead | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Olaf Hering <ohering> |
| Component: | YaST2 | Assignee: | Martin Vidner <mvidner> |
| Status: | RESOLVED WONTFIX | QA Contact: | Stanislav Visnovsky <visnov> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | aj, jdsn, suse-beta |
| Version: | RC 3 | ||
| Target Milestone: | --- | ||
| Hardware: | PowerPC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
bug170870.tar.bz2
bug170870.tar.bz2 |
||
|
Description
Olaf Hering
2006-04-28 17:49:48 UTC
Created attachment 80880 [details] bug170870.tar.bz2 Register.ycp:297 Server response: $["exit":"7", "stderr":"Cannot start zmd: Starting ZENworks Management Daemon..done\nChecking for ZENworks Management Daemon: ..dead", "stdout":""] happens also with rc5 suse_register bug; inst_suse_register just reports the error The error was from rczmd start. The start of zmd has not worked. We had a similar problem on an other host. assign to tambet. Olaf is the host up and running? Maybe tambet wants to have logs or access. Can I get access to a system where zmd does not start? So far, there have been multiple bugs like that and I've never seen it happening anywhere. Also, the attached log files do not contain zmd-messages.log so I have absolutely no idea what's going on. I think the bug happens on systems with low memory, my ibook at home has 160mb, 300MHz. Olaf sorry :(, but do you mind testing one more time with SL 10.1 Final to see whether this is still happening. Regards. We advertize 256 MB and recomment 512 MB - but I would love to see it working even with less memory. It most likely does work, however it takes more time than the installer waits for the successful start. Even the parse-metadata alone uses over 100 mb, so there isn't much I can do on zmd side. is there a state 'zmd (or whatever) is busy starting up'? Maybe that state should be checked, and if its not ready, sleep for a few more seconds. I don't think it's worth the effort and not sure if it's possible to add a new state and keep the LSB compatibility. Anyway, Martin, please, comment. (In reply to comment #11) > It most likely does work, however it takes more time than the installer > waits for the successful start. Even the parse-metadata alone uses over 100 > mb, so there isn't much I can do on zmd side. No, in this case it is not the yast timeout but suse_register calls "/etc/init.d/novell-zmd status" and it returns 7 (dead). (Hmm, returning 7 from status is already non-LSB.) (In reply to comment #14) > I don't think it's worth the effort and not sure if it's possible to add a > new state and keep the LSB compatibility. One way would be to have rczmd status return codes < 100 and rczmd status -x return a richer set of codes in the 100-149 area (distro reserved). LSB: http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html cached copy, the above does not work right now: http://66.102.9.104/search?q=cache:d1AsXyZhhycJ:refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html+init+script+actions&hl=en&ct=clnk&cd=1&ie=UTF-8 We have only yast logs. We need also the zmd logs and /var/log/messages for suse_register. Olaf, please get all the logs if you can reproduce it. Tambet, any other info to help debug this? Olaf, do you have the logs? Created attachment 95312 [details] bug170870.tar.bz2 We will not fix this bug anymore since ZENworks has been removed for 10.3. Therefore closing as WONTFIX. |