smb - not running (SOLVED)

[old_guy]

I have two machines, each has a number of partitions with various versions of PCLOS on them.
The older machine works fine.
The newer machine is the problem. The partitions with 2009, Zen mini, Gnome are Ok.
The partitions (4) with various installs of 2010 KDE (full & mini) have my problem.
I boot up and my lan is not working. I can check the services in PCC and it has smb checked to run on boot, but shows it stopped - therefore this machine does not show up on the lan. I can start sbm and everything is fine, but what is knocking it off?

As stated before - the hardware must be OK - It is fine on all the non KDE 4 partitions, but fails the same way on 4 different KDE 4 partitions.

Earl

[old_guy]

Update:

1. booted up first KDE 2010 and cleared logs - logged out
2. booted Zen mini 2010 and cleared logs - logged out
3. rebooted into each  and compared


bad:
/var/log/samba/log.nmbd

[2010/10/15 16:10:48,  0] nmbd/nmbd.c:857(main)
  nmbd version 3.5.6 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2010
[2010/10/15 16:10:48.932023,  0] lib/interface.c:519(load_interfaces)
  ERROR: Could not determine network interfaces, you must use a interfaces config line

/var/log/samba/smbd.log

[2010/10/15 16:10:48.567423,  0] lib/interface.c:519(load_interfaces)
  ERROR: Could not determine network interfaces, you must use a interfaces config line


good:
/var/log/samba/log.nmbd

[2010/10/15 16:19:44,  0] nmbd/nmbd.c:857(main)
  nmbd version 3.5.5 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2010

/var/log/samba/smbd.log

[2010/10/15 16:19:45.226799,  0] smbd/server.c:500(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use

Anyone able to explain the error to me?

Earl

[ThirdOfSix]

Don't get your hopes up on seeing this post.

It has been months since I have done anything with network setup and I have difficulty remembering the stuff after a few days.

You did not mention whether this is a problem in systems that once worked as you expect but quit after an update or if you have never had them working on the network as desired.

I seem to remember that some folks had some of their network configuration files  revert to default settings or something after a recent update.

You might do a search on smb.conf on the two machines that you are comparing and see what is different between them in the lines that are not commented out.

Even better, if you have a liveCD backup of one of the machines that was made when it worked, compare the smb.conf file on it with the current version.

I believe that we have a couple of guys in the group who are very knowledgeable  on the network stuff

Hopefully they will come along shortly and do you a bit more good than I can do.

[kjpetrie]

If it stopped working after an upgrade, check for /etc/samba/smb.conf.rpmsave. If it's there it will be your previous config file so rename the present one and then drop the .rpmsave off the end of the old one.

[old_guy]

kjpetrie
It works when I restart samba. The problem is that in PCC smb is checked to run on boot,but is not running.

EDIT:
I have a backup of my KDE4 that was made on Sept. 2, 2010. I booted into it and the smb WAS running.

[kjpetrie]

Have a look back through /var/log/syslog (you have to be root to read the file) for any messages about smb start and stop. Might give you a clue as to when it starts and stops or whether it hits any errors.

[old_guy]

kjpetrie
Read my second post!
It shows the log errors.

[old_guy]

Next Update:

I removed:
samba-common
samba-cilent
samba-server
version 3.5.6-2pclos2010
and installed
version 3.5.5-1pclos2010
that I had saved in apt
On boot smb is up and running and everything works.

[old_guy]

Texstar updates fixed it!

[wedgetail]

old_guy
I don't quite understand.  Do you mean that the update broke your latest systems?   

[Texstar]

old_guy
I don't quite understand.  Do you mean that the update broke your latest systems?   

It means 3.5.6 had a tiny bug in the smb init script that prevented it from starting at boot when selected in the PCLinuxOS Control Center and has been fixed so it starts at boot in a package update after it was reported in broken packages.