Re: webalizer bug in debian jessie

2018-05-02 Thread deloptes
BASSAGET Cédric wrote:

> Can not install 2.23.08-3 because it needs libpng16-16

This refers to Buster https://packages.debian.org/testing/web/webalizer

either look for backport or recompile source on jessie





Re: how to keep geoip database uptodate

2018-05-02 Thread Henning Follmann
On Tue, May 01, 2018 at 07:14:47PM -0400, kamaraju kusumanchi wrote:
> How do I keep geoip database up to date on Debian stable? Currently, I
> am not able to get information on some IP addresses. For example,
> 
>  % geoiplookup 45.229.2.42
> GeoIP Country Edition: IP Address not found
> 
> I tried geoipupdate, but it is looking for a license.
> 
>  % geoipupdate -v
> geoipupdate 2.3.1
> Can't open license file /etc/GeoIP.conf
>  % ls -al /etc/GeoIP.conf
> ls: cannot access '/etc/GeoIP.conf': No such file or directory
> 
> % dpkg -l \*geoip\* | grep ^ii
> ii  geoip-bin   1.6.9-4  amd64IP lookup command line
> tools that use the GeoIP library
> ii  geoip-database  20170512-1   all  IP lookup command line
> tools that use the GeoIP library (country database)
> ii  geoipupdate 2.3.1-1  amd64MaxMind GeoIP/GeoIP2
> database updates
> ii  libgeoip1:amd64 1.6.9-4  amd64non-DNS IP-to-country
> resolver library
> 
> % cat /etc/debian_version
> 9.4
> 
> 
Hello,

you could download the latest file manually.
>From here:
http://geolite.maxmind.com/download/geoip/database/GeoLiteCountry/GeoIP.dat.gz
- backup your old GeoIP.dat
- move the new version into /usr/share/GeoIP.dat


-H
 



-- 
Henning Follmann   | hfollm...@itcfollmann.com



Re: how to keep geoip database uptodate

2018-05-02 Thread kamaraju kusumanchi
On Wed, May 2, 2018 at 7:01 AM, Henning Follmann
 wrote:
> Hello,
>
> you could download the latest file manually.
> From here:
> http://geolite.maxmind.com/download/geoip/database/GeoLiteCountry/GeoIP.dat.gz
> - backup your old GeoIP.dat
> - move the new version into /usr/share/GeoIP.dat

Thanks. It worked.

 % wget 
http://geolite.maxmind.com/download/geoip/database/GeoLiteCountry/GeoIP.dat.gz
...
Saving to: ‘GeoIP.dat.gz’
...
2018-05-02 07:15:54 (11.1 MB/s) - ‘GeoIP.dat.gz’ saved [711428/711428]

 % gunzip GeoIP.dat.gz
 % geoiplookup -f ./GeoIP.dat 45.229.2.42
GeoIP Country Edition: BR, Brazil

So, all I need is a cron job that regularly updates this file.

-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog



Re: Inexplicable memory usage after move to Debian9

2018-05-02 Thread Simon Beirnaert

I've been out for a bit, I'll bundle multiple replies in a single mail.
Before I start: thank you to everybody taking the time to respond in this
thread :)



How are you determining what you call "consumed memory"?


Memory which isn't available to the system. So "used" minus "buffers/cache"


Keep in mind that the kernel will by default use almost all free
memory (not actually used by processes and libraries) as cache
space, because it makes no sense to leave memory just laying around.
However, once it's really needed, the caches will be dropped. Thus
"free" memory is usually reported as low. Compare with "available"
memory as reported by free.


Yup. I'm aware of this and it's not the issue I'm trying to solve. Disk cache
is good.





The free's 'available' value is computed without taking "SUnreclaim"
(unreclaimable kernel slabs) value from /proc/meminfo.
The difference is not that great, usually, but for NFS server it can
lead to funny things like "I have plenty of free swap and OOM killer was
invoked, despite 'available' telling me there's plenty of free RAM".
Can happen with Java too, as OP e-mail shows us.


Unfortunately the system I was currently seeing the issues on has apparently
been rebooted by the client, so right now I don't have a system to verify,
but it sounds like this is what I'm on about. I'll verify as soon as another
system with issues pops up.


Happened to me with kernel 4.9.0-5, continued with kernel 4.9.0-6, seems
to be solved by upgrading to backported kernel version 4.14.


Hm. This could bite me in the ass. Thanks for your feedback.





