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
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 PackagesSource RPM: (none) => dhcpd, namedKeywords: (none) => NEEDINFOCC: sysadmin-bugs => guillomovitch, marja11, shlomif
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...
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
Created attachment 9168 [details] journal for named and the same for named. Fail to create user named didn't fail to install bind.
(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.mga6CC: (none) => davidwhodgins, luigiwalser, pterjanSummary: 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)
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.
(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
Source RPM: dhcp-4.3.5-1.mga6, bind-9.10.4.P6-1.mga6, shadow-utils, => shadow-utils
Mageia 6 is long since EOL. Closing.
Resolution: (none) => OLDStatus: NEW => RESOLVED