My Oracle Support Banner

Solaris 10 Samba Enters Maintenance Mode And smbd Core Dumps Due To Printer Failures (Doc ID 1569559.1)

Last updated on OCTOBER 12, 2019

Applies to:

Solaris Operating System - Version 10 10/09 U8 to 10 1/13 U11 [Release 10.0]
Information in this document applies to any platform.

Symptoms

On a Solaris 10 systems after installing Samba Patch 119757-27, that upgrades Samba to version 3.6.12 , the Samba SMF service may enter into maintenance mode due to repeated smbd core dumps. The failure occurs on the Samba operations that automatically load LP printer information from the operating system environment.

The /var/svc/log/network-samba:default.log would contain the following:

[ Jul  9 09:56:05 Leaving maintenance because clear requested. ]
[ Jul  9 09:56:05 Enabled. ]
[ Jul  9 09:56:05 Executing start method ("/lib/svc/method/samba start /usr/sbin/smbd -D") ]
[ Jul  9 09:56:05 Method "start" exited with status 0 ]
[ Jul  9 10:18:25 Stopping because process dumped core. ]
[ Jul  9 10:18:25 Executing stop method ("/lib/svc/method/samba stop 857") ]
[ Jul  9 10:18:30 Method "stop" exited with status 0 ]
[ Jul  9 10:18:30 Executing start method ("/lib/svc/method/samba start /usr/sbin/smbd -D") ]
[ Jul  9 10:18:31 Method "start" exited with status 0 ]
[ Jul  9 10:24:56 Stopping because process dumped core. ]
[ Jul  9 10:24:57 Executing stop method ("/lib/svc/method/samba stop 868") ]
[ Jul  9 10:25:02 Method "stop" exited with status 0 ]
[ Jul  9 10:25:02 Executing start method ("/lib/svc/method/samba start /usr/sbin/smbd -D")

 

A pstack command run on the smbd core file would contain the following stack dump:


core 'smbd.core' of 28702: /usr/sbin/smbd -D
fefaebd4 _lwp_kill (6, 0, 0, fef8e0f0, ffffffff, 6) + 8
fef229f0 abort    (7c10, 1, 974284, ffb04, ff025518, 0) + 110
003ca534 fault_report (b, 701e, a12d58, 85be6c, 6ce765, 97be78) + 1bc
fefab00c __sighndlr (b, 0, ffbfe8e8, 3ca598, 0, 1) + c
fef9f6bc call_user_handler (b, 400, 4, 0, ff072a00, ffbfe8e8) + 3b8
fef9f8a4 sigacthandler (b, 0, ffbfe8e8, 6c7ee9, 0, 0) + 60
--- called from signal handler with signal 11 (SIGSEGV) ---
0028fc38 enum_all_printers_info_1_name (a26d58, a20e88, a18220, 0, a44a08, a449c8) + 7c
002901d4 _spoolss_EnumPrinters (a1e4d0, a445b8, 7c57e4, a445cc, a20e88, 974268) + 184
0029c5b4 api_spoolss_EnumPrinters (a1e4d0, 7c00, a44618, a445b8, a17a00, 66ef9c) + 1ac
002d6acc api_rpcTNP (a1e4d0, a26a88, 97b248, 6e, 7e84a0, 97b248) + 258
002d683c api_pipe_request (a1e4d0, a26a88, a37268, 1, a26aa0, 7e83a8) + 198
002d7804 process_complete_pdu (a1e4d0, 7e8dcc, 0, 234, a26a88, 974268) + 5e4
002d7fd0 process_incoming_data (a1e4d0, a44188, 224, 224, 69c444, 974268) + 1b8
002d80c8 write_to_internal_pipe (a1e4d0, a44188, 234, 0, 224, 974268) + 94
002d8810 np_write_send (a44138, a13f88, a43c68, a44178, 234, a443e8) + f0
000b2cb0 api_dcerpc_cmd (a44138, 234, a20690, 6db918, 974268, 1000) + 138
000b3910 named_pipe (a232f8, 0, a44068, a26a26, a46050, a45d80) + 1d8
000b3cac handle_trans (a44068, 6, a26998, 6dbf10, 7c10, a232f8) + 210
000b43a0 reply_trans (a44068, a43dcf, a26998, 6dbf64, 2, a232f8) + 6c4
0011d340 switch_message (25, a44068, 28c, a232f8, c0000000, b3cdc) + 564
0011d4b0 construct_reply (a14000, a43da8, 6f75f0, 0, 0, a440a8) + 15c
0011d768 process_smb (a14000, a43da8, 28c, 0, 0, 0) + 1a0
0011e8c4 smbd_server_connection_read_handler (a14000, 8, 8, 0, 974268, 27c800) + 1c0
003ec958 run_events_poll (a13f88, 1, a35f20, 11e8d4, a1deb0, 587da4) + 49c
0011c9e4 smbd_server_connection_loop_once (a14000, a13370, 0, ea60, 3, e800) + d4
00120b88 smbd_process (a14000, c000022d, ffbff5c4, a19e40, a13f88, 6f8808) + a0c
006bcc84 smbd_accept_connection (a13f88, a18220, 10c00, 96341c, 974268, a13f88) + 3c0
003ec958 run_events_poll (a13f88, 1, a47858, 6bc8c4, a454d0, 587da4) + 49c
003ecc7c s3_event_loop_once (a13f88, 7fffffff, 7ffffc00, 587710, 974268, a1a258) + 128
003edac4 _tevent_loop_once (a13f88, 9638f0, 974268, 0, 582cd0, 7c00) + a0
006bd6ac smbd_parent_loop (a17a00, 97be78, a190f8, 7c10, 2b6c44, 7c00) + 8c
006be534 main     (0, ff732024, a139e0, 964004, a13f88, 974268) + e04
00091618 _start   (0, 0, 0, 0, 0, 0) + 108

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.