PeerSession:ERROR: Cannot connect to the remote server: [Errno 111] Connection refused

Bug #526716 reported by Martin Schaaf
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
BeeSeek
Fix Released
Undecided
Unassigned

Bug Description

Beeseek peer does not start.

console output:
PeerSession:ERROR: Cannot connect to the remote server: [Errno 111] Connection refused
Exception OSError: (1, 'Operation not permitted', '/var/lock/beeseek-peer.pid') in <bound method LockFile.__del__ of <beeseek.app.filelocking.LockFile object at 0x8c6ea2c>> ignored

log file:
[2010-02-23 23:03:22 CET] <PeerSession> INFO: Session started with arguments '/usr/bin/beeseek-peer start'
[2010-02-23 23:03:22 CET] <PeerSession> INFO: Bound address localhost:8080
[2010-02-23 23:03:22 CET] <PeerSession> INFO: Bound address localhost:4096
[2010-02-23 23:03:22 CET] <PeerSession> INFO: Running as user www-data
[2010-02-23 23:03:22 CET] <PeerSession> INFO: Bound address /var/lock/beeseek-peer.sock
[2010-02-23 23:03:22 CET] <PeerSession> INFO: Database connected
[2010-02-23 23:03:22 CET] <PeerSession> INFO: Templates loaded
[2010-02-23 23:03:22 CET] <PeerSession> ERROR: Cannot connect to the remote server: [Errno 111] Connection refused
[2010-02-23 23:03:22 CET] <PeerSession> INFO: Process interrupted

Revision history for this message
Andrea Corbellini (andrea.corbellini) wrote :

The server is now started. Please feel free to revert the status of this bug back to New if the problem persists.

Changed in beeseek:
status: New → Fix Released
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.