Bug#1043510: Rox removal

[Benoit-Pierre DEMAINE]

I may be the last user of ROX, but ... I still INTENSIVELY use ROX. On all
my machines, all the time. Continuously. It starts automatically during
startx, and never get killed because I never shutdown (system freeses and
needs reset after 20 or 30 days uptime).

-- 
>o_/ DEMAINE Benoit-Pierre (Gmail) (aka DoubleHP) http://benoit.demaine.info
/
If computing were an exact science, IT engineers would'nt have work \_o<

"So all that's left, Is the proof that love's not only blind but deaf."
(FAKE TALES OF SAN FRANCISCO, Arctic Monkeys)

Bug#1027085: Still hapening on 5.10.0-22-amd64

[Benoit-Pierre DEMAINE]

Still hapening on 5.10.0-22-amd64. My backup kernels 5.10.0-20-amd64 and
5.10.0-22-amd64 are also broken. I am an hair away from not being able to
work anymore: kernels that used to work ... break without even me touching
them.

-- 
>o_/ DEMAINE Benoit-Pierre (Gmail) (aka DoubleHP) http://benoit.demaine.info
/
If computing were an exact science, IT engineers would'nt have work \_o<

"So all that's left, Is the proof that love's not only blind but deaf."
(FAKE TALES OF SAN FRANCISCO, Arctic Monkeys)

Bug#870140: zoneminder should depend on php-gd

[Benoit-Pierre Demaine (aka Doublehp)]

Package: zoneminder
Version: 1.30.0+dfsg-2
Severity: normal

Dear Maintainer,

https://forums.zoneminder.com/viewtopic.php?p=101599#p101599
ZM should depend on php-gd, or some major features won't work properly.

-- System Information:
Debian Release: stretch/sid
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages zoneminder depends on:
ii  cakephp  2.8.5-1
ii  init-system-helpers  1.46
ii  javascript-common11
ii  libarchive-zip-perl  1.59-1
ii  libavcodec57 7:3.2.4-1
ii  libavformat577:3.2.4-1
ii  libavutil55  7:3.2.4-1
ii  libc62.24-8
ii  libclass-std-fast-perl   0.0.8-2
ii  libcurl3-gnutls  7.50.1-1
ii  libdata-dump-perl1.23-1
ii  libdata-uuid-perl1.220-1+b2
ii  libdate-manip-perl   6.56-1
ii  libdbd-mysql-perl4.041-1
ii  libdevice-serialport-perl1.04-3+b3
ii  libgcc1  1:6.2.1-5
ii  libgcrypt20  1.7.5-2
ii  libgnutls-openssl27  3.5.7-3
ii  libimage-info-perl   1.39-1
ii  libio-socket-multicast-perl  1.12-2+b3
ii  libjpeg62-turbo  1:1.5.1-2
ii  libjs-mootools   1.4.5~debian1-2.1
ii  libjson-any-perl 1.39-1
ii  libmariadbclient18   10.0.28-2
ii  libmime-lite-perl3.030-2
ii  libmime-tools-perl   5.508-1
ii  libmodule-load-conditional-perl  0.68-1
ii  libnet-sftp-foreign-perl 1.86+dfsg-1
ii  libpcre3 2:8.39-2
ii  libperl5.24 [libdigest-sha-perl] 5.24.1~rc4-1
ii  libphp-serialization-perl0.34-1
ii  libsoap-wsdl-perl3.003-2
ii  libstdc++6   6.2.1-5
ii  libswscale4  7:3.2.4-1
ii  libsys-cpu-perl  0.61-2+b1
ii  libsys-meminfo-perl  0.99-1
ii  libsys-mmap-perl 0.17-1+b2
ii  liburi-encode-perl   1.1.1-1
ii  libvlc5  2.2.4-10
ii  libwww-perl  6.15-1
ii  mariadb-client-10.1 [virtual-mysql-client]   10.1.21-5+b1
ii  perl 5.24.1~rc4-1
ii  perl-modules-5.24 [libmodule-load-conditional-perl]  5.24.1~rc4-1
ii  php-mysql1:7.0+47
ii  policykit-1  0.105-17
ii  rsyslog [system-log-daemon]  8.23.0-2
ii  zip  3.0-11
ii  zlib1g   1:1.2.8.dfsg-4

Versions of packages zoneminder recommends:
ii  apache2 [httpd] 2.4.23-8
ii  ffmpeg  7:3.2.4-1
ii  libapache2-mod-php  1:7.0+47
ii  libapache2-mod-php7.0 [libapache2-mod-php]  7.0.19-1
ii  mariadb-server-10.1 [virtual-mysql-server]  10.1.21-5+b1
ic  mysql-server-5.7 [virtual-mysql-server] 5.7.17-1
ii  zoneminder-doc  1.30.0+dfsg-2

