My Oracle Support Banner

Up2date Fails With "Connection Timed Out On Readline" Error (Doc ID 1276763.1)

Last updated on AUGUST 04, 2018

Applies to:

Linux OS - Version: 2.6.18-92.el5 and later   [Release: RHEL5U2 and later ]
Information in this document applies to any platform.

Symptoms

If run "up2date --dry-run -uf" on one of the server, it fails with "Connection timed out on readline" error,
the "/var/log/up2date" display following error message:
[Mon Dec 20 12:11:52 2010] up2date solving dep for: ['dnsmasq', 'libdbus-1.so.3()(64bit)', 
'libdbus-1.so.3()(64bit)', 'libdbus-1.so.3()(64bit)', 'e4fsprogs', 'libdbus-1.so.3',
...
'libdbus-1.so.3()(64bit)', 'xorg-x11-drv-qxl', 'libdbus-1.so.3', 'libdbus-1.so.3()(64bit)',
'libnotify-devel', 'libdbus-1.so.3()(64bit)']
[Mon Dec 20 12:12:58 2010] up2date A socket error occurred: Timeout Exception, attempt #2
[Mon Dec 20 12:13:34 2010] up2date A socket error occurred: Timeout Exception, attempt #3
[Mon Dec 20 12:14:09 2010] up2date A socket error occurred: Timeout Exception, attempt #4
[Mon Dec 20 12:14:45 2010] up2date A socket error occurred: Timeout Exception, attempt #5

Changes

N/A

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
  Symptoms
  Changes
  Cause
  Solution
  References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.