Recent changes to Debugging_xCAT_Problems

Debugging_xCAT_Problems modified by XiaoPeng Wang

XiaoPeng Wang — Thu, 16 Jul 2015 07:41:41 -0000

--- v71
+++ v72
@@ -389,6 +389,8 @@
 Make sure the installp and rpm packages have been updated to the nimimage.

 ### Collect information and logs from the installer during os installation
+**NOTE:** This is a experimental feature in xCAT 2.10 release.
+
 OS installer is an initrd running to perform the os installation, such as anaconda on Redhat, autoyast on SLES and debian-installer on Ubuntu. Collecting Logs and other information from the installer or even accessing the installer would be quite helpful while looking into the installation problem. By setting the "site.xcatdebugmode" to "1" before running "nodeset", the administrator can inspect the installer with the following methods provided by xCAT:
 1) all the installation logs will be forwarded to the logserver(management node) from the installer, this is currently only available on Redhat and SLES.

Debugging_xCAT_Problems modified by yangsong

yangsong — Tue, 07 Jul 2015 07:01:30 -0000

--- v70
+++ v71
@@ -408,6 +408,17 @@
 ~~~~     
    just as the message above suggests, the admin can open 2 sessions and run "ssh -X root@<node>" with the password "cluster" to login into the installer, then run "yast" to continue installation in one session and inspect the installation process in the installer in the other session.

+after the installation is finished, the system requires a reboot. the installation will halt again before the system configuration, the console output shows:
+
+~~~~
+
+*** Preparing SSH installation for reboot ***
+*** NOTE: after reboot, you have to reconnect and call yast.ssh ***
+
+~~~~
+
+just as the message above suggests, the admin should run "ssh -X root@<node>" to access the installer and run "yast.ssh" to finish the installation.
+
    (2) For Redhat, the installation won't halt, just login into the installer with "ssh root@<node>".

    (3) For Ubuntu, the installation will halt on the following message in the console:

Debugging_xCAT_Problems modified by yangsong

yangsong — Tue, 07 Jul 2015 06:56:11 -0000

--- v69
+++ v70
@@ -406,20 +406,7 @@
       ***  run 'yast' to start the installation  ***

 ~~~~     
-
    just as the message above suggests, the admin can open 2 sessions and run "ssh -X root@<node>" with the password "cluster" to login into the installer, then run "yast" to continue installation in one session and inspect the installation process in the installer in the other session. 
-
-after the installation is finished, the system requires a reboot. the installation will halt again before the system configuration, the console output shows:
-
-~~~~
-
-*** Preparing SSH installation for reboot ***
-*** NOTE: after reboot, you have to reconnect and call yast.ssh ***
-
-~~~~
-
-just as the message above suggests, the admin should run "ssh -X root@<node>" to access the installer and run "yast.ssh" to finish the installation.
-

    (2) For Redhat, the installation won't halt, just login into the installer with "ssh root@<node>".

Debugging_xCAT_Problems modified by yangsong

yangsong — Tue, 07 Jul 2015 06:50:28 -0000

--- v68
+++ v69
@@ -406,7 +406,20 @@
       ***  run 'yast' to start the installation  ***

 ~~~~     
+
    just as the message above suggests, the admin can open 2 sessions and run "ssh -X root@<node>" with the password "cluster" to login into the installer, then run "yast" to continue installation in one session and inspect the installation process in the installer in the other session. 
+
+after the installation is finished, the system requires a reboot. the installation will halt again before the system configuration, the console output shows:
+
+~~~~
+
+*** Preparing SSH installation for reboot ***
+*** NOTE: after reboot, you have to reconnect and call yast.ssh ***
+
+~~~~
+
+just as the message above suggests, the admin should run "ssh -X root@<node>" to access the installer and run "yast.ssh" to finish the installation.
+

    (2) For Redhat, the installation won't halt, just login into the installer with "ssh root@<node>".

Debugging_xCAT_Problems modified by yangsong

yangsong — Wed, 17 Jun 2015 14:52:56 -0000

--- v67
+++ v68
@@ -392,6 +392,8 @@
 OS installer is an initrd running to perform the os installation, such as anaconda on Redhat, autoyast on SLES and debian-installer on Ubuntu. Collecting Logs and other information from the installer or even accessing the installer would be quite helpful while looking into the installation problem. By setting the "site.xcatdebugmode" to "1" before running "nodeset", the administrator can inspect the installer with the following methods provided by xCAT:
 1) all the installation logs will be forwarded to the logserver(management node) from the installer, this is currently only available on Redhat and SLES.

+Note: For anaconda in Redhat, the syslog is forwarded via TCP protocol. The remote syslog process on log Server must be configured to accept incoming connections. For information on how to configure a syslog service to accept incoming connections, see [the Red Hat Enterprise Linux 7 System Administrator's Guide](https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/s1-configuring_rsyslog_on_a_logging_server.html).
+
 2) the ssh access to the installer is enabled, the admin can login into the installer thru:
    (1) For SLES, the installation will halt after the ssh server is started, the console output shows:

Debugging_xCAT_Problems modified by yangsong

yangsong — Mon, 15 Jun 2015 09:01:40 -0000

--- v66
+++ v67
@@ -447,14 +447,20 @@

 Note: the postscript "syncfiles" won't work in the debug mode.

-3)  a simple service daemon is started in the installer, which listens to the port 3001 and executes the commands sent from the management node and returns the output as the respond to the management.
+3)  a simple server is started in the installer, which listens to the port 3001 and executes the commands sent from the management node and returns the output as the response to the management.

