Sponsored Content
Operating Systems Linux SuSE Server hung with firmware error Post 302613799 by hedkandi on Wednesday 28th of March 2012 05:23:45 AM
Old 03-28-2012
A little help here?

---------- Post updated at 05:23 PM ---------- Previous update was at 10:37 AM ----------

Please close this thread

If someone comes across this thread, this is the problem

1. Firmware does not recognize the HW i.e CPU and Motherboard may not be fully compatible with each other

The solution

1. Upgrade your BIOS software to the latest version available, this usually solves this problem. Check with your HW vendor for this

To check Bios firmware version,
Code:
dmidecode -s bios-version

Smilie
 

10 More Discussions You Might Find Interesting

1. IP Networking

system hung

I installed sco unix v 5.0.5 in the hp server lc 2000 HD size 27gb & ram 256 , used micro focus cobol for unix , aplication system bank , the problem is the system hung 2 or 3 times a day will you pls. give me the solution. thanks talib alsaadi :( (2 Replies)
Discussion started by: talib alsaadi
2 Replies

2. HP-UX

Server hung

So my server was hung when I came in this morning. It was responding to pings, but the console and telnet sessions would not respond. There was no disk activity. The display said FA1F which I discovered that the "A" represents a high CPU load. I tired several things to get it going but was forced... (6 Replies)
Discussion started by: biznatch
6 Replies

3. HP-UX

Hung Port

Here's a difficult one for you. I am on HPUX 11.0. I have a hung port, it is stuck in FIN_WAIT_2. Short of rebooting, how can I terminate the connection the system thinks still exists? I found a script online that uses adb but have not been able to get it to work. I am still open to using... (6 Replies)
Discussion started by: TioTony
6 Replies

4. UNIX for Advanced & Expert Users

close_wait connections causing a server to hung

Hi Guys, Just wondering if anyone of you have been in a situation where you end up having around 100 close_wait connections and seems to me those connections are locking up resources/processes in the server so unless the server is rebooted those processes won't be released by the close_wait... (3 Replies)
Discussion started by: hariza
3 Replies

5. Solaris

Error while upgrading firmware on X4500.

I get an error message when I try to upgrade the firmware. The error message is displayed below. Image has no uboot. DO NOT RESET OR YOU WILL BRICK THE ILOM. Please retry with the correct image I do not understand anything about this message. May I know what does it mean ? How can I get rid... (6 Replies)
Discussion started by: bharu_sri
6 Replies

6. Solaris

Error updating Firmware in X4500

I have X4500 machine with solaris 10 OS and software version 5.10. The firmware version is 1.1.1 and I am planning to upgrade the firmware. C H A P T E R 1 - Flash Upgrading Your Server to Software Release 1.2 I referred to the above link to do so. But, I do not understand what is the... (6 Replies)
Discussion started by: bharu_sri
6 Replies

7. HP-UX

ssh session getting hung (smilar to hpux telnet session is getting hung after about 15 minutes)

Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also? (1 Reply)
Discussion started by: yoda9691
1 Replies

8. AIX

Platform Firmware Unrecovered Error

this error is appear in my server . please can anyone help me with it . IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION BFE4C025 0323100711 P H sysplanar0 UNDETERMINED ERROR BFE4C025 0323100611 P H sysplanar0 UNDETERMINED ERROR BFE4C025 0323090711 P H sysplanar0 ... (4 Replies)
Discussion started by: thecobra151
4 Replies

9. Linux

Server hung, is this a stack trace?

Hi everyone, Our Red Hat server hung yesterday, and I managed to log into the console and see the following message: RIP: 0010: mwait_idle_with_hints+0x66/ 0x67 RSP: 0018:ffffffff80457f40 EFLAGS: 00000046 RAX: 0000000000000010 RBX: ffff810c20075910 RCX: 0000000000000001 RDX:... (6 Replies)
Discussion started by: badoshi
6 Replies

10. Infrastructure Monitoring

Can HPOV monitor server hung state ?

Hi, We have Solaris-10 running on VMware (x86). It is being monitored by HP Openview. Sometimes when this server hungs, while ping still works, HPOpenview can't alert that server is down (which is actually unresponsive). First symptom we see is, login failure. It will ask user name and after... (7 Replies)
Discussion started by: solaris_1977
7 Replies
asmigrate(1m)						    Application Server Utility						     asmigrate(1m)

NAME
asmigrate - automates migration of J2EE applications from other J2EE platforms to Sun Java System Application Server SYNOPSIS
asmigrate [-h | --help] [-v | --version] [(-c |--commandline) | (-u --ui) ] [-q | --quiet] [-d | --debug][-s | --sourcedirectory source_directory] [-S | --sourceserver source_application_server] [-t | --targetdirectory target_directory] [-T | --targetserver tar- get_application_server] [-n | --scan-native-apis-only ] [-p | --scan-packages package_list] [-j | --java2db create-tables=true, drop- tables=true, db-vendor-name=dbVendorName] [-m | --migrate-cmp comment-pk-modifiers=true, overwrite-conflicting-accessors=true] [-f | --file-filter all-files=true, html-files=true, java-files=true, jsp-files=true, xml-files=true, archive-files=true] [-a | --append-logs ][operands] Use the asmigrate utility to analyze your J2EE application and translate vendor specific settings to Sun JavaTMTM System Application Server specific settings making the application deployable on Sun's J2EE products. The following table identifies the supported J2EE product migrations: +--------------------------+--------------------------------+ | Source J2EE Platform | Destination J2EE Platform | +--------------------------+--------------------------------+ |WebSphere Application |Sun ONE Application Server 6.5 | |Server 4.0 | | | | | |WebLogic Application | | |Server 5.1 | | +--------------------------+--------------------------------+ |WebLogic Application |Sun ONE Application Server 7 | |Server 5.1, 6.0, 6.1 | | | | | |WebSphere Application | | |Server 4.0 | | | | | |JavaTMTM 2 Platform | | |Enterprise Edition 1.3 | | | | | |Sun ONE Application | | |Server 6.x | | | | | |Sun ONE Web Server 6.0 | | | | | |JBoss Application Server | | |3.0 | | | | | |Tomcat Web Server 4.1.12 | | +--------------------------+--------------------------------+ |WebLogic Application |JavaTMTM 2 Platform, Enterprise | |Server 5.1, 6.0, 6.1 |Edition 1.4 Application Server | | | | |WebSphere Application | | |Server 4.0 | | | | | |JavaTMTM 2 Platform | | |Enterprise Edition | | |1.3/1.4 | | | | | |Sun ONE Application | | |Server 6.x | | | | | |Sun ONE Web Server 6.0 | | | | | |JBoss Application Server | | |3.0 | | | | | |Tomcat Web Server 4.1.12 | | +--------------------------+--------------------------------+ |WebLogic Application |Sun JavaTMTM System Application | |Server 5.1, 6.0, 6.1 |Server Platform Edition 8 | | | | |WebSphere Application | | |Server 4.0 | | | | | |JavTMTMa 2 Platform | | |Enterprise Edition | | |1.3/1.4 | | | | | |Sun ONE Application | | |Server 6.x | | | | | |Sun ONE Web Server 6.0 | | | | | |JBoss Application Server | | |3.0 | | | | | |JBoss Application Server | | |3.2 | | | | | |Tomcat Web Server 4.1.12 | | +--------------------------+--------------------------------+ OPTIONS
-h --help displays the arguments for launching the MigrationTool. -v --version displays the version of the MigrationTool. -u --ui invokes the tool in user interface mode. -c --commandline invokes the tool in command-line mode. -q --quiet launches the tool in quiet mode. -d --debug launches the tool in debug mode. -s --sourcedirectory identifes the directory where the source code to migrate or scan is present. -S --sourceserver identifes the source application server of the applications to be migrated. Possible servers include: o wl51: WebLogic Application Server 5.1 o wl60: WebLogic Application Server 6.0 o wl61: WebLogic Application Server 6.1 o as65: Sun ONE Application Server 6.5 o as70: Sun ONE Application Server 7.0 o ws40: WebSphere Application Server 4.0 o ri13: JavaTMTM 2 Platform Enterprise Edition 1.3 o ri14: JavaTMTM 2 Platform Enterprise Edition 1.3 o s1ws: Sun ONE Web Server o jb30: JBoss Application Server 3.0 o tc41: Tomcat Application Server 4.1 -t --targetdirectory target or output directory where the migrated application should be placed. -T --targetserver target application server to which the application is to be migrated. -n --scan-native-apis-onlscans the source code only for the presence of application server specific proprietary APIs. -p --scan-packages comma-separated list of Java packages to scan. -j --java2db bypasses the creation of the sun-cmp-mapping.xml file. Instead, introduces the option argument into the sun-ejb- jar.xml file. Option arguments are: o create-tables: if set to true (default), creates tables at deploy. If set to false tables are not created. o drop-tables: if set to true (default), tables are dropped at undeploy. If set to false tables are not dropped. o db-vendor-name: name of the database vendor for the application to be migrated. Supported vendor names include: Oracle, Sybase, DB2, Generic SQL92, PointBase, MSSQL. -m --migrate-cmp migrates 1.1 compliant CMPs, if any, to 2.0. Option arguments are: o overwrite-conflicting-accessors: if set to true (default), conflicting accessors are overwritten. If set to false, conflicting accessors are not overwritten. o comment-pk-modifiers: if set to true (default), setters of primary key are commented. If set to false, setters of primary key are not commented. -f --file-filter selects the type of files to migrate. Option arguments are: o all-files: if specified and set to true (default), migrates all types of files. o html-files: if specified and set to true (default), migrates HTML files. o java-files: if specified and set to true (default), migrates Java files. o jsp-files: if specified and set to true (default), migrates JSP type files. o archive-files: if specified and set to true (default), migrates jar/ear/war/rar file types. -a --append-logs if specified, appends the logging to the existing or previous logs without overwriting them. If not specified, previous logs are overwritten. operands identifes the archive file (jar/ear/war/rar) to be migrated. SEE ALSO
asupgrade(1M) J2EE 1.4 SDK March 2004 asmigrate(1m)
All times are GMT -4. The time now is 06:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy