Modify

Opened 9 years ago

Closed 8 years ago

#2852 closed defect (fixed)

samba could not work

Reported by: zephyrs Owned by: developers
Priority: high Milestone:
Component: packages Version:
Keywords: Cc:

Description

I found samba package could not work for a long time in Kamikaze,
released 7.09 version could work, but after that I tried later development build,
seems all could not bring up samba. the smbd and nmbd did not show in top command,
and windows machine also could not find the share directories

I'm using a netgear wgt634u box,
when I tried to restart the service, it said:
root@OpenWrt:~# /etc/init.d/samba restart
sh: cannot kill pid 774: No such process
sh: cannot kill pid 776: No such process

here is the content of /etc/samba/smb.conf:
[global]
syslog = 0
syslog only = yes
workgroup = OpenWrt
server string = OpenWrt Samba Server
security = share
encrypt passwords = yes
guest account = root
local master = yes
name resolve order = lmhosts hosts bcast

[tmp]
comment = /tmp
path = /tmp
browseable = yes
public = yes
writeable = no

My installed package:
amule - 2.1.3-1 -
base-files-brcm47xx - 12-r9723 -
bridge - 1.0.6-1 -
busybox - 1.8.2-1 -
ctorrent - dnh3.2-1 -
dnsmasq - 2.40-1 -
dropbear - 0.50-3 -
fdisk - 2.13.0.1-1 -
hotplug2 - 0.9+r102-2 -
iptables - 1.3.8-2 -
kernel - 2.6.23.1-brcm47xx-1 -
kmod-diag - 2.6.23.1-brcm47xx-2 -
kmod-fs-ntfs - 2.6.23.1-brcm47xx-1 -
kmod-fs-vfat - 2.6.23.1-brcm47xx-1 -
kmod-ipt-nathelper - 2.6.23.1-brcm47xx-1 -
kmod-madwifi - 2.6.23.1+r3053-brcm47xx-1 -
kmod-nls-base - 2.6.23.1-brcm47xx-1 -
kmod-nls-cp1250 - 2.6.23.1-brcm47xx-1 -
kmod-nls-cp437 - 2.6.23.1-brcm47xx-1 -
kmod-nls-iso8859-1 - 2.6.23.1-brcm47xx-1 -
kmod-nls-utf8 - 2.6.23.1-brcm47xx-1 -
kmod-ppp - 2.6.23.1-brcm47xx-1 -
kmod-pppoe - 2.6.23.1-brcm47xx-1 -
kmod-scsi-core - 2.6.23.1-brcm47xx-1 -
kmod-switch - 2.6.23.1-brcm47xx-1 -
kmod-usb-core - 2.6.23.1-brcm47xx-1 -
kmod-usb-storage - 2.6.23.1-brcm47xx-1 -
kmod-usb-uhci - 2.6.23.1-brcm47xx-1 -
kmod-usb2 - 2.6.23.1-brcm47xx-1 -
libexpat - 1.95.8-1 -
libgcc - 4.1.2-12 -
libncurses - 5.6-1 -
libopenssl - 0.9.8e-3 -
libpng - 1.2.8-1 -
libpthread - 0.9.28.2-12 -
libreadline - 5.1-1 -
libwxbase - 2.6.4-1 -
mtd - 6 -
ppp - 2.4.3-9 -
ppp-mod-pppoe - 2.4.3-9 -
samba-common - 2.0.10-4 -
samba-server - 2.0.10-4 -
uclibc - 0.9.28.2-12 -
uclibcxx - 0.2.2-1 -
udevtrigger - 106-1 -
wireless-tools - 29-1 -
zlib - 1.2.3-5 -

Attachments (0)

Change History (3)

comment:1 Changed 8 years ago by rene@…

Hi zephyrs,

Have you checked the hosts file and added an entry to make sure the lan name resolves to a host name? This fixed the issue for me

comment:2 Changed 8 years ago by yasha

Yeah, the hosts file is the issue, it doesn't like using the loopback entry in the hosts file. I suspect it can't read the resolve.config's.

comment:3 Changed 8 years ago by florian

  • Resolution set to fixed
  • Status changed from new to closed

Should be fixed with the samba3 version.

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.