Modify ↓
Ticket #29 (closed defect: fixed)
Server tracebacks
| Reported by: | lueningh@… | Owned by: | desai |
|---|---|---|---|
| Priority: | major | Milestone: | Bcfg2 0.8.1 Release |
| Component: | bcfg2-server | Version: | |
| Keywords: | Cc: |
Description
On the server 0.8.0pre7 console when a client runs:
Traceback (most recent call last):
File "/usr/lib/python2.3/logging/handlers.py", line 408, in emit
self.socket.send(msg)
error: (107, 'Transport endpoint is not connected')
Client tg-c001.uc.teragrid.org reported state dirty
Traceback (most recent call last):
File "/usr/lib/python2.3/logging/handlers.py", line 408, in emit
self.socket.send(msg)
error: (107, 'Transport endpoint is not connected')
Attachments
Change History
comment:2 Changed 15 years ago by desai
- Status changed from new to assigned
- Milestone set to Bcfg2 0.8.1 Release
I think this is caused by syslog rotation. The attached patch should fix things.
comment:3 Changed 15 years ago by desai
- Status changed from assigned to closed
- Resolution set to fixed
Fixed in changeset [0c4bb9314b84e6a798fe9c33767d5cf456462a47] (SVN r1777)
Note: See
TracTickets for help on using
tickets.
I see now that this isn't just when a client runs. The server is just sitting there spitting out these messages every once and a while now, perhaps when a fam event happens.