This is a freshly install from the 3.8.7 ISO, which I installed and upgraded, and then went ahead and changed the IP to the static one I use for the NAS. After another reboot, I get different IP’s shown. I access the NAS via 172.26.1.8 (also SSH), but the Web interface shows 172.26.1.17.
I actually had to reinstall, because the original update left me in a state where the cli told me the system had no IP, and I couldn’t connect to the NAS from other machines.
So I’m worried that something is wrong with the networking setup somewhere.
@KarstenV Thanks for reportign this and yes it is a bit disconcerting. I haven’t managed to reproduce here but need to put more time into it. I know the network stuff has been reworked of late so the 3.8-7 and 3.8-8 systems are actually different. Here I have agreement on the actual and displayed ip so far (fresh 3.8-7 to 3.8-8 upgrade) but still using dhcp. Will try your steps once I’ve done with some other loose ends.
I have seen the “system has no ip message” and we have an open issue on this: bogus noip message in console In that case I was not infrequently seeing that message and after just a little wait and a carriage return and the message was updated to what might be expected. Some kind of timing issue. However the scope of the changes in the network config may well have changed this completely. I think we are going to have to wait until @suman can comment / reproduce.
Glad you got up and running again. Really we need some kind of “Find my Rockstor” web based thing which has been discussed but I just don’t know how this can be done just yet, I was thinking of some kind of network scan that looked for modern kernel signatures in ip returns. Any ideas welcome as this console message is only part of the story really.
@roweryan Just chipping in, a fresh install of 3.8-7 with 3.8-8 upgrade looks like this:-
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.1.203 rockstor
No network changes have been made.
My DHCP server hands out adresses from 172.26.1.12 and up, and Rockstor was given .17 on install, and that was the ip I used to log in and reconfigure from DHCP to static .8. After this I can access Rockstor on .8 as I should, but the Web-interface shows the old adress.
I worry that the wrong input into hosts will have other effects on e.g. rockons?
Given that
cat /etc/nsswitch.conf | grep hosts
gives:-
#hosts: db files nisplus nis dns
hosts: files dns myhostname
Then with files first the hosts file is going to upset something or other if it gets out of kilter in your configs at one time or another.
It should be that if one does nslookup on a machine name it should resolve to it’s actual ip, both locally and remotely. Also proper if nslookup on the actual ip resolves to the machine name ie:-
Server: 192.168.1.1
Address: 192.168.1.1#53
179.1.168.192.in-addr.arpa name = rockstor.lan.
Here my dns server is 192.168.1.1 and hosts a local domain called lan, not all routers do this properly though.
So all looks good on my default dhcp Rockstor. @KarstenV I think you can safely change you’re /etc/hosts file to match the actual configured IP like @roweryan did as this does look like a bug to me.
However I’m going to have to pass this one over to @suman to issue / final say etc. The above stipulation is proper but not always absolutely necessary, but servers do like it that way is my understanding, especially with things like kerberos authentication and the like.
Hope that helps (nslookup is in bind-utils by the way).