The last line from smem sticks out with high usage figures:
566 jetty /usr/lib/jvm/java-8-openjdk 493896 958124 958381 959804


Java is actually consuming the expected amount of RAM for the settings we
start it with. Also, the hight memory usage presists after shutting down
Jetty (and pretty much any other service), which is why I was hinting at
possible kernel issues (not much else was running).



Packagekit spamming syslog

2018-05-02 Thread Tony van der Hoff
Running fully up to date stretch, I'm seeing the following in my syslog
every 5 minutes:

May  2 15:55:25 tony-lx PackageKit: refresh-cache transaction
/144833_aadbeecc from uid 1000 finished with success after 2225ms
May  2 15:55:27 tony-lx PackageKit: get-updates transaction
/144834_dacaaceb from uid 1000 finished with success after 1502ms
May  2 15:55:27 tony-lx PackageKit: get-updates transaction
/144835_cdcacaca from uid 1000 finished with success after 452ms
May  2 15:55:28 tony-lx PackageKit: get-updates transaction
/144837_aabccdcd from uid 1000 finished with success after 496ms
May  2 15:55:29 tony-lx PackageKit: get-updates transaction
/144838_bddedcad from uid 1000 finished with success after 451ms

Can someone please explain why PackageKit needs to update so often, and
maybe how to tame it.

Thanks,
Tony

-- 
Tony van der Hoff    | mailto:t...@vanderhoff.org
Buckinghamshire, England |



Re: Packagekit spamming syslog

2018-05-02 Thread Curt
On 2018-05-02, Tony van der Hoff  wrote:
> Running fully up to date stretch, I'm seeing the following in my syslog
> every 5 minutes:
>
> May  2 15:55:25 tony-lx PackageKit: refresh-cache transaction
> /144833_aadbeecc from uid 1000 finished with success after 2225ms
> May  2 15:55:27 tony-lx PackageKit: get-updates transaction
> /144834_dacaaceb from uid 1000 finished with success after 1502ms
> May  2 15:55:27 tony-lx PackageKit: get-updates transaction
> /144835_cdcacaca from uid 1000 finished with success after 452ms
> May  2 15:55:28 tony-lx PackageKit: get-updates transaction
> /144837_aabccdcd from uid 1000 finished with success after 496ms
> May  2 15:55:29 tony-lx PackageKit: get-updates transaction
> /144838_bddedcad from uid 1000 finished with success after 451ms
>
> Can someone please explain why PackageKit needs to update so often, and
> maybe how to tame it.

There's a bug report looks relevant:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881787

Jason Rodrigues in that thread suspects the KDE update notifier (he
removed 'apper', finding no other palliative measure).

Of course if you're not running KDE (or apper) it must be--implacable
logic--something else.

> Thanks,
> Tony
>


-- 




Re: Packagekit spamming syslog

2018-05-02 Thread Kenneth Parker
You might want to bring this up, on the Packagekit email list:

http://lists.freedesktop.org/mailman/listinfo/packagekit

(Note:  I am not a Packagekit expert.  I got this from the Debian Wiki Page
on Packagekit).

Kenneth Parker

On Wed, May 2, 2018, 11:30 AM Tony van der Hoff 
wrote:

> Running fully up to date stretch, I'm seeing the following in my syslog
> every 5 minutes:
>
> May  2 15:55:25 tony-lx PackageKit: refresh-cache transaction
> /144833_aadbeecc from uid 1000 finished with success after 2225ms
> May  2 15:55:27 tony-lx PackageKit: get-updates transaction
> /144834_dacaaceb from uid 1000 finished with success after 1502ms
> May  2 15:55:27 tony-lx PackageKit: get-updates transaction
> /144835_cdcacaca from uid 1000 finished with success after 452ms
> May  2 15:55:28 tony-lx PackageKit: get-updates transaction
> /144837_aabccdcd from uid 1000 finished with success after 496ms
> May  2 15:55:29 tony-lx PackageKit: get-updates transaction
> /144838_bddedcad from uid 1000 finished with success after 451ms
>
> Can someone please explain why PackageKit needs to update so often, and
> maybe how to tame it.
>
> Thanks,
> Tony
>
> --
> Tony van der Hoff| mailto:t...@vanderhoff.org
> Buckinghamshire, England |
>
>


gegl: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0: undefined symbol: babl_process_rows

