Bug#1028045: php-8.1-solr and php-solr and missing in testing (hard package freeze in 2 months)
Package: php-8.1-solr Version: 2.5.1+2.4.0-15 Hi, it seems that php-8.1-solr (and php-solr) aren't in testing at all at current time of write, and last changelog entry is from 08 Mar 2022 : -- Ondřej Surý Tue, 08 Mar 2022 15:09:07 +0100 If by any chance I can help somehow, let me know (I'm not enrolled as d-d). Thanks for all the fish, -- Ludovic Pouzenc Ingénieur Informatique de Gestion Direction du Numérique - Service des Systèmes Applicatifs 04 79 75 83 54
Bug#1012046: References / previous reports
Hi, Friends pointed me out to older bugs reports of the quite same problem with libvte. Situation has changed since but it seems kept in the wrong choices to me... Problems are there since 09/2009 (vte-0.21.6). https://www.climagic.org/bugreports/libvte-scrollback-written-to-disk.html It is pointing out that the suggestion I made in previous comment was also made in 2015 and has drawbacks : [...] it is inherited by all child processed launched inside the terminal which is probably not what they want. https://bugzilla.gnome.org/show_bug.cgi?id=631685#c50 Someone pointed out inhttps://bugzilla.xfce.org/show_bug.cgi?id=8183: While setting TMPDIR to a shm or tmpfs based location is a nice workaround for those who definitely want their scrollback in memory, it is cumbersome: it is inherited by all child processed launched inside the terminal which is probably not what they want. Moreover, it's not feasible to set this in some global environment definition file. For these people it would be convenient to support VTETMPDIR - if defined, it would take precedence over the standard tmp dir locations. Regards,
Bug#1012046: /usr/libexec/gnome-terminal-server: gnome-terminal-server writes on disk data when a program output data on term
Package: gnome-terminal
Version: 3.44.0-1
Severity: normal
File: /usr/libexec/gnome-terminal-server
X-Debbugs-Cc: bugrepo...@pouzenc.fr
Dear Maintainer,
I see on debian 10, 11 and testing a potential security problem with
gnome-terminal-server. It makes IO on disk when some program output on terminal.
It uses deleted files in /tmp instead of no files or files in RAM in /run.
My use case is sysadmin a lot of machines, with sometimes confidential
data displayed on terminal. For me everything should be in RAM as
xterm does.
The simplest way to spot code path that seems to be bad for me is :
* install debian 10, 11 or testing on a physical amd64 computer
* open a gnome session with a normal user
* open a gnome-terminal
* wait until there is not significant activity on IO physical LED
* start the following command : yes
* terminal starts to scroll fast
* IO LED should go to "solid on" now, because many IO
* sudo apt install iotop strace
* sudo iotop should display something like :
Total DISK READ: 0.00 B/s | Total DISK WRITE: 2.21 M/s
Current DISK READ: 0.00 B/s | Current DISK WRITE: 191.00 K/s
TID PRIO USER DISK READ DISK WRITE SWAPIN IO>COMMAND
2260 be/4 lpouzenc0.00 B/s 176.86 K/s ?unavailable?
gnome-terminal-server
1 be/4 root0.00 B/s0.00 B/s ?unavailable? init
2 be/4 root0.00 B/s0.00 B/s ?unavailable? [kthreadd]
* sudo strace -p2260 -fc # for 10 seconds or so
strace: Process 2260 attached with 4 threads
^Cstrace: Process 2260 detached
strace: Process 2315 detached
strace: Process 2316 detached
strace: Process 2327 detached
% time seconds usecs/call callserrors syscall
-- --- --- - -
66,590,9991151546 646 poll
32,060,480939 4100426 4 read
0,310,004600 2 2156 pread64
0,260,003925 4 915 593 recvmsg
0,190,002921 1 2334 pwrite64
0,160,002460 1 1898 ftruncate
0,130,001926 6 312 write
0,080,001240 10 116 fallocate
0,070,001086 7 13631 futex
0,050,000774 774 1 restart_syscall
0,040,000645 1157 sendmsg
0,040,000550 775 writev
0,010,000109 13 8 ioctl
0,000,45 220 clock_nanosleep
-- --- --- - -
100,001,500335 13109100 628 total
* sudo strace -p2260 -fo /dev/shm/gts
* less /dev/shm/gts
[...]
2260 write(14, "\r", 1)= 1
2260 recvmsg(3, {msg_namelen=0}, 0)= -1 EAGAIN (Ressource temporairement
non disponible)
2260 poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5,
events=POLLIN}, {fd=13, events=POLLIN|POLLPRI}, {fd=14, events=POLLIN|POLLPRI},
{fd=19, events=POLLIN|POLLPRI}], 6, 600) = 1 ([{fd=14, revents=POLLIN}])
2260 write(4, "\1\0\0\0\0\0\0\0", 8) = 8
2260 read(14, "\0\r\n\33[?2004l\r", 8136) = 12
2260 read(14, 0x562c26142083, 8125)= -1 EAGAIN (Ressource temporairement
non disponible)
2260 write(4, "\1\0\0\0\0\0\0\0", 8) = 8
2260 recvmsg(3, {msg_namelen=0}, 0)= -1 EAGAIN (Ressource temporairement
non disponible)
2260 poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5,
events=POLLIN}, {fd=13, events=POLLIN|POLLPRI}, {fd=14, events=POLLIN|POLLPRI},
{fd=19, events=POLLIN|POLLPRI}], 6, 10) = 1 ([{fd=4, revents=POLLIN}])
2260 read(4, "\2\0\0\0\0\0\0\0", 16) = 8
2260 recvmsg(3, {msg_namelen=0}, 0)= -1 EAGAIN (Ressource temporairement
non disponible)
2260 poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5,
events=POLLIN}, {fd=13, events=POLLIN|POLLPRI}, {fd=14, events=POLLIN|POLLPRI},
{fd=19, events=POLLIN|POLLPRI}], 6, 10) = 1 ([{fd=14, revents=POLLIN}])
2260 write(4, "\1\0\0\0\0\0\0\0", 8) = 8
2260 read(14, "\0y\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny"...,
8125) = 1361
2260 read(14, "\0\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r"...,
6765) = 289
2260 read(14, "\0\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r"...,
6477) = 295
2260 read(14, "\0\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r"...,
6183) = 292
2260 read(14, "\0\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r"...,
5892) = 292
2260 read(14, "\0\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r"...,
5601) = 288
2260 read(14, "\0y\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny\r\ny"...,
5314) = 262
[...]
* sudo lsof -np 2260 | grep -v mem
lsof: WARNING: cant stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
Output information may be incomplete.
lsof: WARNING: cant stat() fuse.portal file system
Bug#1009906: haproxy: HTTPS proxyfied requests randomly delayed by 50 seconds (default timeout server)
Package: haproxy
Version: 2.2.9-2+deb11u3
Severity: important
X-Debbugs-Cc: bugrepo...@pouzenc.fr
Dear Maintainer,
We have a (Wordpress) PHP web-site hosted on 3 LAMP nodes. We use haproxy to
load-balance the incomming web trafic.
We've got 240k lines of apache2 access log yesterday.
The problem can be reproduced with a test infra without any concurrent user
and a basic test.php thats readfile("jquery.min.js")
and a basic index.html referencing multiple (24) times the test.php
to have Firefox starting multiple HTTP requests in parallel.
The problem is hard or impossible to trigger with Firefox with http2 enabled.
The problem is easy to reproduce with firefox forced in http/1.1 mode.
The problem doesn't show with a echo "Hello World" in test.php,
it seems that the response size is important. 30kio is enough to trigger it
for sure.
Out of 25 requests (including GET /), Firefox will get results about 20 of
them, and about 4 will be delayed by a huge amount of 50 seconds.
(50 seconds if haproxy have : default timeout server 5).
I tried nbproc 1 and nbthreads 1 with no improvements.
I tried haproxy 2.4.15-1~bpo11+1 and it DOES fix the situation without changing
anything else.
# apt install -t bullseye-backports haproxy
I didn't find any bugreports mentionning major troubles in "basic" usage of
haproxy.
I post it here to get someone else luck with Googling about the troubles I hit.
I can't find exactly what line in haproxy changelog could correspond to this.
I think I can try, if useful, to find the smallest configuration that breaks.
PHP seems unrelated. Direct access to the apache don't show up any trouble.
It may be broken in Ubuntu 21.04 (hirsute) and Ubuntu 21.10 (impish) also.
Thanks for all the fish,
Ludovic
-- System Information:
Debian Release: 11.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-13-amd64 (SMP w/1 CPU thread)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages haproxy depends on:
ii adduser 3.118
ii dpkg 1.20.9
ii init-system-helpers 1.60
ii libc62.31-13+deb11u3
ii libcrypt11:4.4.18-4
ii libgcc-s110.2.1-6
ii liblua5.3-0 5.3.3-1.1+b1
ii libpcre2-8-0 10.36-2
ii libssl1.11.1.1n-0+deb11u1
ii libsystemd0 247.3-7
ii lsb-base 11.1.0
ii zlib1g 1:1.2.11.dfsg-2+deb11u1
haproxy recommends no packages.
Versions of packages haproxy suggests:
pn haproxy-doc
pn vim-haproxy
-- Configuration Files:
/etc/haproxy/haproxy.cfg changed:
global
log /dev/loglocal0
log /dev/loglocal1 notice
chroot /var/lib/haproxy
stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd
listeners
stats timeout 30s
user haproxy
group haproxy
daemon
# Default SSL material locations
ca-base /etc/ssl/certs
crt-base /etc/ssl/private
# See:
https://ssl-config.mozilla.org/#server=haproxy=2.0.3=intermediate
ssl-default-bind-ciphers
ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384
ssl-default-bind-ciphersuites
TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256
ssl-default-bind-options ssl-min-ver TLSv1.2 no-tls-tickets
defaults
log global
modehttp
option httplog
option dontlognull
timeout connect 5000
timeout client 5
timeout server 5
errorfile 400 /etc/haproxy/errors/400.http
errorfile 403 /etc/haproxy/errors/403.http
errorfile 408 /etc/haproxy/errors/408.http
errorfile 500 /etc/haproxy/errors/500.http
errorfile 502 /etc/haproxy/errors/502.http
errorfile 503 /etc/haproxy/errors/503.http
errorfile 504 /etc/haproxy/errors/504.http
frontend http
bind *:80
mode http
# redirects to https
redirect scheme https if !{ ssl_fc }
default_backend http
frontend https
bind *:443 ssl crt /etc/haproxy/certs/ alpn h2,http/1.1
mode http
# [some acl with our IPs stripped here]
default_backend http
backend http
balance roundrobin
# ensures the forwarded request includes the actual client IP address
option forwardfor
#defines the check HAProxy uses to test if a web server is still valid for
forwarding requests
option httpchk
http-check send meth GET uri /
# use cookies for sticky sessions
cookie SRVNAME insert indirect nocache
server www1 192.168.120.41:443 cookie s1 check ssl
Bug#1008682: Security: updates & upgrades too delayed
Package: unattended-upgrades Version: 2.8 Severity: normal X-Debbugs-Cc: bugrepo...@pouzenc.fr Dear Maintainer, Unattended-upgrade installs security upgrades with too much (random) delay, more than 24h after DSA and mirror availability. On a pool of about twenty debian 11 VM, the majority ends with 2 day of lagg on published DSA. I expect things like in pre-systemd debian : all upgrades applied before the start of the current working day. I believe it's mostly an apt problem with /usr/lib/apt/apt.systemd.daily. I've reported this as #1008679 on src:apt. I create a BR against unattended-upgrades because it set in /etc/apt/apt.conf.d/20auto-upgrades : APT::Periodic::Update-Package-Lists "1"; Witch is mostly bad with the default (apt) /lib/systemd/system/apt-daily.timer : OnCalendar=*-*-* 6,18:00 (twice a day) "1" random skip apt update for 36h in worst cases I believe. Extra delay is added with apt-daily-upgrade.timer. APT::Periodic::Update-Package-Lists "always"; may be an other value to consider (or not). Code using APT::Periodic::Update-Package-Lists is currently very complicated. (in debian 11 at least). /etc/apt/apt.conf.d/20auto-upgrades does not provide comments for helping admins about tuning that. Be cautious: the comment in /usr/lib/apt/apt.systemd.daily about Update-Package-Lists seems wrong and misleading for me. I have detailed everything I can in #1008679. Cheers, Ludovic Pouzenc -- System Information: Debian Release: 11.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-12-amd64 (SMP w/2 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages unattended-upgrades depends on: ii debconf [debconf-2.0] 1.5.77 ii lsb-base 11.1.0 ii lsb-release11.1.0 ii python33.9.2-3 ii python3-apt2.2.1 ii python3-dbus 1.2.16-5 ii python3-distro-info1.0 ii ucf3.0043 ii xz-utils 5.2.5-2 Versions of packages unattended-upgrades recommends: ii anacron 2.3-30 ii cron [cron-daemon] 3.0pl1-137 ii systemd-sysv247.3-6 Versions of packages unattended-upgrades suggests: pn bsd-mailx pn default-mta | mail-transport-agent pn needrestart pn powermgmt-base ii python3-gi 3.38.0-2 -- debconf information: unattended-upgrades/enable_auto_updates: true
Bug#1008679: Security: updates & upgrades too delayed by /usr/lib/apt/apt.systemd.daily
think that : - setting APT::Periodic::Update-Package-Lists "always" or removing the "06," in apt-daily.timer - removing the "After=" dependency of the timer slightly improve the situation without patching code for the admins that wants to change their config quickly and not make troubles to mirror maintainers. I think that the current code is too error-prone of every one. I think that the tone of my bug report is going bad as I am ending writing it. Sorry about that, everything is almost very great. I wish to add that I'm very happy the celebrate this year my 15 years of nearly full-time sysadmin on Debian based systems for various purposes ! Cheers, Ludovic Pouzenc -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "amd64"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "1"; APT::Install-Suggests "0"; APT::Sandbox ""; APT::Sandbox::User "_apt"; APT::Authentication ""; APT::Authentication::TrustCDROM "true"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^firmware-linux.*"; APT::NeverAutoRemove:: "^linux-firmware$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$"; APT::VersionedKernelPackages ""; APT::VersionedKernelPackages:: "linux-.*"; APT::VersionedKernelPackages:: "kfreebsd-.*"; APT::VersionedKernelPackages:: "gnumach-.*"; APT::VersionedKernelPackages:: ".*-modules"; APT::VersionedKernelPackages:: ".*-kernel"; APT::Never-MarkAuto-Sections ""; APT::Never-MarkAuto-Sections:: "metapackages"; APT::Never-MarkAuto-Sections:: "contrib/metapackages"; APT::Never-MarkAuto-Sections:: "non-free/metapackages"; APT::Never-MarkAuto-Sections:: "restricted/metapackages"; APT::Never-MarkAuto-Sections:: "universe/metapackages"; APT::Never-MarkAuto-Sections:: "multiverse/metapackages"; APT::Move-Autobit-Sections ""; APT::Move-Autobit-Sections:: "oldlibs"; APT::Move-Autobit-Sections:: "contrib/oldlibs"; APT::Move-Autobit-Sections:: "non-free/oldlibs"; APT::Move-Autobit-Sections:: "restricted/oldlibs"; APT::Move-Autobit-Sections:: "universe/oldlibs"; APT::Move-Autobit-Sections:: "multiverse/oldlibs"; APT::LastInstalledKernel "5.10.0-12-amd64"; APT::Periodic ""; APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Unattended-Upgrade "1"; APT::Update ""; APT::Update::Post-Invoke-Success ""; APT::Update::Post-Invoke-Success:: "/usr/bin/test -e /usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && /usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call --system --dest org.freedesktop.PackageKit --object-path /org/freedesktop/PackageKit --timeout 4 --method org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo > /dev/null"; APT::Update::Post-Invoke-Success:: "if /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null || true; fi"; APT::Architectures ""; APT::Architectures:: "amd64"; APT::Architectures:: "i386"; APT::Compressor ""; APT::Compressor::. ""; APT::Compressor::.::Name "."; APT::Compressor::.::Extension ""; APT::Compressor::.::Binary ""; APT::Compressor::.::Cost "0"; APT::Compressor::zstd ""; APT::Compressor::zstd::Name "zstd"; APT::Compressor::zstd::Extension ".zst"; APT::Compressor::zstd::Binary "zstd"; APT::Compressor::zstd::Cost "60"; APT::Compressor::zstd::CompressArg ""; APT::Compressor::zstd::CompressArg:: "-19"; APT::Compressor::zstd::UncompressArg ""; APT::Compressor::zstd::UncompressArg:: "-d"; APT::Compressor::lz4 ""; APT::Compressor::lz4::Name "lz4"; APT::Compressor::lz4::Extension ".lz4"; APT::Compressor::lz4::Binary "lz4"; APT::Compressor::lz4::Cost "50"; APT::Compressor::lz4::CompressArg ""; APT::Compressor::lz4::CompressArg:: "-1"; APT::Compressor::lz4::UncompressArg ""; APT::Compressor::lz4::UncompressArg:: "-d"; APT::Compressor::gzip ""; APT::Compressor::gzip::Name "gzip"; APT::Compressor::gzip::Extension ".gz"; APT::Compressor::gzip::Binary "gzip"; APT::Compressor::gzip::Cost "100"; APT::Compressor::gzip::CompressArg ""; APT::Compressor::gzip::CompressArg:: "-6n"; APT::Compressor::gzip::UncompressArg ""; APT::Compressor::gzip::U
Bug#986462: automysqlbackup: LATEST=yes broken code: cp .gz /var/lib/automysqlbackup/latest/ (No such file or directory)
Hi, First try on an already installed debian 11 test server : it seems to work properly. (see term1.html) I've tried this version on debian 10 before a full upgrade to debian 11, no post-inst problems seen, backup successful. Then I've tried to upgrade to debian 11 this VM, no problems found. (see term2.html) I think everything is now working in my usecases and I didnt find any bad side effects. Cheers, Ludovic Le 30/08/2021 à 17:29, Thomas Goirand a écrit : On 8/30/21 5:02 PM, Ludovic Pouzenc wrote: Thank you very much. I can test right now but I can't find now a mirror that reflects your upload. Could you point me the right thing to do ? Wait until the next Dak run, as I've just uploaded it it takes time for the package to reach the mirrors. It should be available later this evening. Cheers, Thomas Goirand (zigo) -- Ludovic Pouzenc Ingénieur Informatique de Gestion Direction du Numérique, DN : Applications 04 79 75 83 54 (test)root@app-d11-test:~# date; lsb_release -a; apt policy automysqlbackup mar. 31 août 2021 11:10:06 CEST No LSB modules are available. Distributor ID: Debian Description:Debian GNU/Linux 11 (bullseye) Release:11 Codename: bullseye automysqlbackup: Installé : 2.6+debian.4-4 Candidat : 2.6+debian.4-4 Table de version : *** 2.6+debian.4-4 100 100 /var/lib/dpkg/status 2.6+debian.4-3 500 500 http://ftp.fr.debian.org/debian bullseye/main amd64 Packages (test)root@app-d11-test:~# automysqlbackup ; echo $? 0 (test)root@app-d11-test:~# date mar. 31 août 2021 11:10:19 CEST (test)root@app-d11-test:~# ls -lh /var/lib/automysqlbackup/latest/ total 12K -rw--- 1 root root 8,2K 31 août 11:10 wp_test_2021-08-31_11h10m.mardi.sql.gz (test)root@app-d11-test:~# ls -lh /var/lib/automysqlbackup/daily/ total 4,0K drwxr-xr-x 2 root root 4,0K 31 août 11:10 wp_test (test)root@app-d11-test:~# ls -lh /var/lib/automysqlbackup/daily/wp_test/ total 36K -rw--- 1 root root 8,2K 29 août 06:25 wp_test_2021-08-29_06h25m.dimanche.sql.gz -rw--- 1 root root 8,2K 30 août 06:25 wp_test_2021-08-30_06h25m.lundi.sql.gz -rw--- 1 root root 8,2K 31 août 11:10 wp_test_2021-08-31_11h10m.mardi.sql.gz (test)root@app-d11-test:~# (vbox)root@vmdev1-pouzencl:~# date; lsb_release -a mardi 31 août 2021, 11:45:45 (UTC+0200) No LSB modules are available. Distributor ID: Debian Description:Debian GNU/Linux 10 (buster) Release:10 Codename: buster (vbox)root@vmdev1-pouzencl:~# wget http://ftp.fr.debian.org/debian/pool/main/a/automysqlbackup/automysqlbackup_2.6+debian.4-4_all.deb --2021-08-31 11:41:39-- http://ftp.fr.debian.org/debian/pool/main/a/automysqlbackup/automysqlbackup_2.6+debian.4-4_all.deb Résolution de ftp.fr.debian.org (ftp.fr.debian.org)… 212.27.32.66, 2a01:e0c:1:1598::2 Connexion à ftp.fr.debian.org (ftp.fr.debian.org)|212.27.32.66|:80… connecté. requête HTTP transmise, en attente de la réponse… 200 OK Taille : 14576 (14K) [application/octet-stream] Sauvegarde en : « automysqlbackup_2.6+debian.4-4_all.deb » automysqlbackup_2.6 100%[===>] 14,23K --.-KB/sds 0,04s 2021-08-31 11:41:39 (378 KB/s) — « automysqlbackup_2.6+debian.4-4_all.deb » sauvegardé [14576/14576] (vbox)root@vmdev1-pouzencl:~# dpkg -i automysqlbackup_2.6+debian.4-4_all.deb (Lecture de la base de données... 65569 fichiers et répertoires déjà installés.) Préparation du dépaquetage de automysqlbackup_2.6+debian.4-4_all.deb ... Dépaquetage de automysqlbackup (2.6+debian.4-4) sur (2.6+debian.4-2) ... Paramétrage de automysqlbackup (2.6+debian.4-4) ... Fichier de configuration « /etc/default/automysqlbackup » ==> Modifié (par vous ou par un script) depuis l'installation. ==> Le distributeur du paquet a fourni une version mise à jour. Que voulez-vous faire ? Vos options sont les suivantes : Y ou I : installer la version du responsable du paquet N ou O : garder votre version actuellement installée D : afficher les différences entre les versions Z : suspendre ce processus pour examiner la situation L'action par défaut garde votre version actuelle. *** automysqlbackup (Y/I/N/O/D/Z) [défaut=N] ? d --- /etc/default/automysqlbackup2021-05-25 19:50:08.903741914 +0200 +++ /etc/default/automysqlbackup.dpkg-new 2021-08-30 16:50:19.0 +0 @@ -56,7 +56,7 @@ DBEXCLUDE="" # Include CREATE DATABASE in backup? -CREATE_DATABASE=no +CREATE_DATABASE=yes # Separate backup directory and file for each DB? (yes or no) SEPDIR=yes @@ -64,15 +64,22 @@ # Which day do you want weekly backups? (1 to 7 where 1 is Monday) DOWEEKLY=6 +# Which day of the month to execute the monthly backup (00 = no monthly backup) +# Two digit required +DOMONTHLY=01 + # Choose Compression type. (gzip or bzip2) COMP=gzip +# Compress backups on the fly with gzip or bzip2 (yes or no) +COMPDIRECT=no + # Compress communications between backup server and MySQL server? COMMCOMP=no # Addit
Bug#986462: automysqlbackup: LATEST=yes broken code: cp .gz /var/lib/automysqlbackup/latest/ (No such file or directory)
Thank you very much. I can test right now but I can't find now a mirror that reflects your upload. Could you point me the right thing to do ? Le 30/08/2021 à 16:54, Thomas Goirand a écrit : On 4/6/21 3:29 PM, Ludovic Pouzenc wrote: - cp $1$SUFFIX "$BACKUPDIR/latest/" + cp $2$SUFFIX "$BACKUPDIR/latest/" Hi Ludovic and Gabriel, I've commited and uploaded the above patch. Can you please check the version in Debian unstable, and confirm it fixes the problem? If it's ok, then I'll try to get the package fixed in Stable as well. Cheers, Thomas Goirand (zigo) -- Ludovic Pouzenc Ingénieur Informatique de Gestion Direction du Numérique, DN : Applications 04 79 75 83 54
Bug#986462: (no subject)
Dear maintainer, This bug has landed in debian stable and I think there is people that are starting to migrate real things on it. At least me and theorically all users using LATEST=yes in their config. This is a 1 byte patch. (or a 2 bits patch). Regards, -- Ludovic Pouzenc Ingénieur Informatique de Gestion Direction du Numérique, DN : Applications 04 79 75 83 54
Bug#986462: (no subject)
Hi, I confirm that I didn't see any troubles since then with the proposed patch. I ran this only on single a amd64 VM but it's shell script func call with numbered args... so should be fine for any arch. Regards, -- Ludovic Pouzenc Ingénieur Informatique de Gestion Direction du Numérique, DN : Applications 04 79 75 83 54
Bug#986462: automysqlbackup: LATEST=yes broken code: cp .gz /var/lib/automysqlbackup/latest/ (No such file or directory)
Package: automysqlbackup
Version: 2.6+debian.4-3
Severity: normal
Tags: newcomer patch upstream
Dear Maintainer,
I use automysqlbackup on many Debian 10 with LATEST=yes in
/etc/default/automysqlbackup
(and a psotscript which seem unreleated to this BR)
I start doing the same on Debian testing on 2021-04-02.
automysqlbackup is sending 2 error e-mails earch morning since then.
> Subject: ERRORS REPORTED: MySQL Backup error Log for logapp -
> 2021-04-06_06h25m
>
> cp: impossible d'évaluer 'icinga2.gz': Aucun fichier ou dossier de ce type
> (= No Such file or directory in french)
> Subject: MySQL Backup Log for servername - 2021-04-06_06h25m
>
> (No errors in it at all)
> ==
> AutoMySQLBackup VER 2.5
> http://sourceforge.net/projects/automysqlbackup/
>
> Backup of Database Server - servername
> ==
> Backup Start Time mar. 06 avril 2021 06:25:01 CEST
> ==
> Daily Backup of Database ( dbname )
> Rotating last weeks Backup...
> '/var/lib/automysqlbackup/daily/dbname/dbname_2021-03-30_06h25m.mardi.sql.gz'
> supprimé
>
>
> Backup Information for
> /var/lib/automysqlbackup/daily/dbname/dbname_2021-04-06_06h25m.mardi.sql
> compresseduncompressed ratio uncompressed_name
> 48414 299090 83.8%
> /var/lib/automysqlbackup/daily/dbname/dbname_2021-04-06_06h25m.mardi.sql
> --
> Backup End mar. 06 avril 2021 06:25:02 CEST
> ==
> Total disk space used for backup storage..
> Size - Location
> 596K /var/lib/automysqlbackup
>
> ==
> If you find AutoMySQLBackup valuable please make a donation at
> http://sourceforge.net/project/project_donations.php?group_id=101066
> ==
> ==
> Postbackup command output.
>
>
> ==
If I ran manually automysqlbackup ithout args as root, the exit code is
1 and no outpout or stderr on terminal.
If I ran manually bash -x $(which automysqlbackup), no usefull output on
terminal, but detailled email :
> + SUFFIX=
> + '[' '' ']'
> + '[' yes = yes ']'
> + '[' yes = no ']'
> + OPT='--quote-names --events --routines --databases'
> + '[' localhost = localhost ']'
> ++ hostname
> + HOST=servername
> + '[' '' ']'
> + '[' 'dbname ' = all ']'
> + echo ==
> + echo AutoMySQLBackup VER 2.5
> + echo http://sourceforge.net/projects/automysqlbackup/
> + echo
> + echo Backup of Database Server - servername
> + echo ==
> + '[' yes = yes ']'
> ++ date
> + echo Backup Start Time mar. 06 avril 2021 15:01:37 CEST
> + echo ==
> + '[' 06 = 01 ']'
> + for DB in $DBNAMES
> ++ sed 's/%/ /g'
> ++ echo dbname
> + DB=dbname
> + '[' '!' -e /var/lib/automysqlbackup/daily/dbname ']'
> + '[' '!' -e /var/lib/automysqlbackup/weekly/dbname ']'
> + '[' 2 = 6 ']'
> + echo Daily Backup of Database '(' dbname ')'
> + echo Rotating last weeks Backup...
> + rm -fv
> /var/lib/automysqlbackup/daily/dbname/dbname_2021-04-06_15h00m.mardi.sql.gz
> + echo
> + dbdump dbname
> /var/lib/automysqlbackup/daily/dbname/dbname_2021-04-06_15h01m.mardi.sql
> + '[' dbname = information_schema ']'
> + NEWOPT='--opt --quote-names --events --routines --databases '
> + '[' no = yes ']'
> + touch
> /var/lib/automysqlbackup/daily/dbname/dbname_2021-04-06_15h01m.mardi.sql
> + chmod 600
> /var/lib/automysqlbackup/daily/dbname/dbname_2021-04-06_15h01m.mardi.sql
> + '[' -z '' -o -z '' ']'
> + mysqldump --defaults-file=/etc/mysql/debian.cnf --opt --quote-names
> --events --routines --databases dbname
> + compression
> /var/lib/automysqlbackup/daily/dbname/dbname_2021-04-06_15h01m.mardi.sql
> + '[' gzip = gzip ']'
> + gzip -f
> /var/lib/automysqlbackup/daily/dbname/dbname_2021-04-06_15h01m.mardi.sql
> + echo
> + echo Backup Information for
> /var/lib/automysqlbackup/daily/dbname/dbname_2021-04-06_15h01m.mardi.sql
> + gzip -l
> /var/lib/automysqlbackup/daily/dbname/dbname_2021-04-06_15h01m.mardi.sql.gz
> + SUFFIX=.gz
> + return 0
> + '[' yes = yes ']'
> + cp dbname.gz /var/lib/automysqlbackup/latest/
> cp: impossible d'évaluer 'dbname.gz': Aucun fichier ou dossier de ce type
> + return 0
> + BACKUPFILES='
> /var/lib/automysqlbackup/daily/dbname/dbname_2021-04-06_15h01m.mardi.sql.gz'
> + echo --
> ++ date
> + echo Backup End mar. 06
Bug#977327: (no subject)
Hi, It seems that ansible 2.9 currently in testing still try to use python 2.7. Using ansible-pull with a playbook using a ansible.builtin.apt task that juste ask for "apt update" just break as it tries to install "python-apt" first and this is not currently available in testing (python3-apt is available). It seems important to me as bulleye soft freeze is started. If I can help in any way, say me. I'm a sysadmin that had occasionally created some local packages, but I'm clearly not a dd. Regards, -- Ludovic Pouzenc www.pouzenc.fr
Bug#983047: Erratum
Erratum : I've written : I don't know if it doable to get them for*buster*, but it should help It wanted to say : I don't know if it doable to get them for*bulleye*, but it should help Sorry, -- Ludovic Pouzenc Ingénieur Informatique de Gestion Direction du Numérique, DN : Applications 04 79 75 83 54
Bug#983047: linux-image-5.10.0-3-amd64: Virtualbox Shared Folder vboxsf in 5.10 is racy / unusable with git clone
Package: src:linux
Version: 5.10.13-1
Severity: normal
Dear Maintainer,
The current kernel in testing has vboxsf properly integrated and signed.
With Buster, we should use VirtualBoxGuestAdditions.iso to dkms it.
It implies linux-headers, dkms, toolchain... 300 or 400 Mio of stuff.
The integrated vboxsf is way easy to use but it currently fails for "git
clone" like work loads. Steps to reproduce :
* install debian testing in a virtualbox VM, everything as default
* configure a shared folder in virtualbox
* mount in from debian VM somewhere
* from VM, go into this folder, then :
* git clone https://a-random-non-empty-public-git-repo.git
* it fails at unpacking stage.
If host is Windows, there is 2 problems (spurious EINTR, and "File Already
exists").
If host is Linux, there is 1 problem (a third one : spurious EPERM)
It's reported, patches are written by one of the person who a have took
the initiative about mainline it, I use it since some weeks locally.
https://bugzilla.kernel.org/show_bug.cgi?id=211171
Hans de Goede has submited patches to fs and char-misc teams.
On 2021-02-18 only 1/5 patches are on linux-next. Kernel fs team seems
not have pickup the 4 remaining patches yet.
I don't know if it doable to get them for buster, but it should help
everyone who tries to use this feature.
Here we use it as a way to give local development env to web developers.
Please found the patches has Hans mailed me, they should appears in
linux-next soon.
-- Package-specific info:
** Version:
Linux version 5.10.0-3-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP
Debian 5.10.13-1 (2021-02-06)
** Not tainted
>From 684a3a9a4570991863398e65840d94ec454eb6ad Mon Sep 17 00:00:00 2001
From: Hans de Goede
Date: Thu, 21 Jan 2021 10:08:59 +0100
Subject: [PATCH v4 1/4] vboxsf: Honor excl flag to the dir-inode create op
Honor the excl flag to the dir-inode create op, instead of behaving
as if it is always set.
Note the old behavior still worked most of the time since a non-exclusive
open only calls the create op, if there is a race and the file is created
between the dentry lookup and the calling of the create call.
While at it change the type of the is_dir parameter to the
vboxsf_dir_create() helper from an int to a bool, to be consistent with
the use of bool for the excl parameter.
Fixes: 0fd169576648 ("fs: Add VirtualBox guest shared folder (vboxsf) support")
Signed-off-by: Hans de Goede
---
fs/vboxsf/dir.c | 16 +---
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/vboxsf/dir.c b/fs/vboxsf/dir.c
index 4d569f14a8d8..c3e68ad6c0f4 100644
--- a/fs/vboxsf/dir.c
+++ b/fs/vboxsf/dir.c
@@ -253,7 +253,7 @@ static int vboxsf_dir_instantiate(struct inode *parent,
struct dentry *dentry,
}
static int vboxsf_dir_create(struct inode *parent, struct dentry *dentry,
-umode_t mode, int is_dir)
+umode_t mode, bool is_dir, bool excl)
{
struct vboxsf_inode *sf_parent_i = VBOXSF_I(parent);
struct vboxsf_sbi *sbi = VBOXSF_SBI(parent->i_sb);
@@ -261,10 +261,12 @@ static int vboxsf_dir_create(struct inode *parent, struct
dentry *dentry,
int err;
params.handle = SHFL_HANDLE_NIL;
- params.create_flags = SHFL_CF_ACT_CREATE_IF_NEW |
- SHFL_CF_ACT_FAIL_IF_EXISTS |
- SHFL_CF_ACCESS_READWRITE |
- (is_dir ? SHFL_CF_DIRECTORY : 0);
+ params.create_flags = SHFL_CF_ACT_CREATE_IF_NEW |
SHFL_CF_ACCESS_READWRITE;
+ if (is_dir)
+ params.create_flags |= SHFL_CF_DIRECTORY;
+ if (excl)
+ params.create_flags |= SHFL_CF_ACT_FAIL_IF_EXISTS;
+
params.info.attr.mode = (mode & 0777) |
(is_dir ? SHFL_TYPE_DIRECTORY : SHFL_TYPE_FILE);
params.info.attr.additional = SHFLFSOBJATTRADD_NOTHING;
@@ -291,13 +293,13 @@ static int vboxsf_dir_create(struct inode *parent, struct
dentry *dentry,
static int vboxsf_dir_mkfile(struct inode *parent, struct dentry *dentry,
umode_t mode, bool excl)
{
- return vboxsf_dir_create(parent, dentry, mode, 0);
+ return vboxsf_dir_create(parent, dentry, mode, false, excl);
}
static int vboxsf_dir_mkdir(struct inode *parent, struct dentry *dentry,
umode_t mode)
{
- return vboxsf_dir_create(parent, dentry, mode, 1);
+ return vboxsf_dir_create(parent, dentry, mode, true, true);
}
static int vboxsf_dir_unlink(struct inode *parent, struct dentry *dentry)
--
2.28.0
>From 315010a5a43a468ea2d5a5d1fdec48c01ecffadd Mon Sep 17 00:00:00 2001
From: Hans de Goede
Date: Thu, 21 Jan 2021 10:22:27 +0100
Subject: [PATCH v4 2/4] vboxsf: Make vboxsf_dir_create() return the handle for
the created file
Make vboxsf_dir_create() optionally return the vboxsf-handle for
Bug#982968: ansible-pull output on terminal is buffered (not live)
Source: ansible Version: 2.9.6+dfsg-1~bpo10+1 Severity: normal Dear Maintainer, Using ansible-pull command from a virtual machine console works but the progression of the work done is not displayed live. It is buffered (4kio ?) and bunch of text appears at once, "too late". It shows up also via ssh but with a less big buffer (less annoying, but happens too). For me it affects current buster and current buster-backports. I didn't see any clue upstream about solving this issue. I just report it here for now. I expect that the output should be live as when using ansible-playbook. Code appears to handle that. strace shows up many unbuffered read from forked ansible commands, but only a few big writes to terminal. Please find attached a patch that works for me on 2.9 and 2.7. I suspect that is an upstream that may be distro-agnotic bug but I didn't tried it elsewhere right now. diff --git a/ansible/utils/cmd_functions.py b/ansible/utils/cmd_functions.py index 7a0fb23..ef6cb14 100644 --- a/ansible/utils/cmd_functions.py +++ b/ansible/utils/cmd_functions.py @@ -57,6 +57,7 @@ def run_cmd(cmd, live=False, readsize=10): sys.stdout.buffer.write(dat) else: sys.stdout.write(dat) +sys.stdout.flush() stdout += dat if dat == b'': rpipes.remove(p.stdout) @@ -69,6 +70,7 @@ def run_cmd(cmd, live=False, readsize=10): sys.stdout.buffer.write(dat) else: sys.stdout.write(dat) +sys.stdout.flush() if dat == b'': rpipes.remove(p.stderr) # only break out if we've emptied the pipes, or there is nothing to I may have tested onnly 1 code path of the two that are patched above. I am unclear about python 2/3 mixing and ansible on Debian 10. -- System Information: Debian Release: 10.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-0.bpo.5-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff --git a/ansible/utils/cmd_functions.py b/ansible/utils/cmd_functions.py index 7a0fb23..ef6cb14 100644 --- a/ansible/utils/cmd_functions.py +++ b/ansible/utils/cmd_functions.py @@ -57,6 +57,7 @@ def run_cmd(cmd, live=False, readsize=10): sys.stdout.buffer.write(dat) else: sys.stdout.write(dat) +sys.stdout.flush() stdout += dat if dat == b'': rpipes.remove(p.stdout) @@ -69,6 +70,7 @@ def run_cmd(cmd, live=False, readsize=10): sys.stdout.buffer.write(dat) else: sys.stdout.write(dat) +sys.stdout.flush() if dat == b'': rpipes.remove(p.stderr) # only break out if we've emptied the pipes, or there is nothing to
Bug#982961: tomcat9: cron.daily/tomcat9 compress /var/log/tomcat9 *subfolders* breaking some deployed apps
Package: tomcat9 Version: 9.0.31-1~deb10u3 Severity: normal Dear Maintainer, I have deployed some tomcat apps. The have thier own logging facilities outputing plain files. I thing tomcat9 packages invite me to put them under a subfolder of /Var/log/tomcat9. If I do that, cron.daily/tomcat9 gzip them, even if they live, even if they are not rotated, and it fail every day starting on installation day + 1 (at 2nd cron exec). Similar but different from #925926 as it concerns application logs and not tomcat own logs. tomcat9.service systemd unit restrict app writes heavily (great) : lpouzenc@lud-hp1:~$ grep ^Read /lib/systemd/system/tomcat9.service ReadWritePaths=/etc/tomcat9/Catalina/ ReadWritePaths=/var/lib/tomcat9/webapps/ ReadWritePaths=/var/log/tomcat9/ I didn't see any documentation mentionning that subfolders there are handled by debian script... but it does : lpouzenc@lud-hp1:~$ grep -A 1 '^\s*find' /etc/cron.daily/tomcat9 find /var/log/$NAME/ -name \*.$EXT -daystart -mtime +0 -print0 \ | xargs --no-run-if-empty -0 gzip -9 (because there is no -maxdepth 1) So this cron gzip some app's live logs, and mail sysadmin everynight (except first one) with about .gz file that already exists in those subfolders, assuming the deployed app have at least one log file that have a stable filename without date of the day in it. Maybe the cron should only handle tomcat own logs (catalina.out is already excluded by $EXT). OR may be default unit should provide a writable subfolders for the app logs to be deployed by users by default. Thanks for all the packaging work already well done. Regards, Ludovic Pouzenc -- System Information: Debian Release: 10.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-0.bpo.5-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tomcat9 depends on: ii lsb-base10.2019051400 ii systemd 241-7~deb10u6 ii tomcat9-common 9.0.31-1~deb10u3 ii ucf 3.0038+nmu1 Versions of packages tomcat9 recommends: ii libtcnative-1 1.2.21-1 Versions of packages tomcat9 suggests: pn tomcat9-admin pn tomcat9-docs pn tomcat9-examples pn tomcat9-user -- Configuration Files: /etc/tomcat9/policy.d/01system.policy [Errno 13] Permission non accordée: '/etc/tomcat9/policy.d/01system.policy' /etc/tomcat9/policy.d/02debian.policy [Errno 13] Permission non accordée: '/etc/tomcat9/policy.d/02debian.policy' /etc/tomcat9/policy.d/03catalina.policy [Errno 13] Permission non accordée: '/etc/tomcat9/policy.d/03catalina.policy' /etc/tomcat9/policy.d/04webapps.policy [Errno 13] Permission non accordée: '/etc/tomcat9/policy.d/04webapps.policy' /etc/tomcat9/policy.d/50local.policy [Errno 13] Permission non accordée: '/etc/tomcat9/policy.d/50local.policy' -- no debconf information
Bug#929896: diffutils: diff -r found devnodes of same minor/major as different in some cases
Package: diffutils Version: 1:3.7-3 Severity: minor Dear Maintainer, I found a diff strangeness by accident while diffing two chroot trees. It seems to be always reproductible for me, at least on this example : root@lud-mn1:~# mkdir a b c; mknod a/null c 1 3; sleep .1; mknod b/null c 1 3; sleep 1; mknod c/null c 1 3 diffing the files 2 by 2 on one side, and diffing the folders 2 by 2 on other side give different results. I was expecting all following commands to give a 0 return code and no output : root@lud-mn1:~# LANG=C diff a/null b/null; echo $? 0 root@lud-mn1:~# LANG=C diff b/null c/null; echo $? 0 root@lud-mn1:~# LANG=C diff -r a b; echo $? 0 root@lud-mn1:~# LANG=C diff -r b c; echo $? File b/null is a character special file while file c/null is a character special file 1 For completeness, stat output to show that all timestamps are different. I am on a regular ext4 mountpoint. root@lud-mn1:~# LANG=C stat ?/null File: a/null Size: 0 Blocks: 0 IO Block: 4096 character special file Device: 807h/2055d Inode: 522435 Links: 1 Device type: 1,3 Access: (0644/crw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2019-06-02 21:39:41.061736947 +0200 Modify: 2019-06-02 21:39:41.061736947 +0200 Change: 2019-06-02 21:39:41.061736947 +0200 Birth: - File: b/null Size: 0 Blocks: 0 IO Block: 4096 character special file Device: 807h/2055d Inode: 547588 Links: 1 Device type: 1,3 Access: (0644/crw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2019-06-02 21:39:41.165737120 +0200 Modify: 2019-06-02 21:39:41.165737120 +0200 Change: 2019-06-02 21:39:41.165737120 +0200 Birth: - File: c/null Size: 0 Blocks: 0 IO Block: 4096 character special file Device: 807h/2055d Inode: 547590 Links: 1 Device type: 1,3 Access: (0644/crw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2019-06-02 21:39:42.165738785 +0200 Modify: 2019-06-02 21:39:42.165738785 +0200 Change: 2019-06-02 21:39:42.165738785 +0200 Birth: - root@lud-mn1:~# LANG=C df -h . Filesystem Size Used Avail Use% Mounted on /dev/sda7 16G 14G 1.3G 92% / root@lud-mn1:~# mount | grep ^/dev/sda7 /dev/sda7 on / type ext4 (rw,noatime,discard,errors=remount-ro) This clearly do not cause real important troubles to me. But may be nasty for containers fans. -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/6 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages diffutils depends on: ii libc6 2.28-10 diffutils recommends no packages. Versions of packages diffutils suggests: pn diffutils-doc pn wdiff -- no debconf information
Bug#929172: Same issue as already reported, and partially fixed
I can confirm that packages landed in unstable solve the situation for me (libdebian-installer4 0.119, cdebootstrap 0.7.7+b12, cdebootstrap-static 0.7.7+b12). At time if writing, it's seem not landed in testing yet. Thanks to all involved people. -- Ludovic Pouzenc www.pouzenc.fr This is GNU/Linux land. In silent nights you can hear the Windows machines rebooting.
Bug#927831: (no subject)
Picking some parts of the strace from attached
strace-lspci-dmesg-dpkg-config-pulse.tar.bz2/buster/nouveau-hdmi/terminal-output
ludovic@lud-mn1:~$ strace -fftttTAo /dev/shm/gn-sh -p "$(pidof gnome-shell)" & strace
-fftttTAo /dev/shm/pulse -p "$(pidof pulseaudio)" &
[1] 8271
[2] 8272
ludovic@lud-mn1:~$ strace: Process 6509 attached with 26 threads
strace: Process 6556 attached with 4 threads
*qwertggg^C*
ludovic@lud-mn1:~$ kill %1 %2
strace: Process 6509 detached
[...]
ludovic@lud-mn1:~$ grep -vE '(futex|poll)' /dev/shm/* | sed -ne
's/^\(.*\)<\([0-9.]\+\)>/\2 \1/p' | sort -rn | head
grep: /dev/shm/mb: est un dossier
*2.380555* /dev/shm/pulse.6557:1556048473.471096 openat(AT_FDCWD,
"*/dev/snd/pcmC0D3p*", O_RDWR|O_NONBLOCK|O_CLOEXEC) = 29
0.189954 /dev/shm/pulse.6557:1556048475.853690 ioctl(29,
SNDRV_PCM_IOCTL_PREPARE, 0x199d) = 0
0.000499 /dev/shm/gn-sh.6509:1556048476.717525 ioctl(13,
DRM_IOCTL_NOUVEAU_GEM_NEW, 0x7ffd0f29c110) = 0
[...]
ludovic@lud-mn1:~$ grep . /dev/shm/* | sed -ne 's/^\(.*\)<\([0-9.]\+\)>/\2
\1/p' | grep ^2
2.578621 /dev/shm/gn-sh.6509:1556048473.467013 futex(*0x55d9a144852c*,
FUTEX_WAIT_PRIVATE, 0, NULL) = 0
2.578165 /dev/shm/gn-sh.6555:1556048473.467158 poll([{fd=43, events=POLLIN},
{fd=46, events=POLLIN}, {fd=47, events=POLLIN}], 3, 3) = 1 (*[{fd=47,
revents=POLLIN}]*)
2.574173 /dev/shm/pulse.6556:1556048473.469774 futex(0x5627a9e5ef10,
FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL,
FUTEX_BITSET_MATCH_ANY) = 0
2.380555 /dev/shm/pulse.6557:1556048473.471096 openat(AT_FDCWD,
"/dev/snd/pcmC0D3p", O_RDWR|O_NONBLOCK|O_CLOEXEC) = 29
ludovic@lud-mn1:~$ grep -F 0x55d9a144852c /dev/shm/*
/dev/shm/gn-sh.6509:1556048473.467013 futex(0x55d9a144852c, FUTEX_WAIT_PRIVATE, 0,
NULL) = 0 <2.578621>
/dev/shm/gn-sh.6555:1556048476.045573 futex(0x55d9a144852c, FUTEX_WAKE_PRIVATE,
2147483647) = 1 <0.19>
ludovic@lud-mn1:~$ lsof -np $(pidof gnome-shell) > /dev/shm/gn-sh.lsof
lsof: WARNING: can't stat() ext4 file system /media/lpouzenc/Debian9-gaming
Output information may be incomplete.
[...]
gnome-she 6509 ludovic 41u unix 0x8eb7907f 0t0 71920
type=STREAM
gnome-she 6509 ludovic 42u a_inode 0,1308365
[eventfd]
gnome-she 6509 ludovic 43r FIFO 0,12 0t0 71923 pipe
gnome-she 6509 ludovic 44w FIFO 0,12 0t0 71923 pipe
gnome-she 6509 ludovic 45u a_inode 0,1308365
[eventfd]
gnome-she 6509 ludovic 46u unix 0x46a9941d 0t0 71926
type=STREAM
gnome-she 6509 ludovic 47u a_inode 0,1308365
[eventfd]
gnome-she 6509 ludovic 48u a_inode 0,1308365
[timerfd]
[...]
ludovic@lud-mn1:~$ lsof -np $(pidof pulseaudio) > /dev/shm/pulse.lsof
lsof: WARNING: can't stat() ext4 file system /media/lpouzenc/Debian9-gaming
Output information may be incomplete.
[...]
pulseaudi 6556 ludovic 22u unix 0xdfc5bc44 0t0 102049
/run/user/1001/pulse/native type=STREAM
pulseaudi 6556 ludovic 23u CHR 116,13 0t0 26845
/dev/snd/controlC0
pulseaudi 6556 ludovic 24u CHR 116,7 0t0 21579
/dev/snd/controlC1
pulseaudi 6556 ludovic 25u a_inode 0,130 8365
[eventfd]
pulseaudi 6556 ludovic 26u a_inode 0,130 8365
[eventfd]
pulseaudi 6556 ludovic 27u a_inode 0,130 8365
[eventfd]
pulseaudi 6556 ludovic*28u* a_inode 0,130 8365
[eventfd]
pulseaudi 6556 ludovic*31u* CHR 116,7 0t0 21579
/dev/snd/controlC1
pulseaudi 6556 ludovic 32u a_inode 0,130 8365
[eventfd]
pulseaudi 6556 ludovic 33u a_inode 0,130 8365
[eventfd]
pulseaudi 6556 ludovic 34u a_inode 0,130 8365
[eventfd]
pulseaudi 6556 ludovic 35u a_inode 0,130 8365
[eventfd]
pulseaudi 6556 ludovic 36u CHR 116,7 0t0 21579
/dev/snd/controlC1
[...]
ludovic@lud-mn1:~$ dpkg -l | grep -E '^ii
(gnome-shell|dbus|pulseaudio|linux-image-4.19.0-4-amd64) '
ii dbus 1.12.12-1
amd64simple interprocess messaging system (daemon and utilities)
ii gnome-shell 3.30.2-7
amd64graphical shell for the GNOME desktop
ii linux-image-4.19.0-4-amd644.19.28-2
amd64Linux 4.19 for 64-bit PCs (signed)
ii pulseaudio12.2-4
amd64PulseAudio sound server
Regards,
--
Ludovic Pouzenc
www.pouzenc.fr
This is GNU/Linux land. In silent nights you can hear the Windows machines
rebooting.
Bug#927833: gnome-shell: any user can definitely freeze a seat, preventing any VT switch
Package: gnome-shell Version: 3.32.1-1 Severity: normal Dear Maintainer, While trying to get trace for #927831, I realized that any user that have an active gnome3 wayland session could lock-up the whole seat, preventing any VT switch just by starting a gnome-terminal and typing : ludovic@lud-mn1:~$ kill -SIGSTOP $(pidof gnome-shell) The only thing I can think of to get unstuck is : * force poweroff with button * Alt + PrintScrn + B (magic keys for sysrq "reBoot") Resulting in loose all things (files) opened by all (others) users. It could been seen as a defect in user input event loop processing at a global scope. It could be seen as security related. Regards, Ludovic
Bug#903197: similar troubles in the past
It seems Debian 9 was getting this sort of problem too, but with Network-Manager : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760029 https://github.com/systemd/systemd/issues/4271 Saving/restoring entropy seems to not be the point (bug 760029, msg 47): In other words, the seed that is loaded at boot time can only help the randomness of the random device, but not its estimate and therefore not its "blockingness". Regards, Le 07/07/2018 à 16:03, Ludovic Pouzenc a écrit : Hi, I missed to indicate that I have enabled gdm3 autologin for the username "lpouzenc" and I was expecting my gnome session auto-load without waiting me to generate some entropy. Regards, -- Ludovic Pouzenc www.pouzenc.fr This is GNU/Linux land. In silent nights you can hear the Windows machines rebooting.
Bug#903197: Missing infomations
Hi, I missed to indicate that I have enabled gdm3 autologin for the username "lpouzenc" and I was expecting my gnome session auto-load without waiting me to generate some entropy. Regards, -- Ludovic Pouzenc www.pouzenc.fr This is GNU/Linux land. In silent nights you can hear the Windows machines rebooting.
Bug#901990: linux-image-4.16.0-2-amd64: kernel BUG at startup in usercopy.c ; impossible to boot
Package: nvidia-kernel-dkms Version: 390.48-2~bpo9+3 Followup-For: Bug #901990 Dear Maintainer, It happens to me to, with AMD Ryzen and 4.16.0-0.bpo.2-amd64. I am fine with 4.16.0-0.bpo.1-amd64. I've rebooted on vmlinux.old to reportbug. I'll try driver from sid. -- Package-specific info: uname -a: Linux lud-MN1 4.16.0-0.bpo.1-amd64 #1 SMP Debian 4.16.5-1~bpo9+1 (2018-05-06) x86_64 GNU/Linux /proc/version: Linux version 4.16.0-0.bpo.1-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP Debian 4.16.5-1~bpo9+1 (2018-05-06) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) lspci 'display controller [030?]': 07:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP106 [GeForce GTX 1060 3GB] [1043:85b9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidia dmesg: Device node permissions: crw-rw+ 1 root video 226, 0 Jul 4 19:57 /dev/dri/card0 crw-rw+ 1 root video 226, 128 Jul 4 19:57 /dev/dri/renderD128 crw-rw-rw- 1 root root 195, 254 Jul 4 19:57 /dev/nvidia-modeset crw-rw-rw- 1 root root 195, 0 Jul 4 19:57 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Jul 4 19:57 /dev/nvidiactl video:x:44:lpouzenc OpenGL and NVIDIA library files installed: lrwxrwxrwx 1 root root 15 Feb 17 12:02 /etc/alternatives/glx -> /usr/lib/nvidia lrwxrwxrwx 1 root root 42 Feb 17 12:02 /etc/alternatives/glx--libEGL.so.1-i386-linux-gnu -> /usr/lib/i386-linux-gnu/nvidia/libEGL.so.1 lrwxrwxrwx 1 root root 44 Feb 17 12:02 /etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1 lrwxrwxrwx 1 root root 41 Feb 17 12:02 /etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> /usr/lib/i386-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 41 Feb 17 12:02 /etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> /usr/lib/i386-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Feb 17 12:02 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Feb 17 12:02 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 48 Feb 17 12:02 /etc/alternatives/glx--libGLESv1_CM.so.1-i386-linux-gnu -> /usr/lib/i386-linux-gnu/nvidia/libGLESv1_CM.so.1 lrwxrwxrwx 1 root root 48 Feb 17 12:02 /etc/alternatives/glx--libGLESv1_CM.so.1-i386-linux-gnu -> /usr/lib/i386-linux-gnu/nvidia/libGLESv1_CM.so.1 lrwxrwxrwx 1 root root 50 Feb 17 12:02 /etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1 lrwxrwxrwx 1 root root 50 Feb 17 12:02 /etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1 lrwxrwxrwx 1 root root 45 Feb 17 12:02 /etc/alternatives/glx--libGLESv2.so.2-i386-linux-gnu -> /usr/lib/i386-linux-gnu/nvidia/libGLESv2.so.2 lrwxrwxrwx 1 root root 45 Feb 17 12:02 /etc/alternatives/glx--libGLESv2.so.2-i386-linux-gnu -> /usr/lib/i386-linux-gnu/nvidia/libGLESv2.so.2 lrwxrwxrwx 1 root root 47 Feb 17 12:02 /etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2 lrwxrwxrwx 1 root root 47 Feb 17 12:02 /etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2 lrwxrwxrwx 1 root root 49 Feb 17 12:02 /etc/alternatives/glx--libnvidia-cfg.so.1-i386-linux-gnu -> /usr/lib/i386-linux-gnu/nvidia/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 51 Feb 17 12:02 /etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 25 Feb 17 12:02 /etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so lrwxrwxrwx 1 root root 42 Feb 17 12:02 /etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> /etc/nvidia/nvidia-blacklists-nouveau.conf lrwxrwxrwx 1 root root 36 Feb 17 12:02 /etc/alternatives/glx--nvidia-bug-report.sh -> /usr/lib/nvidia/nvidia-bug-report.sh lrwxrwxrwx 1 root root 39 Feb 17 12:02 /etc/alternatives/glx--nvidia-drm-outputclass.conf -> /etc/nvidia/nvidia-drm-outputclass.conf lrwxrwxrwx 1 root root 28 Feb 17 12:02 /etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf lrwxrwxrwx 1 root root 32 Feb 17 12:02 /etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf lrwxrwxrwx 1 root root
Bug#867661: Typo + precision about mouse cursor
Sorry about the not-os-weel reviewed subject with a big typo (read gnome-on-wayland instead). In the videos, the mouse cursor is not updated correctly. I think this is a (gnome-)recorder related problem, this does not happens on my screen. The sole problem is spurious clicks. Cheers, -- Ludovic Pouzenc www.pouzenc.fr This is GNU/Linux land. In silent nights you can hear the Windows machines rebooting.
Bug#812200: installation-guide: Syslinux.cfg snippet in doc is misleading (4.1 Preparing Files for USB Memory)
Source: installation-guide Severity: normal Dear Maintainer, In 4.3.3. Manually copying files to the USB stick — the flexible way, there is a syslinux.cfg snippet : default vmlinuz append initrd=initrd.gz This particular one does not work for me : kernel panic when mount root. Seen on jessie / amd64 current hd-images. I *think* that this conf boots vmlinuz without appending the parameters. A working minimal conf from syslinux doc, adapted for hd-media is : DEFAULT linux LABEL linux KERNEL vmlinuz APPEND initrd=initrd.gz Cheers, Ludovic -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#682562: (no subject)
Hi, This affects me too. Saw 500 error, checked the logs, saw the whole web page in apache error.log. Read README.Debian : nothing. Hopefully, found this open bug on my second web search about this "glitch". Many thanks for huge and high quality work almost everywhere :) Cheers, Ludovic
Bug#799851: (no subject)
Hi, Thanks for the info about the deprecation / future remove. No problem for me about using libapache2-mod-php5. Hoping this bug report will save time for sysadmin that will fall into this bad behavior. Is that packages will be removed in Jessie+1 ? Regards, Ludovic
Bug#799851: (no subject)
On FusionInventory Agent, with debug enbled, logs contains the following : XML not well formed! -- Ludovic Pouzenc - Administrateur Système CUFR J.-F. Champollion, Site d'Albi Tél: 05.63.48.64.08, ext. 2221# Unix is user-friendly; it's just picky about who its friends are.
Bug#799851: libapache2-mod-php5filter: HTTP_RAW_POST_DATA mangled when bin data is sent in HTTP POST request
Package: libapache2-mod-php5filter Version: 5.6.13+dfsg-0+deb8u1 Severity: important Dear Maintainer, When using Fusion Inventory plugin over GLPI 0.84 (from debian repo), we have hit a bug. It happens when the agent tries to send a huge (30k) XML chunk, xlib compressed over HTTP POST. The PHP code in Fusion Inventory uses $HTTP_RAW_POST_DATA. We have found that the binary blob in the POST is around 13kB but the PHP var contains way less data, like 120 bytes or 1.5 kB in other situations. Tried php://input : same size as in $HTTP_RAW_POST_DATA. In apache2 log, shitty things happens : 172.16.2.120 - - [23/Sep/2015:10:50:40 +0200] "POST /glpi/plugins/fusioninventory/ HTTP/1.1" 200 0 "-" "FusionInventory-Agent_v2.3.16" 172.16.2.120 - - [23/Sep/2015:10:50:40 +0200] "\x9cv\xdej\xc0\xe3e\xc2H\xc5\x99\x0e" 400 0 "-" "-" With Wireshark, we have found that on the HTTP connection, there is 2 replies on the Fusion Inventory single request (an HTTP/200 from PHP, a HTTP 400 from apache). Everything starts to work normally when replacing libapache2-mod-php5filter with libapache2-mod-php5. The expected behavior is to have $HTTP_RAW_POST_DATA or php://input reflecting the whole binary data sent over the wire. You could check in atttachement the tcp tchat between fusion Inventory agent and theh GLPI server. Taken from Wireshark / follow TCP stream / Save as... The agent talks first with HTTP POSTING a "big" blob, then server replies HTTP/1.1 200 OK with another zlib compressed blob and a second reply (without any request from the agent) is sent by apache (HTTP 400). -- Package-specific info: Additional PHP 5 information PHP 5 SAPI (php5query -S): cli apache2filter PHP 5 Extensions (php5query -M -v): opcache (Enabled for cli by maintainer script) opcache (Enabled for apache2filter by maintainer script) json (Enabled for cli by maintainer script) json (Enabled for apache2filter by maintainer script) readline (Enabled for cli by maintainer script) readline (Enabled for apache2filter by maintainer script) pdo (Enabled for cli by maintainer script) pdo (Enabled for apache2filter by maintainer script) Configuration files: [PHP] engine = On short_open_tag = Off asp_tags = Off precision = 14 output_buffering = 4096 zlib.output_compression = Off implicit_flush = Off unserialize_callback_func = serialize_precision = 17 disable_functions = pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority, disable_classes = zend.enable_gc = On expose_php = Off max_execution_time = 30 max_input_time = 60 memory_limit = 128M error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT display_errors = Off display_startup_errors = Off log_errors = On log_errors_max_len = 1024 ignore_repeated_errors = Off ignore_repeated_source = Off report_memleaks = On track_errors = Off html_errors = On variables_order = "GPCS" request_order = "GP" register_argc_argv = Off auto_globals_jit = On post_max_size = 8M auto_prepend_file = auto_append_file = default_mimetype = "text/html" default_charset = "UTF-8" doc_root = user_dir = enable_dl = Off file_uploads = On upload_max_filesize = 2M max_file_uploads = 20 allow_url_fopen = On allow_url_include = Off default_socket_timeout = 60 [CLI Server] cli_server.color = On [Date] [filter] [iconv] [intl] [sqlite] [sqlite3] [Pcre] [Pdo] [Pdo_mysql] pdo_mysql.cache_size = 2000 pdo_mysql.default_socket= [Phar] [mail function] SMTP = localhost smtp_port = 25 mail.add_x_header = On [SQL] sql.safe_mode = Off [ODBC] odbc.allow_persistent = On odbc.check_persistent = On odbc.max_persistent = -1 odbc.max_links = -1 odbc.defaultlrl = 4096 odbc.defaultbinmode = 1 [Interbase] ibase.allow_persistent = 1 ibase.max_persistent = -1 ibase.max_links = -1 ibase.timestampformat = "%Y-%m-%d %H:%M:%S" ibase.dateformat = "%Y-%m-%d" ibase.timeformat = "%H:%M:%S" [MySQL] mysql.allow_local_infile = On mysql.allow_persistent = On mysql.cache_size = 2000 mysql.max_persistent = -1 mysql.max_links = -1 mysql.default_port = mysql.default_socket = mysql.default_host = mysql.default_user = mysql.default_password = mysql.connect_timeout = 60 mysql.trace_mode = Off [MySQLi] mysqli.max_persistent = -1 mysqli.allow_persistent = On mysqli.max_links = -1 mysqli.cache_size = 2000 mysqli.default_port = 3306 mysqli.default_socket = mysqli.default_host = mysqli.default_user = mysqli.default_pw = mysqli.reconnect = Off [mysqlnd] mysqlnd.collect_statistics = On mysqlnd.collect_memory_statistics = Off [OCI8] [PostgreSQL] pgsql.allow_persistent = On pgsql.auto_reset_persistent = Off pgsql.max_persistent = -1 pgsql.max_links = -1 pgsql.ignore_notice = 0 pgsql.log_notice = 0 [Sybase-CT] sybct.allow_persistent = On sybct.max_persistent = -1 sybct.max_links =
Bug#783963: tracker-extract runs concurrently with updatedb.mlocate when opening Gnome session
Hi all and thanks for replies.
It seems that trackers already runs under ionice (at least on my machine)
.
2146 lpouzenc 20 0 465412 15988 8168 S 96,6 0,4 0:05.16
tracker-store
2132 lpouzenc 39 19 1104792 19016 11496 R 58,0 0,5 0:05.68
tracker-miner-f
lpouzenc@lud-GB1:~$ ionice -p 2146 2132
idle
idle
I was thinking to suggest using pid file to signal existance of other
crawlers instances. For /var/run, Debian FHS says program-name.pid,
so may use a generic folder like /var/run/crawlers/ or so. /var/lock is
more apropriate ? Already rwxrwxrwx although.
https://www.debian.org/doc/packaging-manuals/fhs/fhs-2.3.html#VARLOCKLOCKFILES
Lock files for devices and other resources shared by multiple
applications, such as the serial device lock files that were originally
found in either /usr/spool/locks or /usr/spool/uucp, must now be stored
in /var/lock.
There is probably a problem about the ownership of the suggestion
subfolder (which package creates it, which user/group/rights on the folder).
strace suggest that mlocate protect itself from parallel exec by locking
his db file.
open(/var/lib/mlocate/mlocate.db, O_RDWR) = 4
read(4, \0mlocate\0\0\0\370\0\1\0\0/\0prune_bind_mou..., 8192) = 8192
fcntl(4, F_SETLK, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) =
-1 EAGAIN (Resource temporarily unavailable)
tracker-control opens all /proc/*/cmdline to find his friends ? Sounds
weird.
lpouzenc@lud-GB1:~$ strace -ff -e lstat tracker-control 21
Found 210 PIDs…
Process 3210 attached
[pid 3209] lstat(/proc/3209/cmdline, {st_mode=S_IFREG|0444,
st_size=0, ...}) = 0
[pid 3209] lstat(/proc/1/cmdline, {st_mode=S_IFREG|0444,
st_size=0, ...}) = 0
[pid 3209] lstat(/proc/2/cmdline, {st_mode=S_IFREG|0444,
st_size=0, ...}) = 0
[pid 3209] lstat(/proc/3/cmdline, {st_mode=S_IFREG|0444,
st_size=0, ...}) = 0
[pid 3209] lstat(/proc/5/cmdline, {st_mode=S_IFREG|0444,
st_size=0, ...}) = 0
[pid 3209] lstat(/proc/7/cmdline, {st_mode=S_IFREG|0444,
st_size=0, ...}) = 0
It seems that updatedb.mlocate and tracker does not use any pid file..
so I may go wrong :)
Why tracker don't use PID's ? It about the random user of the spawned
processes ?
Potential troll : Is systemd could solve that ? (I know that tracker is
started via xdg autostart and updatedb via cron)
Regards,
Ludovic
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783964: screenshot: Spurious triggers of activity menu while validating screenshot region
Hi, Additionnal info : I have disabled the functionnality that open Activity overlay without any click. (I don't know the right english wording about this functionnality). The bug with screenshot occurs even in this config. I was thinking about an uninitialised [0;0] pointer coords in some way that triggers the hot spot... but no. Regards, Ludovic -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783964: gnome-screenshot: Spurious triggers of activity menu while validating screenshot region
Package: gnome-screenshot Version: 3.14.0-1 Severity: normal Dear Maintainer, On my fresh defaut install of Debian 8 with dual monitor setup on ATI card, I have pseudo random problem while trying to screenshot a region of my main screen. I trigger gnome-screenshot by pressing Ctrl+Alt+Printscreen, draw a region from upper-left corner to bottom-right. Sometimes the region is the right one and every goes ok, sometime the region start at position that is not the cursor one (may be a x==0 on current screen ?) then Activity menu is trggered then the screenshot is taken but not contains what I want to screenshot. There is also stange region drawing when going bottom without any x variation. Seems tru in the reverse : moving on x axis without variying on y. 2 videos for illustrating the whole fuck :) http://www.pouzenc.fr/misc/tmp/gnome-screenshot-triggers-activity-menu.webm http://www.pouzenc.fr/misc/tmp/gnome-screenshot-triggers-strange-rects.webm I don't know how to report it properly upstream and if gnome-screenshot is the root source of the problem. Cheers, Ludovic -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-screenshot depends on: ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii libc62.19-18 ii libcairo21.14.0-2.1 ii libcanberra-gtk3-0 0.30-2.1 ii libcanberra0 0.30-2.1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk-3-0 3.14.5-1 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 gnome-screenshot recommends no packages. gnome-screenshot suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783963: tracker-extract runs concurrently with updatedb.mlocate when opening Gnome session
Package: tracker Version: 1.2.4-2 Severity: normal Dear Maintainer, Right after booting and logging into a fresh default install of Debian 8 with a good quantity of files imported into ~/Documents/ my system came very slow. This seems to happens roughly on each boot. Opening a terminal takes 2 or 3 seconds. top says : PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2156 lpouzenc 39 19 1723740 89952 32812 D 16,6 2,2 0:59.10 tracker-extract 2159 lpouzenc 20 0 479944 33744 S 12,3 0,8 1:25.00 tracker-store 2233 lpouzenc 20 0 130956 6284 5348 S 1,3 0,2 0:07.84 gvfsd-metadata 2439 lpouzenc 20 0 421344 30744 4 S 1,3 0,8 0:02.05 gnome-terminal- 2896 root 20 06904 2460 1856 D 1,3 0,1 0:04.77 updatedb.mlocat 812 root 20 0 250200 45012 23656 S 0,7 1,1 0:05.02 Xorg updatedb.mlocate eats IO, tracker-extract too, and when started together everything goes slow, heads of my HDD go crazy. Please try to see what you could do for preventing multiples file crawler programs to be ran concurrently. If you cannot make simple things, around that just defer a bit tracker update upon session start. À là Windows (tm). -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages tracker depends on: ii dbus 1.8.16-1 ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii libc62.19-18 ii libexempi3 2.2.1-2 ii libglib2.0-0 2.42.1-1 ii libtracker-control-1.0-0 1.2.4-2 ii libtracker-sparql-1.0-0 1.2.4-2 ii shared-mime-info 1.3-1 Versions of packages tracker recommends: ii tracker-gui 1.2.4-2 ii tracker-miner-fs 1.2.4-2 ii tracker-utils 1.2.4-2 tracker suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783964: Info received (gnome-screenshot: Spurious triggers of activity menu while validating screenshot region)
Hi again and again,
I went wrong, it seems the offending code is now in JavaScript in
gnome-shell (may in js/ui/screenshot.js).
It's purely unreadable and uncommented. Worst, I have no clue to dump
out values in code like :
_onMotionEvent: function(actor, event) {
if (this._startX == -1 || this._startY == -1)
return Clutter.EVENT_PROPAGATE;
[this._lastX, this._lastY] = event.get_coords();
let geometry = this._getGeometry();
this._rubberband.set_position(geometry.x, geometry.y);
this._rubberband.set_size(geometry.width, geometry.height);
return Clutter.EVENT_PROPAGATE;
},
I could try to keep calm and trace this if you have any pointers for me
about overring things in gnome-shell :)
Ludovic
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783964: gnome-screenshot: Spurious triggers of activity menu while validating screenshot region
Hi again, I think finally gnome-screenshot is not affected while I added huge debug in the code... and it clearly does not run at all. sources.debian.net allows me to see that gnome-screenshot code have been duplicated in mate-utils. Please correct my mistake. (gnome-screenshot = mate-utils) Regards, Ludovic -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758782: tiger: TigerCron should randomize start time
Package: tiger
Version: 1:3.2.3-10
Severity: wishlist
Dear Maintainer,
In virtualized environnements, tiger could cause I/O storms. An example of bad
situation :
tiger with default conf on 15 VM in a same KVM host.
The first August at 2:00 AM , all VM + the host starts find_files check.
IO load gets very high at 02:01 and other services are impacted.
I think we could imitate apt cron behavior to randomize start time, adjusting
the minute part only. Basicaly they use a sleep $(random 1800).
I this could be done only by altering the tigercron script and adding a
function like the apt one :
From wheezy default /etc/cron.daily/apt :
# sleep for a random interval of time (default 30min)
# (some code taken from cron-apt, thanks)
random_sleep()
{
RandomSleep=1800
eval $(apt-config shell RandomSleep APT::Periodic::RandomSleep)
if [ $RandomSleep -eq 0 ]; then
return
fi
if [ -z $RANDOM ] ; then
# A fix for shells that do not have this bash feature.
RANDOM=$(dd if=/dev/urandom count=1 2 /dev/null | cksum | cut -c1-5)
fi
TIME=$(($RANDOM % $RandomSleep))
debug_echo sleeping for $TIME seconds
sleep $TIME
}
Maybe this introduce some dependancies like coreutils (but seems a common
case).
Regards,
Ludovic
-- System Information:
Debian Release: 7.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages tiger depends on:
ii binutils 2.22-8
ii bsdmainutils 9.0.3
ii debconf [debconf-2.0] 1.5.49
ii libc6 2.13-38+deb7u3
ii net-tools 1.60-24.2
ii ucf3.0025+nmu3
Versions of packages tiger recommends:
ii chkrootkit 0.49-4.1+deb7u2
ii exim4-daemon-light [mail-transport-agent] 4.80-7
ii john 1.7.8-1
ii tripwire 2.4.2.2-2
Versions of packages tiger suggests:
ii lsof 4.86+dfsg-1
-- debconf information:
tiger/mail_rcpt: root
tiger/policy_adapt:
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746304: fglrx-modules-dkms: fglrx module fails to build with kernel built from linux-source/make-kpkg
Hi, You're right my kernel config is stripped down. I've just tried with the new upstream release 14.4 : same compilation error, same fix, build successful. Traces and updated patch attached. With the 14.4 release, I have another bug when running modprobe fglrx about Unknown symbol KCL_AGP_FindCapsRegisters. I beleive that my .config file disable AGP related things entirely... But this is another bug. Should I report this one directly upstream ? Regards, Ludovic Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area cd /var/lib/dkms/fglrx/14.10.1006/build; sh make.sh --nohints --uname_r=3.10.11 --norootcheck(bad exit status: 1) Error! Bad return status for module build on kernel: 3.10.11 (x86_64) Consult /var/lib/dkms/fglrx/14.10.1006/build/make.log for more information. Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area cd /var/lib/dkms/fglrx/14.10.1006/build; sh make.sh --nohints --uname_r=3.10.11 --norootcheck. cleaning build area DKMS: build completed. diff -Naur orig/firegl_public.c new/firegl_public.c --- orig/firegl_public.c 2014-04-29 13:42:55.220613893 +0200 +++ new/firegl_public.c 2014-04-29 13:45:28.088617384 +0200 @@ -146,6 +146,10 @@ #include asm/delay.h #include linux/agp_backend.h +#if LINUX_VERSION_CODE = KERNEL_VERSION(3,10,0) +#include linux/seq_file.h +#endif + #ifndef EXPORT_NO_SYMBOLS #define EXPORT_NO_SYMBOLS #endif Supported adapter detected. Check if system has the tools required for installation. Uninstalling any previously installed drivers. Creating symlink /var/lib/dkms/fglrx/14.10.1006/source - /usr/src/fglrx-14.10.1006 DKMS: add completed. Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area cd /var/lib/dkms/fglrx/14.10.1006/build; sh make.sh --nohints --uname_r=3.10.11 --norootcheck..(bad exit status: 1) [Error] Kernel Module : Failed to build fglrx-14.10.1006 with DKMS [Error] Kernel Module : Removing fglrx-14.10.1006 from DKMS -- Deleting module version: 14.10.1006 completely from the DKMS tree. -- Done. [Reboot] Kernel Module : update-initramfs DKMS make.log for fglrx-14.10.1006 for kernel 3.10.11 (x86_64) Tue Apr 29 13:23:18 CEST 2014 AMD kernel module generator version 2.1 doing Makefile based build for kernel 2.6.x and higher rm -rf *.c *.h *.o *.ko *.a .??* *.symvers make -C /lib/modules/3.10.11/build SUBDIRS=/var/lib/dkms/fglrx/14.10.1006/build/2.6.x modules make[1]: Entering directory `/usr/src/linux-source-3.10' CC [M] /var/lib/dkms/fglrx/14.10.1006/build/2.6.x/firegl_public.o /var/lib/dkms/fglrx/14.10.1006/build/2.6.x/firegl_public.c: In function 'drm_name_info_wrap': /var/lib/dkms/fglrx/14.10.1006/build/2.6.x/firegl_public.c:548:1: error: dereferencing pointer to incomplete type /var/lib/dkms/fglrx/14.10.1006/build/2.6.x/firegl_public.c:548:1: error: dereferencing pointer to incomplete type /var/lib/dkms/fglrx/14.10.1006/build/2.6.x/firegl_public.c:548:1: error: dereferencing pointer to incomplete type /var/lib/dkms/fglrx/14.10.1006/build/2.6.x/firegl_public.c:548:1: error: dereferencing pointer to incomplete type /var/lib/dkms/fglrx/14.10.1006/build/2.6.x/firegl_public.c:548:1: error: dereferencing pointer to incomplete type /var/lib/dkms/fglrx/14.10.1006/build/2.6.x/firegl_public.c:548:1: error: dereferencing pointer to incomplete type /var/lib/dkms/fglrx/14.10.1006/build/2.6.x/firegl_public.c:548:1: error: dereferencing pointer to incomplete type /var/lib/dkms/fglrx/14.10.1006/build/2.6.x/firegl_public.c:548:1: error: dereferencing pointer to incomplete type /var/lib/dkms/fglrx/14.10.1006/build/2.6.x/firegl_public.c:548:1: error: dereferencing pointer to incomplete type /var/lib/dkms/fglrx/14.10.1006/build/2.6.x/firegl_public.c:548:1: error: dereferencing pointer to incomplete type /var/lib/dkms/fglrx/14.10.1006/build/2.6.x/firegl_public.c: In function 'drm_mem_info_wrap': /var/lib/dkms/fglrx/14.10.1006/build/2.6.x/firegl_public.c:549:1: error: dereferencing pointer to incomplete type /var/lib/dkms/fglrx/14.10.1006/build/2.6.x/firegl_public.c:549:1: error: dereferencing pointer to incomplete type /var/lib/dkms/fglrx/14.10.1006/build/2.6.x/firegl_public.c:549:1: error: dereferencing pointer to incomplete type /var/lib/dkms/fglrx/14.10.1006/build/2.6.x/firegl_public.c:549:1: error: dereferencing pointer to incomplete type /var/lib/dkms/fglrx/14.10.1006/build/2.6.x/firegl_public.c:549:1: error: dereferencing pointer to incomplete type /var/lib/dkms/fglrx/14.10.1006/build/2.6.x/firegl_public.c:549:1: error: dereferencing pointer to incomplete type /var/lib/dkms/fglrx/14.10.1006/build/2.6.x/firegl_public.c:549:1: error: dereferencing pointer to incomplete type /var/lib/dkms/fglrx/14.10.1006/build/2.6.x/firegl_public.c:549:1: error: dereferencing pointer to incomplete type
Bug#746304: fglrx-modules-dkms: fglrx module fails to build with kernel built from linux-source/make-kpkg
I've reported the compilation problem at upstream : http://ati.cchtml.com/show_bug.cgi?id=1065 Ludovic -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#737554: dracut-network: Dracut with NFS ro + tmpfs + AUFS give a world-writable rootfs
Package: dracut-network Version: 020-2 Severity: normal Dear Maintainer, I am using dracut because I make automatic debian installation through FAI (fai-server). FAI generates a minimal debian (debootstrap), exported via NFS for PXE booting. FAI wants this scenario : NFS read-only + writable tmpfs + AUFS When I boot a physicial or a virtual machine with PXE, the debian correctly boots, but I have : # ls -ld / drwxrwxrwt 32 root root 260 Feb 3 17:53 / The AUFS mont is done by dracut between a 0755 NFS mount point and a 1777 tmpfs. The resulting merged filesystem keeps 1777. This is not usual nor safe for a root. I expect 0755 for my root. This cause some proprietary MegaRAID cli to complain because it checks if any path component is writable on the path of an important file and the first test : is / writable ? yes. FAI does not seem to change default config values in dracut for this aspects. I have successfully circumvent this problem by altering the tmpfs creation : --- ./usr/lib/dracut/modules.d/90aufs/aufs-mount.sh 2012-11-08 14:54:14.0 +0100 +++ ./usr/lib/dracut/modules.d/90aufs/aufs-mount.sh.new 2014-02-03 18:33:35.827657399 +0100 @@ -23,7 +23,7 @@ mount --move $NEWROOT /live/image mkdir /cow -mount -n -t tmpfs tmpfs /cow +mount -n -t tmpfs -o mode=0755 tmpfs /cow mount -t aufs -o noatime,noxino,dirs=/cow=rw:/live/image=rr aufs $NEWROOT But I'm not sure that this is the right place to do that. And may be it could be tunable by the end-user. -- System Information: Debian Release: 7.3 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dracut-network depends on: ii dracut 020-2 ii iputils-arping 3:20101006-1+b1 ii isc-dhcp-client 4.2.2.dfsg.1-5+deb70u6 Versions of packages dracut-network recommends: pn nbd-client none ii nfs-common 1:1.2.6-4 pn open-iscsi none dracut-network suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#737554: dracut-network: Dracut with NFS ro + tmpfs + AUFS give a world-writable rootfs
Additional information : boot parameters used when PXE booting : # generated by fai-chboot for host bugreport with IP XXX.XXX.XXX.XXX default fai-generated label fai-generated kernel vmlinuz-3.2.0-4-amd64 append initrd=initrd.img-3.2.0-4-amd64 ip=eth0:dhcp root=nfs:/srv/fai/nfsroot/wheezy/amd64:nfsvers=3 aufs rd.lvm=0 FAI_FLAGS=verbose,sshd FAI_ACTION=install On Mon, Feb 3, 2014 at 6:43 PM, Ludovic Pouzenc lpouz...@gmail.com wrote: Package: dracut-network Version: 020-2 Severity: normal Dear Maintainer, I am using dracut because I make automatic debian installation through FAI (fai-server). FAI generates a minimal debian (debootstrap), exported via NFS for PXE booting. FAI wants this scenario : NFS read-only + writable tmpfs + AUFS When I boot a physicial or a virtual machine with PXE, the debian correctly boots, but I have : # ls -ld / drwxrwxrwt 32 root root 260 Feb 3 17:53 / The AUFS mont is done by dracut between a 0755 NFS mount point and a 1777 tmpfs. The resulting merged filesystem keeps 1777. This is not usual nor safe for a root. I expect 0755 for my root. This cause some proprietary MegaRAID cli to complain because it checks if any path component is writable on the path of an important file and the first test : is / writable ? yes. FAI does not seem to change default config values in dracut for this aspects. I have successfully circumvent this problem by altering the tmpfs creation : --- ./usr/lib/dracut/modules.d/90aufs/aufs-mount.sh 2012-11-08 14:54:14.0 +0100 +++ ./usr/lib/dracut/modules.d/90aufs/aufs-mount.sh.new 2014-02-03 18:33:35.827657399 +0100 @@ -23,7 +23,7 @@ mount --move $NEWROOT /live/image mkdir /cow -mount -n -t tmpfs tmpfs /cow +mount -n -t tmpfs -o mode=0755 tmpfs /cow mount -t aufs -o noatime,noxino,dirs=/cow=rw:/live/image=rr aufs $NEWROOT But I'm not sure that this is the right place to do that. And may be it could be tunable by the end-user. -- System Information: Debian Release: 7.3 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dracut-network depends on: ii dracut 020-2 ii iputils-arping 3:20101006-1+b1 ii isc-dhcp-client 4.2.2.dfsg.1-5+deb70u6 Versions of packages dracut-network recommends: pn nbd-client none ii nfs-common 1:1.2.6-4 pn open-iscsi none dracut-network suggests no packages. -- no debconf information -- Ludovic Pouzenc
Bug#705473: thttpd: HTTP Header Content-Type: missing MIME detection for 3GP video (and many others)
Package: thttpd Version: 2.25b-11 Severity: normal Tags: upstream patch thttp use the default text/plain; Content-Type: header for many files types, including 3GP ones. So mobile phones fail to read 3GP videos served by thttpd. Always reproductible : * setup a default thttpd server * put a .3gp in served documentroot * try to GET it via HTTP client. HTTP header will contain Content-Type: text/plain; and is not correct. MIME type detection is done with file extension in thttpd, based on a fixed list at compile time and 3gp extension entry is missing. Attached : a patch that add file extensions present in /etc/mime.types from package mime-support 3.48-1 and are missing in thttpd fixed list. I am not including extensions that have a MIME type contianing an x- prefix (ie non standardised). -- System Information: Debian Release: 6.0.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages thttpd depends on: ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib Versions of packages thttpd recommends: ii logrotate 3.7.8-6Log rotation utility Versions of packages thttpd suggests: pn thttpd-util none (no description available) -- Configuration Files: /etc/default/thttpd changed: ENABLED=yes /etc/thttpd/thttpd.conf changed: port=8080 dir=/var/www2 chroot user=www-data cgipat=/cgi-bin/* throttles=/etc/thttpd/throttle.conf logfile=/var/log/thttpd.log -- no debconf information #! /bin/sh /usr/share/dpatch/dpatch-run ## 13-extra-mimetypes.dpatch by r...@sd-30464.dedibox.fr ## ## All lines beginning with `## DP:' are a description of the patch. ## DP: No description. @DPATCH@ diff -urNad '--exclude=CVS' '--exclude=.svn' '--exclude=.git' '--exclude=.arch' '--exclude=.hg' '--exclude=_darcs' '--exclude=.bzr' thttpd-2.25b~/mime_types.txt thttpd-2.25b/mime_types.txt --- thttpd-2.25b~/mime_types.txt 2013-04-12 16:52:57.332789434 +0200 +++ thttpd-2.25b/mime_types.txt 2013-04-12 16:52:57.364732735 +0200 @@ -3,115 +3,197 @@ # A list of file extensions followed by the corresponding MIME type. # Extensions not found in the table are returned as text/plain. -a application/octet-stream +323 text/h323 +3gp video/3gpp aab application/x-authorware-bin aam application/x-authorware-map +a application/octet-stream aas application/x-authorware-seg ai application/postscript aif audio/x-aiff aifc audio/x-aiff aiff audio/x-aiff +amr audio/amr +anx application/annodex +apk application/vnd.android.package-archive asc text/plain asf video/x-ms-asf asx video/x-ms-asf +atom application/atom+xml +atomcat application/atomcat+xml +atomsrv application/atomserv+xml au audio/basic avi video/x-msvideo +awb audio/amr-wb +axa audio/annodex +axv video/annodex bcpio application/x-bcpio bin application/octet-stream bmp image/bmp +brf text/plain +cap application/cap +cat application/vnd.ms-pki.seccat cdf application/x-netcdf +cdy application/vnd.cinderella +class application/java-vm class application/x-java-vm +cod application/vnd.rim.cod cpio application/x-cpio cpt application/mac-compactpro crl application/x-pkcs7-crl crt application/x-x509-ca-cert csh application/x-csh css text/css +csv text/csv +cu application/cu-seeme +davmount application/davmount+xml dcr application/x-director +dif video/dv dir application/x-director djv image/vnd.djvu djvu image/vnd.djvu dll application/octet-stream +dl video/dl dms application/octet-stream doc application/msword +docx application/vnd.openxmlformats-officedocument.wordprocessingml.document +dot application/msword +dotx application/vnd.openxmlformats-officedocument.wordprocessingml.template dtd text/xml dump application/octet-stream dvi application/x-dvi +dv video/dv dxr application/x-director +eml message/rfc822 +eps2 application/postscript +eps3 application/postscript eps application/postscript +epsf application/postscript +epsi application/postscript +es application/ecmascript etx text/x-setext exe application/octet-stream ez application/andrew-inset fgd application/x-director -fh image/x-freehand fh4 image/x-freehand fh5 image/x-freehand fh7 image/x-freehand fhc image/x-freehand +fh image/x-freehand +flac audio/flac +fli video/fli gif image/gif +gl video/gl gtar application/x-gtar hdf application/x-hdf hqx application/mac-binhex40 -htm text/html; charset=%s +hta application/hta html text/html; charset=%s +htm text/html; charset=%s ice x-conference/x-cooltalk +ics text/calendar +icz text/calendar ief image/ief iges model/iges igs model/iges iv application/x-inventor +jad text/vnd.sun.j2me.app-descriptor +jar application/java-archive jar application/x-java-archive jfif image/jpeg -jpe image/jpeg jpeg image/jpeg +jpe image/jpeg jpg image/jpeg
Bug#619630: xen-tools: debian.d/50-setup-hostname : target /etc/hosts permissions and Dom0 umask value
Package: xen-tools Version: 3.9-4+lenny1 Severity: normal Hi, I think I have discovered a bug in xen-tools. I have a custom /etc/profile that insures one thing : root user have umask 077. When I whant to crate a new VM by using xen-tools, I start a tiny bash script from my root shell (with 077 umask) tha do some varaibles setting and finally start te following : xen-create-image --hostname $vmname --ip $vmip --memory $3 --partitions $4 No erros in logs file, everything seems fine. I start the VM without any problems but some apps have a strange behavior like : lpouzenc@sdfsvn1:~$ ping localhost ping: unknown host localhost This behavior is related to rights of the hosts file : lpouzenc@sdfsvn1:~$ ls -l /etc/hosts -rw--- 1 root root 511 mar 25 15:09 /etc/hosts Next, if I do a chmod 755 /etc/hosts, everything works well. I think that the problem is around /usr/lib/xen-tools/debian.d/50-setup-hostname script. Ths script do some echo something /etc/hosts without umask preoccupations. There is may be some other scripts that are affected by this bad behavior and I don't have seen anything that fix the umask value before hooks execution. Regards, Ludovic Pouzenc -- System Information: Debian Release: 5.0.8 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xen-tools depends on: ii debootstrap 1.0.10lenny1Bootstrap a basic Debian system ii libconfig-inifiles-perl 2.39-5 Read .ini-style configuration file ii libtext-template-perl1.44-1.2Text::Template perl module ii perl-modules 5.10.0-19lenny3 Core Perl modules Versions of packages xen-tools recommends: pn libexpect-perlnone (no description available) pn reiserfsprogs none (no description available) pn rinse none (no description available) ii xen-hypervisor-3.2-1-amd64 [x 3.2.1-2The Xen Hypervisor on AMD64 pn xen-shell none (no description available) pn xfsprogs none (no description available) xen-tools suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
