Devuan bug report logs -
#721
Jabberd2 start failture on devuan
Reported by: Leonid <cppleo@ya.ru>
Date: Tue, 1 Nov 2022 07:32:02 UTC
Severity: normal
Tags: debian, moreinfo, patch
Found in version 2.7.0-2
Reply or subscribe to this bug.
Toggle useless messages
Report forwarded
to devuan-bugs@lists.dyne.org, devuan-dev@lists.dyne.org
:
bug#721
; Package jabberd2
.
(Tue, 01 Nov 2022 07:32:02 GMT) (full text, mbox, link).
Acknowledgement sent
to Leonid <cppleo@ya.ru>
:
New bug report received and forwarded. Copy sent to devuan-dev@lists.dyne.org
.
(Tue, 01 Nov 2022 07:32:04 GMT) (full text, mbox, link).
Message #5 received at submit@bugs.devuan.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
Package: jabberd2
Version: 2.7.0-2
Hello, dear Devuan developers!
I can't fix this bug:
I try run jabberd2 service, it doesn't work.
```
root@hostname~# service jabberd2 start
Starting Jabber services: router smstart-stop-daemon: missing group name
<Failed> s2sstart-stop-daemon: missing group name
<Failed> c2sstart-stop-daemon: missing group name
<Failed>.
```
What do you think about this problem?
P.S.:
I'm using Devuan 4.
5.10.74-v8 aarch64 GNU/Linux
--
Devuan user,
Leonid
[Message part 2 (text/html, inline)]
Information forwarded
to devuan-bugs@lists.dyne.org, devuan-dev@lists.dyne.org
:
bug#721
; Package jabberd2
.
(Wed, 02 Nov 2022 09:26:01 GMT) (full text, mbox, link).
Message #8 received at 721@bugs.devuan.org (full text, mbox, reply):
Control: tags -1 moreinfo
Control: tags -1 debian
Leonid,
On Tue, Nov 01, 2022 at 12:28:46PM +0500, Leonid wrote:
> Package: jabberd2
> Version: 2.7.0-2
> Hello, dear Devuan developers!
>
> I can't fix this bug:
> I try run jabberd2 service, it doesn't work.
Thanks for this. In general jabberd2 is not forked in Devuan and we use Debian's
packages directly without recompilation. So any bug should be reported to
Debian's BTS.
Looking at Debian's tracker[1], I don't see any significant recent changes. You
will need to provide more information.
- What group is jabber trying to run as? It looks[2] as if it should be
jabber. Does the group exist? It should be created in the preinst[3]
Mark
[1] https://tracker.debian.org/pkg/jabberd2
[2] https://salsa.debian.org/xmpp-team/jabberd2/-/blob/master/debian/init#L18
[3] https://salsa.debian.org/xmpp-team/jabberd2/-/blob/master/debian/preinst#L38
Added tag(s) moreinfo.
Request was from Mark Hindley <mark@hindley.org.uk>
to 721-submit@bugs.devuan.org
.
(Wed, 02 Nov 2022 09:26:03 GMT) (full text, mbox, link).
Added tag(s) debian.
Request was from Mark Hindley <mark@hindley.org.uk>
to 721-submit@bugs.devuan.org
.
(Wed, 02 Nov 2022 09:26:03 GMT) (full text, mbox, link).
Information forwarded
to devuan-bugs@lists.dyne.org, devuan-dev@lists.dyne.org
:
bug#721
; Package jabberd2
.
(Wed, 11 Jan 2023 19:42:02 GMT) (full text, mbox, link).
Message #15 received at 721@bugs.devuan.org (full text, mbox, reply):
Control: tags -1 patch
On Wed, Nov 02, 2022 at 09:24:03AM +0000, Mark Hindley wrote:
> - What group is jabber trying to run as? It looks[2] as if it should be
> jabber. Does the group exist? It should be created in the preinst[3]
I have had a quick look at this and the USER and GROUP environment variables
need to be exported so that they are passed to the scripts in
/etc/jabberd2/component.d.
USER is already an exported variable, so actually works either way, but GROUP
isn't so fails.
Try this.
diff -u /home/mark/Downloads/jabberd2.init /home/mark/Downloads/jabberd2.init.new
--- /home/mark/Downloads/jabberd2.init 2023-01-11 19:36:24.104716244 +0000
+++ /home/mark/Downloads/jabberd2.init.new 2023-01-11 19:37:12.319574513 +0000
@@ -14,8 +14,8 @@
set -e
# user and group
-USER=jabber
-GROUP=jabber
+export USER=jabber
+export GROUP=jabber
test -f /etc/default/jabberd2 && . /etc/default/jabberd2
COMPONENTDPATH=/etc/jabberd2/component.d
Diff finished. Wed Jan 11 19:38:28 2023
Added tag(s) patch.
Request was from Mark Hindley <mark@hindley.org.uk>
to 721-submit@bugs.devuan.org
.
(Wed, 11 Jan 2023 19:42:03 GMT) (full text, mbox, link).
Send a report that this bug log contains spam.