Hi All, We have been running Samba (3.0.2), CUPS on SUSE 9 Pro for some time now with no problems. This morning however it all seems to have gone wrong, and the users on site can no longer print. When a user prints a document nothing comes out on the printer and further investigation in the Windows printers folder reveals the printers are sat with 'x' amount of jobs on them and constantly refreshing, opening the print queue on the users window machine reveals no jobs in the queue at all. I have tried all the usual, restarting the daemons and rebooting the machine, I even considered a removal and reinstall of Samba, the system logs show that the SMBD is having a panic each time a user tries to print or view the print queues. Does anyone have any suggestions how I can resolve this issue? We migrated this box from Windows due to stability problems, and I really don't want to have to go back to Windows for my print server. Many Thanks In Advance Jez.
Jeramy Eling schrieb:> Hi All, > > We have been running Samba (3.0.2), CUPS on SUSE 9 Pro for some time now with no problems. This morning however it all seems to have gone wrong, and the users on site can no longer print. When a user prints a document nothing comes out on the printer and further investigation in the Windows printers folder reveals the printers are sat with 'x' amount of jobs on them and constantly refreshing, opening the print queue on the users window machine reveals no jobs in the queue at all. > > I have tried all the usual, restarting the daemons and rebooting the machine, I even considered a removal and reinstall of Samba, the system logs show that the SMBD is having a panic each time a user tries to print or view the print queues. > > Does anyone have any suggestions how I can resolve this issue? We migrated this box from Windows due to stability problems, and I really don't want to have to go back to Windows for my print server. > > Many Thanks In Advance > > Jez. >what said your samba and the cups log ,is /var/spool/samba accesible to everybody regards
same problem here (samba 3.0.2a cups 1.1.19, suse9 pro) with win9x clients. Until we update to 3.0.3pre1 (rpms on ftp.suse.com/people/gd/) there were no more "lib/util.c:smb_panic"-messages at all. bye, Rainer> Hi All, > > We have been running Samba (3.0.2), CUPS on SUSE 9 Pro for some time now with no problems. This morning however it all seems to have gone wrong, and the users on site can no longer print. When a user prints a document nothing comes out on the printer and further investigation in the Windows printers folder reveals the printers are sat with 'x' amount of jobs on them and constantly refreshing, opening the print queue on the users window machine reveals no jobs in the queue at all. > > I have tried all the usual, restarting the daemons and rebooting the machine, I even considered a removal and reinstall of Samba, the system logs show that the SMBD is having a panic each time a user tries to print or view the print queues. > > Does anyone have any suggestions how I can resolve this issue? We migrated this box from Windows due to stability problems, and I really don't want to have to go back to Windows for my print server. > > Many Thanks In Advance > > Jez. > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba > >
> I've been having issues with Win98 printing on RedHat ES 3, which isusing> Samba 3.0.2-6.ES. The WinXP computers print fine, but the Win98 onestend> to lose the print queue and I've noticed that even if they print jobfiles> tend to remain in the /var/spool/samba directory.Are these zero-byte smbprn files, or is there really print data there that just doesn't get submitted to cups for some reason? If they are zero-length then check your samba logs for the client/machine in question. I've seen zero length smbprn files with corrupted print tdb's. ~ Daniel ----------------------------------------------------------------------- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you.
> I haven't been seeing any more files in the /var/spool/samba > directory, but these errors are showing up in my message log > file all the time now. > > Apr 8 15:27:09 fs3 smbd[22335]: register_message_flags: > tdb_fetch failedNo, you'd be seeing messages like bad magic 0x42424242 and the like if it were a tdb corruption problem. The message you listed is normal for Samba 3 print, not indicative of corruption. You can try turning up debugging on the server to see if anything looks unusual, and checking out the event viewer on the client. Other than that, I suppose just making sure the drivers you have installed are suitable for W98 clients is a given, and that NETBIOS is working correctly since that's required for Windows clients pre w2k. ~ Daniel ----------------------------------------------------------------------- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you.