Versions of packages zoneminder suggests:
pn  fcgiwrap   
ii  logrotate  3.8.7-2

-- Configuration Files:
/etc/logrotate.d/zoneminder changed [not included]

-- no debconf information

Bug#863103: munin-plugins-core: plugin ps_ breaks for perl

[Benoit-Pierre Demaine (aka Doublehp)]

Package: munin-plugins-core
Version: 2.0.33-1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


I have set munin to have plugin called ps_perl. Other ps_* plgins are
working fine, but the perl one broke in fall january 2017.

All ps_* plugins used to work fine for a few weeks after setting them.
But after some systme update, ps_perl stopped working.

My thinking is that /usr/bin/pgrep changed behaviour in january.
/usr/bin/pgrep is owned by procps. Here is why I think so:

# $PGREP -f -l "\"
685 apache2
692 htcacheclean
4025 apache2
5800 apache2
5803 apache2
...

But ...
# $PGREP -f -l "\"
23689 munin-node
27041 zmdc.pl
27191 zmfilter.pl
27200 zmaudit.pl
27208 zmwatch.pl
27215 zmtelemetry.pl

So, for some reason, gprep will show the process name for most process,
but, for scripts, it will show the name of calling script. And,
according to my Munin graphs, plugin had been working fine for 3 weeks.
So, I guess there must have been an update of procps somewhere around
january (or a few months before; I rarely update).

So, once pgrep shows calling script instead of binary file, the next
filter will fail:
$PGREP -f -l "$name" | grep "$REGEX" | grep -v grep | wc -l
will fail on the middle part '' grep "$REGEX" '' for obvious reasons.
Then, plugin returns value of 0 even when many process are running. For
me, this issue occurs only on perl, which happens to be a script
interpreter; plugin works fine for apache2 and kworker.

There are tons of ways to fix this on plugin side.

But, this may also reveal a change of behaviour of pgrep in the bad way
... and if so, this may affect many other scripts relying on pgrep. So,
potentially, any script calling /usr/bin/pgrep, and/or any package
depending on procps.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages munin-plugins-core depends on:
ii  munin-common  2.0.33-1
ii  perl  5.24.1~rc4-1

Versions of packages munin-plugins-core recommends:
ii  libnet-snmp-perl  6.0.1-2

Versions of packages munin-plugins-core suggests:
pn  conntrack
pn  libcache-cache-perl  
ii  libdbd-mysql-perl4.041-1
ii  libnet-dns-perl  1.06-1
pn  libnet-netmask-perl  
pn  libnet-telnet-perl   
ii  libxml-parser-perl   2.44-2+b1
ii  python   2.7.11-2
pn  ruby | ruby-interpreter  

-- no debconf information

Bug#860487: munin-plugins-core: psu_ plugin provides invalid config

[Benoit-Pierre Demaine (aka Doublehp)]

Package: munin-plugins-core
Version: 2.0.33-1
Severity: minor

munin-update.log from server reports:
Missing required attribute 'label' for data source 'processes' in service 
psu_root on leon-01.doublehp.org/leon-host:4949

The root issue is trivial:
echo graph_title Number of processes owned by $name
echo 'graph_args --base 1000 --vertical-label processes -l 0'
echo 'graph_category processes'
echo "count.label $name"
echo 'processes.draw LINE2'
exit 0

I guess we want
echo 'count.draw LINE2'


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages munin-plugins-core depends on:
ii  munin-common  2.0.33-1
ii  perl  5.24.1-2

Versions of packages munin-plugins-core recommends:
ii  libnet-snmp-perl  6.0.1-2

Versions of packages munin-plugins-core suggests:
pn  conntrack
pn  libcache-cache-perl  
pn  libdbd-mysql-perl
ii  libnet-dns-perl  1.07-1
ii  libnet-netmask-perl  1.9022-1
pn  libnet-telnet-perl   
ii  libxml-parser-perl   2.44-2+b1
ii  python   2.7.13-2
pn  ruby | ruby-interpreter  

-- no debconf information

Bug#849948: munin-plugins-core: sensors_ shuffles fields after sensor package update

[Benoit-Pierre Demaine (aka Doublehp)]

Package: munin-plugins-core
Version: 2.0.28-1
Severity: normal

Here is the old web page of my sensors_temp plugin, last month (backup)

Field   Internal name   TypeWarnCritInfo
Core 0  temp2   gauge   105.0   105.0
Core 1  temp3   gauge   105.0   105.0
Core 2  temp4   gauge   105.0   105.0
Core 3  temp5   gauge   105.0   105.0
SYSTIN  temp6   gauge   65  75   
CPUTIN  temp7   gauge   75.080.0 
AUXTIN  temp8   gauge   75.080.0 

