Bug 752898

With -dthread, I get a similar message:


Sleeping for 5:00
***** Finished processing account gmx
Copying folder structure from IMAP to Maildir
Exception in thread Thread-9:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/threading.py", line 552, in __bootstrap_inner
    self.run()
  File "/usr/lib64/python2.7/threading.py", line 505, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib/python2.7/site-packages/offlineimap/imapserver.py", line 433, in noop
    imapobj.noop()
  File "/usr/lib/python2.7/site-packages/offlineimap/imaplib2.py", line 876, in noop
    return self._simple_command('NOOP', **kw)
  File "/usr/lib/python2.7/site-packages/offlineimap/imaplib2.py", line 1549, in _simple_command
    return self._command_complete(self._command(name, *args), kw)
  File "/usr/lib/python2.7/site-packages/offlineimap/imaplib2.py", line 1310, in _command_complete
    typ, dat = rqb.get_response('command: %s => %%s' % rqb.name)
  File "/usr/lib/python2.7/site-packages/offlineimap/imaplib2.py", line 172, in get_response
    raise typ(exc_fmt % str(val))
abort: command: NOOP => no response after 60.0 secs

DEBUG[thread]: Unregister thread 'Keep alive gmxRemote'



With -1 -dthread, I get a similar message, plus ^C doesn't kill the app:

Sleeping for 5:00
Exception in thread Thread-6:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/threading.py", line 552, in __bootstrap_inner
    self.run()
  File "/usr/lib64/python2.7/threading.py", line 505, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib/python2.7/site-packages/offlineimap/imapserver.py", line 433, in noop
    imapobj.noop()
  File "/usr/lib/python2.7/site-packages/offlineimap/imaplib2.py", line 876, in noop
    return self._simple_command('NOOP', **kw)
  File "/usr/lib/python2.7/site-packages/offlineimap/imaplib2.py", line 1549, in _simple_command
    return self._command_complete(self._command(name, *args), kw)
  File "/usr/lib/python2.7/site-packages/offlineimap/imaplib2.py", line 1310, in _command_complete
    typ, dat = rqb.get_response('command: %s => %%s' % rqb.name)
  File "/usr/lib/python2.7/site-packages/offlineimap/imaplib2.py", line 172, in get_response
    raise typ(exc_fmt % str(val))
abort: command: NOOP => no response after 60.0 secs

***** Finished processing account gmx
Copying folder structure from IMAP to Maildir
^C^C^C^C

^C^C

Removing 'keepalive=60' from the config file helps, but occasionally produces another backtrace:

Copying folder structure from IMAP to Maildir
WARNING: Error occured attempting to sync account 'gmx':
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/offlineimap/accounts.py", line 177, in syncrunner
    self.sync()
  File "/usr/lib/python2.7/site-packages/offlineimap/accounts.py", line 235, in sync
    remoterepos.syncfoldersto(localrepos, [statusrepos])
  File "/usr/lib/python2.7/site-packages/offlineimap/repository/Base.py", line 124, in syncfoldersto
    srcfolders = src.getfolders()
  File "/usr/lib/python2.7/site-packages/offlineimap/repository/IMAP.py", line 283, in getfolders
    listresult = listfunction(directory = self.imapserver.reference)[1]
  File "/usr/lib/python2.7/site-packages/offlineimap/imaplib2.py", line 782, in list
    return self._simple_command(name, directory, pattern, **kw)
  File "/usr/lib/python2.7/site-packages/offlineimap/imaplib2.py", line 1549, in _simple_command
    return self._command_complete(self._command(name, *args), kw)
  File "/usr/lib/python2.7/site-packages/offlineimap/imaplib2.py", line 1310, in _command_complete
    typ, dat = rqb.get_response('command: %s => %%s' % rqb.name)
  File "/usr/lib/python2.7/site-packages/offlineimap/imaplib2.py", line 172, in get_response
    raise typ(exc_fmt % str(val))
abort: command: LIST => no response after 60.0 secs

Sleeping for 5:00

These backtraces went away after I modified the autorefresh timeout to 4 mins instead of 5 mins.

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.