package ntp 1:4.2.6.p2+dfsg-1ubuntu5 failed to install/upgrade: error writing <standard output>: No such file or directory

Bug #767450 reported by Qfito
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ntp (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: ntp

installing lubuntu-desktop package

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: ntp 1:4.2.6.p2+dfsg-1ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Wed Apr 20 13:20:55 2011
ErrorMessage: error al escribir en `<salida estándar>': No existe el fichero o el directorio
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
NtpStatus:
 remote refid st t when poll reach delay offset jitter
 ==============================================================================
  cronos.uanl.mx 69.164.213.205 4 u 27 64 7 39.004 -13.059 55.619
  dsl-201-120-53- .GPS. 1 u 26 64 7 40.815 -20.561 55.370
  europium.canoni 193.79.237.14 2 u 27 64 7 167.226 -4.748 49.943
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=d50f4160-ad46-43ad-98d8-148448b762f6 ro quiet splash vt.handoff=7
ProcVersionSignature_: Ubuntu 2.6.38-8.42-generic 2.6.38.2
SourcePackage: ntp
Title: package ntp 1:4.2.6.p2+dfsg-1ubuntu5 failed to install/upgrade: error al escribir en `<salida estándar>': No existe el fichero o el directorio
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Qfito (gary-mayet) wrote :
Revision history for this message
James Page (james-page) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Unfortunately there is not much information to help diagnose what went wrong in the attached logs.

Please could you run the following commands in a terminal and attach the output of each to this bug report:

 apt-cache policy ntp
 ps -aef | grep ntp
 ntpq -p

Thanks

summary: - package ntp 1:4.2.6.p2+dfsg-1ubuntu5 failed to install/upgrade: error al
- escribir en `<salida estándar>': No existe el fichero o el directorio
+ package ntp 1:4.2.6.p2+dfsg-1ubuntu5 failed to install/upgrade: error
+ writing <standard output>: No such file or directory
Changed in ntp (Ubuntu):
status: New → Incomplete
Revision history for this message
Qfito (gary-mayet) wrote :

Do not worry I provide the output of the commands:

# apt-cache policy ntp

ntp:
  Instalados: 1:4.2.6.p2+dfsg-1ubuntu5
  Candidato: 1:4.2.6.p2+dfsg-1ubuntu5
  Tabla de versión:
 *** 1:4.2.6.p2+dfsg-1ubuntu5 0
        500 http://mx.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
        100 /var/lib/dpkg/status

For the second command:

#ps -aef | grep ntp

ntp 4982 1 0 10:38 ? 00:00:00 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 113:124
user 5443 5362 0 10:45 pts/0 00:00:00 grep --color=auto ntp

#ntpq -p

     remote refid st t when poll reach delay offset jitter
==============================================================================
+cronos.uanl.mx 65.212.71.103 2 u 46 64 377 38.764 8.460 76.972
*europium.canoni 193.79.237.14 2 u 48 64 377 162.327 -6.815 3.084

Is the information I can give. Apparently the problem was that some packages were not updated

Revision history for this message
James Page (james-page) wrote :

Hmmm - not sure what happened during the installation but your system appears to be running the most up-to-date version of ntp and is correctly sync'ed with two time servers.

Its possible that we might find more information in /var/log/apt/term.log; please could you attach this file to this bug report. You may also find some archived versions of this file (named term.log.X.gz) in the same directory - please could you attach the most recent one of these as well if it exists.

Thanks

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ntp (Ubuntu) because there has been no activity for 60 days.]

Changed in ntp (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.