Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

no ip address given in console #924

Closed
phillxnet opened this issue Oct 4, 2015 · 5 comments
Closed

no ip address given in console #924

phillxnet opened this issue Oct 4, 2015 · 5 comments

Comments

@phillxnet
Copy link
Member

As of 3.8-8 the console displays "The system does not have an ip address"
Yet it does, login and ifconfig displays this.
Reproduced by fresh 3.8-7 install, applied 3.8-8 update and then rebooted.
All subsequent reboots display this same misleading message.

Rockstor machine can be found in list of all machines via "fing" app on android or "arp -a" in terminal on linux system or via router webUI dhcp / connected clients section.

@phillxnet
Copy link
Member Author

Turns our Fing is available for Android, iOS, Windows, and OS X.

There is a fing package for linux but it is of dubious packaging quality as per my Ubuntu 15.04.
Haven't tried the rpm.

@phillxnet
Copy link
Member Author

On an ubuntu system one can:-
sudo apt-get install arp-scan
sudo arp-scan -l
should list available hosts and their manufacturer (of the network card) on the local lan.

@phillxnet
Copy link
Member Author

I still have this happening on testing 3.8-8.05, upgraded from a clean install of 3.8-7 to 3.8-8 then testing selected and updates applied. system is core 2 duo but boot from msata in pci so pretty quickly.

phillxnet added a commit to phillxnet/rockstor-core that referenced this issue Oct 11, 2015
…#924

Previously /etc/issue was updated by initrock but sometimes
this took a few goes. Recently only a single try has been attempted.
Return to multiple tries as needed in many instances.
@phillxnet
Copy link
Member Author

I am now working on a pull request to return prior behaviour as we have recently had a regression that caused only a single try when the interface was still in the throws of getting it's IP. This resulted in /etc/issues never getting updated with an IP, even after multiple presses use to be the case in #734 . Should be ready to merge later today.

phillxnet added a commit to phillxnet/rockstor-core that referenced this issue Oct 11, 2015
As we may still be waiting for a background update of the /etc/issue
message that Enter will provide updated network status as this will
cause a re-read of the possibly now updated /etc/issue containing the
just configured ip.
phillxnet added a commit to phillxnet/rockstor-core that referenced this issue Oct 11, 2015


system.osi.update_issue used by storageadmin/views/network.py
is used for a more basic task so to avoid future confusion this
rename makes initrocks's update_issue more obvious to locate.
schakrava added a commit to schakrava/rockstor-core that referenced this issue Oct 12, 2015
@phillxnet
Copy link
Member Author

Closing as pr #940 should address this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant