[Samba] smb_panic
We upgraded several servers to samba version 3.0.23d. On a few sites there are messages as shown below. The reason for this message is that a workstation want to use a share as administrator. This account does not exist in a local tdb file. That is correct because we use LDAP as backend. In the LDAP an account administrator exists but it is not available for this domain (SID does not match). It seems to me that, although our administrator account is not logic and not as expected, there is no reason for this panic. The account is just invalid, nothing more then that. pdb_get_group_sid: Failed to find Unix account for Administrator [2006/11/22 09:52:08, 0] smbd/sec_ctx.c:push_sec_ctx(194) Security context stack overflow! [2006/11/22 09:52:08, 0] lib/util.c:smb_panic(1599) PANIC (pid 19575): Security context stack overflow! [2006/11/22 09:52:08, 0] lib/util.c:log_stack_trace(1706) BACKTRACE: 64 stack frames: #0 /usr/sbin/smbd(log_stack_trace+0x23) [0x822d683] #1 /usr/sbin/smbd(smb_panic+0x48) [0x822d508] #2 /usr/sbin/smbd(push_sec_ctx+0x1cc) [0x80da3dc] #3 /usr/sbin/smbd(become_root+0xb) [0x80d0e4b] #4 /usr/sbin/smbd [0x81ee10f] #5 /usr/sbin/smbd [0x81edbd0] #6 /usr/sbin/smbd(pdb_sid_to_id+0x29) [0x81ed1a9] #7 /usr/sbin/smbd(sid_to_gid+0x189) [0x81f2509] #8 /usr/sbin/smbd(pdb_set_group_sid+0x5f) [0x81e610f] #9 /usr/sbin/smbd(pdb_set_group_sid_from_rid+0x73) [0x81efa13] #10 /usr/sbin/smbd(init_sam_from_buffer_v3+0x750) [0x81e9550] #11 /usr/sbin/smbd(pdb_copy_sam_account+0x56) [0x81ea446] #12 /usr/sbin/smbd(pdb_getsampwsid+0xb0) [0x81eb840] #13 /usr/sbin/smbd [0x81ee11b] #14 /usr/sbin/smbd [0x81edbd0] #15 /usr/sbin/smbd(pdb_sid_to_id+0x29) [0x81ed1a9] #16 /usr/sbin/smbd(sid_to_gid+0x189) [0x81f2509] #17 /usr/sbin/smbd(pdb_set_group_sid+0x5f) [0x81e610f] #18 /usr/sbin/smbd(pdb_set_group_sid_from_rid+0x73) [0x81efa13] #19 /usr/sbin/smbd(init_sam_from_buffer_v3+0x750) [0x81e9550] #20 /usr/sbin/smbd(pdb_copy_sam_account+0x56) [0x81ea446] #21 /usr/sbin/smbd(pdb_getsampwsid+0xb0) [0x81eb840] #22 /usr/sbin/smbd [0x81ee11b] #23 /usr/sbin/smbd [0x81edbd0] #24 /usr/sbin/smbd(pdb_sid_to_id+0x29) [0x81ed1a9] #25 /usr/sbin/smbd(sid_to_gid+0x189) [0x81f2509] #26 /usr/sbin/smbd(pdb_set_group_sid+0x5f) [0x81e610f] #27 /usr/sbin/smbd(pdb_set_group_sid_from_rid+0x73) [0x81efa13] #28 /usr/sbin/smbd(init_sam_from_buffer_v3+0x750) [0x81e9550] #29 /usr/sbin/smbd(pdb_copy_sam_account+0x56) [0x81ea446] #30 /usr/sbin/smbd(pdb_getsampwsid+0xb0) [0x81eb840] #31 /usr/sbin/smbd [0x81ee11b] #32 /usr/sbin/smbd [0x81edbd0] #33 /usr/sbin/smbd(pdb_sid_to_id+0x29) [0x81ed1a9] #34 /usr/sbin/smbd(sid_to_gid+0x189) [0x81f2509] #35 /usr/sbin/smbd(pdb_set_group_sid+0x5f) [0x81e610f] #36 /usr/sbin/smbd(pdb_set_group_sid_from_rid+0x73) [0x81efa13] #37 /usr/sbin/smbd(init_sam_from_buffer_v3+0x750) [0x81e9550] #38 /usr/sbin/smbd(pdb_copy_sam_account+0x56) [0x81ea446] #39 /usr/sbin/smbd(pdb_getsampwsid+0xb0) [0x81eb840] #40 /usr/sbin/smbd [0x81ee11b] #41 /usr/sbin/smbd [0x81edbd0] #42 /usr/sbin/smbd(pdb_sid_to_id+0x29) [0x81ed1a9] #43 /usr/sbin/smbd(sid_to_gid+0x189) [0x81f2509] #44 /usr/sbin/smbd(pdb_set_group_sid+0x5f) [0x81e610f] #45 /usr/sbin/smbd(pdb_set_group_sid_from_rid+0x73) [0x81efa13] #46 /usr/sbin/smbd(init_sam_from_buffer_v3+0x750) [0x81e9550] #47 /usr/sbin/smbd(pdb_copy_sam_account+0x56) [0x81ea446] #48 /usr/sbin/smbd(pdb_getsampwsid+0xb0) [0x81eb840] #49 /usr/sbin/smbd [0x81ee11b] #50 /usr/sbin/smbd [0x81edbd0] #51 /usr/sbin/smbd(pdb_sid_to_id+0x29) [0x81ed1a9] #52 /usr/sbin/smbd(sid_to_gid+0x189) [0x81f2509] #53 /usr/sbin/smbd(pdb_set_group_sid+0x5f) [0x81e610f] #54 /usr/sbin/smbd(pdb_set_group_sid_from_rid+0x73) [0x81efa13] #55 /usr/sbin/smbd(init_sam_from_buffer_v3+0x750) [0x81e9550] #56 /usr/sbin/smbd(pdb_copy_sam_account+0x56) [0x81ea446] #57 /usr/sbin/smbd(pdb_getsampwsid+0xb0) [0x81eb840] #58 /usr/sbin/smbd [0x81ee11b] #59 /usr/sbin/smbd [0x81edbd0] #60 /usr/sbin/smbd(pdb_sid_to_id+0x29) [0x81ed1a9] #61 /usr/sbin/smbd(sid_to_gid+0x189) [0x81f2509] #62 /usr/sbin/smbd(pdb_set_group_sid+0x5f) [0x81e610f] #63 /usr/sbin/smbd(pdb_set_group_sid_from_rid+0x73) [0x81efa13] Regards, Ruud Baart -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbpasswd overwrites existing displayname in LDAP entry
Made mistake in my question, sorry. Question should be: Configuration: Samba 2.2.8a with openLDAP 2.1.30 on a SeSE 8.2. server When adding a user using a ldif file we give the user a displayName, say Ruud Baart. The cn and uid are the same, say 21cs12345 (a studentnumber). After adding the user to LDAP the displayname is as expected: "Ruud Baart". However after "smbpasswd -a 21cs12345 -s secret" the displayname is suddenly "21cs12345". That is, of course, not what we want. Is there any solution for this problem? Met vriendelijke groet/Regards, Prompt R.J. Baart Kerkstraat 173 5261 CW Vught Netherlands Http://WWW.Prompt.NL Tel.: +31 73 6567041 Fax.: +31 73 6573513 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] smbpasswd overwrites existing displayname in LDAP entry
Configuration: Samba 2.2.8a with openLDAP 2.1.30 on a SeSE 8.2. server When adding a user using a ldif file we give the user a given name, say Ruud Baart. The cn and uid are the same, say 21cs12345 (a studentnumber). After adding the user to LDAP the displayname is as expected: "Ruud Baart". However after smbpasswd -a 21cs12345 -s secret the displayname is "21cs12345". That is, of course, not what we want. Is there any solution for this problem? Met vriendelijke groet/Regards, Prompt R.J. Baart Kerkstraat 173 5261 CW Vught Netherlands Http://WWW.Prompt.NL Tel.: +31 73 6567041 Fax.: +31 73 6573513 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] ldap problem
We use samba 2.2.8a, openldap 2.1.12 When adding a workstation to the PDC normally a machine account is added with a script (e.g. /usr/local/bin/smbaddmachine). The script runs with the userid root. That is neccesary because smbpasswd requires root-id for running: smbpasswd -m -a machinename We have written a shellscript that works fine: an account is added to the LDAP tree and sambaaccount is added with smbpasswd. It works only from the commandline and it must be run as root because of smbpasswd. When using this script from an unattend install from a W2K client it won't work because root is in /etc/passwd and not in de LDAP tree. But we can't add root as a samba account because root is not in de LDAP tree. So we can't use root as account to run the script. Using another userid is not possible because smbpasswd requires root. Sudo smbpasswd won't because all samba userid are not in /etc/passwd but in de LDAP tree and therefore they can't run sudo. Any idea how to solve this problem? Met vriendelijke groet/Regards, Prompt R.J. Baart Marktveldpassage 35c 5261 ED Vught Netherlands Mailto:[EMAIL PROTECTED] Http://WWW.Prompt.NL Tel.: +31 73 6567041 Fax.: +31 73 6573513 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] High cpu load
Server is PII-350MHz/256 MB RAM, hardware mirrored high speed SCSI disks. Installed is SuSE 8.2 with Samba 2.2.8a RPM, XFS filesystems and LPRng as printservices. Server acts as PDC and WINS server. Clients are W2K SP2 (a few with SP3). There are +/- 100 clients. We see a server that is 100% busy and we see during a long time a very high CPU load (60- 95%) related to one W2K client. When this smbd process is finished (can take more then an hour) or killed there is a very big change another client behaves the same way. The server is in use for one week now. The first days the server didn't have any problems as far as we know. We think -- but are not sure -- the problematic behavior of a W2K client starts during a login because the files in use are related to connecting to the printers and reading the printerdrivers. In the logfile we see quite a lot of lock problems: Jun 30 10:31:54 ux-254 smbd[13838]: [2003/06/30 10:31:54, 0] smbd/oplock.c:request_oplock_break(1011) Jun 30 10:31:54 ux-254 smbd[13838]: request_oplock_break: no response received to oplock break request to pid 15915 on port 37496 for dev = 811, inode = 130892307, file_id = 252 Jun 30 10:31:54 ux-254 smbd[3002]: [2003/06/30 10:31:54, 0] smbd/oplock.c:request_oplock_break(1011) Jun 30 10:31:54 ux-254 smbd[3002]: request_oplock_break: no response received to oplock break request to pid 15915 on port 37496 for dev = 811, inode = 130892307, file_id = 252 Jun 30 10:31:54 ux-254 smbd[3208]: [2003/06/30 10:31:54, 0] smbd/oplock.c:request_oplock_break(1011) Jun 30 10:31:54 ux-254 smbd[3208]: request_oplock_break: no response received to oplock break request to pid 15915 on port 37496 for dev = 811, inode = 130892307, file_id = 252 Jun 30 10:31:54 ux-254 smbd[3389]: [2003/06/30 10:31:54, 0] smbd/oplock.c:request_oplock_break(1011) Jun 30 10:31:54 ux-254 smbd[3389]: request_oplock_break: no response received to oplock break request to pid 15915 on port 37496 for dev = 811, inode = 130892307, file_id = 252 Jun 30 10:31:54 ux-254 smbd[24402]: [2003/06/30 10:31:54, 0] smbd/oplock.c:request_oplock_break(1011) Jun 30 10:31:54 ux-254 smbd[24402]: request_oplock_break: no response received to oplock break request to pid 15915 on port 37496 for dev = 811, inode = 130892307, file_id = 252 Below an example of top and smbstatus: TOP top - 09:56:49 up 9 days, 12:00, 2 users, load average: 1.26, 1.25, 1.36 Tasks: 157 total, 3 running, 154 sleeping, 0 stopped, 0 zombie Cpu(s): 39.2% user, 60.8% system, 0.0% nice, 0.0% idle Mem:255960k total, 228220k used,27740k free, 112k buffers Swap: 514072k total,31172k used, 482900k free,95540k cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ Command 15915 xxx 25 0 3168 2828 2268 R 91.9 1.1 22:58.51 smbd SMBSTATUS Samba version 2.2.8a-SuSE Service uid gid pid machine -- user user groupid 15915 w00a0245751e0 (192.168.246.80) Mon Jun 30 09:30:18 2003 user user groupid 15977 w00a0245751e0 (192.168.246.80) Mon Jun 30 09:31:38 2003 applicatie user groupid 15915 w00a0245751e0 (192.168.246.80) Mon Jun 30 09:30:21 2003 applicatie user groupid 15977 w00a0245751e0 (192.168.246.80) Mon Jun 30 09:33:16 2003 docs user groupid 15915 w00a0245751e0 (192.168.246.80) Mon Jun 30 09:30:21 2003 profile user groupid 15915 w00a0245751e0 (192.168.246.80) Mon Jun 30 09:30:03 2003 print$ user beheer 15915 w00a0245751e0 (192.168.246.80) Mon Jun 30 09:30:30 2003 netlogon user beheer 15915 w00a0245751e0 (192.168.246.80) Mon Jun 30 09:30:17 2003 docs user groupid 15977 w00a0245751e0 (192.168.246.80) Mon Jun 30 09:33:16 2003 IPC$ user groupid 15915 w00a0245751e0 (192.168.246.80) Mon Jun 30 09:30:20 2003 user user groupid 15915 w00a0245751e0 (192.168.246.80) Mon Jun 30 09:30:21 2003 IPC$ user groupid 15977 w00a0245751e0 (192.168.246.80) Mon Jun 30 09:31:43 2003 netlogon user beheer 15915 w00a0245751e0 (192.168.246.80) Mon Jun 30 09:30:19 2003 Locked files: PidDenyMode Access R/WOplock Name -- 15915 DENY_WRITE 0x20089 RDONLY NONE /home/holleweg/printers/W32X86/3/UNIDRVUI.DLL Mon Jun 30 09:30:30 2003 15915 DENY_WRITE 0x20089 RDONLY NONE /home/holleweg/printers/W32X86/3/TTFSUB.GPD Mon Jun 30 09:30:30 2003 15915 DENY_WRITE 0x20089 RDONLY NONE /home/holleweg/printers/W32X86/3/xxui3a.dll Mon Jun 30 09:30:30 2003 15915 DENY_WRITE 0x20089 RDONLY NONE /home/holleweg/printers/W32X86/3/XCWFAX32.EXE Mon Jun 30 09:30:30 2003 15915 DENY_WRITE 0x20089 RDONLY NONE /home/holleweg/printers/W32X86/3/UNIDRV.DLL Mon Jun 30 09:30:30 2003 15915 DENY_WRITE 0x20089 RDONLY NONE /home/holleweg/printers/
Re: [Samba] LPR or LPRng or CUPS
In our opion: use LPRng. We like cups, but we have had several time consuming problems with cups. We also don't use the "old" BSD lpr/lpd services. We choose the combination LPRng and raw tcpip on port 9100 (jetdirect). This gives bidirectional communication between printer and server. Very useful, good debugging information. Met vriendelijke groet/Regards, Prompt R.J. Baart Marktveldpassage 35c 5261 ED Vught Netherlands Mailto:[EMAIL PROTECTED] Http://WWW.Prompt.NL Tel.: +31 73 6567041 Fax.: +31 73 6573513 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] printer admin problems with 2.2.4
We upgraded from 2.2.3a to 2.2.4 on a SuSE 7.2 server. We compiled Samba just default. The new version seems to work ok with the exception of printer administration. Printer admins are not able to see the properties of the printers (right click on printer gives on error). Our workstations are W2k SP2. But users that are not printer admin are able to see the properties of a printer, but they are not allowed to change the settings or to upload drivers. I don't think it is important, but we use the latest lprng- version as printserver. * We tried the patch on the file rpc_parse/parse_spoolss.c * We tried the current CVS version * We installed the whole samba from scratch (new tdb-files) All no difference. With a lot of debugging on we can't see what is the problem. Any ideas? Met vriendelijke groet/Regards, Prompt R.J. Baart Marktveldpassage 35c 5261 ED Vught Netherlands Mailto:[EMAIL PROTECTED] Http://WWW.Prompt.NL Tel.: +31 73 6567041 Fax.: +31 73 6573513 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] W2k devmode
Our server is a SuSE Linux 7.2 with CVS samba 2.2 branche. Version number is 2.2.pre-4. We updated today. We have a problem with the default devmode in Windows 2000 (SP2) clients. We have uploaded the printerdrivers to the share print$. The Samba printeradministrator is able to change the printer capabilities as memory, trays, papersize. etc. Changes are global: when a user logs in, he sees the new global printersettings. In Europe we use page size A4. So far, so good. But the default printersettings per user are not conform the settings the printeradministrator made. We don't know why. To be more specific: we want all users to have as default pagesize not "Letter" but "A4". Althoud the administrator set all papersizes to A4 the default user setting is "Letter". This default user printersettings are saved in the register, several places in "HKEY_CURRENT_USER\Printers". Before allowing the user to make his own settings we: - We made paperformat adjustments to the ppd-file in appriate directory in the print$- share - We made a paperadjustment adjustment in the samba source (nt_printing.c) and replaced the default "Letter" by "A4". We also changed PAPER_LETTER to PAPER_A4. - In the registerkeys HKEY_CURRENT_USER\Printers all devmodes were absent or removed. Still the default peruser papersize setting is Letter. We changed the smb.conf file and added "default devmode = Yes". We expected with the last adjustment that a default devmode was generated when there is no key in HKEY_CURRENT_USER\Printers. But even now the "Letter"-format is the default for the peruser printersettings. How is that possible? Can we do something to change this behaviour? Met vriendelijke groet/Regards, Prompt R.J. Baart Marktveldpassage 35c 5261 ED Vught Netherlands Mailto:[EMAIL PROTECTED] Http://WWW.Prompt.NL Tel.: +31 73 6567041 Fax.: +31 73 6573513 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
