|
Bugzilla – Full Text Bug Listing |
| Summary: | yast2 firewall not starting | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Andreas Jaeger <aj> |
| Component: | Installation | Assignee: | Lukas Ocilka <locilka> |
| Status: | RESOLVED INVALID | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Blocker | ||
| Priority: | P5 - None | CC: | asklein, diehl, ihno, michael.raskey, ro, werner |
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | yast2 log files | ||
|
Description
Andreas Jaeger
2006-01-18 12:43:58 UTC
Created attachment 63808 [details]
yast2 log files
This might be the same problem as described in #135595, comment 59. Note this worked now for me - but now the internet test failed. HOpe you can reproduce either of this once beta1 is out. Andreas, I've installed Beta1 just now and the problem was that it the Firewall::Write() was unable to enable `insserv SuSEfirewall2_init` but the Firewall was started. It says: "boot.localfs has to be enabled for service SuSEfirewall2_init" Note, that this behavior is with NetworkManager, I'll try the same without. I'll check it against your YaST logs, but if you have any additional installation information (behavior description), please, try to write them down. boot.localfs is enabled at that point of time. I checked it but please double check. You might want to call insserv -f. Werner, what do you suggest? `insserv -f` is probably not a way to go since all YaST modules use Service::Enable($service_name) for enabling the service. That would change the behavior for all modules. Andreas, this is part of your y2log: clients/firewall_proposal.ycp:16 Firewall proposal started clients/firewall_proposal.ycp:17 Arguments: ["Write", $[]] SuSEFirewall.ycp:2316 Firewall configuration has been changed. Writing: $[... "FW_SERVICES_EXT_TCP":"ssh", "enable_firewall":true, "start_firewall":true]. SuSEFirewall.ycp:2333 Enabling firewall services Service.ycp:386 Enabling service SuSEfirewall2_init --- important --- ShellCommand.cc(shellcommand):78 insserv: There is a loop between service cron and syslog Service.ycp:386 Enabling service SuSEfirewall2_setup ShellCommand.cc(shellcommand):78 insserv: Service network has to be enabled for service SuSEfirewall2_setup ShellCommand.cc(shellcommand):78 insserv: exiting now! Service.ycp:195 Unable to enable service SuSEfirewall2_setup: insserv: Service network has to be enabled for service SuSEfirewall2_setup insserv: exiting now! ... SuSEFirewall.ycp:1406 Firewall service SuSEfirewall2_setup is not enabled --- important --- So, that's it. There are two ways to repair that: 1.) hack YaST Firewall to enable the SuSEirewall service with the "--force" option 2.) fix dependencies... Rudi, we might need to do our hack earlier. I suggest to use --force - Rudi, Werner, what do you think? well, the plan is that the SuSEconfig.insserv_cleanup will go away and insserv will automatically restart itself with "-d" if a loop is detected. So this should work unchanged again once insserv is changed. (but please keep an eye on this to monitor it really works then). Try out the newest insserv from STABLE. The problem was in insserv, but is was already said that it didn't work... *** Bug 144791 has been marked as a duplicate of this bug. *** *** Bug 144698 has been marked as a duplicate of this bug. *** *** Bug 144791 has been marked as a duplicate of this bug. *** *** Bug 145344 has been marked as a duplicate of this bug. *** |