Loading ...
Sorry, an error occurred while loading the content.

Re: Help - smbd PANIC

Expand Messages
  • Heath
    thanks, I ll give that a try. Any idea how it got messed up? I haven t touched the samba config files as part of unslinging my slug. h
    Message 1 of 4 , Sep 30 9:16 AM
    • 0 Attachment
      thanks, I'll give that a try. Any idea how it got messed up? I haven't
      touched the samba config files as part of unslinging my slug.

      h

      Cheng Feng wrote:
      > hi,
      >
      > This is a configure problem in the /etc/samba/smb.conf
      >
      > change the line
      > username map = no
      > to
      > username map = # no
      >
      > basically the 'no' was parsed to the name of the
      > usermap, and smb.log complains about cannot open it.
      >
      > The correct syntax '# no', ie, map the '#' to the
      > beginning of comment
      >
      > al
      >
      > --- chezdude2010 <heath@...>
      > wrote:
      >
      >
      >>chezdude2010 wrote:
      >>
      >>>I just tried connecting from my freshly updated XP
      >>
      >>Home SP2 system to my
      >>
      >>> slug and can't seem to connect to the Samba
      >>
      >>service.
      >>
      >>>It's running Unslung 1.11Beta
      >>>
      >>>The smbd and nmbd processes are both running.
      >>>
      >>>I get the following in /var/log/samba/log.smbd
      >>>
      >>>
      >>>[2004/09/29 22:47:53, 0]
      >>
      >>lib/fault.c:fault_report(38)
      >>
      >>>
      >>
      > ===============================================================
      >
      >>>[2004/09/29 22:47:53, 0]
      >>
      >>lib/fault.c:fault_report(39)
      >>
      >>> INTERNAL ERROR: Signal 11 in pid 531
      >>
      >>(2.2.7b-ja-1.0)
      >>
      >>> Please read the file BUGS.txt in the
      >>
      >>distribution
      >>
      >>>[2004/09/29 22:47:53, 0]
      >>
      >>lib/fault.c:fault_report(41)
      >>
      >>>
      >>
      > ===============================================================
      >
      >>>[2004/09/29 22:47:53, 0]
      >>
      >>lib/util.c:smb_panic(1102)
      >>
      >>> PANIC: internal error
      >>>[2004/09/29 22:47:53, 0]
      >>
      >>lib/fault.c:fault_report(38)
      >>
      >>>
      >>
      > ===============================================================
      >
      >>>[2004/09/29 22:47:53, 0]
      >>
      >>lib/fault.c:fault_report(39)
      >>
      >>> INTERNAL ERROR: Signal 11 in pid 532
      >>
      >>(2.2.7b-ja-1.0)
      >>
      >>> Please read the file BUGS.txt in the
      >>
      >>distribution
      >>
      >>>[2004/09/29 22:47:53, 0]
      >>
      >>lib/fault.c:fault_report(41)
      >>
      >>>
      >>
      > ===============================================================
      >
      >>>[2004/09/29 22:47:53, 0]
      >>
      >>lib/util.c:smb_panic(1102)
      >>
      >>> PANIC: internal error
      >>>[2004/09/29 22:47:53, 0]
      >>
      >>lib/fault.c:fault_report(38)
      >>
      >>>
      >>
      > ===============================================================
      >
      >>>[2004/09/29 22:47:53, 0]
      >>
      >>lib/fault.c:fault_report(39)
      >>
      >>> INTERNAL ERROR: Signal 11 in pid 533
      >>
      >>(2.2.7b-ja-1.0)
      >>
      >>> Please read the file BUGS.txt in the
      >>
      >>distribution
      >>
      >>>[2004/09/29 22:47:53, 0]
      >>
      >>lib/fault.c:fault_report(41)
      >>
      >>>
      >>
      > ===============================================================
      >
      >>>[2004/09/29 22:47:53, 0]
      >>
      >>lib/util.c:smb_panic(1102)
      >>
      >>> PANIC: internal error
      >>>
      >>>
      >>>I'm assuming the pids for the Signal 11 errors are
      >>
      >>for the child
      >>
      >>>processes that are getting spawned to service the
      >>
      >>incoming request as
      >>
      >>>the master smbd and nmbd processes are still
      >>
      >>running.
      >>
      >>>Any suggestions?
      >>>
      >>>h
      >>>
      >>
      >>Well, I restarted the samba server
      >>(/etc/rc.d/rc.samba) and it's now
      >>working, but I'm getting the following in the samba
      >>log file:
      >>
      >>[2004/09/29 23:02:02, 0]
      >>lib/username.c:map_username(133)
      >> can't open username map no. Error No such file or
      >>directory
      >>[2004/09/29 23:02:02, 0]
      >>lib/username.c:map_username(133)
      >> can't open username map no. Error No such file or
      >>directory
      >>[2004/09/29 23:02:04, 0]
      >>lib/username.c:map_username(133)
      >> can't open username map no. Error No such file or
      >>directory
      >>[2004/09/29 23:02:04, 0]
      >>lib/username.c:map_username(133)
      >> can't open username map no. Error No such file or
      >>directory
      >>[2004/09/29 23:02:04, 0]
      >>lib/username.c:map_username(133)
      >> can't open username map no. Error No such file or
      >>directory
      >>
      >>
      >>And that's for 1 access to the samba server. Anyone
      >>have any thoughts
      >>on this one? I doubt that it's anything to do with
      >>unslung, but just
      >>wanted to ask if anyone else has seen this and if
      >>it's normal or not.
      >>
      >>Thanks,
      >>heath
      >>
      >>
      >
      >
      >
      >
      >
      > _______________________________
      > Do you Yahoo!?
      > Declare Yourself - Register online to vote today!
      > http://vote.yahoo.com
      >
      >
      >
      > [ Moderator Note: All static information is slowly moving to the Wiki at http://www.nslu2-linux.org ]
    Your message has been successfully submitted and would be delivered to recipients shortly.