Project

General

Profile

Actions

Bug #7715

closed

Update from 2.3.4 to -p1 mangled many config entries including users, patches, other config

Added by Stilez y almost 7 years ago. Updated almost 7 years ago.

Status:
Rejected
Priority:
Very Low
Assignee:
-
Category:
-
Target version:
-
Start date:
07/21/2017
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

Description

I updated my test router 2.3.4 to 2.3.4-p1 and a load of config got wiped out in the process, including users reset and deleted, system patches deleted, and quite a lot of other config lost. It also crashed during today which it hasn't before.

The update was yesterday (20 July 2017 about 17.42 to 17.46) but only seen today (21 July) when I tried to login and couldn't; it had reverted to the default login/pw as well. (Not sure why the sudo package was updated 24 hours later than everything else - maybe some actions had to wait until I tried to login next?)

The attached file contains all debug info:

1) Dump of system log

2) Dump of config history before-during-after update (scraped from diag_confbak.php)

3) An overall diff to see the overall effect of the update, diffed between -
"last config that looked right before update" (when it updated config to note it was going for update)
"first update when config became stable again after update"
I didn't change config between these.

4) The individual DIFF configs in between, to allow matching of changes to logs and to update actions that were responsible.


Files

Stilez_2.3.4-p1.log (171 KB) Stilez_2.3.4-p1.log Stilez y, 07/21/2017 11:35 AM
Actions

Also available in: Atom PDF