-The following command can be used to send request to installer:
-
-~~~~
-
-nodestat_internal <node> ""
-
+The command "runcmdinstaller" can be used to send request to installer:
+
+~~~~
+Usage:
+
+   runcmdinstaller <node> ""
+
+   make sure all the commands are quoted by ""
+
+
+example:
+   runcmdinstaller c910f03c01p03 "ls /tmp" 
 ~~~~

Debugging_xCAT_Problems modified by yangsong

yangsong — Sun, 14 Jun 2015 14:19:50 -0000

--- v65
+++ v66
@@ -450,9 +450,13 @@
 3)  a simple service daemon is started in the installer, which listens to the port 3001 and executes the commands sent from the management node and returns the output as the respond to the management.

 The following command can be used to send request to installer:
-~~~~
+
+~~~~
+
 nodestat_internal <node> ""
+
 ~~~~ 
+

Debugging_xCAT_Problems modified by yangsong

yangsong — Sun, 14 Jun 2015 14:18:07 -0000

--- v64
+++ v65
@@ -447,8 +447,12 @@

 Note: the postscript "syncfiles" won't work in the debug mode.

-3)  
-   
+3)  a simple service daemon is started in the installer, which listens to the port 3001 and executes the commands sent from the management node and returns the output as the respond to the management.
+  
+The following command can be used to send request to installer:
+~~~~
+nodestat_internal <node> ""
+~~~~

Debugging_xCAT_Problems modified by yangsong

yangsong — Sat, 13 Jun 2015 14:43:19 -0000

--- v63
+++ v64
@@ -388,6 +388,71 @@
 Make sure the installp_bundle or otherpkgs has been configured to the nimimage. 1. Wirte into table nimimage. 2. Put as parameter for 'nimnodeset' command.
 Make sure the installp and rpm packages have been updated to the nimimage.

+### Collect information and logs from the installer during os installation
+OS installer is an initrd running to perform the os installation, such as anaconda on Redhat, autoyast on SLES and debian-installer on Ubuntu. Collecting Logs and other information from the installer or even accessing the installer would be quite helpful while looking into the installation problem. By setting the "site.xcatdebugmode" to "1" before running "nodeset", the administrator can inspect the installer with the following methods provided by xCAT:
+1) all the installation logs will be forwarded to the logserver(management node) from the installer, this is currently only available on Redhat and SLES.
+
+2) the ssh access to the installer is enabled, the admin can login into the installer thru:
+   (1) For SLES, the installation will halt after the ssh server is started, the console output shows:
+ 
+~~~~
+
+      ***  sshd has been started  ***
+
+
+      ***  login using 'ssh -X root@c910f02c01p23'  ***
+      ***  run 'yast' to start the installation  ***
+
+~~~~     
+   just as the message above suggests, the admin can open 2 sessions and run "ssh -X root@<node>" with the password "cluster" to login into the installer, then run "yast" to continue installation in one session and inspect the installation process in the installer in the other session. 
+
+   (2) For Redhat, the installation won't halt, just login into the installer with "ssh root@<node>".
+
+   (3) For Ubuntu, the installation will halt on the following message in the console:
+
+~~~~
+   â”Œâ”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”¤ [!!] Continue installation remotely u   g SSH â”œâ”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”
+   â”‚                                                                       â”‚
+   â”‚                               Start SSH                               â”‚
+   â”‚ To continue the installation, please use an SSH client to connect to  â”‚
+   â”‚ the IP address 9.114.34.82 and log in as the "installer" user. For    â”‚
+   â”‚ example:                                                              â”‚
+   â”‚                                                                       â”‚
+   â”‚    ssh installer@9.114.34.82                                          â”‚
+   â”‚                                                                       â”‚
+   â”‚ The fingerprint of this SSH server's host key is:                     â”‚
+   â”‚ bd:47:9f:d0:0a:3a:d1:d0:37:3a:20:d0:78:84:a8:07                       â”‚
+   â”‚                                                                       â”‚
+   â”‚ Please check this carefully against the fingerprint reported by your  â”‚
+   â”‚ SSH client.                                                           â”‚
+   â”‚                                                                       â”‚
+   â”‚                              <Continue>                               â”‚
+   â”‚                                                                       â”‚
+   â””â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”˜
+
+~~~~ 
+  just as the message show, the admin can run "ssh installer@<node>" with the password "cluster" to login into the installer, the following message shows on login:
+
+~~~~      
+This is the network console for the Debian installer. 
+From here, you may start the Debian installer, or execute an interactive shell. 
+To return to this menu, you will need to log in again. 
+Network console option: 
+           Start installer 
+           Start installer (expert mode) 
+           Start shell                               
+~~~~
+
+  the admin can open 2 sessions and then select "Start installer" to continue installation in one session and select "Start shell" in the other session to inspect the installation process in the installer .
+
+Note: the postscript "syncfiles" won't work in the debug mode.
+
+3)  
+   
+    
+  
+
+
 ### Syncing  files does not work
 The files listed in the synclist are not synced to the node

Debugging_xCAT_Problems modified by Guang Cheng Li

Guang Cheng Li — Mon, 18 May 2015 02:28:47 -0000

--- v62
+++ v63
@@ -243,7 +243,7 @@

 The installation configuration file /install/autoinst/<node>

-This file will be generated for diskfull installation after the running of 'nodeset <node> install'.
+This file will be generated for diskfull installation after the running of 'nodeset <nodename> osimage=<osimage>'.

 Check the following part to work out possible problems: