Description of problem: There is an error somewhere in the system. Whichever legacy sysvinit daemon started, this error messages: example # systemctl status resolvconf.service ● resolvconf.service - LSB: Nameserver information manager Loaded: loaded (/etc/rc.d/init.d/resolvconf; generated) Active: active (exited) since Wed 2021-03-24 16:15:58 CET; 1h 36min ago Docs: man:systemd-sysv-generator(8) Tasks: 0 (limit: 9450) Memory: 0B CPU: 0 CGroup: /system.slice/resolvconf.service márc 24 16:15:57 csablakPC.home systemd[1]: Starting LSB: Nameserver information manager... márc 24 16:15:58 csablakPC.home resolvconf[707]: resolvconf indítása: /etc/init.d/functions: 157. sor: shift: shift-szám kívül esik a tartományon márc 24 16:15:58 csablakPC.home resolvconf[707]: [ OK ] márc 24 16:15:58 csablakPC.home systemd[1]: Started LSB: Nameserver information manager. translate: /etc/init.d/functions: 157. sor: shift: shift-szám kívül esik a tartományon /etc/init.d/functions: 157. line: shift: shift-number is out of range.
Thank you for the report. I suspect this is quite harmless, since I see the same thing in the journal: Maw 24 20:45:28 resolvconf[708]: Starting resolvconf:/etc/init.d/functions: line 157: shift: shift count out of range Maw 24 20:45:28 resolvconf[708]: [ OK ] Assigning this to Olav for 'initscripts'. If you want more information (like more journal), please ask.
CC: (none) => lewyssmithAssignee: bugsquad => olavSeverity: normal => minor
Summary: error messages => initscripts: 'shift count out of range' message with scripts using /etc/init.d/functions
We stopped supporting Mageia 8 almost 8 months ago https://blog.mageia.org/en/2023/12/30/mageia-8-end-of-life/ That means we also stopped fixing Mageia 8 bugs and that this bug report needs to be closed, regardless of whether it was fixed for Mageia 8 or not. If this particular bug did not get fixed for Mageia 8, then we do regret that. If this issue is still present in Mageia 9 or cauldron, then please reopen this report, write a comment and adjust the "Version:" field. If you are not yet a member of one or our teams, then please consider becoming one. https://wiki.mageia.org/en/Contributing Mageia is a community project, meaning that we, the users, make Mageia together. The more active contributors we have, the more bug reports will get fixed. Besides, being active in a team can be very rewarding. It was and is certainly rewarding to me :-D
Status: NEW => RESOLVEDResolution: (none) => OLD
(In reply to Marja Van Waes from comment #2) > We stopped supporting Mageia 8 almost 8 months ago > https://blog.mageia.org/en/2023/12/30/mageia-8-end-of-life/ > > That means we also stopped fixing Mageia 8 bugs and that this bug report > needs to be closed, regardless of whether it was fixed for Mageia 8 or not. > > If this particular bug did not get fixed for Mageia 8, then we do regret > that. > > If this issue is still present in Mageia 9 or cauldron, then please reopen > this report, write a comment and adjust the "Version:" field. > > If you are not yet a member of one or our teams, then please consider > becoming one. https://wiki.mageia.org/en/Contributing https://poppyplaytimechapter3.io > Mageia is a community project, meaning that we, the users, make Mageia > together. > > The more active contributors we have, the more bug reports will get fixed. > Besides, being active in a team can be very rewarding. It was and is > certainly rewarding to me :-D Good to see this bug has been resolved! Addressing issues with 'case out of range' messages improves system stability.
CC: (none) => sarahdhicks
CC: sarahdhicks => davidwhodgins