Re: ipfire 110 testing

[Michael Tremer <michael.tremer@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 3579 bytes --]

Hello,

On Fri, 2017-04-14 at 13:29 +0100, Paul Titjen wrote:
> Hi Michael,
> Firstly please redirect me to a better mail address for reporting things as I
> am pretty sure this distribution list is not the right place.

no, this is the right place.

> Secondly re 110 :
> After getting rid of all add ons and 110 working fine I went to put Samba and
> therefore its dependencies back.  This caused trouble and pakfire went into
> infinite loop.  There is another issue apart from avahi installation needing
> to be set to disabled.  I tracked it down by putting components in one at a
> time.  CUPS has a dependency on new package CUPS-filters.  However CUPS-
> filters has a dependency on CUPS.  Hence the loop.  perhaps Pakfire should
> error gracefully when child package has dependency on parent package.

I have recently pushed out a fix for the independent loop (which did not happen
when CUPS was already installed):

  http://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=621dcd8609a26ffe98fcb7fff05202bf5eb41112

Avahi has been dropped since it is causing this kind of trouble which I could
not fix quickly and which does not serve a purpose at all.

  http://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=076ad71576609f66f9a99cf4c14c75dbcd1a8220

If anyone wants to bring it back, please feel free to send in patches.

-Michael

> Regards,
> Paul
> 
> 
> On 10/04/17 17:08, Michael Tremer wrote:
> > Hello,
> > 
> > this is indeed avahi. The daemon crashes right at the start and just hangs
> > for
> > forever.
> > 
> > I so far have not investigated and no idea why this is happening. This might
> > not
> > even be a new bug but more people are now affected since avahi is pulled in
> > as a
> > dependency by CUPS.
> > 
> > Thanks for reporting this though. I will update you as soon as I have
> > something
> > to test.
> > 
> > -Michael
> > 
> > On Sat, 2017-04-08 at 16:50 +0100, Paul Titjen wrote:
> > > Further investigation:
> > >  Using htop to analyse it seems stopping/starting service in WUI creates
> > > another avahi process.  Each one take a whole cpu core up.
> > > Have taken out samba, cups, and dependencies avahi, dbus, and other
> > > dependencies gone and all is ok.  Seems the avahi refusing to die
> > > gracefully
> > > may be the cause of the reboot failing.
> > > With all of the above gone system now reboots and behaves perfectly.
> > > Regards,
> > > Paul
> > > 
> > > 
> > > 
> > > 
> > > 
> > > On 08/04/17 12:57, Paul Titjen wrote:
> > > > Hi,
> > > > 
> > > > I have upgraded to the 110 version and report the following.
> > > > 
> > > > 110 did not ask for a reboot but I gave it one anyway.  The system did
> > > > not
> > > > reboot correctly but as I do not have a console attached I can not say
> > > > why. 
> > > > Hard reset and it started normally.  net-snmpd did not start at boot but
> > > > then it was a crash shutdown.  started normally thereafter.
> > > > 
> > > > CPU usage. 
> > > > I have cacti running on the ipfire box and the change from 109 to 110
> > > > has
> > > > put 
> > > > CPU usage up from 5% to 55%. 
> > > > 
> > > > 
> > > > 
> > > > Load average up from 0.1 to 2.2
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > System is an AMD fitlet with four intel nics
> > > > Your profile ID: 6d74743620b592b2ea3bdb44bd77e539db98c783 
> > > > 
> > > > If you want me to try anything please let me know
> > > > 
> > > > Regards,
> > > > Paul
> > > > 
> > > 
> > >  
>  

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]