|
Bugzilla – Full Text Bug Listing |
| Summary: | PC Rendered Totally Unassailable and Useless after Loading SAMBA,NFS, NIS Services | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.3 | Reporter: | Scott Couston <scott> |
| Component: | YaST2 | Assignee: | E-mail List <bnc-team-screening> |
| Status: | VERIFIED INVALID | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | jsrain, scott |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 11.4 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Scott Couston
2011-11-06 03:13:55 UTC
Sorry for the delay - I have been away on holidays I logged in as root from a console session at the GUI part user login (non automated) and loaded yast text based interface. I shut down all Network Servers that I had configured,,,SAMBA, NFS client.Server...etc. I rebooted the PC and the GUI interface and PC runs perfectly. Apart from the Yast logs I can send you can you tell me the name/location of the login script by return. Please advise specific logs required to fault report as well as the file containing the login script and results Bug Renamed and Reclassified - This is a compound bug bought on my adding SAMBA, NFS, NIS Services. The actual reason will only be evident in the logs. The latest change to NFS Services shut-down of X_64 PC cause every PC to hang and not complete the shut down script as it hangs on shutting down NFS Services. Again the logs will provide the necessary info. Please specifically request the logs you need, plus the login script and its audit file plus the shut-down script and its audit file Jiri I have set needinfo so you can tell me specifically what logs are needed Scott, I think that you are asking the wrong audience. It looks to me that it is not YaST what's wrong, but some of the services (most likely NFS server) itself. The reason may be that it is configured improperly by YaST, then we'd need to know what is the exact mistake. I suggest to identify which service is the problematic one - by selective enabling. I'd bet on NFS from your initial description. The information about the reason of the time-out may be found in the system log (/var/log/messages). You may try to find out what the problem is there and check if the problem may be in the configuration. I suggest to reassign to different component after you identify the service, unless you find a specific misconfiguration. Thanks Jiri I cannot easily identify what component has the problem but I also think its NFS. I only use NON NFS4 and I dont know whats been changed in the Kernel, but the login script and logout script falter, freeze or delay's further execution (up to 3 minutes) if the nfs Client cant find its NFS Server...I have to turn my file server on just so my PC loads in less than 6 minutes....I have another outstanding bug that seems to be have all the info which I am about to assign to Kernel. I am happy to close this bug until we can fix the huge bug issues with NFS. If I can then repeat the problems in this bug I'll reopen it with more clarity. I believe NFS NON V4 has more problems in it that I car to document...Happy Holidays :-) Closed with reason code of invalid as there is not a reason code 'Place on Hold' |