Bug 12916 - messagebus: multiple "/etc/rc.d/init.d/functions: line 332: shift: 2: shift count out of range"
Summary: messagebus: multiple "/etc/rc.d/init.d/functions: line 332: shift: 2: shift c...
Status: MODIFIED
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: unspecified Unspecified
: Will only affect a few users - Unknown -
Assignee: Peter Müller
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-17 19:03 UTC by Jon
Modified: 2022-10-06 14:36 UTC (History)
2 users (show)

See Also:


Attachments
messagebus stopped (88.68 KB, image/png)
2022-09-08 01:21 UTC, Jon
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jon 2022-08-17 19:03:30 UTC
Running `/etc/rc.d/init.d/messagebus status`
causes thousands of messages:
```
[root@ipfire ~] # /etc/rc.d/init.d/messagebus status
/etc/rc.d/init.d/functions: line 332: shift: 2: shift count out of range
/etc/rc.d/init.d/functions: line 332: shift: 2: shift count out of range
/etc/rc.d/init.d/functions: line 332: shift: 2: shift count out of range
```

Running `/etc/rc.d/init.d/messagebus stop` seems OK
```
[root@ipfire ~] # /etc/rc.d/init.d/messagebus stopStopping the D-Bus Messagebus Daemon...                                                                                                                                  [  OK  ]
```

Running `/etc/rc.d/init.d/messagebus start` causes this message:
```
[root@ipfire ~] # /etc/rc.d/init.d/messagebus start
Starting the D-Bus Messagebus Daemon...
dbus[28213]: Unknown group "netdev" in message bus configuration file                                                                                                    [  OK  ]
```

This happened in CU 169 and in CU 170 test.
Comment 1 Jon 2022-08-17 19:09:45 UTC
FYI - this came about when installing pakfire Netatalk in CU 170 test.
Comment 2 Peter Müller 2022-08-22 20:31:52 UTC
I can reproduce this here:

[root@maverick ~]# bash -x /etc/rc.d/init.d/messagebus status
+ . /etc/sysconfig/rc
++ rc_base=/etc/rc.d
++ rc_functions=/etc/rc.d/init.d/functions
++ network_devices=/etc/sysconfig/network-devices
+ . /etc/rc.d/init.d/functions
++ umask 022
++ export PATH=/bin:/usr/bin:/sbin:/usr/sbin
++ PATH=/bin:/usr/bin:/sbin:/usr/sbin
++ RELOADSIG=HUP
++ KILLDELAY=10
++ '[' -z '' ']'
+++ stty size
++ COLUMNS='55 238'
++ COLUMNS=238
++ '[' 238 = 0 ']'
++ COL=230
++ WCOL=228
++ SET_COL='\033[230G'
++ SET_WCOL='\033[228G'
++ CURS_UP='\033[1A\033[0G'
++ NORMAL='\033[0;39m'
++ SUCCESS='\033[1;32m'
++ WARNING='\033[1;33m'
++ FAILURE='\033[1;31m'
++ INFO='\033[1;36m'
++ BRACKET='\033[1;34m'
++ STRING_LENGTH=0
+ pidfile=/var/run/dbus/pid
+ socket=/var/run/dbus/system_bus_socket
+ case "$1" in
+ statusproc -p /var/run/dbus/pid /usr/bin/dbus-daemon
+ '[' 3 = 0 ']'
+ getpids -p
+ '[' -z '' ']'
+ pidofproc -s -p '' -p
+ local pidfile=
+ local lpids=
+ local silent=
+ pidlist=
+ true

[ad infinitum]
Comment 4 Jon 2022-08-24 02:25:23 UTC
Peter - did you see the error related to `messagebus start`?

"dbus[28213]: Unknown group "netdev" in message bus configuration file"


```
[root@ipfire ~] # /etc/rc.d/init.d/messagebus start
Starting the D-Bus Messagebus Daemon...
dbus[28213]: Unknown group "netdev" in message bus configuration file                                                                                                    [  OK  ]
```
Comment 6 Peter Müller 2022-09-01 20:40:55 UTC
(In reply to Jon from comment #4)
> Peter - did you see the error related to `messagebus start`?
> 
> "dbus[28213]: Unknown group "netdev" in message bus configuration file"
> 
> 
> ```
> [root@ipfire ~] # /etc/rc.d/init.d/messagebus start
> Starting the D-Bus Messagebus Daemon...
> dbus[28213]: Unknown group "netdev" in message bus configuration file       
> [  OK  ]
> ```

Um, no, this does not seem to appear over here:

[root@maverick ~]# cat /etc/os-release 
NAME="IPFire"
VERSION="2.27"
ID=ipfire
VERSION_ID=2
PRETTY_NAME="IPFire 2.27 (x86_64) - core170 Development Build: next/f241a8c8"
ANSI_COLOR="0:31"
[root@maverick ~]# /etc/rc.d/init.d/messagebus status
dbus-daemon is running with Process ID(s) 32549.
[root@maverick ~]# /etc/rc.d/init.d/messagebus stop
Stopping the D-Bus Messagebus Daemon...                                                                                                                                                                                              [  OK  ]
[root@maverick ~]# /etc/rc.d/init.d/messagebus start
Starting the D-Bus Messagebus Daemon...                                                                                                                                                                                              [  OK  ]
[root@maverick ~]# /etc/rc.d/init.d/messagebus status
dbus-daemon is running with Process ID(s) 32691.

Does it have any impact on dbus operations on your machine?
Comment 7 Jon 2022-09-02 01:50:31 UTC
(In reply to Peter Müller from comment #6)
> 
> Does it have any impact on dbus operations on your machine?

messagebus doesn't seem to run once stopped.

see this image:
https://community.ipfire.org/t/cups-broken-in-current-testing-build-170/8492/3?u=jon

I have not tried the new patch in Comment 5.
Comment 8 Jon 2022-09-07 02:55:54 UTC
I applied the patch but I still see this error:

[root@ipfireAPU ~]# /etc/rc.d/init.d/messagebus start
Starting the D-Bus Messagebus Daemon...
dbus[6070]: Unknown group "netdev" in message bus configuration file       [  OK  ]
[root@ipfireAPU ~]#
Comment 9 Jon 2022-09-08 01:21:59 UTC
Created attachment 1086 [details]
messagebus stopped

I just installed IPFire 2.27 (x86_64) - Core-Update 170 Development Build: master/48a19ee5

Looks like messagebus is stopped on boot.
Comment 10 Adolf Belka 2022-09-19 15:12:58 UTC
(In reply to Jon from comment #9)
> Created attachment 1086 [details]
> messagebus stopped
> 
> I just installed IPFire 2.27 (x86_64) - Core-Update 170 Development Build:
> master/48a19ee5
> 
> Looks like messagebus is stopped on boot.

That is a problem with the new SERVICES meta data on the Services addons table. It shows stopped there but if you run messagebus status it shows that it is running but this looks like it is not being picked up in the services.cgi page.
Someone else found this on the forum today (19th Sep) and they are raising a bug for that.