-
Notifications
You must be signed in to change notification settings - Fork 108
Install troubleshooting with ssh #392
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
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Yann Dirson <[email protected]>
Signed-off-by: Yann Dirson <[email protected]>
Note you can specify an interface name such as `eth1` instead of `all` | ||
if necessary, which can be useful when you need to setup a static IP | ||
address. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be useful to also explain:
- When the SSH server becomes available
- How to connect (which user, which hostname/IP - that's obvious but it doesn't hurt being explicit, which password - same)
|
||
### Getting remote access to host during installation | ||
|
||
While for simple problems access through the console as described |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The wording could be a bit more natural, something like that:
While the console access method described above may be sufficient for simple issues, collecting full logs (install logs, kernel logs, etc.) often requires copying large amounts of data, which is impractical without direct file access.
To enable SSH/SCP access during installation, you can use the Linux kernel command line to:
- Activate the network
- Enable the sshd service
- Set a root password of your choice
For the most common case (setting up the network via DHCP), add the following parameter to the Linux boot section:
network_device=all sshpassword=YOURCHOICE | ||
``` | ||
|
||
You may select an alternative setup using `network_config` (which |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest this wording:
You can also use the network_config parameter (which defaults to dhcp) to define an alternative network setup. Here’s how it works:
- Replace the capitalized values with your own settings. Square brackets ([]) indicate optional parameters.
network_config=dhcp[:vlan=VLAN]
network_config=static:ip=IP;netmask=NETMASK[;gateway=GW][;dns=DNS1[,DNS2]][;domain=DOMAIN][;vlan=VLAN]
network_config=static:ip=IP;netmask=NETMASK[;gateway=GW][;dns=DNS1[,DNS2]][;domain=DOMAIN][;vlan=VLAN] | ||
``` | ||
|
||
Note you can specify an interface name such as `eth1` instead of `all` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Feel free to use Docusaurus' "Note" element:
:::note
You can specify an interface name such as `eth1` instead of `all` if necessary, which can be useful when you need to setup a static IP address.
:::
## Installation logs | ||
|
||
The installer writes in `/var/log/installer/`. | ||
On the installed system, the installer logs are kept in `/var/log/installer/`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On the installed system, the installer logs are kept in `/var/log/installer/`. | |
On the installed system, installer logs are kept in `/var/log/installer/`. |
Those instructions will be useful to refer users to from forum or support tickets.