Bug 20605 - dhcpd and named can't start after an update from mga5 to cauldron, because the named and dhcpd users no longer exist.
Summary: dhcpd and named can't start after an update from mga5 to cauldron, because th...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-30 20:34 CEST by john gibbe
Modified: 2021-07-03 21:12 CEST (History)
6 users (show)

See Also:
Source RPM: shadow-utils
CVE:
Status comment:


Attachments
journal for dhcpd (5.57 KB, text/plain)
2017-03-31 08:16 CEST, john gibbe
Details
journal for named (10.63 KB, text/plain)
2017-03-31 08:19 CEST, john gibbe
Details

Description john gibbe 2017-03-30 20:34:56 CEST
Description of problem:

After an update from mga5 to cauldron dhcpd and named can't restart. They lack of the new system user dhcpd (uid 976 gid 976) and user named (uid ??? gid ???) that have not been created.
e.g. for systemctl status named.service:
[CODE]
...
mars 30 17:39:48 PC-JOHN named[16488]: named: user 'named' unknown
mars 30 17:39:48 PC-JOHN systemd[1]: named.service: Control process exited, code=exited status=1
mars 30 17:39:48 PC-JOHN systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
mars 30 17:39:48 PC-JOHN systemd[1]: named.service: Unit entered failed state.
mars 30 17:39:48 PC-JOHN systemd[1]: named.service: Failed with result 'exit-code'.

[/CODE]


  
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. change your packages repository to cauldron
2. update your system
3. restart your machine
4. Check the services status
Comment 1 Marja Van Waes 2017-03-30 21:03:19 CEST
Hi John,

Thanks for your report. I suppose you upgraded today, March 30?

Please attach journal.txt that is the result of running, as root,

    
     journalctl --since="2017-03-30" > journal.txt

If you upgraded yesterday, you can run

    journalctl --since="2017-03-29" --until="2017-03-30" > journal.txt


(If journal.txt is too large to attach, then please compress it with xz

   xz journal.txt

 and attach journal.txt.xz)

Component: Release (media or process) => RPM Packages
Source RPM: (none) => dhcpd, named
Keywords: (none) => NEEDINFO
CC: sysadmin-bugs => guillomovitch, marja11, shlomif

Comment 2 john gibbe 2017-03-30 22:34:31 CEST
Marja, 
No, unfortunately I managed this upgrade a while ago because I needed some package versions that were not in mga5. I update regularly now to follow cauldron improvement. But as it's quiet rare I rely on this computer as a dhcp server. I only realize now it's not running anymore. If needed I will try to find in the huge journal when I've done that...
Comment 3 john gibbe 2017-03-31 08:16:52 CEST
Created attachment 9167 [details]
journal for dhcpd

We can see that creating user dhcpd failed but that the transaction is ok and dhcp-server is installed
Comment 4 john gibbe 2017-03-31 08:19:54 CEST
Created attachment 9168 [details]
journal for named

and the same for named. Fail to create user named didn't fail to install bind.
Comment 5 Marja Van Waes 2017-03-31 08:46:30 CEST
(In reply to john gibbe from comment #3)
> Created attachment 9167 [details]
> journal for dhcpd
> 
> We can see that creating user dhcpd failed but that the transaction is ok
> and dhcp-server is installed

indeed: 

mars 26 08:25:59 PC-JOHN useradd[21336]: failed adding user 'dhcpd', data deleted

mars 26 08:25:59 PC-JOHN [RPM][20807]: install dhcp-server-3:4.3.5-1.mga6.x86_64: success

(In reply to john gibbe from comment #4)
> Created attachment 9168 [details]
> journal for named
> 
> and the same for named. Fail to create user named didn't fail to install
> bind.

mars 30 17:37:22 PC-JOHN useradd[13697]: failed adding user 'named', data deleted

mars 30 17:37:23 PC-JOHN [RPM][13178]: install bind-9.10.4.P6-1.mga6.x86_64: success

I don't know whether this bug report should be cloned and then one kept for & assigned to bind and the other for dhcp, or whether there's one underlying issue with a different package.

CC'ing some more people with much more related knowledge than me.

Source RPM: dhcpd, named => dhcp-4.3.5-1.mga6, bind-9.10.4.P6-1.mga6
CC: (none) => davidwhodgins, luigiwalser, pterjan
Summary: dhcpd and named can't start after an update from mga5 to cauldron => dhcpd and named can't start after an update from mga5 to cauldron, because the named and dhcpd users no longer exist.
Keywords: NEEDINFO => (none)

Comment 6 David Walser 2017-03-31 14:14:44 CEST
Certainly the issue isn't with the BIND or DHCP packages.  The useradd command shouldn't be failing miserably like that, so there's your problem.
Comment 7 Marja Van Waes 2017-04-01 16:18:06 CEST
(In reply to David Walser from comment #6)
> Certainly the issue isn't with the BIND or DHCP packages.  The useradd
> command shouldn't be failing miserably like that, so there's your problem.

I failed to see how useradd could be the problem, when I've never seen it fail, but now it pops to my mind that it could be a problem with how it is called, with whatever switches/options or so.

In the bind spec there is:

   %pre
   %_pre_useradd named /var/lib/named /bin/false


and in the dhcp spec there is:

  %pre server
  %_pre_useradd dhcpd /dev/null /bin/false


"rpm --eval %_pre_useradd" returns:
/usr/share/rpm-helper/add-user %{name} $1 %{1} %{2} %{3} 

But I fail to understand the /usr/share/rpm-helper/add-user script, so I fail to see how I can test on which part useradd fails.

Assigning to all packagers collectively.

Source RPM: dhcp-4.3.5-1.mga6, bind-9.10.4.P6-1.mga6 => dhcp-4.3.5-1.mga6, bind-9.10.4.P6-1.mga6, shadow-utils,
Assignee: bugsquad => pkg-bugs

David Walser 2017-04-01 16:21:18 CEST

Source RPM: dhcp-4.3.5-1.mga6, bind-9.10.4.P6-1.mga6, shadow-utils, => shadow-utils

Comment 8 David Walser 2021-07-03 21:12:54 CEST
Mageia 6 is long since EOL.  Closing.

Resolution: (none) => OLD
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.