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

Re: [nslu2-general] Re: Problem with Optware - Samba 3.4.5 problem for DNS323 package

Expand Messages
  • Robert Hammond
    I just added to the build feeds a fix for the gid problem, it should be available probably tomorrow or shortly afterwards. It will be version 3 of the ipk.
    Message 1 of 5 , Feb 21, 2010
    • 0 Attachment
      I just added to the build feeds a fix for the gid problem, it should be
      available probably tomorrow or shortly afterwards. It will be version 3
      of the ipk.

      My understanding is that this version does not use smbpasswd or secrets
      files to store user data but instead stores user data in a tdb file
      located in the same location. You may have to re-add all users
      including the guest user (default is nobody) using the smbpasswd -a
      command line option.


      In message <hls3si+oaom@...>, Patrick <patrick@...>
      writes

      >
      >My main concern is with the panic and core dump log message. I added
      >your "touch" recommendation about printcap. I also also removed most
      >configuration files (smbpasswd, secrets, etc) and only left smb.conf.
      >
      >Here's the log:
      >[2010/02/21 15:03:30, 1] lib/account_pol.c:325(account_policy_get)
      >account_policy_get: tdb_fetch_uint32 failed for field 1 (min password
      >length), returning 0
      >[2010/02/21 15:03:30, 1] lib/account_pol.c:325(account_policy_get)
      >account_policy_get: tdb_fetch_uint32 failed for field 2 (password history),
      >returning 0
      >[2010/02/21 15:03:30, 1] lib/account_pol.c:325(account_policy_get)
      >account_policy_get: tdb_fetch_uint32 failed for field 3 (user must logon to
      >change password), returning 0
      >[2010/02/21 15:03:30, 1] lib/account_pol.c:325(account_policy_get)
      >account_policy_get: tdb_fetch_uint32 failed for field 4 (maximum password
      >age), returning 0
      >[2010/02/21 15:03:30, 1] lib/account_pol.c:325(account_policy_get)
      >account_policy_get: tdb_fetch_uint32 failed for field 5 (minimum password
      >age), returning 0
      >[2010/02/21 15:03:30, 1] lib/account_pol.c:325(account_policy_get)
      >account_policy_get: tdb_fetch_uint32 failed for field 6 (lockout duration),
      >returning 0
      >[2010/02/21 15:03:30, 1] lib/account_pol.c:325(account_policy_get)
      >account_policy_get: tdb_fetch_uint32 failed for field 7 (reset count
      >minutes), returning 0
      >[2010/02/21 15:03:30, 1] lib/account_pol.c:325(account_policy_get)
      >account_policy_get: tdb_fetch_uint32 failed for field 8 (bad lockout
      >attempt), returning 0
      >[2010/02/21 15:03:30, 1] lib/account_pol.c:325(account_policy_get)
      >account_policy_get: tdb_fetch_uint32 failed for field 9 (disconnect time),
      >returning 0
      >[2010/02/21 15:03:30, 1] lib/account_pol.c:325(account_policy_get)
      >account_policy_get: tdb_fetch_uint32 failed for field 10 (refuse machine
      >password change), returning 0
      >[2010/02/21 15:03:30, 0] lib/util_sec.c:118(assert_gid)
      >Failed to set gid privileges to (-1,501) now set to (0,0) uid=(0,0)
      >[2010/02/21 15:03:30, 0] lib/util.c:1480(smb_panic)
      >PANIC (pid 23938): failed to set gid
      >
      >[2010/02/21 15:03:30, 0] lib/util.c:1634(log_stack_trace)
      >unable to produce a stack trace on this platform
      >[2010/02/21 15:03:30, 0] lib/fault.c:326(dump_core)
      >dumping core in /opt/var/samba/cores/smbd
      >
      >-Patrick
      >
      >--- In nslu2-general@yahoogroups.com, Robert Hammond <robham@...>
      >wrote:
      >>
      >> In message <hlmg7e+tpmi@...>, Patrick <patrick@...>
      >> writes
      >> > 
      >> >
      >> >I've just tried Samba34 3.4.5-2 (posted Feb 19), with no success (core
      >> >dump). I am using the same configuration as Samba 3 3.2.15-1.
      >> >
      >> >Please let me know if you need more info.
      >> >
      >> >-Patrick
      >> >
      >> >log.smb:
      >> >--------
      >> >[2010/02/19 11:45:21, 0] printing/pcap.c:178(pcap_cache_reload)
      >> >Unable to open printcap file /etc/printcap for read!
      >> >[2010/02/19 11:45:21, 0] printing/pcap.c:178(pcap_cache_reload)
      >> >Unable to open printcap file /etc/printcap for read!
      >> Regarding the printcap error, this happens with most versions of samba
      >> and is normally caused if the printcap file is missing.
      >>
      >> Can be fixed by
      >>
      >> touch /etc/printcap
      >>
      >> or preferably change the printcap line in the samba conf file to move
      >> the location of the file to /opt/etc/printcap and then
      >>
      >> touch /opt/etc/printcap
      >> --
      >> Robert Hammond
      >> PGP:0x154144DA
      >> 592B 0199 2D7F FC05 C4B1 0404 2258 4471 1541 44DA
      >>
      >
      >

      --
      Robert Hammond
      PGP:0x154144DA
      592B 0199 2D7F FC05 C4B1 0404 2258 4471 1541 44DA
    • Robert Hammond
      In message , Patrick writes ... The Optware feed now contains 3.4.5-4, this latest version seems to run just
      Message 2 of 5 , Feb 25, 2010
      • 0 Attachment
        In message <hls3si+oaom@...>, Patrick <patrick@...>
        writes

        >My main concern is with the panic and core dump log message. I added
        >your "touch" recommendation about printcap. I also also removed most
        >configuration files (smbpasswd, secrets, etc) and only left smb.conf.
        >
        The Optware feed now contains 3.4.5-4, this latest version seems to run
        just fine on the NSLU2 so should be OK on your device.

        --
        Robert Hammond
        PGP:0x154144DA
        592B 0199 2D7F FC05 C4B1 0404 2258 4471 1541 44DA
      Your message has been successfully submitted and would be delivered to recipients shortly.