Update & Upgrade Errors

BackWoodsTech · Apr 9th 2019

[I cleaned this up a bit in an effort to make it more readable and put it into a more appropriate sub-forum].
[EDIT: I have been reading similar error issues here but one thing that seems to be different is that I'm getting errors for both system updates as well as OMV Extras; I'm not seeing a specific match yet]

System info in attached image.
I reviewed the system log and nothing jumps out in terms of these update errors.
When I go to:

System>Update Management>Updates>Check I get a huge
set of errors which I've not seen yet...but I haven't checked for
updates in a couple of months. This is how the error starts:

Display Spoiler

Failed to execute command 'export
PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin;
export LANG=C.UTF-8; apt-get update 2>&1' with exit code '100':
Get:1 file:/var/cache/openmediavault/archives InReleaseIgn:1
file:/var/cache/openmediavault/archives InReleaseGet:2
file:/var/cache/openmediavault/archives ReleaseIgn:2
file:/var/cache/openmediavault/archives ReleaseGet:3
file:/var/cache/openmediavault/archives PackagesIgn:3
file:/var/cache/openmediavault/archives PackagesGet:4
file:/var/cache/openmediavault/archives Translation-enIgn:4
file:/var/cache/openmediavault/archives Translation-enGet:3
file:/var/cache/openmediavault/archives PackagesIgn:3
file:/var/cache/openmediavault/archives PackagesGet:4
file:/var/cache/openmediavault/archives Translation-enIgn:4
file:/var/cache/openmediavault/archives Translation-enGet:3
file:/var/cache/openmediavault/archives PackagesIgn:3
file:/var/cache/openmediavault/archives PackagesGet:4
file:/var/cache/openmediavault/archives Translation-enIgn:4
file:/var/cache/openmediavault/archives Translation-enGet:3
file:/var/cache/openmediavault/archives PackagesIgn:3
file:/var/cache/openmediavault/archives PackagesGet:4
file:/var/cache/openmediavault/archives Translation-enIgn:4
file:/var/cache/openmediavault/archives Translation-enGet:3.....

Details:
Error #0:OMV\ExecException: Failed to
execute command 'export
PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin;
export LANG=C.UTF-8; apt-get update 2>&1' with exit code '100':
Get:1 file:/var/cache/openmediavault/archives InReleaseIgn:1
file:/var/cache/openmediavault/archives InReleaseGet:2
file:/var/cache/openmediavault/archives ReleaseIgn:2
file:/var/cache/openmediavault/archives ReleaseGet:3
file:/var/cache/openmediavault/archives PackagesIgn:3
file:/var/cache/openmediavault/archives PackagesGet:4
file:/var/cache/openmediavault/archives Translation-enIgn:4
file:/var/cache/openmediavault/archives Translation-enGet:3
file:/var/cache/openmediavault/archives PackagesIgn:3
file:/var/cache/openmediavault/archives PackagesGet:4
file:/var/cache/openmediavault/archives Translation-enIgn:4
file:/var/cache/openmediavault/archives Translation-enGet:3
file:/var/cache/openmediavault/archives PackagesIgn:3
file:/var/cache/openmediavault/archives PackagesGet:4
file:/var/cache/openmediavault/archives Translation-enIgn:4
file:/var/cache/openmediavault/archives Translation-enGet:3
file:/var/cache/openmediavault/archives PackagesIgn:3
file:/var/cache/openmediavault/archives PackagesGet:4
file:/var/cache/openmediavault/archives Translation-enIgn:4
file:/var/cache/openmediavault/archives Translation-enGet:3
file:/var/cache/openmediavault/archives PackagesIgn:3
file:/var/cache/openmediavault/archives PackagesGet:4
file:/var/cache/openmediavault/archives Translation-enIgn:4......

System>Plugins>Check
I get the same error

System>OMV-Extras>Updates>Update (runs Apt-get update)

No Errors

System>OMV-Extras>Updates>OMV-Update (runs OMV-update)
No Errors

System>OMV-Extras>Updates>Upgrade (runs Apt-get upgrade)

Display Spoiler

System>OMV-Extras>Updates>dist-upgrade (runs Apt-get dist-upgrade)

Display Spoiler

BackWoodsTech · Apr 10th 2019

After scouring the forum, it appears that this is a DNS issue. I had thought this was a more complicated issue but seems to just be a case of RTFM:

"The DNS setting is essential for fetching updates, do not leave empty. A common value is to use the same IP address as the gateway...."

I did this and updates appear to be working fine. What I don't understand is how this configuration might have changed since updates were working previously.

ryecoaaron · Apr 10th 2019

Quote from BackWoodsTech

What I don't understand is how this configuration might have changed since updates were working previously.

Were you using dhcp previously?

BackWoodsTech · Apr 10th 2019

Yes, and unfortunately I still am. I know this isn't ideal.
(Short of the long: fighting my verizon jetpack to have an IP reservation for my NAS; locked out of the admin console).

ryecoaaron · Apr 10th 2019

Quote from BackWoodsTech

Yes, and unfortunately I still am. I know this isn't ideal.

dhcp isn't a problem. You shouldn't have to set the dns server with dhcp. Most people forget to set the dns server when switching to static IP.

BackWoodsTech · Apr 10th 2019

Quote from ryecoaaron

dhcp isn't a problem. You shouldn't have to set the dns server with dhcp. Most people forget to set the dns server when switching to static IP.

ugh...so did some kinda 'magic' just happen then??

I have no idea why it'd just start working then. Probably not a big deal but I'd sure like to know for future reference.

ryecoaaron · Apr 11th 2019

Quote from BackWoodsTech

so did some kinda 'magic' just happen then??

Hard to say. Some dhcp servers are better than others.

Participate now!