04-16-2012
Thanks to all for your valueable input.
I am facing the issue of No Connection in HMC, Two Physical Servers are connected in HMC.
Servers are up and LPAR are running fine.
but I am getting NO Connection in HMC for Managed Systems.
I have checked the cables ,cables are connected properly.
How to troubleshoot the issue?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
When I do a hard reboot, the system recognizes both the ttya and the ttyb, but when I do a hard reboot, it only doesn't recognize the ttyb. Is there a way I can fix this???
Thanks!:confused: (5 Replies)
Discussion started by: nattie_h
5 Replies
2. UNIX for Advanced & Expert Users
Hi !
I am working on a server. We have ABAQUS installed on it. I added a compiler to .env file and added usr/local...../IMSL/... to the path.
Then i restarted the computer and I get this error:
when I am doing interactive option (Red hat Lunix OS)
Start service local Yes/no/Continue? no... (1 Reply)
Discussion started by: dsmv
1 Replies
3. UNIX for Dummies Questions & Answers
O/P of the uname -a
Server Server 4.0 3.0 3516 Pentium IV(TM)-ISA/PCI
Server is getting rebooted frequetly...
I don't know what is the problem in server ...
Any help why the server is getting rebooted frequetly.
Can i check what is the problem like in log files (5 Replies)
Discussion started by: srikanthus2002
5 Replies
4. Solaris
while installing unix solaris I found that one of the CD's is corupted so I bring another copy of solaris CD's and type reboot instead of 'reboot cdrom' then the server goes in infinite loop of rebooting resetting??I tried to use ctrl+break but didnt work....how can I break this loop....plz help?? (4 Replies)
Discussion started by: mm00123
4 Replies
5. Shell Programming and Scripting
Hi All,
I have created one script with starting letter 'S' (Example: Start) and stored in the path "/etc/rc.d/".
This script was called automatically when we reboot the server.
In this script i am using 'su' command to switch other user but it is not working, it giving some error.
su... (2 Replies)
Discussion started by: Selva_Kumar
2 Replies
6. Linux
Hi All,
We have two servers DSERV1(red hat 8.0) and DSERV2(scounix 3.2) where DSERV1 is the NFS server and DSERV2 is the NFS client. We want to reboot these servers and wanted to know the steps(precautions) we have to follow in order to do this. After reboot should we do anything specific to... (2 Replies)
Discussion started by: jisha
2 Replies
7. AIX
Anyone faced this?
I rebooted the HMC through command line after patch installation (hmcshutdown -t now -r)
The strange thing happened was the hmc never rebooted, I was not able to connect it through graphical view or through ssh, but the session through which i issued the command was still... (4 Replies)
Discussion started by: balaji_prk
4 Replies
8. Solaris
I got following while whenver i reboot my box
WARNING: add_spec: No major number for hpfc
WARNING: add_spec: No major number for hpfc
Error: Unable to init open counts. Kernel struct change?
and hpfc is related to agilent fiber channel driver .. i do not know why it requires as i 've... (1 Reply)
Discussion started by: fugitive
1 Replies
9. Red Hat
hi,
I have been working on Solaris am very new to linux. My concern is as it goes....our server is getting rebooted automatically and I am not able to understand anything from the var log messages. Could anybody help me out in troubleshooting the issue.
2.6.18-128.el5 #1 x86_64 GNU/Linux is... (1 Reply)
Discussion started by: EmbedUX
1 Replies
10. What is on Your Mind?
Apologies if this is not the correct place to post this.
I used to have a job supporting several custom applications that ran on Unix platforms. I used shell scripting, sed, awk, and SQL, but all on a pretty basic level. I also performed non-technical tasks like helping with project management,... (4 Replies)
Discussion started by: intranslation
4 Replies
LEARN ABOUT DEBIAN
poe::component::client::mpd::connection
POE::Component::Client::MPD::Connection(3pm) User Contributed Perl Documentation POE::Component::Client::MPD::Connection(3pm)
NAME
POE::Component::Client::MPD::Connection - module handling the tcp connection with mpd
VERSION
version 1.121670
DESCRIPTION
This module will spawn a poe session responsible for low-level communication with mpd. It is written as a POE::Component::Client::TCP,
which is taking care of everything needed.
Note that you're not supposed to use this class directly: it's one of the helper class for POE::Component::Client::MPD.
ATTRIBUTES
host
The hostname of the mpd server. Mandatory, no default.
port
The port of the mpd server. Mandatory, no default.
id
The POE session id of the peer to dialog with. Mandatory, no default.
max_retries
How much time to attempt reconnection before giving up. Defaults to 5.
retry_wait
How much time to wait (in seconds) before attempting socket reconnection. Defaults to 2.
METHODS
my $id = POE::Component::Client::MPD::Connection->spawn( \%params );
This method will create a POE::Component::Client::TCP session responsible for low-level communication with mpd.
It will return the poe id of the session newly created.
PUBLIC EVENTS ACCEPTED
disconnect( )
Request the pococm-connection to be shutdown. This does not shut down the MPD server. No argument.
send( $message )
Request pococm-conn to send the $message over the wires. Note that this request is a POE::Component::Client::MPD::Message object properly
filled up, and that the "_commands()" attribute should not be newline terminated.
PUBLIC EVENTS FIRED
The following events are fired from the spawned session.
mpd_connected( $version )
Fired when the session is connected to a mpd server. This event isn't fired when the socket connection takes place, but when the session
has checked that remote peer is a real mpd server. $version is the advertised mpd server version.
mpd_connect_error_fatal( $errstr )
Fired when the session encounters a fatal error. This happens either when the session is connected to a server which happens to be
something else than a mpd server, or if there was more than "max_retries" (see "spawn()" params) connection retries in a row. $errstr will
contain the problem encountered. No retries will be done.
mpd_connect_error_retriable( $errstr )
Fired when the session has troubles connecting to the server. $errstr will point the faulty syscall that failed. Re-connection will be
tried after $retry_wait seconds (see "spawn()" params).
mpd_data( $msg )
Fired when $msg has been sent over the wires, and mpd server has answered with success. The actual output should be looked up in
"$msg-"_data>.
mpd_disconnected( )
Fired when the socket has been disconnected for whatever reason. Note that this event is not fired in the case of a programmed shutdown
(see "disconnect()" event above). A reconnection will be automatically re-tried after $retry_wait (see "spawn()" params).
mpd_error( $msg, $errstr )
Fired when $msg has been sent over the wires, and mpd server has answered with the error message $errstr.
AUTHOR
Jerome Quelin
COPYRIGHT AND LICENSE
This software is copyright (c) 2007 by Jerome Quelin.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.
perl v5.14.2 2012-06-15 POE::Component::Client::MPD::Connection(3pm)