|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: Socket errors.
From: Anders Norrbring (lists
norrbring.se)
Date: Mon May 15 2006 - 04:28:41 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sandy Drobic skrev:
> Anders Norrbring wrote:
>> Anone with ideas on this failure? I upgraded a SuSE system to a newer
>> version, and right after that, I get socket connection errors. I don't
>> even know where to start looking.. Postfix itself creates the sockets
>> at startup...
>>
>>
>> May 15 09:36:30 beata postfix/local[3696]: warning: connect #10 to
>> subsystem private/cyrus: Operation not permitted
>> May 15 09:36:41 beata postfix/qmgr[3648]: warning: premature
>> end-of-input on private/local socket while reading input attribute name
>> May 15 09:36:41 beata postfix/qmgr[3648]: warning: private/local
>> socket: malformed response
>> May 15 09:36:41 beata postfix/qmgr[3648]: warning: transport local
>> failure -- see a previous warning/fatal/panic logfile record for the
>> problem description
>> May 15 09:36:41 beata postfix/master[3634]: warning: process
>> /usr/lib/postfix/local pid 3696 exit status 1
>> May 15 09:36:41 beata postfix/master[3634]: warning:
>> /usr/lib/postfix/local: bad command startup -- throttling
>> May 15 09:36:41 beata postfix/master[3634]: warning: process
>> /usr/lib/postfix/local pid 3668 exit status 1
>
> AppArmor hits again...
>
> You need to edit your AppArmor profile to add the missing permissions or
> deactivate AppArmor completely.
>
> Sandy
Thanks for the shove.. I didn't think of AppArmor.. :) Fixed now, thanks
Sandy!
Anders.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]