On Sun, Apr 22, 2007 at 21:10:25 -0400, Bill Shofner wrote: > On 04/22/2007 11:12:47 AM, Bill Shofner wrote: >> On 04/22/2007 09:57:57 AM, Florian Kulzer wrote:
>>>>> On Fri, Apr 20, 2007 at 11:25:26 -0400, Bill Shofner wrote: >>>>> After upgrading my sarge box to etch, I cannot print and samba no >>>>> longer works. When I re-boot I get the following message from >>>>> root: >>>>> >>>>> The Samba 'panic action' script, /usr/share/samba/panic-action, >>>>> was called for PID 2540 (/usr/sbin/smbd). [ CUPS works now, samba does not. One down, one to go... ] >> I do not immediately see anything wrong with your samba-related >> packages. You could try to restart it and hope for a more illuminating >> error message: > >> /etc/init.d/samba restart > > All this did was send another message from root about the "Samba panic > action script. Just to be sure, I re-booted the computer and got the same > message from root again. So samba is still not working. > >> Finally, let's check if there are other broken packages on your system: > >> aptitude -F '%c %p %20v' search '~b' | sed 's/ \+/ /g' > > L550r:/home/bill# aptitude -F '%c %p %20v' search '~b' | sed 's/ \+/ /g' [ snip: 42 broken packages ] I think you might have to purge and reinstall samba, but first you should fix the broken packages. (I did not see anything that I could immediately connect to samba, but it is probably better to get this out of the way first.) The first thing to do is to tell aptitude to figure things out on its own: aptitude install -f If this has nasty side effects such as scheduling the removal of half of your system then you should abort the command (you will get that opportunity in any case, don't worry) and post all output here. We will then (hopefully) figure out how to proceed based on the symptoms. If this command runs OK then you should verify that aptitude search '~b' finishes without finding any packages anymore. Once that is achieved we will see about samba. -- Regards, | http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
