[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: cups and samba stop working after upgrade to etch



On Sat, Apr 21, 2007 at 18:46:26 -0400, Bill Shofner wrote:
> On 04/21/2007 03:50:43 PM, 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).
>> >
>> > This means there was a problem with the program, such as a
>> > segfault.  Below is a backtrace for this process generated with
>> > gdb, which shows the state of the program at the time the error
>> > occurred.  The Samba log files may contain additional information
>> > about the problem.
>>
>> [...]
>>
>> > I cannot print from the printer attached to this system either and
>> > when I try to go to http://localhost:631 I get:
>> >
>> > An error occurred while loading http://localhost:631: Could not
>> > connect to host localhost (port 631).
>>
>> [...]
>>
>> > At this point I do not know if the underlying problem is in cups or samba
>> > or something else. Any pointers or suggestions will be greatfully received.
>>
>> Just to get this out of the way first: Are you sure that your upgrade
>> is complete? Did you use the procedure outlined in the release notes?
>
> Yes, I'm reasonably sure the upgrade is complete.  I did use the procedure 
> in the release notes as closely as I could - it did involve several 
> itinerations of upgrade and dist-upgrade until aptitude indicated there is 
> nothing to upgrade. The kernel was upgraded last.

OK, let's take a look at your system. Please post the output of this
command:

dpkg -l \*samba\* \*smb\* \*cups\* udev hotplug | awk '/^[^|D+]/{print $1,$2,$3}'

and just to be sure also include the result of:

uname -a

-- 
Regards,            | http://users.icfo.es/Florian.Kulzer
          Florian   |



Reply to: