Just an internal note: same assert message as in https://bugzilla.samba.org/show_bug.cgi?id=10764

I don't know if this is helpful, but I am seeing identical panics on a Debian system which started immediately after an update from Wheezy to Jessie (i.e. from smbd version 3.6.6 to smbd version 4.1.17-Debian). In the two weeks since the upgrade I have received 1500 panic email messages.

On this system I'm seeing panics in the logs relating to four Windows 7 64-bit clients, one Windows Vista 32-bit client, and one Windows 10 64-bit client. It doesn't seem to matter which client I use, any of them will reproduce the panic. For example, adding the shared printer (a USB connected HP 1018) to the Windows 10 64-bit client and attempting to print a test page resulted in 10 panics.

Relevant lines in smb.conf:

   load printers = yes
   printing = cups
   printcap name = cups

[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700

A typical panic:

  STATUS=daemon 'smbd' finished starting up and ready to serve connectionsPANIC: assert failed at ../source3/printing/printing.c(486): pjob->jobid == jobid
[2015/09/16 14:08:38.733610,  0] ../source3/lib/util.c:785(smb_panic_s3)
  PANIC (pid 17433): assert failed: pjob->jobid == jobid
[2015/09/16 14:08:38.734338,  0] ../source3/lib/util.c:896(log_stack_trace)
  BACKTRACE: 27 stack frames:
   #0 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(log_stack_trace+0x1a) [0x7fcf940b62ca]
   #1 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x20) [0x7fcf940b63b0]
   #2 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) [0x7fcf95835caf]
   #3 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(+0x86db2) [0x7fcf9537adb2]
   #4 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(print_queue_status+0x626) [0x7fcf95380e86]
   #5 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(_spoolss_EnumJobs+0x165) [0x7fcf954a27b5]
   #6 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(+0x1c4ff9) [0x7fcf954b8ff9]
   #7 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(+0x1a001b) [0x7fcf9549401b]
   #8 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(process_complete_pdu+0x1134) [0x7fcf95495bf4]
   #9 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(process_incoming_data+0xf0) [0x7fcf954913a0]
   #10 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(np_write_send+0x168) [0x7fcf95491ac8]
   #11 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(smb2_ioctl_named_pipe+0x9d) [0x7fcf9543bc5d]
   #12 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(smbd_smb2_request_process_ioctl+0x820) [0x7fcf9543b400]
   #13 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(smbd_smb2_request_dispatch+0xb6b) [0x7fcf9542c3bb]
   #14 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(+0x139251) [0x7fcf9542d251]
   #15 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(+0x139ddc) [0x7fcf9542dddc]
   #16 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(run_events_poll+0x171) [0x7fcf940d4da1]
   #17 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(+0x44017) [0x7fcf940d5017]
   #18 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d) [0x7fcf92a85f9d]
   #19 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(smbd_process+0xdb4) [0x7fcf95419ce4]
   #20 /usr/sbin/smbd(+0xa1d0) [0x7fcf95e9a1d0]
   #21 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(run_events_poll+0x171) [0x7fcf940d4da1]
   #22 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(+0x44017) [0x7fcf940d5017]
   #23 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d) [0x7fcf92a85f9d]
   #24 /usr/sbin/smbd(main+0x1589) [0x7fcf95e96f19]
   #25 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fcf926fab45]
   #26 /usr/sbin/smbd(+0x713b) [0x7fcf95e9713b]
[2015/09/16 14:08:38.734591,  0] ../source3/lib/util.c:797(smb_panic_s3)
  smb_panic(): calling panic action [/usr/share/samba/panic-action 17433]
[2015/09/16 14:08:38.937080,  0] ../source3/lib/util.c:805(smb_panic_s3)
  smb_panic(): action returned status 0
[2015/09/16 14:08:38.937165,  0] ../source3/lib/dumpcore.c:317(dump_core)
  dumping core in /var/log/samba/cores/smbd

Thanks for the report. Please capture level 10 logs and the network traffic across the print attempt prior to the panic.
See https://wiki.samba.org/index.php/Capture_Packets for details.

I have just upgraded to Debian Jessie and everything seems to be OK apart from printing from a windows machine to my print share. This was working previously under wheezy. I can print a test page from Cups without any problems, but when I try and print from windows, Samba seems to crash completely and is constantly writing these messages to the logs. Then I lose access to the other shares, presumably while it repeatedly crashes.

STATUS=daemon 'smbd' finished starting up and ready to serve connectionsPANIC: assert failed at ../source3/printing/printing.c(486): pjob->jobid == jobid
[2015/09/22 12:02:03.989596, 0] ../source3/lib/util.c:785(smb_panic_s3)
PANIC (pid 3704): assert failed: pjob->jobid == jobid
[2015/09/22 12:02:03.991930, 0] ../source3/lib/util.c:896(log_stack_trace)
BACKTRACE: 27 stack frames:
#0 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(log_stack_trace+0x1a) [0x7fafbbcbc2ca]
#1 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x20) [0x7fafbbcbc3b0]
#2 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) [0x7fafbd43bcaf]
#3 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(+0x86db2) [0x7fafbcf80db2]
#4 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(print_queue_status+0x626) [0x7fafbcf86e86]
#5 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(_spoolss_EnumJobs+0x165) [0x7fafbd0a87b5]
#6 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(+0x1c4ff9) [0x7fafbd0beff9]
#7 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(+0x1a001b) [0x7fafbd09a01b]
#8 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(process_complete_pdu+0x1134) [0x7fafbd09bbf4]
#9 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(process_incoming_data+0xf0) [0x7fafbd0973a0]
#10 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(np_write_send+0x168) [0x7fafbd097ac8]
#11 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(smb2_ioctl_named_pipe+0x9d) [0x7fafbd041c5d]
#12 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(smbd_smb2_request_process_ioctl+0x820) [0x7fafbd041400]
#13 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(smbd_smb2_request_dispatch+0xb6b) [0x7fafbd0323bb]
#14 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(+0x139251) [0x7fafbd033251]
#15 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(+0x139ddc) [0x7fafbd033ddc]
#16 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(run_events_poll+0x171) [0x7fafbbcdada1]
#17 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(+0x44017) [0x7fafbbcdb017]
#18 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d) [0x7fafba68bf9d]
#19 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0(smbd_process+0xdb4) [0x7fafbd01fce4]
#20 /usr/sbin/smbd(+0xa1d0) [0x7fafbdaa01d0]
#21 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(run_events_poll+0x171) [0x7fafbbcdada1]
#22 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(+0x44017) [0x7fafbbcdb017]
#23 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d) [0x7fafba68bf9d]
#24 /usr/sbin/smbd(main+0x1589) [0x7fafbda9cf19]
#25 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fafba300b45]
#26 /usr/sbin/smbd(+0x713b) [0x7fafbda9d13b]
[2015/09/22 12:02:03.992732, 0] ../source3/lib/util.c:797(smb_panic_s3)
smb_panic(): calling panic action [/usr/share/samba/panic-action 3704]
[2015/09/22 12:02:04.319186, 0] ../source3/lib/util.c:805(smb_panic_s3)
smb_panic(): action returned status 0
[2015/09/22 12:02:04.319510, 0] ../source3/lib/dumpcore.c:317(dump_core)
dumping core in /var/log/samba/cores/smbd

(In reply to Ryan from comment #4)
@Ryan: thanks for the report. Please provide the information requested in comment#3.

Created attachment 11461 [details]
Samba and wireshark logs

Created attachment 11462 [details]
More Samba logs

I don't think I got the error on my first attempt, but this definitely did. Tried to print test page (which actually worked) and then usual errors started so captured Samba logs again

Same problem here - sernet-samba 4.1.21-10, cups 1.7.2

Nov  2 14:06:48 prod1 smbd[27839]: [2015/11/02 14:06:48.886991,  0, pid=27839, effective(1177, 513), real(1177, 0)] ../source3/printing/printing.c:486(print_job_find)
Nov  2 14:06:48 prod1 smbd[27839]:   PANIC: assert failed at ../source3/printing/printing.c(486): pjob->jobid == jobid
Nov  2 14:06:48 prod1 smbd[27839]: [2015/11/02 14:06:48.887173,  0, pid=27839, effective(1177, 513), real(1177, 0)] ../source3/lib/util.c:785(smb_panic_s3)
Nov  2 14:06:48 prod1 smbd[27839]:   PANIC (pid 27839): assert failed: pjob->jobid == jobid
Nov  2 14:06:48 prod1 smbd[27839]: [2015/11/02 14:06:48.888290,  0, pid=27839, effective(1177, 513), real(1177, 0)] ../source3/lib/util.c:896(log_stack_trace)
Nov  2 14:06:48 prod1 smbd[27839]:   BACKTRACE: 27 stack frames:
Nov  2 14:06:48 prod1 smbd[27839]:    #0 /usr/lib/x86_64-linux-gnu/samba/libsmbconf.so.0(log_stack_trace+0x1a) [0x7f12411b92b7]
Nov  2 14:06:48 prod1 smbd[27839]:    #1 /usr/lib/x86_64-linux-gnu/samba/libsmbconf.so.0(smb_panic_s3+0x55) [0x7f12411b93b5]
Nov  2 14:06:48 prod1 smbd[27839]:    #2 /usr/lib/x86_64-linux-gnu/samba/libsamba-util.so.0(smb_panic+0x2d) [0x7f1242cf9aa9]
Nov  2 14:06:48 prod1 smbd[27839]:    #3 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so(+0x6d4aa) [0x7f12428684aa]
Nov  2 14:06:48 prod1 smbd[27839]:    #4 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so(print_queue_status+0x607) [0x7f124286dfcc]
Nov  2 14:06:48 prod1 smbd[27839]:    #5 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so(_spoolss_EnumJobs+0x188) [0x7f124298c70a]
Nov  2 14:06:48 prod1 smbd[27839]:    #6 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so(+0x1a4f49) [0x7f124299ff49]
Nov  2 14:06:48 prod1 smbd[27839]:    #7 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so(+0x181b9e) [0x7f124297cb9e]
Nov  2 14:06:48 prod1 smbd[27839]:    #8 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so(process_complete_pdu+0x64c) [0x7f124297da28]
Nov  2 14:06:48 prod1 smbd[27839]:    #9 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so(process_incoming_data+0x3b1) [0x7f124297b05d]
Nov  2 14:06:48 prod1 smbd[27839]:    #10 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so(np_write_send+0x13f) [0x7f124297b404]
Nov  2 14:06:48 prod1 smbd[27839]:    #11 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so(smb2_ioctl_named_pipe+0x112) [0x7f1242921768]
Nov  2 14:06:48 prod1 smbd[27839]:    #12 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so(smbd_smb2_request_process_ioctl+0x76d) [0x7f1242920ef3]
Nov  2 14:06:48 prod1 smbd[27839]:    #13 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so(smbd_smb2_request_dispatch+0xc02) [0x7f124291273d]
Nov  2 14:06:48 prod1 smbd[27839]:    #14 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so(+0x11848c) [0x7f124291348c]
Nov  2 14:06:48 prod1 smbd[27839]:    #15 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so(+0x118dbe) [0x7f1242913dbe]
Nov  2 14:06:48 prod1 smbd[27839]:    #16 /usr/lib/x86_64-linux-gnu/samba/libsmbconf.so.0(run_events_poll+0x2ca) [0x7f12411d598e]
Nov  2 14:06:48 prod1 smbd[27839]:    #17 /usr/lib/x86_64-linux-gnu/samba/libsmbconf.so.0(+0x3daef) [0x7f12411d5aef]
Nov  2 14:06:48 prod1 smbd[27839]:    #18 /usr/lib/x86_64-linux-gnu/samba/libtevent.so.0(_tevent_loop_once+0x87) [0x7f12425f1a9d]
Nov  2 14:06:48 prod1 smbd[27839]:    #19 /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so(smbd_process+0xed6) [0x7f12428ff745]
Nov  2 14:06:48 prod1 smbd[27839]:    #20 /usr/sbin/smbd(+0x8aa0) [0x7f1243361aa0]
Nov  2 14:06:48 prod1 smbd[27839]:    #21 /usr/lib/x86_64-linux-gnu/samba/libsmbconf.so.0(run_events_poll+0x2ca) [0x7f12411d598e]
Nov  2 14:06:48 prod1 smbd[27839]:    #22 /usr/lib/x86_64-linux-gnu/samba/libsmbconf.so.0(+0x3daef) [0x7f12411d5aef]
Nov  2 14:06:48 prod1 smbd[27839]:    #23 /usr/lib/x86_64-linux-gnu/samba/libtevent.so.0(_tevent_loop_once+0x87) [0x7f12425f1a9d]
Nov  2 14:06:48 prod1 smbd[27839]:    #24 /usr/sbin/smbd(main+0x174a) [0x7f124336352e]
Nov  2 14:06:48 prod1 smbd[27839]:    #25 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f123fc28ec5]
Nov  2 14:06:48 prod1 smbd[27839]:    #26 /usr/sbin/smbd(+0x59a9) [0x7f124335e9a9]
Nov  2 14:06:48 prod1 smbd[27839]: [2015/11/02 14:06:48.889363,  0, pid=27839, effective(0, 0), real(0, 0)] ../source3/lib/dumpcore.c:317(dump_core)
Nov  2 14:06:48 prod1 smbd[27839]:   dumping core in /var/log/samba/cores/smbd

changed this in my smb.conf to get only the printing process crashed:

enable spoolss = yes
rpc_server:spoolss = external
rpc_daemon:spoolssd = fork
spoolssd:prefork_min_children = 5           # Minimum number of child processes
        spoolssd:prefork_max_children = 25          # Maximum number of child processes
spoolssd:prefork_spawn_rate = 5             # Start (fork) x new childs if one connection comes in (up to prefork_max_children)
        spoolssd:prefork_max_allowed_clients = 100  # Number of clients, a child process should be responsible for
spoolssd:prefork_child_min_life = 60        # Minimum lifetime of a child process (60 seconds is the minimum)

No new panic messages since I moved the server to another physical machine, more than one month ago.

The move was made by making a new install from scratch (Debian 8)
and copying user data with rsync. The old machine was installed in 2007
and dist-upgraded from Debian stable to Debian stable since then.

Do I need gdb installed for the panic email messages to be sent?

The only explanation I can find for this is that the panic messages
were triggered by some corrupted binary cache file which is either no longer
present in the new machine or created successfully after a new install.

Unfortunately, I don't have any data to back such theory.

People who were able to reproduce this in the past could maybe say if they still can reproduce it with version 2:4.1.17+dfsg-2+deb8u2 from security.debian.org, released 2016-03-16, as it contains fixes for several CVE bugs.

Thanks.

We could localize a print which caused the problem, every time someone accessed that printer we got that samba panic!
After deleting and reinstalling of that printer everything was ok.

I've hitted that bug, again after an upgrade to jessie.

I've narrowed down the trouble, and identified the guilty on a Samsung SCX-4833 MFD, using (windows) driver 'Samsung SCX-483x 5x3x Series'.

Now i try to upgrade the driver...

I've tried to upgrade and downgrade the driver, no luck.

I've also tried to change completely the driver, using the postscript generic driver.

Nope. Every time the user (that have the printer installed on their profile) open the printer folder (control panel or by the way of an application) samba panic.


Boh...

I didn't see any crash like this in recent samba versions. CLosing as worksforme, feel free to reopen if you can still reproduce this issue with the latest 4.13 or 4.14 releases.