Can't login to web interface

snoturtle · 17. November 2019

Hello all,

We recently moved and I am just getting my OMV box back up and running.
First thing I did was updates and changed the DNS address as we changed providers.

Since than I get an error when I try and access the web UI.

I have tried resetting the network settings with omv-firstaid and I am still able to access the server through SSH and from my Windows desktop.

Code

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; hostname --fqdn 2>&1' with exit code '1': hostname: Name or service not known in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/php/openmediavault/system/net/dns.inc(60): OMV\System\Process->execute(Array)
#1 /var/www/openmediavault/rpc/session.inc(121): OMV\System\Net\Dns::getFqdn()
#2 [internal function]: OMVRpcServiceSession->login(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('login', Array, Array)
#5 /usr/share/php/openmediavault/rpc/proxy/json.inc(97): OMV\Rpc\Rpc::call('Session', 'login', Array, Array, 3)
#6 /var/www/openmediavault/rpc.php(45): OMV\Rpc\Proxy\Json->handle()
#7 {main}

Alles anzeigen

Rd65 · 17. November 2019

reset your network with omav-firstaid 1. to dhcp on ipv4 and after reboot reset 2. your webcontrolinterface and 3. use your router as dns provider. there is no need to change network config on providerchange, this is managed by the router.
Its not a good idea to use a external dns server without knowlege because in this way clients ask 1000 things about the internal home-net to external DNS Servers .. without any sense.

snoturtle · 17. November 2019

1. Done already
2. Set to DHCP and same results through WebUI
3. Provider wrong term and router is not DNS server
Spun up a new Pihole when we moved, but have tried to set to router also and no difference

Rd65 · 17. November 2019

on a working and well managed machine i would say:

please post the result of
#nmap --script broadcast-dhcp-discover

but i am afraid this will go wrong now.

maybe you can try

#dhcpdump -i yourinterfacename
or
#dhclient -v

snoturtle · 17. November 2019

nmap results

root@OMV:~# nmap --script broadcast-dhcp-discover

Starting Nmap 7.40 ( https://nmap.org ) at 2019-11-17 12:22 CST
Pre-scan script results:
| broadcast-dhcp-discover:
| Response 1 of 1:
| IP Offered: 192.168.1.49
| DHCP Message Type: DHCPOFFER
| Server Identifier: 192.168.1.1
| IP Address Lease Time: 5m00s
| Subnet Mask: 255.255.255.0
| Router: 192.168.1.1
| Domain Name Server: 1.1.1.1
|_ Domain Name: localdomain
WARNING: No targets were specified, so 0 hosts scanned.
Nmap done: 0 IP addresses (0 hosts up) scanned in 1.34 seconds

dhclient -v results

It is also holding onto the DHCP lease that was given out when I tried it and is still responding to both 192.168.1.189(static) and 192.168.1.13(DHCP)

root@OMV:~# dhclient -v
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/00:15:5d:01:ad:00
Sending on LPF/eth0/00:15:5d:01:ad:00
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
DHCPREQUEST of 192.168.1.13 on eth0 to 255.255.255.255 port 67
DHCPOFFER of 192.168.1.13 from 192.168.1.1
DHCPACK of 192.168.1.13 from 192.168.1.1
/etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /etc/resolvconf/run/resolv.conf
bound to 192.168.1.13 -- renewal in 2916 seconds.

root@OMV:~# ifconfig eth0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.189 netmask 255.255.255.0 broadcast 192.168.1.255
ether 00:15:5d:01:ad:00 txqueuelen 1000 (Ethernet)
RX packets 3793 bytes 1889775 (1.8 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1774 bytes 1854669 (1.7 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

votdev · 18. November 2019

Maybe this will fix your issue. Please report if it works or not.

Bash

# apt-get install libnss-myhostname

Rd65 · 18. November 2019

the dhcp data seem to be ok.
but the warning/error on dhcp -v point to a missconfig of the resolver daemon.
in old times /etc/resolv.conf was a file containing a nameserverip. easy and well done.
in modern times /etc/resolv.conf is a link to a file which is handeled/manages bei the resolv deamon.
if this link is broken, the system complains about... and resolving may gone wrong.
the idea was to manage the resolv.conf depending on events like upcomming and ending dialup modem connections, offlinemode and so on... but on 24/7 systems like a nas this is crap.
in the case the host file and /or hostname is even wrong too... the System can't find its own name. Sometimes this will break nginx. maybe nss-myhostname help.. but the reason for this is a bunch of missconfigured configs.

so the way is:
set a hostname and the domain in omv... or at the system (/etc/hostname)
check your /etc/hosts file

Code

# cat /etc/hosts
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
127.0.0.1 localhost
127.0.1.1 nas.local nas

check if # hostname --fqdn
shows a well formated hostname like this -> nas.local
(2 names with a dot)
now do a #dpkg-reconfigure resolvconf
this will restore the resolv.conf-symlink
mybe you need to delete the /etc/resolv.conf at first.
check your /etc/network/interfaces

Code

# The loopback network interface
auto lo eth0
iface lo inet loopback


# The primary network interface
iface eth0 inet dhcp

shoud look like this - but replace all eth0 with your network adapter name.
enpXsY or whatever - depends on your hardware, udev and lot's of script crap. list with #cat /proc/net/dev

do a #omv-initsystem
omv will re-read configs
#reboot

now dhcp will setup via the daemon resolvconf a working and linked resolv.conf

read about
https://wiki.debian.org/NetworkConfiguration
and
take a look at this:
https://askubuntu.com/question…resolv-conf-must-be-a-sym

snoturtle · 23. November 2019

Sorry for the delay in responding I was out of state for a few days.

root@OMV:~# cat /etc/hosts
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
127.0.0.1 localhost
127.0.1.1 openmediavault
192.168.1.189 openmediavault
root@OMV:~#

root@OMV:~# hostname --fqdn
hostname: Name or service not known

root@OMV:~# omv-initsystem
dnsdomainname: Name or service not known
run-parts: /usr/share/openmediavault/initsystem/20hostname exited with return code 1

root@OMV:~# cat /etc/network/interfaces
# The loopback network interface
auto lo
iface lo inet loopback

# eth0 network interface
auto eth0
allow-hotplug eth0
iface eth0 inet static
address 192.168.1.189
gateway 192.168.1.1
netmask 255.255.255.0
dns-nameservers 192.168.1.1
iface eth0 inet6 manual
pre-down ip -6 addr flush dev $IFACE
# Include additional interface stanzas.
source-directory interfaces.d

Rd65 · 23. November 2019

no hostname.. hm... do a
#hostnamectl set-hostname host.example.com
something like #hostnamectl set-hostname openmediavault.local
as desribed in your hosts file. and restart.
i think this will fix it and nginx will start too.

snoturtle · 24. November 2019

That fixed it!!

Thank you very much for you help

Jetzt mitmachen!