Some of the well known of Data Center Operation and Maintenance standard are: ISO, Uptime® M&O Stamp of Approval, EPI-DCOS® – Data Centre Operations Standard and TIMS – Tiered Infrastructure Maintenance Standards
Which Standards To Follow ? Checkout a Linkedin post by Edward Van Leent, A CEO from EPI Group below:
https://www.linkedin.com/pulse/data-centre-operations-which-standards-follow-edward-van-leent/
Found this site https://instances.vantage.sh/, you can easily compare all AWS EC2 instance. You can filter it based on total number of RAM, vCPU and Storage, also you can select based on its region and cost.
As per the author, Data is scraped from multiple pages on the AWS site and its managed and maintained by Vantage
What is Oracle Explorer?
The Oracle Explorer Data Collector is a collection of shell scripts and a few binary executable that gathers information and creates a detailed snapshot of a system’s configuration and state. Explorer output enables Oracle’s engineers to perform assessments of the system by applying the output against knowledge-based rules engine.
Oracle Explorer Data Collector is part of Oracle Services Tools Bundle (STB). As Explorer uses the Remote Diagnostic Agent (RDA) tool to collect part of its information and because RDA is part of the STB, it is highly advised to install the entire STB bundle.
For more information about Explorer and STB, go to > Oracle Explorer Data Collector Installation and Services Tools Bundle (STB) User’s Guide page.
How to create Explorer report with Oracle Explominer Tools:
Explominer package only available at EIS (Enterprise Installation Service ) DVD – which is intended for Oracle employees and partner only. EIS-DVD can be download at edelivery.oracle.com
install Explominer:
– open EIS-DVD
– search sun – tools – explominer
– copy explominer.tar.gz to destination server
– after that please extract with “gzcat explominer.tar.gz|tar xvf –
– then go to directory ExploMiner
– then run explominer
There is difference script/package based on processor type: i386, Sparc and x86 machine.
bash-3.00# pwd
/opt/explominer
bash-3.00# ls
explominer explominer.i386 explominer.sparc explominer.tar.gz explominer.x86
bash-3.00#
Create Explorer report:
Copy and extract the explorer output file and run explominer, below are the example:
/tmp/output/explorer.853c62da.server-2016.04.15.09.15 >>my explorer extract folder location
/export/home/explominer_report >>report folder
bash-3.00# ./explominer.x86 -h
Copyright (c) 2013, Oracle and/or its affiliates. All right reserved.
ExploMiner v2.11.6 EIS-CD 07/2013usage: explominer.pl [-h]
explominer.pl [-f expdir] [-o outdir] [-e eisdir] [-c] [-m] [-r] [-i] [-a]In the first form explominer.pl prints this help message.
In the second form explominer.pl performs the checks and writes the
results to output files.arguments: none
options: -h print this help message
-f expdir
find explorer output in directory expdir
default: .
-o outdir
write output files to directory outdir
default: .
-e eisdir
compare the results of the patch analysis with the patchdiag.xref and patch.list files from the
EIS-CD found at eisdir and generate the file ExploMiner_EIS_Patchlist_user
-c generate the customer report file ExploMiner_CustomerReport.txt
-m analyze message files even if > 4MByte
-r calculate eOri
-i mention internal, proprietary information as well
-a show all FMA Casesbash-3.00#
bash-3.00# ./explominer.x86 -f /tmp/output/explorer.853c62da.server-2016.04.15.09.15 -o /export/home/explominer_report -e /cdrom/eis-dvd/sun/patch/etc/ -c -m -r -i -a
================================================================================
=== Copyright (c) 201X, Oracle and/or its affiliates. All rights reserved. ===
=== ExploMiner vX.XX.X EIS-CD XX/20XX ===
================================================================================
PRODIR is:
[explorerdir]: /tmp/output/explorer.853c62da.server-2016.04.15.09.15
[outputdir]: /export/home/explominer_report
[eisdir]: /cdrom/eis-dvd/sun/patch/etc/Contents Output file name
——————————————————————————–
HTML_Check_Results [outputdir]/ExploMiner_Output_root.html
Alerts [outputdir]/ExploMiner_Alerts_Output_root
msg.pl output [outputdir]/ExploMiner_messages.out.root
Patchlist [outputdir]/ExploMiner_Patchlist_root
Ordered Patchlist [outputdir]/ExploMiner_Patchorder_root
patchdiag output [outputdir]/ExploMiner_patchdiag.out.root
filtered patchdiag output [outputdir]/ExploMiner_patchdiag.out.root_without_CURRENT
security patches output [outputdir]/ExploMiner_Security_Patches_rootPatch-Matrix-files should not be older than 45 days.
================================================================================
NOTICE: ExploMiner does now also include the revision of patches included in the Solaris Recommended Patch Set (see “rps:”) in addition to the latest revision (see “current:”), and – if this revision is lower than the latest patch revision – the respective release date.IMPORTANT: ExploMiner is primarily intended for reactive, break-fix support. It shows the latest revision (see “current”) or when it’s not installed (see “missing”) of any patch that is found to be relevant,
eventually preceded by the revision of that patch that is included in the Solaris Recommended Patch Set (see “rps”) from the day when ExploMiner was run.Patches listed in its output might be relevant to any known issues, but their presence herein does not necessarily manifest a general patch recommendation.
ExploMiner is not primarily intended for proactive patch management!
IMPORTANT: Please note: Despite the instructions on MOS, some customers may have improperly loaded attachments into this system that contain electronic protected health information (ePHI). Should you encounter any ePHI, immediately delete all copies from this system and purge any local copies. See the GCS Health Legislation Management section of the MOS Desk Manual for procedures on how to do this.
To learn about how to recognize ePHI and Oracle’s need to keep it out of GCS systems, visit the HIPAA Regulatory Compliance workspace at https://stbeehive.oracle.com/teamcollab/overview/Regulatory+Compliance+-+Health+Legislation+Management+(HIPAA+and+HITECH)NOTICE: PatchId: 119368: revision from showrev-p.out (-05) > (-04) from EIS patch.list
NOTICE: PatchId: 123893: revision from showrev-p.out (-25) > (-22) from EIS patch.list
No file ‘sysconfig/ifconfig-a-modlist.out’ found
SunOS_check/Patch_Clusters/SUNOS_pkgadd.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_Kernel.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_Library.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_SMF.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_NTP.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_vold.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_timezones.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_syslogd.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_UFS.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_MTB.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_VXFS.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_Printing.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_Java.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_Webconsole.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_smpatch.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_SMC.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_FMA.patch_matrix is older than 45 days
Sun_Server_check
OBP_check
Network_check
/Patch_Clusters/COMMS_nxge.patch_matrix is older than 45 days
/Patch_Clusters/COMMS_tcp-ip.patch_matrix is older than 45 days
/Patch_Clusters/COMMS_ipmp.patch_matrix is older than 45 days
/Patch_Clusters/COMMS_socket.patch_matrix is older than 45 days
/Patch_Clusters/COMMS_TLI.patch_matrix is older than 45 days
/Patch_Clusters/COMMS_RPC.patch_matrix is older than 45 days
/Patch_Clusters/COMMS_nscd.patch_matrix is older than 45 days
/Patch_Clusters/COMMS_inetd.patch_matrix is older than 45 days
/Patch_Clusters/COMMS_NFSclient.patch_matrix is older than 45 days
OSP_check
/Patch_Clusters/OSP_mpt.patch_matrix is older than 45 days
/Patch_Clusters/OSP_qlc.patch_matrix is older than 45 days
/Patch_Clusters/OSP_SAN.patch_matrix is older than 45 days
/Patch_Clusters/OSP_sd.patch_matrix is older than 45 days
/Patch_Clusters/OSP_DiskUtils.patch_matrix is older than 45 days
/Patch_Clusters/OSP_VXVM.patch_matrix is older than 45 days
/Patch_Clusters/OSP_VXVM-GUI.patch_matrix is older than 45 days
/Patch_Clusters/OSP_VXVM-GUI.patch_matrix is older than 45 days
rootdg: 0
Graphics_check
Security_check
bash-3.00#
Check all in one output:
HTML_Check_Results >> [outputdir]/ExploMiner_Output_root.html
This is how to manual backup, copy or cloning mounted disk partition on Solaris:
source: c0t0d0s0
destination:c0t1d0s0 (will be mounted on /mnt/root-backup)
*copy the disk partition layout
# prtvtoc /dev/rdsk/c0t0d0s2 | fmthard -s – /dev/rdsk/c0t1d0s2
* create UFS file systems on disk c0t1d0s0
# newfs /dev/rdsk/c0t1d0s0
*mount disk:
# mount /dev/dsk/c0t1d0s0 /mnt/root-backup/
*initiate backup and restore in single line command:
# cd /mnt/root-backup ; ufsdump 0uf – /dev/dsk/c0t0d0s0 | ufsrestore rf –
*do similar step for another slice (newfs, mount and initiate backup/restore)
*install the bootblock for c0t1d0s0:
installboot /usr/platform/`uname -i`/lib/fs/zfs/bootblk /dev/rdsk/c0t1d0s0
This is the procedure on how to setup or configure a TFTP Server on Solaris host.
/tftpboot is the default location of tftp, it can be changed through /etc/inetd.conf file. On this below example, lets juts enable the tftp line and use default /tftpboot
root@solaris10 # vi /etc/inetd.conf
*uncomment this line:
tftp dgram udp6 wait root /usr/sbin/in.tftpd in.tftpd -s /tftpboot
*create /tftpboot directory:
root@solaris10 # mkdir /tftpboot
root@solaris10 # chown root /tftpboot
root@solaris10 # chmod 755 /tftpboot
root@solaris10 # cd /tftpboot
root@solaris10 # ln -s . tftpboot
*on this below sample, I move file c2960-lanbasek9-mz.122-55.SE12.bin from root to folder /tftpboot
root@solaris10 # mv c2960-lanbasek9-mz.122-55.SE12.bin /tftpboot/
*chmod the file to 444 (owner/group/other only able to read):
root@solaris10 # chmod 444 c2960-lanbasek9-mz.122-55.SE12.bin
root@solaris10 #
*Use inetconv command to install tftp SMF (Service Management Facility) and bring it online:
root@solaris10 # inetconv -i /etc/inetd.conf
inetconv: Notice: Service manifest for 100235/1 already generated as /var/svc/manifest/network/rpc/100235_1-rpc_ticotsord.xml, skipped
tftp -> /var/svc/manifest/network/tftp-udp6.xml
Importing tftp-udp6.xml ...Done
root@solaris10 #
root@solaris10 # svcs -a | grep -i tftp
online 12:50:11 svc:/network/tftp/udp6:default
root@solaris10 #
*Let’s do tftp and test download the file:
*192.168.0.10 is the IP address of Solaris tftp server
*from other Solaris/unix host:
# tftp <tftp-server-host/IP>
tftp> get
Received xxx bytes in x.x seconds
tftp> quit
*Example from Cisco switch:
c2960-SWITCH#copy tftp: flash:
Address or name of remote host [192.168.0.10]?
Source filename [c2960-lanbasek9-mz.122-55.SE12.bin]?
Destination filename [c2960-lanbasek9-mz.122-55.SE12.bin]?
Accessing tftp://192.168.0.10/c2960-lanbasek9-mz.122-55.SE12.bin...
Loading c2960-lanbasek9-mz.122-55.SE12.bin from 192.168.0.10 (via Vlan1): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 9827106 bytes]
9827106 bytes copied in 187.057 secs (52535 bytes/sec)
c2960-SWITCH#
The easiest way to diagnose the hardware related problem on Oracle Sun server is by using of OBP OK Prompt commands, the Power On Self Test (POST), and the status LEDs on system boards.
ou can diagnose hardware related problems on Oracle Sun server and desktop products. With these low-level diagnostics, you can establish the state of the system and attached devices. For example, you can determine if a device is recognized by the system and working properly, or you can also obtain useful system configuration information.
OBP DIAGNOSTIC COMMANDS AND TOOLS
OBP is a powerful, low-level interface to the system and devices attached to the system (OBP is also known as the ok prompt). By entering simple OBP commands, you can learn system configuration details such as the ethernet address, the CPU and bus speeds, installed memory, and so on. Using OBP, you can also query and set system parameter values such as the default boot device, run tests on devices such as the network interface, and display the SCSI and SBUS devices attached to the system.
Below are the available commands in OBP OK prompt:
—————————-
banner
Displays the power on banner. The banner includes information such as CPU speed, OBP revision, total system memory, ethernet address and hostid.
devalias alias path
Defines a new device alias, where alias is the new alias name and path is the physical path of the device. If devalias is used without arguments, it displays all system device aliases (will run up to 120 MHz).
.enet-addr
Displays the ethernet address
led-off/led-on
Turns the system led off or on.
nvaliasname path
Creates a new alias for a device, where name is the name of the alias and path is the physical path of the device. Note – Run the reset-all or the nvstore command to save the new alias in non-volatile memory (NVRAM).
nvunalias name path
Deletes a user-created alias (see nvalias), where name is the name of the alias and path is the physical path of the device. Note – Run the reset-all or nvstore command to save changes in NVRAM.
nvstore
Copies the contents of the temporary buffer to NVRAM and discards the contents of the temporary buffer.
power-off/power-on
Powers the system off or on.
printenv
Displays all parameters, settings, and values
probe-fcal-all
dentifies Fiber Channel Arbitrated Loop (FCAL) devices on a system. 1
probe-sbus
Identifies devices attached to all SBUS slots. Note – This command works only on systems with SBUS slots.
probe-scsi
Identifies devices attached to the onboard SCSI bus. 1
probe-scsi-all
Identifies devices attached to all SCSI busses. 1
set-default parameter
Resets the value of parameter to the default setting.
set-defaults
Resets the value of all parameters to the default settings. Tip – You can also press the Stop and N keys simultaneously during system power-up to reset the values to their defaults.
setenv parameter value
Sets parameter to specified value. Note – Run the reset-all command to save changes in NVRAM.
show-devs
Displays all the devices recognized by the system.
show-disks
Displays the physical device path for disk controllers.
show-displays
Displays the physical device path for frame buffers.
show-nets
Displays the physical device path for network interfaces
show-post-results
If run after Power On Self Test (POST) is completed, this command displays the findings of POST in a readable format.
show-sbus
Displays devices attached to all SBUS slots. Similar to probe-sbus .
show-tapes
Displays the physical device path for tape controllers.
sifting string
Searches for OBP commands or methods that contain string. For example, the sifting probe command displays probe-scsi, probe-scsi-all, probe-sbus, and so on.
speed
Displays CPU and bus speeds
test device-specifier
Executes the selftest method for device-specifier. For example, the test net command tests the network connection.
test-all
Tests all devices that have a built-in test method.
version
Displays OBP and POST version information.
watch-clock
Tests a clock function.
watch-net
Monitors the network connection for the primary interface.
watch-net-all
Monitors all the network connections.
words
Displays all OBP commands and methods
—————————-
OBDIAG
OBDiag also displays diagnostic and error messages on the system console.
How To Run OBDiag
To run OBDiag, simply type obdiag at the Open Boot ok prompt.
You can also set up OBDiag to run automatically when the system is powered on using the following methods:
Set the OBP diagnostics variable: ok setenv diag-switch true
Press the Stop and D keys simultaneously while you power on the system.
On Ultra Enterprise servers, turn the key switch to the diagnostics position and power on the system.
POWER ON SELF TEST (POST)
POST is a program that resides in the firmware of each board in a system, and it is used to initialize, configure, and test the system boards. POST output is sent to serial port A (on an Ultra Enterprise server, POST output is sent only to serial port A on the system and clock board). The status LEDs of each system board on Ultra Enterprise servers indicate the POST completion status. For example, if a system board fails the POST test, the amber LED stays lit.
You can watch POST ouput in real-time by attaching a terminal device to serial port A. If none is available, you can use the OBP command show-post-results to view the results after POST completes.
How To Run POST
– connect to serial port
– set the dig-switch to ‘true’
ok setenv diag-switch true
– Set the desired testing level (min or max), example:
ok setenv diag-level max
– Set the auto-boot variable to ‘false’
ok setenv auto-boot false
– run ‘reset-all’ >> ok reset-all
– Reboot or Power cycle the system
SOLARIS OPERATING ENVIRONMENT DIAGNOSTIC COMMANDS
The following table describes OS commands you can use to display the system configuration, such as failed Field Replaceable Units (FRU), hardware revision information, installed patches, and so on
/usr/platform/sun4u/sbin/prtdiag -v
Displays system configuration and diagnostic information, and lists any failed Field Replaceable Units (FRU).
/usr/bin/showrev [-p]
Displays revision information for the current hardware and software. When used with the -p option, displays installed patches.
/usr/sbin/prtconf
Displays system configuration information.
/usr/sbin/psrinfo -v
Displays CPU information, including clock speed.
###########
ref# Doc ID 1005946.1
Before changing the Solaris 11 IP address, please read on how the network is configured in Oracle Solaris 11
Oracle Solaris 11 uses profile-based network configuration, which is comprised of two network configuration modes: manual (fixed) and automatic (reactive). Depending on which network configuration mode you choose during an installation, either the DefaultFixed network configuration profile (NCP) or the Automatic NCP is activated on the system. If the DefaultFixed NCP is active, the network is manually configured by using the dladm and ipadm commands . If the Automatic NCP or a user-defined, automatic NCP that you previously created is active, the netcfg and netadm commands (formerly nwamcfg and nwamadm) are used to create and manage network configuration.
more detail, go to this page:
http://docs.oracle.com/cd/E23824_01/html/E24456/glhbr.html
To change the IPv4 static IP address, use below prefix:
ipadm delete-addr <interface>/v4
ipadm create-addr -T static -a <ip_address>/<subnet> <interface>/v4
[exp. changing below “net0” ip address to 192.168.10.2:
# ipadm delete-addr net0/v4
# ipadm create-addr -T static -a 192.168.10.2/24 net0/v4
# ipadm show-addr
*If you want to delete the interface first and then put the new ip address, run below 2 commands:
# ipadm delete-ip net0
# ipadm create-ip net0
*then
# ipadm create-addr -T static -a 192.168.10.2/24 net0/v4
[Configure an interface with DHCP:
# ipadm delete-addr net0
# ipadm create-addr -T dhcp net0/v4
Manually Configuring the Default Route for a System:
route -p add default <ip-address>
As an old Sun/Oracle upload file method has been discontinued, below are the several method on how to upload files to Oracle Support based on file size.
Diagnostic Assistant (DA)
DA 2.2 (included w/RDA/Explorer/STB 8.02) now supports uploads via https to MOS File Upload Service. Use DA via menus,explorer or the command line.
Menu
To use DA do a command line upload:
da.sh upload -p sr=<SR Number>file=path=<path to file>
To use DA to upload with explorer
explorer -w default -T DA -SR <Service Request number>
NOTE: If SR Number is not specified, the file will be uploaded to transport.oracle.com/upload/proactive/
# /opt/SUNWsasm/bin/sasm transport -r
Enter “1” to select:
1) transport.oracle.com
Or, enter:
https://tranport.oracle.com
—
*Reference: Doc ID 1547088.2 and Doc ID 1596914.1
Did your Solaris OS suddenly crashed, hang and rebooted by it self for no reason? After initial checking no amber light found on or HW faulty on the server ? its time to check the crash dump log file.
If your system properly installed and configured, the moment system crash, it will save all data on the memory to specific file so call crash dump log file. Check your dump log file location with “dumpadm” command. Usually, its located at: /var/crash/<server_hostname>/, file name: vmdump.0
What we need to do is to read and analyze this most important file. Unfortunately, this dump log file can’t be read manually, its required special package: SUNWscat – Oracle Solaris Crash Analysis Tool.
Download and install SUNWscat – Solaris Crash Analyzer Tool
The latest version Oracle Solaris Crash Analysis Tool is version 5.5, this patches are available on MOS, and can be found by searching on the patchIDs 21099218 (Combined package supporting SPARC and X86/X64) and 21099215 (platform specific packages).
Go to MOS: https://support.oracle.com and login, Click on tab entitled Patches and Updates at top, Enter 21099218 and 21099215 for patch numbers.
————
[Install the package:
root@solaris10 # ls
p21099218_55000_Generic.zip
root@solaris10 # unzip p21099218_55000_Generic.zip
Archive: p21099218_55000_Generic.zip
inflating: Readme.txt
inflating: SUNWscat5.5-GA-combined.pkg.gz
root@solaris10 #
root@solaris10 # gunzip SUNWscat5.5-GA-combined.pkg.gz
root@solaris10 #
root@solaris10 # ls
Readme.txt SUNWscat5.5-GA-combined.pkg p21099218_55000_Generic.zip
root@solaris10 # pkgadd -d SUNWscat5.5-GA-combined.pkg
The following packages are available:
1 SUNWscat Oracle Solaris Crash Analysis Tool (5.5 GA)
(any) 5.5
Select package(s) you wish to process (or ‘all’ to process
all packages). (default: all) [?,??,q]: all
Processing package instance <SUNWscat> from </export/home/SCAT/SUNWscat5.5-GA-combined.pkg>
….
….
Installation of <SUNWscat> was successful.
[decompress the crash dump log file:
root@solaris10 # savecore -vf vmdump.0
savecore: System dump time: Mon Aug 10 05:43:52 2015
savecore: saving system crash dump in /opt/crash/solaris10/{unix,vmcore}.0
Constructing namelist /opt/crash/solaris10/unix.0
Constructing corefile /opt/crash/solaris10/vmcore.0
1:15 100% done: 341483 of 341483 pages saved
48444 (14%) zero pages were not written
1:16 dump decompress is done
root@solaris10 #
[Let start analyze the log:
root@solaris10 # cd /opt/crash/solaris10/
root@solaris10 # /opt/SUNWscat/bin/scat vmcore.0
Oracle Solaris Crash Analysis Tool
Version 5.5 for Oracle Solaris 10 64-bit UltraSPARC
Copyright (c) 1989, 2015, Oracle and/or its affiliates. All rights reserved.
Please note: Do not submit any health, payment card or other sensitive
production data that requires protections greater than those specified in
the Oracle GCS Security Practices. Information on how to remove data from
your submission is available at:
https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1227943.1
For support, please use the Oracle Solaris kernel community at
https://community.oracle.com/community/support/oracle_sun_technologies/
Select “Subspaces” and then “Oracle Solaris Performance, Panics,
Hangs, and Dtrace”.
Further information may be found at https://blogs.oracle.com/SolarisCAT/
opening unix.0 vmcore.0 …dumphdr…symtab…maps…done
loading crashdump data: modules…CTF…globals…done
crash file: /opt/crash/solaris10/vmcore.0
user: Super-User (root:0)
release: 5.10 (64-bit)
version: Generic_144488-06
machine: sun4v
node name: XXXX
domain: default.solaris10.com
hw_provider: Sun_Microsystems
system type: SUNW,Netra-T5440 (UltraSPARC-T2+)
hostid: XXXXXXXX
…
…
disks…done
[run ‘analyze’:
CAT(vmcore.0/10V)> analyze
crash file: /opt/crash/solaris10/vmcore.0
user: Super-User (root:0)
release: 5.10 (64-bit)
version: Generic_144488-06
machine: sun4v
node name: XXX
domain: default.server.com
hw_provider: Sun_Microsystems
system type: SUNW,Netra-T5440 (UltraSPARC-T2+)
hostid: xxxxxxxx
dump_conflags: 0x10000 (DUMP_KERNEL) on /dev/dsk/c1t0d0s1(8G)
time of crash: Mon Aug 10 05:43:01 WIT 2015
age of system: 37 days 19 hours 54 minutes 4 seconds
panic CPU: 96 (96 CPUs, 15.7G memory, 2 nodes)
panic string: xt_sync: timeout
==== panic thread: 0x300c2653200 ==== CPU: 96 ====
==== panic user (LWP_SYS) thread: 0x300c2653200 PID: 22900 on CPU: 96 ====
cmd: /bin/sh /opt/scripts/xxxxxxx Called from script ‘/opt/scrips’ >>>>THE ROOT CAUSE OF CRASH/HUNG
t_procp: 0x60024f870b0
p_as: 0x6003a631c18 size: 1769472 RSS: 1482752
….
— switch to user thread’s user stack —
——————-
‘analyze’ is just one of initial investigation command, type help for other commands:
CAT(vmcore.0/10V)> help
CAT(vmcore.0/10V)>
I think it’s not too late to play with Redhat Enterprise Server :-). Need a kind of a distraction from Solaris, and other Ora** HW/SW product.. hahaha.
I just install RHEL version 6.4. trying to use yum command to install rpm-build package, but it showing below error messages:
[root@redhat64 ~]# yum install rpm-build Loaded plugins: product-id, security, subscription-manager This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. Setting up Install Process No package rpm-build available. Error: Nothing to do
By default, if you check with “yum repolist all” command, there are 2 repo source with status disabled:
[root@redhat64 ~]# yum repolist all Loaded plugins: product-id, security, subscription-manager This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. repo id repo name status rhel-source Red Hat Enterprise Linux 6Server - x86_64 - Source disabled rhel-source-beta Red Hat Enterprise Linux 6Server Beta - x86_64 - Source disabled repolist: 0 [root@redhat64 ~]#
Check the Redhat repository configuration file, there are two repo name, both are pointed to redhat website:
[root@redhat64 ~]# cd /etc/yum.repos.d/ [root@redhat64 yum.repos.d]# ls rhel-source.repo [root@redhat64 yum.repos.d]# more rhel-source.repo [rhel-source] name=Red Hat Enterprise Linux $releasever - $basearch - Source baseurl=ftp://ftp.redhat.com/pub/redhat/linux/enterprise/$releasever/en/os/SRPMS/ enabled=0 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release [rhel-source-beta] name=Red Hat Enterprise Linux $releasever Beta - $basearch - Source baseurl=ftp://ftp.redhat.com/pub/redhat/linux/beta/$releasever/en/os/SRPMS/ enabled=0 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-beta,file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release [root@redhat64 yum.repos.d]#
We need to register to RHN in order to use those repo source, even you try to enable the repo, by editing the line “enable=0” to “enable=1” but it won’t work. The easy way is build a local repository from your current redhat’s DVD / ISO file:
# mkdir /cdrom
# mount /dev/cdrom /cdrom
Rename existing repo file “rhel-source.repo” to “rhel-source.repo.backup” or whatever you want.
Create another repo file name, example “dvd.repo”:
# vi dvd.repo
[dvd-source]
name=RHEL 6.4 dvd repo
baseurl=file:///cdrom/Server
enabled=1
gpgcheck=0
Check your repo config, Test and try to install the package:
# yum repolist
# yum install rpm-build
[root@redhat64 yum.repos.d]# yum repolist
Loaded plugins: product-id, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
repo id repo name status
dvd-source RHEL 6.4 dvd repo 3,648
repolist: 3,648
[root@redhat64 yum.repos.d]# yum install rpm-build
Loaded plugins: product-id, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
dvd-source | 3.9 kB 00:00 ...
dvd-source/primary_db | 3.1 MB 00:00 ...
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package rpm-build.x86_64 0:4.8.0-32.el6 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
=========================================================================================================================
Package Arch Version Repository Size
=========================================================================================================================
Installing:
rpm-build x86_64 4.8.0-32.el6 dvd-source 126 k
Transaction Summary
=========================================================================================================================
Install 1 Package(s)
Total download size: 126 k
Installed size: 315 k
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Warning: RPMDB altered outside of yum.
Installing : rpm-build-4.8.0-32.el6.x86_64 [ ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [#### ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [##### ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [###### ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [####### ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [######## ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [################# ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [######################### ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [############################### ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [################################# ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [################################### ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [#################################### ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [######################################### ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [########################################## ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [########################################### ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [############################################ ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [############################################## ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [################################################ ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [################################################# ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [######################################################## ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [######################################################### ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [########################################################## ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [################################################################ ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [################################################################## ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [################################################################### ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 [#################################################################### ] 1/1
Installing : rpm-build-4.8.0-32.el6.x86_64 1/1
dvd-source/productid | 1.7 kB 00:00 ...
Verifying : rpm-build-4.8.0-32.el6.x86_64 1/1
Installed:
rpm-build.x86_64 0:4.8.0-32.el6
Complete!
[root@redhat64 yum.repos.d]#
##################
We can also build a local http or ftp repository server, will talk later on another post.
SAIFUL AZIZ's BLOG 