Sponsored Content
Operating Systems Solaris Error: prtdiag failed! property not found Post 302413239 by mpics66 on Thursday 15th of April 2010 03:43:56 AM
Old 04-15-2010
I don't have a proper solution to your problem, but i have faced issues where prtdiag gets stuck while running on T5220 box, sun recomended OBP upgrade & the issue got fixed, if possible try OBP upgrade, though this is not an exact way of resolving issues. This could save time in case of emergency.

I hope some one else will also post some other solution, so that we both can learn.

Thanks.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Question on prtdiag output ...

Hello all , This is the output of my prtdiag command ...The speed of each of the CPUs is listed below (1281 MHz ) ..That's fine ..I'm confused about the (System clock frequency: 183 MHZ ) ..What is the difference between System Clock freq and CPU freq ...THanks.. System Configuration: Sun... (5 Replies)
Discussion started by: luft
5 Replies

2. Solaris

prtdiag and memory banks

hi, we have an e6900 and my sys admin says that the number of processors and memory were reduced to 4 and 8GB. However, a prtdiag |grep Memory returns 16GB of memory. So what is my system's memory? psrinfo returns 4 online and 4 offline CPUs. Thanks. Kumar (1 Reply)
Discussion started by: kumar27
1 Replies

3. Shell Programming and Scripting

source a property file in script give error

I have sourced a property file in my script like this to load some variables in the script Then i am able to echo all the property file values inside script but the script is not able to recognize other unix commands #!/bin/bash . build.properties mkdir build i am getting error ... (3 Replies)
Discussion started by: codeman007
3 Replies

4. Solaris

prtdiag - Segmentation Fault

Hi, Recently installed a Firmware patch on T5120 (solaris 10,138888-03). The patch installation was Success and system came up fine as well. My apps are running fine too. Problem is prtdiag does not work as it used to earlier. the output is very different from other t5120s I have and... (1 Reply)
Discussion started by: upengan78
1 Replies

5. Programming

Eclipse C - Launch Failed. Binary Not found

Hi guys. I installed eclipse now and run "Hello World" program in C. but it gives me Launch Failed. Binary Not foundi searched in forums that say: set proper binary parser. mine is set to GNU Elf parser. could anyone help? My eclipse version is: Version: 3.6.1 Build id:... (0 Replies)
Discussion started by: majid.merkava
0 Replies

6. Solaris

Cygwin X Server error: xdmcp fatal error session failed session 23 failed for display

Hi, i got the following error when i tried to access the cygwin x server from a windows XP PC. "xdmcp fatal error session failed session 23 failed for display" Alternatively, when i tried to access the same Cygwin X Server from another windows XP PC which is on a different LAN... (3 Replies)
Discussion started by: HarishKumarM
3 Replies

7. Shell Programming and Scripting

Report a missing property and property value mis match script.

Hi All, I have 2 properties files - one is a master templete and other one is a node specific properties file, I need to comapre these 2 properties files and make sure the node Specific properties file contains all the properties in the master temple properties file else report the missing... (5 Replies)
Discussion started by: jayka
5 Replies

8. Solaris

prtdiag

Hi everyone, Please can you tell me what kind of memro we are talking about when we run : prtdiag -v Memory size: 98016 Megabytes Thank you (7 Replies)
Discussion started by: adilyos
7 Replies

9. Solaris

prtdiag -v troubleshooting

selected lines from the output of the "prtdiag -v" command on a T5240 SUN server running Solaris 10. Are the following known as FRU names and what do they mean? MB/CMP0/BR0/CH0/D0 MB/CMP0/BR0/CH1/D0 SYS/FANBD0/FM0/F0 SYS/FANBD0/FM0/F1 SYS/MB/CMP0/BR1/CH0/D1 ... (1 Reply)
Discussion started by: snoman1
1 Replies

10. Solaris

Rpcinfo: can't contact portmapper: RPC: Authentication error; why = Failed (unspecified error)

I have two servers with a fresh install of Solaris 11, and having problems when doing rpcinfo between them. There is no firewall involved, so everything should theoretically be getting through. Does anyone have any ideas? I did a lot of Google searches, and haven't found a working solution yet. ... (2 Replies)
Discussion started by: christr
2 Replies
DH_SYSTEMD_START(1)						     Debhelper						       DH_SYSTEMD_START(1)

NAME
       dh_systemd_start - start/stop/restart systemd unit files

SYNOPSIS
       dh_systemd_start [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [unitfile...]

DESCRIPTION
       dh_systemd_start is a debhelper program that is responsible for starting/stopping or restarting systemd unit files in case no corresponding
       sysv init script is available.

       As with dh_installinit, the unit file is stopped before upgrades and started afterwards (unless --restart-after-upgrade is specified, in
       which case it will only be restarted after the upgrade).  This logic is not used when there is a corresponding SysV init script because
       invoke-rc.d performs the stop/start/restart in that case.

OPTIONS
       --restart-after-upgrade
	   Do not stop the unit file until after the package upgrade has been completed.  This is the default behaviour in compat 10.

	   In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst.

	   This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
	   will not get confused by the package being upgraded while it's running before using this option.

       --no-restart-after-upgrade
	   Undo a previous --restart-after-upgrade (or the default of compat 10).  If no other options are given, this will cause the service to
	   be stopped in the prerm script and started again in the postinst script.

       -r, --no-stop-on-upgrade, --no-restart-on-upgrade
	   Do not stop service on upgrade.

       --no-start
	   Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a
	   corresponding init script).

NOTES
       Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments).
       Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts.

       Note that dh_systemd_start should be run after dh_installinit so that it can detect corresponding SysV init scripts. The default sequence
       in dh does the right thing, this note is only relevant when you are calling dh_systemd_start manually.

SEE ALSO
       debhelper(7)

AUTHORS
       pkg-systemd-maintainers@lists.alioth.debian.org

11.1.6ubuntu2							    2018-05-10						       DH_SYSTEMD_START(1)
All times are GMT -4. The time now is 09:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy