From: Michael K. <li...@mk...> - 2017-08-31 06:57:14
|
> Am 31.08.2017 um 05:47 schrieb Michael Knill <mic...@ip...>: > > Ok after dropping out Monit and Darkstat and rebooting (it didn't free up the memory until I did), I now have above 50M free on my systems so that's not ideal but workable. > I will not bother upgrading just yet. Maybe next year ☺ > > Regards > Michael Knill Also Asterisk 13 needs more RAM then Asterisk 11. But if don't need PJSIP or ARI you can configure Asterisk to not load these modules. > From: Michael Knill <mic...@ip...> > Reply-To: AstLinux List <ast...@li...> > Date: Wednesday, 30 August 2017 at 5:56 pm > To: AstLinux List <ast...@li...> > Subject: Re: [Astlinux-users] Getting high processor load on ALIX box > > Thanks Michael. I will make sure I turn off Monit on all my ALIX boxes. > I get that I can fine tune things to make them work but frankly for the money I think I will just change them all out to APU’s or not upgrade. > > Regards > Michael Knill > > From: Michael Keuter <li...@mk...> > Reply-To: AstLinux List <ast...@li...> > Date: Wednesday, 30 August 2017 at 5:40 pm > To: AstLinux List <ast...@li...> > Subject: Re: [Astlinux-users] Getting high processor load on ALIX box > > > > > Am 30.08.2017 um 05:17 schrieb Michael Knill <mic...@ip...>: > > Hmm looks like Monit will need to go as nearly 15M. > Chrony is also fairly heavy on memory. Is this all I have in 1.2.10? > Do I disable SNMP by just removing mnt/kd/snmp/snmpd.conf ? > I have PHP using 45M plus. Is this normal? Anything I can do in php.ini? > > Regards > Michael Knill > > -----Original Message----- > From: Michael Knill <mic...@ip...> > Reply-To: AstLinux List <ast...@li...> > Date: Wednesday, 30 August 2017 at 12:45 pm > To: AstLinux List <ast...@li...> > Subject: Re: [Astlinux-users] Getting high processor load on ALIX box > > Hmm Im a bit worried actually about upgrading to 1.2.10 with Asterisk 13 on my ALIX boxes. > Some sites showing 5M free. > > Regards > Michael Knill > > -----Original Message----- > From: Lonnie Abelbeck <li...@lo...> > Reply-To: AstLinux List <ast...@li...> > Date: Wednesday, 30 August 2017 at 12:13 pm > To: AstLinux List <ast...@li...> > Subject: Re: [Astlinux-users] Getting high processor load on ALIX box > > Michael, > > Since this is an ALIX box, (low RAM, low performance) best to not enable anything "extra" IMHO. > > Lonnie > > > On Aug 29, 2017, at 8:45 PM, Michael Knill <mic...@ip...> wrote: > > > > So do you think I should turn it off by default and only turn it on when I need it? > > Regards > Michael Knill > > From: Michael Knill <mic...@ip...> > Reply-To: AstLinux List <ast...@li...> > Date: Wednesday, 30 August 2017 at 9:01 am > To: AstLinux List <ast...@li...> > Subject: [Astlinux-users] Getting high processor load on ALIX box > > Hmm I liked it better before I implemented Monit. Blissful ignorance ☺ > > I got am email from one of my servers with the following: > Event: Resource limit matched > Service 3016-Tilton-CM1 > Date: Tue, 29 Aug 2017 16:26:14 > Action: alert > Host: 3016-Tilton-CM1 > Description: loadavg(5min) of 2.2 matches resource limit [loadavg(5min) > 2.0] > > I found this in the logs of the server: > Aug 29 16:04:23 3016-Tilton-CM1 user.info kernel: AIF:Port 0 OS fingerprint: IN=ppp0 OUT= MAC= SRC=221.122.59.98 DST=115.187.184.60 LEN=69 TOS=0x00 PREC=0x00 TTL=44 ID=31131 PROTO=UDP SPT=6973 DPT=0 LEN=49 > Aug 29 16:04:56 3016-Tilton-CM1 daemon.debug darkstat[1424]: WARNING: pcap_dispatch took too long (took 1023275970 nsec, over threshold of 1000000000 nsec) > Aug 29 16:04:56 3016-Tilton-CM1 daemon.debug darkstat[1424]: WARNING: event processing took longer than a second (took 1319566069 nsec, over threshold of 1000000000 nsec) > Aug 29 16:05:02 3016-Tilton-CM1 daemon.debug darkstat[1424]: WARNING: pcap_dispatch took too long (took 1274262839 nsec, over threshold of 1000000000 nsec) > Aug 29 16:05:02 3016-Tilton-CM1 daemon.debug darkstat[1424]: WARNING: event processing took longer than a second (took 1461235038 nsec, over threshold of 1000000000 nsec) > Aug 29 16:05:04 3016-Tilton-CM1 daemon.debug darkstat[1424]: WARNING: event processing took longer than a second (took 1057674551 nsec, over threshold of 1000000000 nsec) > Aug 29 16:05:11 3016-Tilton-CM1 daemon.debug darkstat[1424]: WARNING: event processing took longer than a second (took 1513263031 nsec, over threshold of 1000000000 nsec) > Aug 29 16:05:14 3016-Tilton-CM1 daemon.debug darkstat[1424]: WARNING: pcap_dispatch took too long (took 1548211950 nsec, over threshold of 1000000000 nsec) > Aug 29 16:05:14 3016-Tilton-CM1 daemon.debug darkstat[1424]: WARNING: event processing took longer than a second (took 2129665587 nsec, over threshold of 1000000000 nsec) > > ..... and lots more > > Should I turn off the Netstat server? I assume this turns off darkstat! > > Regards > Michael Knill > > Hi Michael, > > I have a few Alix 2D13 PBX running in the field (with Asterisk 11 though). They usually have between 100 and 50 MB of free RAM. > I always create my own builds for them and leave out all packages that I don't need (e.g. netsnmp, Zabbix). > > I also don't enable Monit on Geode CPUs, cause there are some memory related issues over a longer time period. > > I you want I can send you my Buildroot .config file offlist. > Since there will be no official Alix/net5501 builds in the future, you need to build yourself anyway. > > Michael > > http://www.mksolutions.info Michael http://www.mksolutions.info |