Bug#958307: ejabberd: Fails to make a backup
Package: ejabberd
Version: 18.12.1-2
Severity: normal
Dear Maintainer,
I have a problem trying yo backup ejabberd database.
I'm using ejabberd (18.12.1-2) with debian buster.
When I do (as root):
ejabberdctl backup /tmp/ejabberd.backup
I don't get any errors, but there is no /tmp/ejabberd.backup file
neither.
journalctl show some lines related with apparmor, although they are
supposed to ALLOW the operations:
--x8--x8--x8--x8
abr 20 12:57:03 xmppsrv1 audit[5875]: AVC apparmor="ALLOWED"
operation="mknod" profile="/usr/sbin/ejabberdctl"
name="/tmp/ejabberd.backup.BUPTMP" pid=
abr 20 12:57:03 xmppsrv1 audit[5875]: AVC apparmor="ALLOWED"
operation="open" profile="/usr/sbin/ejabberdctl"
name="/tmp/ejabberd.backup.BUPTMP" pid=5
abr 20 12:57:03 xmppsrv1 audit[5875]: AVC apparmor="ALLOWED"
operation="truncate" profile="/usr/sbin/ejabberdctl"
name="/tmp/ejabberd.backup.BUPTMP" p
abr 20 12:57:03 xmppsrv1 kernel: audit: type=1400
audit(1587380223.577:51): apparmor="ALLOWED" operation="mknod"
profile="/usr/sbin/ejabberdctl" name=
abr 20 12:57:03 xmppsrv1 kernel: audit: type=1400
audit(1587380223.577:52): apparmor="ALLOWED" operation="open"
profile="/usr/sbin/ejabberdctl" name="
abr 20 12:57:03 xmppsrv1 kernel: audit: type=1400
audit(1587380223.577:53): apparmor="ALLOWED" operation="truncate"
profile="/usr/sbin/ejabberdctl" na
abr 20 12:57:03 xmppsrv1 audit[5875]: AVC apparmor="ALLOWED"
operation="rename_src" profile="/usr/sbin/ejabberdctl"
name="/tmp/ejabberd.backup.BUPTMP"
abr 20 12:57:03 xmppsrv1 audit[5875]: AVC apparmor="ALLOWED"
operation="rename_dest" profile="/usr/sbin/ejabberdctl"
name="/tmp/ejabberd.backup" pid=5
abr 20 12:57:03 xmppsrv1 kernel: audit: type=1400
audit(1587380223.913:54): apparmor="ALLOWED" operation="rename_src"
profile="/usr/sbin/ejabberdctl"
abr 20 12:57:03 xmppsrv1 kernel: audit: type=1400
audit(1587380223.913:55): apparmor="ALLOWED" operation="rename_dest"
profile="/usr/sbin/ejabberdctl"
--x8--x8--x8--x8
The fact is that there is no /tmp/ejabberd.backup file
According to /etc/apparmor.d/usr.sbin.ejabberdctl:
/var/backups/ rw,
/var/backups/ejabberd** rwlk,
So I tried:
ejabberdctl backup /var/backups/ejabberd.backup
and I get this error:
Can't store backup in "/var/backups/ejabberd.backup" at node
ejabberd@localhost: {'EXIT',
{error,
{file_error,
"/var/backups/ejabberd.backup.BUPTMP",
eacces}}}
because /var/backups/ has 755 permissions and is owned by root:root.
I created a directory in /tmp, owned by ejabberd but it did not worked
neither.
The only way I managed to make a backup was in /var/run/ejabberd (it is
owned by ejabberd, and also with "rw" in
/etc/apparmor.d/usr/sbin/ejabberdctl)
ejabberdctl backup /var/run/ejabberd/ejabberd.backup
The documentation (/usr/share/doc/ejabberd/README.Debian.gz says that
backups are stored in /var/backups when ejabberd is upgraded or
restored. I didn't check if this is working or is it also affected by
this problem.
There is not (or at least I didn't find) a proper place to store
backups.
I think it should be documented where to store backups, or have and
specific directory for backups that works.
Regards and thank you.
-- System Information:
Debian Release: 10.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-8-amd64 (SMP w/1 CPU core)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8),
LANGUAGE=es_ES.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 ejabberd depends on:
ii adduser3.118
ii debconf [debconf-2.0] 1.5.71
ii erlang-asn11:21.2.6+dfsg-1
ii erlang-base [erlang-abi-17.0] 1:21.2.6+dfsg-1
ii erlang-base64url 1.0-3
ii erlang-crypto 1:21.2.6+dfsg-1
ii erlang-goldrush0.2.0-1
ii erlang-inets 1:21.2.6+dfsg-1
ii erlang-jiffy 0.14.11+dfsg-4
ii erlang-jose1.9.0-1
ii erlang-lager 3.6.8-1
ii erlang-mnesia 1:21.2.6+dfsg-1
ii erlang-odbc1:21.2.6+dfsg-1
ii erlang-os-mon 1:21.2.6+dfsg-1
ii erlang-p1-cache-tab1.0.17-1
ii erlang-p1-eimp 1.0.9-1
ii erlang-p1-iconv1.0.10-1
ii erlang-p1-pkix 1.0.0-3+deb10u1
ii erlang-p1-stringprep 1.0.14-1
ii erlang-p1-tls
Bug#945788: lightdm: Language support is broken
Package: lightdm Version: 1.26.0-4 Severity: important Tags: l10n Dear Maintainer, I would like to use the language selector of lightdm but I found that it doesn't work. I see there are several bug reports about this (864154, 784065, 765077, 690899, 691446), but they are only addressing small parts of the problem and those bugs doesn't have a proper solution. So i will try to offer a more general view of the problem. - First of all, chosen language at lightdm greeter is overridden if LANG is defined in /etc/default/locale. This is because /etc/pam.d/lightdm contains: session required pam_env.so readenv=1 envfile=/etc/default/locale No matter what Language you choose in lightdm selector. You'll have system wide LANG setting. So first step for language selector to work is to comment the above line. - After commenting the above line, you can choose language with lightdm greeter at login time, but it won't work with that session. It will work the next session. Let me explain it with an example: Before login, according to /home/user/.dmrc, /var/lib/AccountsService/users/user and /var/cache/lightdm/user.dmrc you have Language=de_DE.utf8 (German) In lightdm greeter login you choose "fr_FR.utf8" (French), enter login name and password, and a plasma (in my case) session with German language will start. /home/user/.dmrc, /var/lib/AccountsService/users/user and /var/cache/lightdm/user.dmrc files are updated to fr_FR.utf8 but that first session have the previous language settings. The next time you start a session from lightdm the language will be French, no matter what you choose at language selector. The language selector doesn't set the language for the very next login but the "next login after this login". In other words, the language of the session will be the one we chose the previous login, not what we have choose this login. - There is a third problem with language selector. If accountsservice is installed, files in /var/lib/AccountsService/users/ are read and written, this is correct. But, If accountsservice is uninstalled, and there are files in /var/lib/AccountsService/users/, those files are still read, and this is wrong. If, lets say, a user with accountservice installed choose one language at lightdm greeter, that settings is save in a file in /var/lib/AccountsService/users/. Then, if the user uninstall accountsservice but don't delete the file at /var/lib/AccountsService/users he will always use the Language defined there, no matter what he choose at language selector. Lightdm will read that file, that won't be updated to newer choices of language because accountsservice is no longer running. could this be fixed, please? Thank you very much. -- System Information: Debian Release: 10.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/2 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES.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 lightdm depends on: ii adduser 3.118 ii dbus 1.12.16-1 ii debconf [debconf-2.0] 1.5.71 ii libaudit1 1:2.8.4-3 ii libc6 2.28-10 ii libgcrypt20 1.8.4-5 ii libglib2.0-0 2.58.3-2+deb10u2 ii libpam-systemd [logind] 241-7~deb10u2 ii libpam0g 1.3.1-5 ii libxcb1 1.13.1-2 ii libxdmcp6 1:1.1.2-3 ii lightdm-gtk-greeter [lightdm-greeter] 2.0.6-1 ii lsb-base 10.2019051400 Versions of packages lightdm recommends: ii xserver-xorg 1:7.7+19 Versions of packages lightdm suggests: pn accountsservice ii upower 0.99.10-1 pn xserver-xephyr -- Configuration Files: /etc/pam.d/lightdm changed [not included] -- debconf information: lightdm/daemon_name: /usr/sbin/lightdm * shared/default-x-display-manager: lightdm -- ____ Santiago Castillo Oliscasti...@aragon.es Técnico de Sistemas Informáticos976 71 50 06 Biblioteca de Aragón Doctor Cerrada 22, 50005 Zaragoza
Bug#944110: anacron: Incorrect behavoiur when using @monthly period_name
Package: anacron
Version: 2.3-28
Severity: normal
Dear Maintainer,
I see that @monthly is not a feature of anacron upstream, but it belongs
to a debian patch.
I have found that @monthly period_name doesnt work well sometimes.
Let's see an example: I have an job that was last executed by anacron on
the first of october.
The expected behaviour would be that the next execution will happen on
the first of november.
But the truth is that the next execution happens on the 31st of october.
Looking at lock.c code I see:
if (jr->named_period)
{
int period = 0, bypass = 0;
switch (jr->named_period)
{
case 1:
period = days_last_month ();
bypass = days_this_month ();
break;
case 2:
period = days_last_year ();
bypass = days_this_year ();
break;
default:
die ("Unknown named period for %s (%d)", jr->ident,
jr->named_period);
}
if (day_delta < period && day_delta != bypass)
{
/* Job is still too young */
xclose (jr->timestamp_fd);
return 0;
}
}
Last execution (with MMDD notation): 20191001
Current day: 20191031
day_delta=30
period=30 (Number of days in september)
bypass=31 (Number of days in octuber)
(day_delta < period && day_delta != bypass) = (30 < 30 && 30 !=31) =
(FALSE && TRUE) = FALSE, so the job is executed today
In this case the job is run on the 1st and on the 31st day of october.
Two times in a month. The next one will be at the end of november.
I think this is wrong. If first run is on 1st day it should be again the
first day of following months, assuming that the machine is turned up
everyday.
Not sure about (day_delta < period && day_delta != bypass). It doesn't
work in this case, but it doesnt work with another dates: (i.e.: last
execution on january 31st, won't run on february, but on the first of
march))
Can this be fixed, please?
Thank you and regards.
-- System Information:
Debian Release: 10.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 4.19.0-6-686-pae (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8),
LANGUAGE=es_ES.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 anacron depends on:
ii debianutils 4.8.6.1
ii libc6 2.28-10
ii lsb-base 10.2019051400
Versions of packages anacron recommends:
ii cron [cron-daemon] 3.0pl1-134
ii rsyslog [system-log-daemon] 8.1901.0-1
Versions of packages anacron suggests:
ii exim4-daemon-light [mail-transport-agent] 4.92-8+deb10u3
ii powermgmt-base 1.34
-- no debconf information
Bug#279581: Bug still unresolved but patch no longer be applied
Hi all I'm afraid that this bug is still unresolved. Unfortunately, the patch provided by Fabian Knittel was written against 1.3.1 and can't be applied to 1.4. interface.c has changed between those releases. NSS is a tricky piece of the system and I can't update the patch to 1.4 with much more knowledge about NSS than what I have now. Anyway I have a computer running debian 10 with libnss-pgsql and libpam-pgsql that works when running nscd, but doesn't work when nscd is stopped. I can test patches easily. If someone can write a new patch I will be happy testing it. Regards.
Bug#941653: libnss-pgsql2: Documentation doesn't match example config file
Package: libnss-pgsql2 Version: 1.4.0debian-8 Severity: minor Dear Maintainer, In the /usr/share/doc/libnss-pgsql2/nss-pgsql.html file we have: -x8-x8-x8-x8-x8-x8 getgrnam A query that returns group_name, group_passwd, group_gid for a given group name -x8-x8-x8-x8-x8-x8 In the provided config file nss-pgsql.conf in example directory there we have: -x8-x8-x8-x8-x8-x8 # Must return group_name, group_passwd, group_gid getgrnam = SELECT groupname, passwd, gid, ARRAY(SELECT username FROM usergroups WHERE usergroups.gid = group_table.gid) AS members FROM group_table WHERE groupname = $1 -x8-x8-x8-x8-x8-x8 The nss-pgsql.html file and the comment in the file nss-pgsql.conf are missing the ARRAY part. Regards. -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/2 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES.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 libnss-pgsql2 depends on: ii libc6 2.28-10 ii libpq5 11.5-1+deb10u1 libnss-pgsql2 recommends no packages. Versions of packages libnss-pgsql2 suggests: ii libpam-pgsql 0.7.3.2-1 pn nscd -- no debconf information -- Santiago Castillo Oliscasti...@aragon.es Técnico de Sistemas Informáticos976 71 50 06 Biblioteca de Aragón Doctor Cerrada 22, 50005 Zaragoza
