[opensuse] Samba won't start because of Vmware Networking
Hello: I have a very similar problem to this one: http://fixunix.com/networking/526438-problem-samba-wont-start-because-vmware... Excerpt from the above thread: "smb and nmb boot scripts fail to start smbd and nmbd. Samba is configured to only listen to the host-only network interface from VMware at vmnet1:192.168.230.1. I think what happens is that the vmnet1 interface doesn't appear until after the smb and nmb scripts run, so the smbd/nmbd die. However, when I manually do /etc/init.d/smb restart after my system is fully up, then Samba starts just fine and works too. How to make Samba wait a bit for the vmnet1 interface to appear?" There is no working solution at the above site, so I am asking the question here. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Istvan Gabor wrote:
Hello:
I have a very similar problem to this one:
http://fixunix.com/networking/526438-problem-samba-wont-start-because-vmware...
Excerpt from the above thread:
"smb and nmb boot scripts fail to start smbd and nmbd.
Samba is configured to only listen to the host-only network interface from VMware at vmnet1:192.168.230.1. I think what happens is that the vmnet1 interface doesn't appear until after the smb and nmb scripts run, so the smbd/nmbd die. However, when I manually do /etc/init.d/smb restart after my system is fully up, then Samba starts just fine and works too.
How to make Samba wait a bit for the vmnet1 interface to appear?"
There is no working solution at the above site, so I am asking the question here.
Thanks, Istvan
Are you talking about Linux running in a virtual machine? Are you talking about Linux running as the Host? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello:
I have a very similar problem to this one:
http://fixunix.com/networking/526438-problem-samba-wont-start-because-vmware...
Excerpt from the above thread:
"smb and nmb boot scripts fail to start smbd and nmbd.
Samba is configured to only listen to the host-only network interface from VMware at vmnet1:192.168.230.1. I think what happens is that the vmnet1 interface doesn't appear until after the smb and nmb scripts run, so the smbd/nmbd die. However, when I manually do /etc/init.d/smb restart after my system is fully up, then Samba starts just fine and works too.
How to make Samba wait a bit for the vmnet1 interface to appear?"
There is no working solution at the above site, so I am asking the question >>here.
Thanks, Istvan
Are you talking about Linux running in a virtual machine? Are you talking about Linux running as the Host?
Sorry, I forgot to mention. I am running openSUSE 10.3 as host. I have VMware 5.5.3 workstation installed on this linux system. Samba version is: samba-client-3.0.26a-3.7 yast2-samba-server-2.15.7-57 yast2-samba-client-2.15.11-33 samba-winbind-3.0.26a-3.7 samba-3.0.26a-3.7 kdebase3-samba-3.5.10-102.1 Samba is set in yast to startup at boot. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Istvan Gabor wrote:
Hello:
I have a very similar problem to this one:
http://fixunix.com/networking/526438-problem-samba-wont-start-because-vmware...
Excerpt from the above thread:
"smb and nmb boot scripts fail to start smbd and nmbd.
Samba is configured to only listen to the host-only network interface from VMware at vmnet1:192.168.230.1. I think what happens is that the vmnet1 interface doesn't appear until after the smb and nmb scripts run, so the smbd/nmbd die. However, when I manually do /etc/init.d/smb restart after my system is fully up, then Samba starts just fine and works too.
How to make Samba wait a bit for the vmnet1 interface to appear?"
There is no working solution at the above site, so I am asking the question >>here.
Thanks, Istvan Are you talking about Linux running in a virtual machine? Are you talking about Linux running as the Host?
Sorry, I forgot to mention.
I am running openSUSE 10.3 as host. I have VMware 5.5.3 workstation installed on this linux system. Samba version is: samba-client-3.0.26a-3.7 yast2-samba-server-2.15.7-57 yast2-samba-client-2.15.11-33 samba-winbind-3.0.26a-3.7 samba-3.0.26a-3.7 kdebase3-samba-3.5.10-102.1
Samba is set in yast to startup at boot.
Ah, ok, that helps. There were problems in the Vmware supplied init scripts in Vmware 5, that caused vmware to start at the wrong sequence, but this only affected anything if you configured samba to ONLY listen on host only, or a wireless interface. If at least one interface was up, samba will run normally and pick up the other interfaces as they appear. (Host only is sort of an odd-ball IMHO, and you would be better served by letting it create a NAT subnet so your VMs can talk to each other when/if you get more than VM running at a time.) Anyway, in /etc/rc.d/rc5.d you can rename the links from S0?nmb and S0?smb to have the last number one digit higher than whatever S0?vmware has. (In my case smb/nmb and vmware are S07 but I am running a different release of vmware. This will serve to test things, but is not a permanent fix. A more proper fix might be to edit /etc/rc.d/smb (and nmb) and change the comment line: "# Required-Start: $network syslog " by adding VMware at the end after syslog. (Capitalization important). Then run "insserv" command and check /etc/rc.d/rc5.d to see if these links are straightened out so that the vmware one precedes the samba ones. In later releases of Opensuse the start sequences of services is controlled by something different. Later versions of Vmware do not seem to have this problem. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello:
I have a very similar problem to this one:
http://fixunix.com/networking/526438-problem-samba-wont-start-because-vmware...
Excerpt from the above thread:
"smb and nmb boot scripts fail to start smbd and nmbd.
Samba is configured to only listen to the host-only network interface from VMware at vmnet1:192.168.230.1. I think what happens is that the vmnet1 interface doesn't appear until after the smb and nmb scripts run, so the smbd/nmbd die. However, when I manually do /etc/init.d/smb restart after my system is fully up, then Samba starts just fine and works too.
How to make Samba wait a bit for the vmnet1 interface to appear?"
There is no working solution at the above site, so I am asking the question >>here.
Thanks, Istvan Are you talking about Linux running in a virtual machine? Are you talking about Linux running as the Host?
I am running openSUSE 10.3 as host. I have VMware 5.5.3 workstation installed on this linux system. Samba is set in yast to startup at boot.
Ah, ok, that helps.
There were problems in the Vmware supplied init scripts in Vmware 5, that caused vmware to start at the wrong sequence, but this only affected anything if you configured samba to ONLY listen on host only, or a wireless interface.
This applies exactly to my configuration.
If at least one interface was up, samba will run normally and pick up the other interfaces as they appear.
(Host only is sort of an odd-ball IMHO, and you would be better served by letting it create a NAT subnet so your VMs can talk to each other when/if you get more than VM running at a time.)
I want to separate my virtual system and virtual network completely from the internet. I am not familiar with virtual networking and guessed that this setup can be the safest.
Anyway, in /etc/rc.d/rc5.d you can rename the links from S0?nmb and S0?smb to have the last number one digit higher than whatever S0?vmware has. (In my case smb/nmb and vmware are S07 but I am running a different release of vmware.
I did this, changed the names by hand but it did not work.
This will serve to test things, but is not a permanent fix. A more proper fix might be to edit /etc/rc.d/smb (and nmb) and change the comment line: "# Required-Start: $network syslog " by adding VMware at the end after syslog. (Capitalization important).
Then run "insserv" command and check /etc/rc.d/rc5.d to see if these links are straightened out so that the vmware one precedes the samba ones.
This solution works. 2 questions: 1. The name/number of the links does only determine the order of the init scripts, or one script can only be run when the previous script has started already? 2. How does one know that VMware is what has to be put in the "# Required-Start" line and not vmware, as the init script name would suggest? Now it seems that the problem is solved. Thank you. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Istvan Gabor wrote:
This solution works. 2 questions: 1. The name/number of the links does only determine the order of the init scripts, or one script can only be run when the previous script has started already?
The Name of the link USED TO determine the start sequence. I think there is newer methods in play these days. The fact that simply renameing the links did not work suggests something else is afoot, OR that this had to be done EARLIER, such as in rc3.d instead of rc5.d. Supposedly a script can not start until the successful completion of any script it Requires
2. How does one know that VMware is what has to be put in the "# Required-Start" line and not vmware, as the init script name would suggest?
By looking inside the vmware script at the #Provides: line. Believe me, I went round and round looking for why it didn't work and when I found that Vmware was using inconsistent capitalization I sent them a nastygram. "Provides" need not be related in any way to script name, but usually is.
Now it seems that the problem is solved. Thank you.
Istvan
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Istvan Gabor
-
John Andersen