LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
 
Search this Thread
Old 11-12-2012, 07:09 AM   #1
root@linux
LQ Newbie
 
Registered: Aug 2011
Location: Pakistan
Distribution: Ubuntu
Posts: 11

Rep: Reputation: Disabled
Question Samba server on fedora 15 won't work after this error.


i have a strange problem with my server on fedora 15. few days ago my hdd was crashed and i had to replace it and reinstall fedora 15. but unfortunately the samba server stops working. the output of error log is.
Code:
Nov 12 17:29:37 skylink dbus-daemon: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Nov 12 17:29:37 skylink dbus-daemon: [system] Successfully activated service 'net.reactivated.Fprint'
Nov 12 17:29:47 skylink smbd[6027]: [2012/11/12 17:29:47.466267,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Nov 12 17:29:47 skylink smbd[6027]:   getpeername failed. Error was Transport endpoint is not connected
Nov 12 17:29:47 skylink smbd[6027]: [2012/11/12 17:29:47.467129,  0] lib/util_sock.c:680(write_data)
Nov 12 17:29:47 skylink smbd[6027]: [2012/11/12 17:29:47.467254,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Nov 12 17:29:47 skylink smbd[6027]:   getpeername failed. Error was Transport endpoint is not connected
Nov 12 17:29:47 skylink smbd[6027]:   write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
Nov 12 17:29:47 skylink smbd[6027]: [2012/11/12 17:29:47.467490,  0] smbd/process.c:79(srv_send_smb)
Nov 12 17:29:47 skylink smbd[6027]:   Error writing 4 bytes to client. -1. (Transport endpoint is not connected)
Nov 12 17:38:14 skylink smbd[6197]: [2012/11/12 17:38:14.779700,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Nov 12 17:38:14 skylink smbd[6197]:   getpeername failed. Error was Transport endpoint is not connected
Nov 12 17:38:14 skylink smbd[6197]: [2012/11/12 17:38:14.780857,  0] lib/util_sock.c:680(write_data)
Nov 12 17:38:14 skylink smbd[6197]: [2012/11/12 17:38:14.796006,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Nov 12 17:38:14 skylink smbd[6197]:   getpeername failed. Error was Transport endpoint is not connected
Nov 12 17:38:14 skylink smbd[6197]:   write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
Nov 12 17:38:14 skylink smbd[6197]: [2012/11/12 17:38:14.796121,  0] smbd/process.c:79(srv_send_smb)
Nov 12 17:38:14 skylink smbd[6197]:   Error writing 4 bytes to client. -1. (Transport endpoint is not connected)
Nov 12 17:39:45 skylink ntfs-3g[719]: Incomplete multi-sector transfer: magic: 0x454c4946  size: 1024  usa_ofs: 48  usa_count: 1  data: 17519  usn: 17518: Input/output error
Nov 12 17:39:45 skylink ntfs-3g[719]: Record 3040 has no FILE magic (0x44414142)
Nov 12 17:42:51 skylink smbd[6104]: [2012/11/12 17:42:51.679532,  0] lib/util_sock.c:474(read_fd_with_timeout)
Nov 12 17:42:51 skylink smbd[6104]: [2012/11/12 17:42:51.684453,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Nov 12 17:42:51 skylink smbd[6104]:   getpeername failed. Error was Transport endpoint is not connected
Nov 12 17:42:51 skylink smbd[6104]:   read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer.
Nov 12 17:42:51 skylink smbd[6104]: [2012/11/12 17:42:51.684812,  0] lib/util_sock.c:680(write_data)
Nov 12 17:42:51 skylink smbd[6104]: [2012/11/12 17:42:51.684870,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Nov 12 17:42:51 skylink smbd[6104]:   getpeername failed. Error was Transport endpoint is not connected
Nov 12 17:42:51 skylink smbd[6104]:   write_data: write failure in writing to client 0.0.0.0. Error Broken pipe
Nov 12 17:42:51 skylink smbd[6104]: [2012/11/12 17:42:51.685150,  0] smbd/process.c:79(srv_send_smb)
Nov 12 17:42:51 skylink smbd[6104]:   Error writing 75 bytes to client. -1. (Transport endpoint is not connected)
Nov 12 17:43:09 skylink smbd[6297]: [2012/11/12 17:43:09.136134,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Nov 12 17:43:09 skylink smbd[6297]:   getpeername failed. Error was Transport endpoint is not connected
Nov 12 17:43:09 skylink smbd[6297]: [2012/11/12 17:43:09.136808,  0] lib/util_sock.c:680(write_data)
Nov 12 17:43:09 skylink smbd[6297]: [2012/11/12 17:43:09.146906,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Nov 12 17:43:09 skylink smbd[6297]:   getpeername failed. Error was Transport endpoint is not connected
Nov 12 17:43:09 skylink smbd[6297]:   write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
Nov 12 17:43:09 skylink smbd[6297]: [2012/11/12 17:43:09.147015,  0] smbd/process.c:79(srv_send_smb)
Nov 12 17:43:09 skylink smbd[6297]:   Error writing 4 bytes to client. -1. (Transport endpoint is not connected)
Nov 12 17:44:16 skylink smbd[6306]: [2012/11/12 17:44:16.884635,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Nov 12 17:44:16 skylink smbd[6306]:   getpeername failed. Error was Transport endpoint is not connected
Nov 12 17:44:16 skylink smbd[6306]: [2012/11/12 17:44:16.885162,  0] lib/util_sock.c:474(read_fd_with_timeout)
Nov 12 17:44:16 skylink smbd[6306]: [2012/11/12 17:44:16.903585,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Nov 12 17:44:16 skylink smbd[6306]:   getpeername failed. Error was Transport endpoint is not connected
Nov 12 17:44:16 skylink smbd[6306]:   read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer.
Nov 12 17:45:35 skylink dbus-daemon: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Nov 12 17:45:36 skylink dbus-daemon: [system] Successfully activated service 'org.freedesktop.PackageKit'
Nov 12 17:48:17 skylink smbd[6302]: [2012/11/12 17:48:17.469670,  0] lib/util_sock.c:474(read_fd_with_timeout)
Nov 12 17:48:17 skylink smbd[6302]: [2012/11/12 17:48:17.469845,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Nov 12 17:48:17 skylink smbd[6302]:   getpeername failed. Error was Transport endpoint is not connected
Nov 12 17:48:17 skylink smbd[6302]:   read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer.
Nov 12 17:50:27 skylink ntfs-3g[719]: Incomplete multi-sector transfer: magic: 0x454c4946  size: 1024  usa_ofs: 48  usa_count: 1  data: 17519  usn: 17518: Input/output error
Nov 12 17:50:27 skylink ntfs-3g[719]: Record 3040 has no FILE magic (0x44414142)
Nov 12 17:50:34 skylink smbd[6391]: [2012/11/12 17:50:34.196682,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Nov 12 17:50:34 skylink smbd[6391]:   getpeername failed. Error was Transport endpoint is not connected
Nov 12 17:50:34 skylink smbd[6391]: [2012/11/12 17:50:34.197738,  0] lib/util_sock.c:680(write_data)
Nov 12 17:50:34 skylink smbd[6391]: [2012/11/12 17:50:34.197890,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Nov 12 17:50:34 skylink smbd[6391]:   getpeername failed. Error was Transport endpoint is not connected
Nov 12 17:50:34 skylink smbd[6391]:   write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
Nov 12 17:50:34 skylink smbd[6391]: [2012/11/12 17:50:34.198363,  0] smbd/process.c:79(srv_send_smb)
Nov 12 17:50:34 skylink smbd[6391]:   Error writing 4 bytes to client. -1. (Transport endpoint is not connected)
Nov 12 17:50:40 skylink ntfs-3g[719]: Incomplete multi-sector transfer: magic: 0x454c4946  size: 1024  usa_ofs: 48  usa_count: 1  data: 17519  usn: 17518: Input/output error
Nov 12 17:50:40 skylink ntfs-3g[719]: Record 3040 has no FILE magic (0x44414142)
Nov 12 17:51:44 skylink ntfs-3g[719]: Incomplete multi-sector transfer: magic: 0x454c4946  size: 1024  usa_ofs: 48  usa_count: 1  data: 17519  usn: 17518: Input/output error
Nov 12 17:51:44 skylink ntfs-3g[719]: Record 3040 has no FILE magic (0x44414142)
any suggestions?
 
Old 11-13-2012, 03:47 AM   #2
John VV
Guru
 
Registered: Aug 2005
Posts: 14,455

Rep: Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962
you reinstalled with a unsupported version of fedora ?
why?
It went End Of Life back in June ( June 26)

you might want to use fedora 17 and 'replace / port to 17' the data from the known good back up


as to the errors
are you reusing the config files from the old drive
the one with a different uuid #

and is the drive partitioned the same and is the block size the same as the old drive
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Samba share won't work..... OtisLinux Linux - Server 4 05-16-2007 03:09 PM
Samba Won't Work, No Matter What I Do jlacroix Linux - Networking 2 12-13-2004 03:30 PM
Samba Won't Work. VorlonShadow Linux - Networking 4 11-16-2004 08:43 AM
SAMBA: one mount won't work where others will insectile Linux - Networking 1 05-14-2004 04:44 PM
HP710c/Samba Won't work drjimstuckinwin Linux - Software 2 04-02-2001 02:26 PM


All times are GMT -5. The time now is 01:44 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration