search for: printer_list

...amba/sbin/smbd: Registering messaging pointer for type 33 - private_data=0xb78143e0 /usr/local/samba/sbin/smbd: Registering messaging pointer for type 517 - private_data=(nil) /usr/local/samba/sbin/smbd: reloading printcap cache /usr/local/samba/sbin/smbd: check lock order 1 for /srv/samba/locks/printer_list.tdb /usr/local/samba/sbin/smbd: release lock order 1 for /srv/samba/locks/printer_list.tdb /usr/local/samba/sbin/smbd: cups_pcap_load_async: asynchronously loading cups printers /usr/local/samba/sbin/smbd: reload status: ok /usr/local/samba/sbin/smbd: start_background_queue: background LPQ thread...

...es installed or even running because the system is running on a micro-sd card iwas tempted more than once move "/var/lib/samba/private/msg.sock/" and "/var/lib/samba/lock/msg.lock/" in a tmpfs but that won't solve the issue 20K -rw-r--r-- 1 root root 20K 2018-11-07 12:16 printer_list.tdb 16K -rw-r--r-- 1 root root 16K 2018-11-07 12:16 serverid.tdb [root at nfs:~]$ backup-nfs.sh sending incremental file list sending incremental file list sending incremental file list sending incremental file list deleting samba/lock/msg.lock/1041903 deleting samba/private/msg.sock/1041903 sam...

...amba/sbin/smbd: Registering messaging pointer for type 33 - private_data=0xb78143e0 /usr/local/samba/sbin/smbd: Registering messaging pointer for type 517 - private_data=(nil) /usr/local/samba/sbin/smbd: reloading printcap cache /usr/local/samba/sbin/smbd: check lock order 1 for /srv/samba/locks/printer_list.tdb /usr/local/samba/sbin/smbd: release lock order 1 for /srv/samba/locks/printer_list.tdb /usr/local/samba/sbin/smbd: cups_pcap_load_async: asynchronously loading cups printers /usr/local/samba/sbin/smbd: reload status: ok /usr/local/samba/sbin/smbd: start_background_queue: background LPQ thread...

...x4e66c2b2 name:brlock.tdb path:/var/lib/ctdb/brlock.tdb.1 dbid:0x7a19d84d name:locking.tdb path:/var/lib/ctdb/locking.tdb.1 dbid:0x06916e77 name:leases.tdb path:/var/lib/ctdb/leases.tdb.1 dbid:0x66f71b8c name:smbXsrv_open_global.tdb path:/var/lib/ctdb/smbXsrv_open_global.tdb.1 dbid:0x5bcfcbd7 name:printer_list.tdb path:/var/lib/ctdb/printer_list.tdb.1 dbid:0x477d2e20 name:smbXsrv_client_global.tdb path:/var/lib/ctdb/smbXsrv_client_global.tdb.1 dbid:0x2ca251cf name:account_policy.tdb path:/var/lib/ctdb/persistent/account_policy.tdb.1 PERSISTENT dbid:0x3ef19640 name:passdb.tdb path:/var/lib/ctdb/persist...

Dear All, We're running smbd "Version 4.3.9-Ubuntu", and it populates our log files with these two lines per every connect: === [2016/07/18 18:42:31.544726, 1] ../source3/printing/printer_list.c:234(printer_list_get_last_refresh) Failed to fetch record! [2016/07/18 18:42:31.544780, 1] ../source3/smbd/server_reload.c:69(delete_and_reload_printers) pcap cache not loaded === I have tried various mantras to disable printing, e.g. === |load printers = no printing = bsd printcap name...

On Wed, 13 Feb 2019 18:17:40 +0100 marco pirola via samba <samba at lists.samba.org> wrote: > No but in the file fstab i have > UUID=30a7a2fe-e1b0-4336-a6b6-7f11390f7afa /home           ext4 > user_xattr      0       2 And it shouldn't be there, it is part of the ext4 default settings. Just a thought, are the acl & xattr packages installed ? Rowland

Hi list We recently upgraded our fileservers from Centos supplied 4.2.10 to Sernet 4.4.6, and then our DCs from 3.6.x to 4.4.6. It seems that since then we've had problems with locks not being obeyed on all nodes - they only seem to work when a second client opens a file on the same node as the first client. For example, when a user opens an Excel file I will see something like this

...rror during PAC signature verification: NT_STATUS_UNSUCCESSFUL [2018/06/27 12:50:17.766117, 1] ../source3/winbindd/winbindd_pam.c:2502(extract_pac_vrfy_sigs) Failed to initialize kerberos context: Invalid argument win-client.log (AD Member) [2018/06/27 12:49:13.354207, 1] ../source3/printing/printer_list.c:234(printer_list_get_last_refresh) Failed to fetch record! [2018/06/27 12:49:13.354282, 1] ../source3/smbd/server_reload.c:69(delete_and_reload_printers) pcap cache not loaded smb.conf (AD Member) security = ADS workgroup = DOM realm = DOM.EXAMPLE.COM bind interfaces only = ye...

In the desktop (hostname machine windows 10 professional joined in the domain ROBINOOD.tst) appared [2019/02/07 17:25:44.347710,  1] ../source3/printing/printer_list.c:234(printer_ list_get_last_refresh)   Failed to fetch record! [2019/02/07 17:25:44.364344,  1] ../source3/smbd/server_reload.c:69(delete_and_r eload_printers)   pcap cache not loaded [2019/02/07 17:26:14.139330,  0] ../source3/rpc_server/srv_pipe.c:726(api_pipe_b ind_req)   unknown interface...

Hi, Has anyone had any success using a Canon LBP5300 with CentOS or any other RH type os for that matter, using the rpms and intructions downloaded from the Canon website? I have it working on XP and OS X both via USB and network but am having no success with either on CentOS 5.4 . Print jobs seem to be processed correctly by CUPS but the printer doesn't respond at all and the jobs show

I am down to reconciling these last few samba_server startup messages in smbd.log: Item 1. [2020/06/29 11:29:49.887167, 1] ../../source3/printing/printer_list.c:234(printer_list_get_last_refresh) Failed to fetch record! We do not use samba as a print server and no printers are defined for that host. How do we turn off this message? Item 2. [2020/06/29 11:29:49.900481, 1] ../../source3/lib/messages.c:899(send_all_fn) send_all_fn: messaging_send_b...

Hi, we have a problem with your Samba4 Domain Member as with Shares. when i would connect i got an Error. In Samba Logs it tells me ==> /var/log/samba/computerid349.log <== [2016/02/10 14:39:50.313835, 1] ../source3/printing/printer_list.c:226(printer_list_get_last_refresh) Failed to fetch record! [2016/02/10 14:39:50.313949, 1] ../source3/smbd/server_reload.c:69(delete_and_reload_printers) pcap cache not loaded [2016/02/10 14:39:52.775084, 1] ../source3/smbd/service.c:550(make_connection_snum) create_connection_session_inf...

...hk=25/79) samba/private/msg.sock/ samba/private/msg.sock/1041903 sending incremental file list ------------------------------------------ [root at nfs:~]$ backup-nfs.sh sending incremental file list sending incremental file list sending incremental file list sending incremental file list samba/lock/printer_list.tdb 20,480 100% 0.00kB/s 0:00:00 (xfr#1, to-chk=34/79) samba/lock/serverid.tdb 16,384 100% 15.62MB/s 0:00:00 (xfr#2, to-chk=33/79) sending incremental file list

...> because the system is running on a micro-sd card iwas tempted more > than once move "/var/lib/samba/private/msg.sock/" and > "/var/lib/samba/lock/msg.lock/" in a tmpfs > > but that won't solve the issue > 20K -rw-r--r-- 1 root root 20K 2018-11-07 12:16 printer_list.tdb > 16K -rw-r--r-- 1 root root 16K 2018-11-07 12:16 serverid.tdb > > [root at nfs:~]$ backup-nfs.sh > sending incremental file list > sending incremental file list > sending incremental file list > sending incremental file list > deleting samba/lock/msg.lock/1041903 &gt...

Hai, but dont forget that if you use samba also as print server you need to backup the /var/lib/samba/drivers en printing also. ( and in my case a different folder. ) In /var/cache/samba is the file printer_list.tdb I dont think that recreated, and if it is, you probely will loose the printer settings. I'll have to look that up. Maybe its an option to let the backup scrip detect if it running on a DC or Member server so it always backups what is needed. Greetz, Louis > -----Oorspronkel...

...n order for my client machines to print. Every 5 or so minutes, the printers from this print server appear as "Server offline" in Windows. If I restart smbd and winbind at the same time, they come back for a bit, and everyone can print as per normal. I have seen the bug report to delete printer_list.tdb, and done that yesterday. In the log.rpcd_spoolss file, I see entries such as this below: [2023/10/26 09:27:21, 0] ../../librpc/rpc/dcesrv_handles.c:130(dcesrv_handle_lookup) dcesrv_handle_lookup: Attempt to use invalid sid S-1-5-21-3018909051-3044254431-1064828747-1113 - S-1-5-21-301890905...

...n order for my client machines to print. Every 5 or so minutes, the printers from this print server appear as "Server offline" in Windows. If I restart smbd and winbind at the same time, they come back for a bit, and everyone can print as per normal. I have seen the bug report to delete printer_list.tdb, and done that yesterday. In the log.rpcd_spoolss file, I see entries such as this below: [2023/10/26 09:27:21, 0] ../../librpc/rpc/dcesrv_handles.c:130(dcesrv_handle_lookup) dcesrv_handle_lookup: Attempt to use invalid sid S-1-5-21-3018909051-3044254431-1064828747-1113 - S-1-5-21-301890905...

...b/util_sock.c:455(open_socket_in) open_socket_in(): socket() call failed: Protocol not supported [2015/07/10 20:01:31.573832, 0] ../source3/smbd/server.c:690(smbd_open_one_socket) smbd_open_once_socket: open_socket_in: Protocol not supported [2015/07/10 20:01:31.574017, 1] ../source3/printing/printer_list.c:227(printer_list_get_last_refresh) Failed to fetch record! [2015/07/10 20:01:38.007082, 1] ../source3/auth/user_krb5.c:164(get_user_from_kerberos_info) Username NYINGMA\leeb is invalid on this system [2015/07/10 20:01:38.007103, 1] ../source3/auth/auth_generic.c:99(auth3_generate_session_in...

...06/27 12:50:17.766117, 1] >> ../source3/winbindd/winbindd_pam.c:2502(extract_pac_vrfy_sigs) >> Failed to initialize kerberos context: Invalid argument >> >> >> win-client.log (AD Member) >> >> [2018/06/27 12:49:13.354207, 1] >> ../source3/printing/printer_list.c:234(printer_list_get_last_refresh) >> Failed to fetch record! >> [2018/06/27 12:49:13.354282, 1] >> ../source3/smbd/server_reload.c:69(delete_and_reload_printers) >> pcap cache not loaded >> >> >> smb.conf (AD Member) >> >> security = A...

...rint. > > Every 5 or so minutes, the printers from this print server appear as > "Server offline" in Windows. If I restart smbd and winbind at the > same time, they come back for a bit, and everyone can print as per > normal. > > I have seen the bug report to delete printer_list.tdb, and done that > yesterday. In the log.rpcd_spoolss file, I see entries such as this > below: > > [2023/10/26 09:27:21, 0] > ../../librpc/rpc/dcesrv_handles.c:130(dcesrv_handle_lookup) > dcesrv_handle_lookup: Attempt to use invalid sid > S-1-5-21-3018909051-3044254431-106...