win10/64位 使用ubuntu16.04.2/64位共享打印机问题

[hanlif]

win10/64位 使用ubuntu16.04.2/64位共享打印机问题:
访问共享文件夹正常,正常添加共享打印机,但问题是每开一次win10机,能打印一次,再次打印还得重新开机,网上说win10打印服务可能临时关闭,但重新启动打印服务,有时候可以,有时候不可以,打印机型号BROTHER MFC-J3520

[poloshiao]

打印机型号BROTHER MFC-J3520

1. http://support.brother.com/g/b/spec.asp ... 0_eu_as_cn
Interfaces
USB A USB 2.0 interface cable that is no longer than 2 m.
LAN cable Ethernet UTP cable category 5 or greater.
Wireless LAN IEEE 802.11b/g/n (Infrastructure/Ad-hoc Mode)
IEEE 802.11g/n (Wi-Fi Direct)
1-1. 該型號印表機共有 3 個界面 USB / 有線 / 無線
你使用 哪一種 界面 ？
1-2. 如果是 USB
參考這一篇 看看 有沒有幫助
http://www.zedt.eu/tech/windows/install ... indows-10/
Installing an IPP printer in Windows 10
or, my personal choice, set it up on a Raspberry PI and share it with the world.

ubuntu16.04.2/64

1-2-1. 此處的 Raspberry PI 你可以假設是 ubuntu16.04.2/64

2. 上述 1-1. 的 3 個界面 USB / 有線 / 無線
無論是哪一種
都可以使用 CUPS 提供的 網頁界面 幫助你 測試
https://help.ubuntu.com/16.04/servergui ... l#cups-web
在 Ubuntu 或 Windows 瀏覽器 輸入
http://IPv4:631/admin
上述 IPv4 指 BROTHER MFC-J3520 連接的那一台 PC 的 IPv4
2-1. 如果 USB 是連接在 IP 分享器 或 路由器 需要確認 該 IP 分享器 或 路由器 是否支援 CUPS.

[hanlif]

UBUNRU与打印机USB连接,目前具体情况是,WIN7系统所有电脑用我的Ubuntu打印机一切正常,只有一台win10发生这种情况,其他win10正常;我电脑又增加了个win10系统,问题的电脑能用我的win10打印机正常.

[poloshiao]

UBUNRU 与 打印机 USB 连接

USB 直接插在 Ubuntu 機器上 還是 插在 IP 分享器 或 路由器 上面 ? (後面需要 IP 分享器 或 路由器 有此功能)

只有一台 win10 发生这种情况,其他 win10 正常;

BROTHER MFC-J3520

核對一下 設定 有沒有遺漏
http://www.zedt.eu/tech/windows/install ... indows-10/
Installing an IPP printer in Windows 10
The steps below assume that the printer is already configured and available via CUPS.

[hanlif]

usb连接，那台win10不是每次不能打，是每次打印前需要重新启动下printer spools服务，看状态其实这个服务没有关闭，是必须重新启动下

[poloshiao]

那台win10不是每次不能打，是每次打印前需要重新启动下printer spools服务，看状态其实这个服务没有关闭，是必须重新启动下

只有一台win10发生这种情况,其他win10正常

1. 如果 其它 Win 10 正常 只有 這一台 不正常
優先從 這一台 Win 10 的設定 或 紀錄檔 檢查或比較

2. 另一個思考方向 是查閱 CUPS 的 記錄檔 /var/log/cups/error_log 看看 有沒有 相關資訊
2-1. 記錄內容可以更改 LogLevel 讓它更詳細
2-2. https://help.ubuntu.com/16.04/servergui ... stallation
For troubleshooting purposes, you can access CUPS server errors via the error log file at: /var/log/cups/error_log. If the error log does not show enough information to troubleshoot any problems you encounter, the verbosity of the CUPS log can be increased by changing the LogLevel directive in the configuration file (discussed below) to "debug" or even "debug2", which logs everything, from the default of "info". If you make this change, remember to change it back once you've solved your problem, to prevent the log file from becoming overly large.

[hanlif]

