On Saturday 23 July 2011 1455:06 Mark Goldstein Mark Goldstein
On Sat, Jul 23, 2011 at 2:41 PM, Stan Goodman
wrote: In reviewing my firewall settings, I found that the firewall in my router (D-link 2670U) is running, but the SuSE firewall 0f my v11.4 laptop is not. When I tried to start it, I got the following error messages: Cannot enable service SuSEfirewall2_init Cannot enable service SuSEfirewall2_setup
The same thing happens from the CLI: # yast firewall startup atboot
Start-Up: ---------
Enabling firewall in the boot process...
Errors: Cannot enable service 'SuSEfirewall2_init'. Cannot enable service 'SuSEfirewall2_setup'.
Seeking a hint about why this is so:
# chkconfig SuSEfirewall2_init on insserv: FATAL: service syslog is missed in the runlevels 4 to use service vboxdrv insserv: exiting now! /sbin/insserv failed, exit code 1 # chkconfig SuSEfirewall2_setup on insserv: FATAL: service SuSEfirewall2_init has to be enabled to use service SuSEfirewall2_setup insserv: FATAL: service syslog is missed in the runlevels 4 to use service vboxdrv insserv: exiting now! /sbin/insserv failed, exit code 1
So this is connected with VirtualBox (not the one from openSuSE repository) Vbox is indeed installed, but it is not running now, so apparently it is the mere presence of VirtualBox that stymies the firewall. The easest solution is to uninstall VirtualBox, since I use it only infrequently, and try the VMware equivalent at a later time. But VirtualBox is not so eacy to remove:
# rpm -e virtualbox error: package virtualbox is not installed # rpm -e vbox error: package vbox is not installed #
Yet I can run VirtualBox from VirtualBox from the run command, and it appears in the launcher. What do I have to do to ditch it?
Stan,
It should not be Virtual Box. I do have Virtual Box from Oracle repository in my system (11.4 - 32 bit). I did not use SuSE FW, but just tried enabling it and it went OK.
I should have mentioned that this is a 64bit system; perhaps that makes the diffeence. The failure is not special to me, by the way: googling the original error message retrieved 295 hits, which, although a record low for Google, shows that it does happen.
Now, the package name is VirtualBox-4.0 (in my case). So if you want to delete it, use the exact name (try rpm -qa|grep -i virtual).
Mine is not v4, but I will see if I can remove it with the proper version number.
Regards,
-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org