Search

Language:  
Search for:

Available article translations:

Commands to operate with VMs or list VMs end with connection timeout

APPLIES TO:
  • Parallels Server

Symptoms

Any command related to Parallels Server fails wrong response or with connection timeout like in the output below:

~# prlctl list
Login failed: Unable to connect to the server "localhost". An invalid response has been received from the server. Make sure that Parallels Server is running on the server "localhost" and is up to date and try again.

In the log file /var/log/parallels.log the following messages might appear:

08-19 11:05:03.864 F /disp:2061:c7fff700/ Task '32Task_AuthUserWithGuestSecurityDb' with uuid = {2ec2b64f-f481-4b65-ba9e-234e7af6955f} was started. Flags = 0
08-19 11:09:36.200 F /cmn_utils:550310:37340760/ ParallelsDirs::Init( ) was called. Current app mode = 0 ( SERVER ) build version: 5.0.13392.803029 Wed, 26 Sep 2012 16:57:17
08-19 11:10:36.302 F /IOCommunication:550310:22ae4700/ IO client ctx [read thr] (sender 3): Wait for read failed: timeout expired!
08-19 11:10:36.302 F /IOCommunication:550310:22ae4700/ IO client ctx [read thr] (sender 3): Handshake error: protocol version read failed!
08-19 11:10:36.302 F /IOCommunication:550310:22ae4700/ IO client ctx [read thr] (sender 3): Handshake failed!
08-19 11:10:36.302 F /sdk:550310:22eea700/ Can't connect to dispatcher!
08-19 11:10:36.305 F /sdk:550310:37340760/ PrEvtPrm_ToHandle(): unsupported event parameter with name 'vm_message_param_0'
08-19 11:22:42.055 F /cmn_utils:551201:ebb62760/ ParallelsDirs::Init( ) was called. Current app mode = 0 ( SERVER ) build version: 5.0.13392.803029 Wed, 26 Sep 2012 16:57:17
08-19 11:23:42.149 F /IOCommunication:551201:e55c1700/ IO client ctx [read thr] (sender 3): Wait for read failed: timeout expired!
08-19 11:23:42.149 F /IOCommunication:551201:e55c1700/ IO client ctx [read thr] (sender 3): Handshake error: protocol version read failed!
08-19 11:23:42.149 F /IOCommunication:551201:e55c1700/ IO client ctx [read thr] (sender 3): Handshake failed!
08-19 11:23:42.149 F /sdk:551201:e59ce700/ Can't connect to dispatcher!
08-19 11:25:24.806 F /cmn_utils:551401:ee30e760/ ParallelsDirs::Init( ) was called. Current app mode = 0 ( SERVER ) build version: 5.0.13392.803029 Wed, 26 Sep 2012 16:57:17

Cause

The process of Dispatcher does not respond to new requests due to all handles being used by the process.

Resolution

As the quick fix, forcibly terminate the process and start the service back.

~# killall -9 prl_disp_service
~# service parallels-server start

To prevent the issue, update the installation of Parallels Server and reboot the system to the latest kernel.

~# vzup2date -m batch install --core --tools --self-update --loader-autoconfig

And schedule the server's reboot to the appropriate maintenance window.

Search words:

An invalid response has been received from the server

Login failed




ca05eaf5b843fbd53589c90d7228a6df 2897d76d56d2010f4e3a28f864d69223

FEEDBACK
Was this article helpful?
Tell us how we may improve it.
Yes No
 
 
 
 
 
 
Desktop Virtualization
- Parallels Desktop 9 for Mac
- Parallels Transporter
- Parallels Desktop Switch to Mac Edition
- Parallels Desktop for Mac Enterprise Edition
- Parallels Management-Mac for Microsoft SCCM
Server Virtualization
- Parallels Cloud Server
- Parallels Containers for Windows 6.0 Beta
- Parallels Virtuozzo Containers
Automation
- Parallels Automation
- Parallels Automation for Cloud Infrastructure
- Parallels Business Automation Standard
- Parallels Virtual Automation
- Parallels Plesk Panel Suite
- Web Presence Builder
- Parallels Plesk Automation
- Parallels Small Business Panel
- Value-added Services for Hosters
- Parallels Partner Storefront
Services & Resources
- Cloud Acceleration Services
- Professional Services
- Support Services
- Training & Certification