Last week, I made a global system update.

Here is the same page today:

Field   Internal name   TypeWarnCritInfo
SYSTIN  temp1   gauge   0.0 0.0
CPUTIN  temp2   gauge   75.080.0 
AUXTIN  temp3   gauge   75.080.0 
PCH_CHIP_TEMP   temp4   gauge   
PCH_CPU_TEMPtemp5   gauge   
PCH_MCH_TEMPtemp6   gauge   20:6510:75
temp1   temp7   gauge   90.0 
Core 0  temp8   gauge   105.0   105.0

Forget about missing lines like temp1; I have disable some fields in
server conf. The core problem is that some probes have changed name:
SYSTIN used to be temp6 and is now temp1; implies two problems:
new SYSTIN inherits the past RRD of temp1 (which was probably a stupid
probe since I had it disabled).

Other way to look at it: temp8 was AUXTIN and is now core0; before the
update the curve represents external probe; after the update, internal
CPU. So, a given rrd(curve) will represent two different probes,
depending on the date we are looking at.

This is a severe problem: I had the machine setup with warnings and
criticals for security reasons. After update, all my settings are
messed-up; what means, the configuration I made to wanr me about failing
parts is lost; if I had not dig in Munin, some critical part of the
server could have failed without a single warning. In my machine, when
any fan is broken, the machine has to stop (and stop before a component
overheats; I had a PSU fan diyng; when PSU overheated, it came into
short circuit, and injected high voltage into the HDD: bad PSU fan
killed my disk !!!).

Munin is not responsible for sensors package updates, and potential
changes; but the plugin needs to provide a way to keep track of which
field is pointing to which probe. And have that stable over years.

If plugin can not record things this way, it needs to provide a manual
way to associate sensors-probes to munin-field-name.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages munin-plugins-core depends on:
ii  munin-common  2.0.28-1
ii  perl  5.24.1~rc4-1

Versions of packages munin-plugins-core recommends:
ii  libnet-snmp-perl  6.0.1-2

Versions of packages munin-plugins-core suggests:
pn  conntrack
pn  libcache-cache-perl  
ii  libdbd-mysql-perl4.041-1
pn  libnet-dns-perl  
pn  libnet-netmask-perl  
pn  libnet-telnet-perl   
ii  libxml-parser-perl   2.44-2+b1
ii  python   2.7.11-2
pn  ruby | ruby-interpreter  

-- no debconf information

Bug#849548: munin-plugins-extra: apt_all Could not get lock /var/lib/dpkg/lock Resource temporarily unavailable

[Benoit-Pierre Demaine (aka Doublehp)]

Package: munin-plugins-extra
Version: 2.0.28-1
Severity: minor

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Each time I run a long apt command, Munin complains about locks:

