Re: sysupgrade with sysmerge failure

[Sean Kamath]

> On Jun 2, 2020, at 02:15, rgc  wrote:
> 
> On Mon, Jun 01, 2020 at 10:47:02PM -0700, Sean Kamath wrote:
>> I didn???t see any place in sysmerge that used mail, and did not receive any 
>> mail for the failed sysmerge. 
>> But I see in /etc/rc that it does mail the output of sysmerge to the root 
>> user.   Guess I got other issues.
> 
> did you already check /etc/mail/aliases and verified contents of 
> /root/.forward?

The clue was in the first email — merging smtpd.conf.  I had a jacked up 
smtpd.conf as I was working on getting internal relaying working.

Sean

Re: sysupgrade with sysmerge failure

[rgc]

On Mon, Jun 01, 2020 at 10:47:02PM -0700, Sean Kamath wrote:
> I didn???t see any place in sysmerge that used mail, and did not receive any 
> mail for the failed sysmerge. 
> But I see in /etc/rc that it does mail the output of sysmerge to the root 
> user.   Guess I got other issues.

did you already check /etc/mail/aliases and verified contents of /root/.forward?

> 
> Thanks,
> Sean
> 
> 
> 

Re: sysupgrade with sysmerge failure

[Sean Kamath]

> On Jun 1, 2020, at 03:43, Stuart Henderson  wrote:
> Normally the output from rc.firsttime is mailed to root. e.g.

I didn’t see any place in sysmerge that used mail, and did not receive any mail 
for the failed sysmerge.  But I see in /etc/rc that it does mail the output of 
sysmerge to the root user.   Guess I got other issues.

Thanks,
Sean

Re: sysupgrade with sysmerge failure

[Stuart Henderson]

On 2020-05-31, Sean Kamath  wrote:
> Hi.
>
> I just used the new ‘sysupgrade’ to upgrade my little Alix boxes to 6.7.  It 
> worked very well, and thank you for this upgrade simplification tool.
>
> I do have one question.  After upgrading the first machine, when I ran 
> syspatch to patch the system, I got a failure saying that the user 
> _rpki_client didn’t exist.  My question is not about that, but I realized 
> that the sysmerge script apparently did not finish successfully.  I ran it 
> and merged the files and then was able to proceed normally.  On another box, 
> this time I was watching for it (I have a little terminal server on the alix 
> machines), and indeed:

BTW this is because rpki-client reuses a uid that was previously allocated
to named (and removed in 2014). I am running into this on a lot of machines
(there is an automated process to add new users in sysmerge, but not to
remove them - sysmerge doesn't allow manual merges of the password database).

>  /etc/mail/smtpd.conf unhandled, re-run sysmerge to merge the new version
>
> My question is, is there a “standard” place/way to confirm that sysmerge 
> finished successfully (other than looking at the console output on first 
> boot)?  For some reason (I don’t know if I’m editing in a way that sysmerge 
> doesn’t like to merge) this seems to happen a lot with unbound.conf, nsd.conf 
> and smtpd.conf (for example), so I run into sysmerge conflicts often.

Normally the output from rc.firsttime is mailed to root. e.g.

From: Charlie Root 
Date: Sat, 9 May 2020 18:57:32 + (GMT)
To: root@somehost.somedomain
Subject: somehost.somedomain rc.firsttime output

 Not adding group _rpki-client, GID 70 already exists
 Not adding group _rad, GID 94 already exists
 Not adding user _rpki-client, UID 70 already exists
 Not adding user _rad, UID 94 already exists
===> Updating /etc/changelist
===> Updating /etc/fbtab
===> Updating /etc/gettytab
===> Updating /etc/mail/smtpd.conf
===> Updating /etc/npppd/npppd.conf
===> Updating /etc/skel/.cshrc
===> Updating /etc/skel/.profile
===> Updating /etc/ssh/ssh_config
===> Updating /etc/ssl/cert.pem
===> Updating /etc/X11/twm/system.twmrc
===> Updating /etc/X11/xenodm/GiveConsole
===> Updating /etc/X11/xenodm/TakeConsole
===> Updating /etc/X11/xenodm/Xresources
===> Updating /etc/X11/xenodm/Xsetup_0
===> Updating /var/cron/tabs/root
===> Installing /var/db/rpki-client/openbgpd
===> Updating /var/unbound/etc/unbound.conf
 /etc/login.conf unhandled, re-run sysmerge to merge the new version
 /etc/mail/aliases unhandled, re-run sysmerge to merge the new version

mtree: unknown user _rpki-client
mtree: failed at line 615 of the specification

sysupgrade with sysmerge failure

[Sean Kamath]

Hi.

I just used the new ‘sysupgrade’ to upgrade my little Alix boxes to 6.7.  It 
worked very well, and thank you for this upgrade simplification tool.

I do have one question.  After upgrading the first machine, when I ran syspatch 
to patch the system, I got a failure saying that the user _rpki_client didn’t 
exist.  My question is not about that, but I realized that the sysmerge script 
apparently did not finish successfully.  I ran it and merged the files and then 
was able to proceed normally.  On another box, this time I was watching for it 
(I have a little terminal server on the alix machines), and indeed:

 /etc/mail/smtpd.conf unhandled, re-run sysmerge to merge the new version

My question is, is there a “standard” place/way to confirm that sysmerge 
finished successfully (other than looking at the console output on first boot)? 
 For some reason (I don’t know if I’m editing in a way that sysmerge doesn’t 
like to merge) this seems to happen a lot with unbound.conf, nsd.conf and 
smtpd.conf (for example), so I run into sysmerge conflicts often.

Sean