twistd crashed with OperationalError in __init__(): (2002, "Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)")

Bug #760988 reported by Alessandro Lattao
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
twisted (Ubuntu)
New
Undecided
Unassigned

Bug Description

Description: Ubuntu Natty (development branch)
Release: 11.04

python-twisted-core:
  Installato: 10.2.0-1
  Candidato: 10.2.0-1
  Tabella versione:
 *** 10.2.0-1 0
        500 http://it.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
        100 /var/lib/dpkg/status

It happened soon after system boot up :)

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: python-twisted-core 10.2.0-1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Thu Apr 14 19:52:32 2011
ExecutablePath: /usr/bin/twistd
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100329)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/twistd --pidfile=/var/run/poker-network-server.pid --logfile=/var/log/poker-network-server.log --no_save --reactor=poll pokerserver
ProcEnviron: PATH=(custom, no user)
PythonArgs: ['/usr/bin/twistd', '--pidfile=/var/run/poker-network-server.pid', '--logfile=/var/log/poker-network-server.log', '--no_save', '--reactor=poll', 'pokerserver']
SourcePackage: twisted
Title: twistd crashed with OperationalError in __init__(): (2002, "Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)")
UpgradeStatus: Upgraded to natty on 2011-03-31 (14 days ago)
UserGroups:

Revision history for this message
Alessandro Lattao (blackhole) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #725383, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-duplicate-check
visibility: private → public
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.