[2017/03/28 11:24:40.882394, 0] ../source3/smbd/uid.c:317(change_to_user_internal)
PANIC: assert failed at ../source3/smbd/uid.c(317): conn->force_group_gid != (gid_t)-1
[2017/03/28 11:24:40.882475, 0] ../source3/lib/util.c:789(smb_panic_s3)
PANIC (pid 12030): assert failed: conn->force_group_gid != (gid_t)-1
[2017/03/28 11:24:40.914710, 0] ../source3/lib/util.c:900(log_stack_trace)
BACKTRACE: 19 stack frames:
#0 /usr/lib/x86_64-linux-gnu/samba/libsmbregistry.so.0(log_stack_trace+0x1a) [0x7fa52e1d77aa]
#1 /usr/lib/x86_64-linux-gnu/samba/libsmbregistry.so.0(smb_panic_s3+0x20) [0x7fa52e1d7880]
#2 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) [0x7fa52ef60f1f]
#3 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0xec9b9) [0x7fa52eb029b9]
#4 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(smbd_smb2_request_dispatch+0x2c8) [0x7fa52eb3d248]
#5 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x12851b) [0x7fa52eb3e51b]
#6 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(run_events_poll+0x167) [0x7fa52ce4a917]
#7 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(+0x2cb77) [0x7fa52ce4ab77]
#8 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d) [0x7fa52ba79d3d]
#9 /usr/lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x7fa52ba79edb]
#10 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(smbd_process+0x718) [0x7fa52eb2d298]
#11 /usr/sbin/smbd(+0x8e12) [0x558d6a74fe12]
#12 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(run_events_poll+0x167) [0x7fa52ce4a917]
#13 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(+0x2cb77) [0x7fa52ce4ab77]
#14 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d) [0x7fa52ba79d3d]
#15 /usr/lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x7fa52ba79edb]
#16 /usr/sbin/smbd(main+0x1899) [0x558d6a74e099]
#17 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7fa52b6c6830]
#18 /usr/sbin/smbd(_start+0x29) [0x558d6a74e199]
[2017/03/28 11:24:40.914913, 0] ../source3/lib/util.c:801(smb_panic_s3)
smb_panic(): calling panic action [/usr/share/samba/panic-action 12030]
[2017/03/28 11:24:40.956940, 0] ../source3/lib/util.c:809(smb_panic_s3)
smb_panic(): action returned status 0
[2017/03/28 11:24:40.959900, 0] ../source3/lib/dumpcore.c:303(dump_core)
dumping core in /var/log/samba/cores/smbd

[hanlif]

以上是问题电脑在samba中的日志，cups日志等上班后让他打印在贴上啦，因为分不清那个是他的日志

[hanlif]

[2017/04/09 20:44:07.422858, 0] ../source3/nmbd/nmbd.c:58(terminate)
Got SIGTERM: going down...
[2017/04/09 20:44:07.422973, 0] ../source3/libsmb/nmblib.c:873(send_udp)
Packet send failed to 192.168.57.255(138) ERRNO=无效的参数
[2017/04/09 20:44:07.423102, 0] ../source3/libsmb/nmblib.c:873(send_udp)
Packet send failed to 192.168.57.255(138) ERRNO=无效的参数
[2017/04/10 08:41:30.996195, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2017/04/10 08:41:54.037035, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
*****

Samba name server WEIDATONG-1 is now a local master browser for workgroup WORKGROUP on subnet 192.168.57.1

*****
[2017/04/10 08:41:54.037124, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
*****

Samba name server WEIDATONG-1 is now a local master browser for workgroup WORKGROUP on subnet 192.168.152.1

*****
[2017/04/10 15:48:01.156660, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
*****

Samba name server WEIDATONG-1 is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.100

*****
[2017/04/10 17:43:50.259314, 0] ../source3/nmbd/nmbd.c:58(terminate)
Got SIGTERM: going down...
[2017/04/10 17:56:24.120827, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2017/04/10 17:56:47.154760, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
*****

Samba name server WEIDATONG-1 is now a local master browser for workgroup WORKGROUP on subnet 192.168.57.1

*****
[2017/04/10 17:56:47.154889, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
*****

Samba name server WEIDATONG-1 is now a local master browser for workgroup WORKGROUP on subnet 192.168.152.1

*****
[2017/04/10 18:00:16.649519, 0] ../source3/nmbd/nmbd.c:58(terminate)
Got SIGTERM: going down...
[2017/04/10 18:02:44.736445, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2017/04/10 18:03:07.776082, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
*****

Samba name server WEIDATONG-1 is now a local master browser for workgroup WORKGROUP on subnet 192.168.57.1

*****
[2017/04/10 18:03:07.776174, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
*****

Samba name server WEIDATONG-1 is now a local master browser for workgroup WORKGROUP on subnet 192.168.152.1

*****
[2017/04/10 18:13:36.000848, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
*****

Samba name server WEIDATONG-1 is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.100

*****