[Samba] RE: migrating samba to new hardware and different OS
Andrew Jeremy Gargan
agargan at gmail.com
Sun Aug 26 13:12:30 GMT 2007
Hi All
I have done as much as I can to try and figure out what is going wrong
with my samba migration by googleing and reading mailing list archives
and reading documentation etc.
I have an existing SAMBA 3.0.5 domain running on suse linux 9.3.
I am trying to migrate this setup to a new server which is running
Fedora Core 6
smbd 3.0.24-7.fc6
I have migrated the data across to the new system and some of it is
working very well.
the \\server\username shares are working a charm.
My issue comes when I try and access any share that uses
write list = @agroup, auser, another user
The groups seems to be what breaks it, on the client side the
authentication dialogue box keeps popping up and the server logs are
as follows:
---snip ---
Aug 26 13:05:58 server1 smbd[9624]: [2007/08/26 13:05:58, 0]
lib/fault.c:fault_report(42)
Aug 26 13:05:58 server1 smbd[9624]: INTERNAL ERROR: Signal 11 in pid
9624 (3.0.24-7.fc6)
Aug 26 13:05:58 server1 smbd[9624]: Please read the Trouble-Shooting
section of the Samba3-HOWTO
Aug 26 13:05:58 server1 smbd[9624]: [2007/08/26 13:05:58, 0]
lib/fault.c:fault_report(44)
Aug 26 13:05:58 server1 smbd[9624]:
Aug 26 13:05:58 server1 smbd[9624]: From:
http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
Aug 26 13:05:58 server1 smbd[9624]: [2007/08/26 13:05:58, 0]
lib/fault.c:fault_report(45)
Aug 26 13:05:58 server1 smbd[9624]:
===============================================================
Aug 26 13:05:58 server1 smbd[9624]: [2007/08/26 13:05:58, 0]
lib/util.c:smb_panic(1621)
Aug 26 13:05:58 server1 smbd[9624]: PANIC (pid 9624): internal error
Aug 26 13:05:58 server1 smbd[9624]: [2007/08/26 13:05:58, 0]
lib/util.c:log_stack_trace(1728)
Aug 26 13:05:58 server1 smbd[9624]: BACKTRACE: 21 stack frames:
Aug 26 13:05:58 server1 smbd[9624]: #0 smbd(log_stack_trace+0x2d) [0x45e3fd]
Aug 26 13:05:58 server1 smbd[9624]: #1 smbd(smb_panic+0x5d) [0x45e52d]
Aug 26 13:05:58 server1 smbd[9624]: #2 smbd [0x4499ca]
Aug 26 13:05:58 server1 smbd[9624]: #3 [0xb37420]
Aug 26 13:05:58 server1 smbd[9624]: #4 /lib/libc.so.6(strlen+0x33) [0x65f2d3]
Aug 26 13:05:58 server1 smbd[9624]: #5
/lib/libc.so.6(__strdup+0x25) [0x65f015]
Aug 26 13:05:58 server1 smbd[9624]: #6
/lib/libnsl.so.1(nis_list+0x62f) [0x16ac5f]
Aug 26 13:05:58 server1 smbd[9624]: #7
/lib/libnss_nisplus.so.2(_nss_nisplus_setnetgrent+0x94) [0x2237c4]
Aug 26 13:05:58 server1 smbd[9624]: #8 /lib/libc.so.6(innetgr+0xb6)
[0x6dd2e6]
Aug 26 13:05:58 server1 smbd[9624]: #9 smbd(user_in_netgroup+0x65) [0x293ca5]
Aug 26 13:05:58 server1 smbd[9624]: #10
smbd(token_contains_name_in_list+0x23d) [0x29670d]
Aug 26 13:05:58 server1 smbd[9624]: #11
smbd(is_share_read_only_for_token+0x98) [0x296a08]
Aug 26 13:05:58 server1 smbd[9624]: #12 smbd(change_to_user+0x440) [0x2d5360]
Aug 26 13:05:58 server1 smbd[9624]: #13 smbd [0x2f49a8]
Aug 26 13:05:58 server1 smbd[9624]: #14 smbd(make_connection+0x194)
[0x2f5e74]
Aug 26 13:05:58 server1 smbd[9624]: #15
smbd(reply_tcon_and_X+0x217) [0x2b9647]
Aug 26 13:05:58 server1 smbd[9624]: #16 smbd [0x2f0f70]
Aug 26 13:05:58 server1 smbd[9624]: #17 smbd(smbd_process+0x7ab) [0x2f209b]
Aug 26 13:05:58 server1 smbd[9624]: #18 smbd(main+0xbd0) [0x50d150]
Aug 26 13:05:58 server1 smbd[9624]: #19
/lib/libc.so.6(__libc_start_main+0xdc) [0x608f2c]
Aug 26 13:05:58 server1 smbd[9624]: #20 smbd [0x27c051]
Aug 26 13:05:58 server1 smbd[9624]: [2007/08/26 13:05:58, 0]
lib/fault.c:dump_core(173)
Aug 26 13:05:58 server1 smbd[9624]: dumping core in /var/log/samba/cores/smbd
Aug 26 13:05:58 server1 smbd[9624]:
--- snip ---
If I remove the 'write list' entries for shares I can then access
those shares as per normal but then I can see anything inside those
shares including stuff that has strict group specific permissions.
Domain logons seem to be working and the users home directories are
being mapped as network drives.
I am really frustrated and stuck here and have followed all the hints
I could scrape from google.
The smbd nmbd etc are the latest versions as per the Fedora yum repo's
I have tried using the tdb backend for passwords as well as the
default but nothing seems to fix this issue.
Regards
Andrew
More information about the samba
mailing list