2018-05-02 Thread Johann Spies
I have installed gimp 2.10 on three computers.  On two it was
successful.  On the third I get the error in the subject line whenever
I run gimp or gegl.  On the computer where I get this error, I could
also not compile the source package for gegl.  I could on of the
others and then I copied the compiled packages to the problem computer
and installed it but I made no progress to solving the problem.

I even upgraded that computer to unstable and purged and reinstalled
all the x11-related packages but I could not find out what the problem
was.

How do I determine what is causing the problem and then solve it?

I have the following packages installed:

ii  gegl
0.4.0-1  amd64Generic Graphics
Library Test Program
ii  gegl-dbgsym
0.4.0-1  amd64debug symbols for
gegl
ii  gir1.2-gegl-0.4:amd64
0.4.0-1  amd64GObject
introspection data for the Generic Graphics Library
ii  libgegl-0.4-0:amd64
0.4.0-1  amd64Generic Graphics
Library
ii  libgegl-0.4-0-dbgsym:amd64
0.4.0-1  amd64debug symbols for
libgegl-0.4-0
ii  libgegl-common
0.4.0-1  all  Generic Graphics
Library - common files
ii  libgegl-dev:amd64
0.4.0-1  amd64Generic Graphics
Library (development files)
ii  libgegl-doc
0.4.0-1  all  Generic Graphics
Library (documentation)

$ wajig list babl
ii  libbabl-0.1-0:amd64
0.1.46-2amd64Dynamic, any to any,
pixel format conversion library
ii  libbabl-dev:amd64
0.1.46-2amd64Dynamic, any to any,
pixel format conversion library (develo..

Regards
Johann


-- 
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)



Re: gegl: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0: undefined symbol: babl_process_rows

2018-05-02 Thread Sven Joachim
On 2018-05-02 22:44 +0200, Johann Spies wrote:

> I have installed gimp 2.10 on three computers.  On two it was
> successful.  On the third I get the error in the subject line whenever
> I run gimp or gegl.  On the computer where I get this error, I could
> also not compile the source package for gegl.  I could on of the
> others and then I copied the compiled packages to the problem computer
> and installed it but I made no progress to solving the problem.
>
> I even upgraded that computer to unstable and purged and reinstalled
> all the x11-related packages but I could not find out what the problem
> was.
>
> How do I determine what is causing the problem and then solve it?

A common cause for symbol lookup errors is locally installed libraries
not under dpkg control.  Start by running "ldd /usr/bin/gimp" and watch
for anything unusual, such as libraries under /usr/local.

> $ wajig list babl
> ii  libbabl-0.1-0:amd64
> 0.1.46-2amd64Dynamic, any to any,
> pixel format conversion library
> ii  libbabl-dev:amd64
> 0.1.46-2amd64Dynamic, any to any,
> pixel format conversion library (develo..

Previous reports of your problem have been #896091 and #897226, but
those were due to having libbabl-0.1-0 from dmo installed.  Apparently
this is not the case on your system.

Cheers,
   Sven



Re: gegl: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0: undefined symbol: babl_process_rows

2018-05-02 Thread tomas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wed, May 02, 2018 at 11:47:16PM +0200, Sven Joachim wrote:
> On 2018-05-02 22:44 +0200, Johann Spies wrote:
> 
> > I have installed gimp 2.10 on three computers.  On two it was
> > successful [...]

> A common cause for symbol lookup errors is locally installed libraries
> not under dpkg control.  Start by running "ldd /usr/bin/gimp" and watch
> for anything unusual, such as libraries under /usr/local.

This might, but it might also not help. I strongly guess libbabl is being
loaded at run time. But...
> 
> > $ wajig list babl
> > ii  libbabl-0.1-0:amd64
> > 0.1.46-2amd64Dynamic, any to any,
> > pixel format conversion library
> > ii  libbabl-dev:amd64
> > 0.1.46-2amd64Dynamic, any to any,
> > pixel format conversion library (develo..

given the bugs you mention, I'd look for some rogue libbabl (e.g.
"locate babl" or some equivalent) or strace a gimp start and look
there for "open" and "libbabl" and see what the gimp is actually
loading. Perhaps it's stumbling upon some older version of libbabl
left behind by some forgotten battle.

Cheers
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlrqkV0ACgkQBcgs9XrR2kZTTgCeNeoLr6Br6FwK4YF0Uli/SL3O
F7gAn2zT/L0yRz/5OknIk/k8xp3iy09n
=0HVN
-END PGP SIGNATURE-