E: Could not get lock /var/lib/dpkg/lock - open (11: Resource
temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is
another process using it?

Can be several emails per day.

Here is my attempt to fix it:
/etc/cron.d/munin-node
if [ -x /etc/munin/plugins/apt_all ]
becomes
if [ ! -e /var/lib/dpkg/lock ]; then if [ -x /etc/munin/plugins/apt_all];
untested ...

There is no perfect way to avoid these messages, but adding this simple
test should avoid 99.9% useless messages.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages munin-plugins-extra depends on:
ii  munin-common  2.0.28-1
pn  perl:any  

munin-plugins-extra recommends no packages.

Versions of packages munin-plugins-extra suggests:
pn  libnet-netmask-perl  
pn  libnet-telnet-perl   
ii  python   2.7.11-2

-- no debconf information

Bug#842615: openssh-server: losing access to server during upgrade

[Benoit-Pierre Demaine (aka Doublehp)]

Package: openssh-server
Version: 1:7.3p1-1
Severity: normal

Dear Maintainer,

aptitude distupgrade 
...
Installing new version of config file /etc/network/if-up.d/openssh-server ...
Connection to server closed by remote host.

Been said this is abnormal. Never happened to me since 1999. Started to have 
this issue on all my stretch machines since june 2016. Thought it was the 
normal behaviour coming with systemd ... but still, this breaks aptitude; after 
reloging in, I may have to run dpkg --configure -a again; also, the dead 
process may be waiting for some dialog stuff; so, I was said there is a bug. 
But so many things are broken in stretch, so this issue is far from the most 
important one.

Affects all cessions to server; even other users not running aptitude.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages openssh-server depends on:
ii  adduser3.115
ii  debconf [debconf-2.0]  1.5.59
ii  dpkg   1.18.10
ii  init-system-helpers1.45
ii  libaudit1  1:2.6.7-1
ii  libc6  2.24-5
ii  libcomerr2 1.43.3-1
ii  libgssapi-krb5-2   1.14.3+dfsg-2
ii  libkrb5-3  1.14.3+dfsg-2
ii  libpam-modules 1.1.8-3.3
ii  libpam-runtime 1.1.8-3.3
ii  libpam0g   1.1.8-3.3
ii  libselinux12.5-3
ii  libssl1.0.21.0.2j-1
ii  libsystemd0231-9
ii  libwrap0   7.6.q-25
ii  lsb-base   9.20161016
ii  openssh-client 1:7.3p1-1
ii  openssh-sftp-server1:7.3p1-1
ii  procps 2:3.3.12-2
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages openssh-server recommends:
ii  libpam-systemd  231-9
ii  ncurses-term6.0+20160917-1
ii  xauth   1:1.0.9-1

Versions of packages openssh-server suggests:
pn  molly-guard   
pn  monkeysphere  
pn  rssh  
pn  ssh-askpass   
pn  ufw   

-- debconf information excluded

Bug#837527: zoneminder: zmaudit.pl can not remove files with spaces

[Benoit-Pierre Demaine (aka Doublehp)]

Package: zoneminder
Version: 1.30.0+dfsg-1
Severity: normal

Dear Maintainer,

Create a camera with a name containing a space, and, get this at cleaning time:
/usr/bin/zmaudit.pl
...
Filesystem monitor link 'NVT cam-01-mycam' does not point to valid monitor 
directory, deleting
rm: cannot remove 'NVT': No such file or directory
rm: cannot remove 'cam-01-mycam': No such file or directory
...
should be self explanatory for everyone.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages zoneminder depends on:
ii  cakephp  2.8.5-1
ii  init-system-helpers  1.36
ii  javascript-common11
ii  libarchive-zip-perl  1.57-1
ii  libavcodec57 7:3.1.1-3
ii  libavformat577:3.1.1-3
ii  libavutil55  7:3.1.1-3
ii  libc62.23-4
ii  libclass-std-fast-perl   0.0.8-2
ii  libcurl3-gnutls  7.47.0-1
ii  libdata-dump-perl1.23-1
ii  libdata-uuid-perl1.220-1+b1
ii  libdate-manip-perl   6.54-1
ii  libdbd-mysql-perl4.035-1
ii  libdevice-serialport-perl1.04-3+b2
ii  libgcc1  1:6.1.1-10
ii  libgcrypt20  1.7.1-2
ii  libgnutls-openssl27  3.4.13-1
ii  libimage-info-perl   1.28-1.2
ii  libio-socket-multicast-perl  1.12-2+b2
ii  libjpeg62-turbo  1:1.5.0-1
ii  libjs-mootools   1.4.5~debian1-2.1
ii  libjson-any-perl 1.39-1
ii  libmime-lite-perl3.030-2
ii  libmime-tools-perl   5.507-1
ii  libmysqlclient18 5.6.30-1
ii  libnet-sftp-foreign-perl 1.86+dfsg-1
ii  libpcre3 2:8.38-3.1
ii  libperl5.22 [libdigest-sha-perl] 5.22.2-3
ii  libphp-serialization-perl0.34-1
ii  libsoap-wsdl-perl3.003-2
ii  libstdc++6   6.1.1-10
ii  libswscale4  7:3.1.1-3
ii  libsys-cpu-perl  0.61-2
ii  libsys-meminfo-perl  0.98-1+b1
ii  libsys-mmap-perl 0.17-1+b1
ii  liburi-encode-perl   1.1.1-1
ii  libvlc5  2.2.4-2
ii  libwww-perl  6.15-1
ii  mysql-client 5.6.30-1
ii  mysql-client-5.6 [virtual-mysql-client]  5.6.30-1
ii  perl 5.22.2-3
ii  perl-modules-5.22 [libmodule-load-conditional-perl]  5.22.2-3
ii  php-mysql1:7.0+42
ii  policykit-1  0.105-16
ii  rsyslog [system-log-daemon]  8.16.0-1+b3
ii  zip  3.0-11
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages zoneminder recommends:
ii  apache2 [httpd] 2.4.23-2
ii  ffmpeg  7:3.1.1-3
ii  libapache2-mod-php  1:7.0+42
ii  libapache2-mod-php7.0 [libapache2-mod-php]  7.0.9-1
ii  mysql-server5.6.30-1
ii  mysql-server-5.6 [virtual-mysql-server] 5.6.30-1
ii  zoneminder-doc  1.30.0+dfsg-1

Versions of packages zoneminder suggests:
pn  fcgiwrap   
ii  logrotate  3.8.7-2

-- no debconf information