[solved] Cannot Update OMV

Andrew Ryan · 6. Juli 2016

Hi all,
Yesterday I set up OMV on my old Notebook, to experiment a little bit with OMV. Unfortunately, I don't have any skills / experience with Linux, so I'm a little bit stranded here...
I tried to update my plugins(?), but I recieved the following error:

Code

Failed to execute command 'export LANG=C; apt-get update 2>&1': Ign file: Release.gpg Ign file: Release Ign cdrom://[Debian GNU/Linux 7.0.0 _Wheezy_ - Official Snapshot amd64 LIVE/INSTALL Binary 20150629-08:52] wheezy Release.gpg Ign cdrom://[Debian GNU/Linux 7.0.0 _Wheezy_ - Official Snapshot amd64 LIVE/INSTALL Binary 20150629-08:52] wheezy Release Ign cdrom://[Debian GNU/Linux 7.0.0 _Wheezy_ - Official Snapshot amd64 LIVE/INSTALL Binary 20150629-08:52] wheezy/contrib amd64 Packages/DiffIndex Err http://security.debian.org wheezy/updates Release.gpg Cannot initiate the connection to security.debian.org:80 (212.211.132.32). - connect (101: Network is unreachable) [IP: 212.211.132.32 80] Err http://packages.openmediavault.org stoneburner Release.gpg Cannot initiate the connection to packages.openmediavault.org:80 (178.254.11.33). - connect (101: Network is unreachable) Ign cdrom://[Debian GNU/Linux 7.0.0 _Wheezy_ - Official Snapshot amd64 LIVE/INSTALL Binary 20150629-08:52] wheezy/main amd64 Packages/DiffIndex Ign http://security.debian.org wheezy/updates Release Ign http://packages.openmediavault.org stoneburner Release Ign cdrom://[Debian GNU/Linux 7.0.0 _Wheezy_ - Official Snapshot amd64 LIVE/INSTALL Binary 20150629-08:52] wheezy/non-free amd64 Packages/DiffIndex Err http://ftp.uni-erlangen.de wheezy Release.gpg Cannot initiate the connection to ftp.uni-erlangen.de:80 (131.188.12.211). - connect (101: Network is unreachable) Err http://ftp.uni-erlangen.de wheezy-updates Release.gpg Cannot initiate the connection to ftp.uni-erlangen.de:80 (131.188.12.211). - connect (101: Network is unreachable) Ign http://security.debian.org wheezy/updates/main Sources/DiffIndex Ign http://packages.openmediavault.org stoneburner/main amd64 Packages/DiffIndex Ign http://ftp.uni-erlangen.de wheezy Release Ign http://security.debian.org wheezy/updates/contrib Sources/DiffIndex Ign http://security.debian.org wheezy/updates/non-free Sources/DiffIndex Ign http://security.debian.org wheezy/updates/main amd64 Packages/DiffIndex Ign http://security.debian.org wheezy/updates/contrib amd64 Packages/DiffIndex Ign http://security.debian.org wheezy/updates/non-free amd64

tinh_x7 · 6. Juli 2016

It couldn't connected to http://security.debian.org wheezy/updates Release.gpg Cannot initiate the connection to security.debian.org:80 (212.211.132.32).
Check your firewall settings.

Andrew Ryan · 7. Juli 2016

Zitat von tinh_x7

Check your firewall settings.

I opened the system of my Router (TL-WR841N), but I didn't found any settings regarding firewall except on/off for the firewall. I never touched any firewall settings, so is there another way to solve this?

gderf · 7. Juli 2016

In my experience it is not at all unusual to be unable to connect to one or more repositories when updating. Just try again. I find it easier to do this from a shell.

ryecoaaron · 7. Juli 2016

What is the output of: cat /etc/network/interfaces

mastermischke · 10. Juli 2016

I somehow have to same problem (but I'm on 3.X so i know no support for this at the time being)

But I think it might help the OP

cat /etc/network/interfaces

Code

# The loopback network interface
auto lo
iface lo inet loopback


# eth0 network interface
auto eth0
allow-hotplug eth0
iface eth0 inet dhcp
    dns-nameservers 192.168.1.1
iface eth0 inet6 manual
    pre-down ip -6 addr flush dev $IFACE

Alles anzeigen

tekkb · 10. Juli 2016

To anyone reading this thread... If one of your source repos is down you will not be able to do updates. You can temporarily comment out the offending repo from your sources.list or the file in the sources.d folder in which the repo resides. Then do "apt-get update" and you will be able to do upgrades again. Later you should take the comment (#) off and do "apt-get update" again. When the repo is working again apt-get update will finish without errors. If there is still an error in the repo add the comment back and do apt-get update again. Repeat the process at periodic times until you see the repo is up again.

repo files are normally in this folder (except sources.list which is in the apt folder):
/etc/apt/sources.d

It is really not necessary to mess with the sources.list file. It is recommend to use the "Custom Repos" TAB in OMV Extras if you want to add additional repos.

Andrew Ryan · 11. Juli 2016

Zitat von ryecoaaron

What is the output of: <code class="inlineCode">cat /etc/network/interfaces</code>

The answer is

Code

# The loopback network interface
auto lo
iface lo inet loopback
iface lo inet6 loopback
# eth0 network interface
auto eth0
allow-hotplug eth0
iface eth0 inet static
  address 192.168.0.199
  netmask 255.255.255.0
  pre-down ethtool -s $IFACE wol g
iface eth0 inet6 manual
  pre-down ip -6 addr flush dev $IFACE

Alles anzeigen

BTW: Is there a "plugin" to use shell on the webinterface instead of using my old laptop? I don't want to switch everytime when i want to use shell.

ryecoaaron · 11. Juli 2016

You didn't set your gateway (usually router IP address).

Yes. There is a plugin for shellinabox.

Andrew Ryan · 11. Juli 2016

Zitat von ryecoaaron

You didn't set your gateway (usually router IP address).

Yes. There is a plugin for shellinabox.

Sorry for asking again: Where / How can I set up my Gateway? Who should the Router Ip look like (Where can i find it). Thx alot, I'm really absolute beginner

ryecoaaron · 11. Juli 2016

Did you look for it? It is in the same place that you set OMV's IP address (which you obviously did from the output).

As for the router's address, how did you know to set the static IP to 192.168.0.199? If you want to know the correct gateway, just use ipconfig on a Windows box.

Andrew Ryan · 11. Juli 2016

Zitat von ryecoaaron

Did you look for it? It is in the same place that you set OMV's IP address (which you obviously did from the output).

As for the router's address, how did you know to set the static IP to 192.168.0.199? If you want to know the correct gateway, just…

That's right, I found it. Now I can connect to the server, problem solved! Thx for your help

tinh_x7 · 11. Juli 2016

I thought the network interface in OMV required all IPv4/v6 fields to be filled out before let you save it.
Gateway is one of them.

ryecoaaron · 12. Juli 2016

It isn't required. You could still use it as a NAS without a gateway but you couldn't update it.

Jetzt mitmachen!