Register Guidelines E-Books Search Today's Posts Mark Forums Read

Go Back   MobileRead Forums > E-Book Software > Calibre > Devices

Notices

Reply
 
Thread Tools Search this Thread
Old 10-19-2013, 06:30 PM   #1
wn1ytw
Member
wn1ytw began at the beginning.
 
Posts: 24
Karma: 10
Join Date: May 2011
Device: kindle
Unhappy Calibre device and server errors

I have a problem that came up today running v 1.6, upgrading to 1,7 did not fix it. On starting calibre I get the following error: calibre, version 1.7.0
ERROR: Problem starting the wireless device: The wireless device driver did not start. It said "Failed to allocate a random port"

I never got that before this morning and can't figure out how to fix it. Calibre now has a different IP address than I show on my network settings. I do not have control of a router, I connect to a network run by the nursing home I live at, they may have changed things? I am using OSX 10.5.8 on a 2011 iMac, nothing connected to USB ports. Help please. (the following is from debug and the content sever works fine in test) (I have tried variations of the IP ane both port 8080 & 9090, no soap, it used to work)
Spoiler:

Traceback (most recent call last):
File "site-packages/calibre/customize/ui.py", line 567, in initialize_plugins
File "site-packages/calibre/customize/ui.py", line 53, in load_plugin
File "site-packages/calibre/customize/zipplugin.py", line 169, in load
File "lib/python2.7/importlib/__init__.py", line 37, in import_module
File "site-packages/calibre/customize/zipplugin.py", line 150, in load_module
File "calibre_plugins.dummy1.__init__", line 18, in <module>
ImportError: No module named fetch
calibre Debug log
calibre 1.7 isfrozen: True is64bit: True
Darwin-12.5.0-x86_64-i386-64bit Darwin ('64bit', '')
('Darwin', '12.5.0', 'Darwin Kernel Version 12.5.0: Sun Sep 29 13:33:47 PDT 2013; root:xnu-2050.48.12~1/RELEASE_X86_64')
Python 2.7.5
OSX: ('10.8.5', ('', '', ''), 'x86_64')
Failed to initialize plugin: '/Users/n1sp1/Library/Preferences/calibre/plugins/LibraryThing.zip'
Starting up...
Started up in 30.91 seconds with 29613 books
SMART_DEV ( 0.00: 0.001) _attach_to_port try ip address "167.20.92.58" on port 9090
SMART_DEV ( 0.11: 0.000) _attach_to_port socket error on port 9090
SMART_DEV ( 0.15: 0.000) _attach_to_port try ip address "167.20.92.58" on port 30050
SMART_DEV ( 0.19: 0.000) _attach_to_port socket error on port 30050
SMART_DEV ( 0.22: 0.000) _attach_to_port try ip address "167.20.92.58" on port 14038
SMART_DEV ( 0.26: 0.000) _attach_to_port socket error on port 14038
SMART_DEV ( 0.30: 0.000) _attach_to_port try ip address "167.20.92.58" on port 24013
SMART_DEV ( 0.33: 0.000) _attach_to_port socket error on port 24013
SMART_DEV ( 0.37: 0.000) _attach_to_port try ip address "167.20.92.58" on port 9559
SMART_DEV ( 0.41: 0.000) _attach_to_port socket error on port 9559
SMART_DEV ( 0.44: 0.000) _attach_to_port try ip address "167.20.92.58" on port 25560
SMART_DEV ( 0.48: 0.000) _attach_to_port socket error on port 25560
SMART_DEV ( 0.52: 0.000) _attach_to_port try ip address "167.20.92.58" on port 28647
SMART_DEV ( 0.55: 0.000) _attach_to_port socket error on port 28647
SMART_DEV ( 0.59: 0.000) _attach_to_port try ip address "167.20.92.58" on port 20760
SMART_DEV ( 0.62: 0.000) _attach_to_port socket error on port 20760
SMART_DEV ( 0.66: 0.000) _attach_to_port try ip address "167.20.92.58" on port 26378
SMART_DEV ( 0.70: 0.000) _attach_to_port socket error on port 26378
SMART_DEV ( 0.73: 0.000) _attach_to_port try ip address "167.20.92.58" on port 17320
SMART_DEV ( 0.77: 0.000) _attach_to_port socket error on port 17320
SMART_DEV ( 0.81: 0.000) _attach_to_port try ip address "167.20.92.58" on port 11369
SMART_DEV ( 0.85: 0.000) _attach_to_port socket error on port 11369
SMART_DEV ( 0.88: 0.000) _attach_to_port try ip address "167.20.92.58" on port 30108
SMART_DEV ( 0.92: 0.000) _attach_to_port socket error on port 30108
SMART_DEV ( 0.96: 0.000) _attach_to_port try ip address "167.20.92.58" on port 9044
SMART_DEV ( 1.00: 0.000) _attach_to_port socket error on port 9044
SMART_DEV ( 1.04: 0.000) _attach_to_port try ip address "167.20.92.58" on port 25302
SMART_DEV ( 1.08: 0.000) _attach_to_port socket error on port 25302
SMART_DEV ( 1.12: 0.000) _attach_to_port try ip address "167.20.92.58" on port 10881
SMART_DEV ( 1.15: 0.000) _attach_to_port socket error on port 10881
SMART_DEV ( 1.19: 0.000) _attach_to_port try ip address "167.20.92.58" on port 30532
SMART_DEV ( 1.23: 0.000) _attach_to_port socket error on port 30532
SMART_DEV ( 1.27: 0.000) _attach_to_port try ip address "167.20.92.58" on port 29972
SMART_DEV ( 1.31: 0.000) _attach_to_port socket error on port 29972
SMART_DEV ( 1.34: 0.000) _attach_to_port try ip address "167.20.92.58" on port 30887
SMART_DEV ( 1.38: 0.000) _attach_to_port socket error on port 30887
SMART_DEV ( 1.42: 0.000) _attach_to_port try ip address "167.20.92.58" on port 23456
SMART_DEV ( 1.46: 0.000) _attach_to_port socket error on port 23456
SMART_DEV ( 1.50: 0.000) _attach_to_port try ip address "167.20.92.58" on port 24223
SMART_DEV ( 1.53: 0.000) _attach_to_port socket error on port 24223
SMART_DEV ( 1.57: 0.000) _attach_to_port try ip address "167.20.92.58" on port 30352
SMART_DEV ( 1.60: 0.000) _attach_to_port socket error on port 30352
SMART_DEV ( 1.64: 0.000) _attach_to_port try ip address "167.20.92.58" on port 24542
SMART_DEV ( 1.67: 0.000) _attach_to_port socket error on port 24542
SMART_DEV ( 1.71: 0.000) _attach_to_port try ip address "167.20.92.58" on port 14498
SMART_DEV ( 1.74: 0.000) _attach_to_port socket error on port 14498
SMART_DEV ( 1.78: 0.000) _attach_to_port try ip address "167.20.92.58" on port 22224
SMART_DEV ( 1.82: 0.000) _attach_to_port socket error on port 22224
SMART_DEV ( 1.85: 0.000) _attach_to_port try ip address "167.20.92.58" on port 28063
SMART_DEV ( 1.89: 0.000) _attach_to_port socket error on port 28063
SMART_DEV ( 1.93: 0.000) _attach_to_port try ip address "167.20.92.58" on port 24504
SMART_DEV ( 1.96: 0.000) _attach_to_port socket error on port 24504
SMART_DEV ( 2.00: 0.000) _attach_to_port try ip address "167.20.92.58" on port 8263
SMART_DEV ( 2.03: 0.000) _attach_to_port socket error on port 8263
SMART_DEV ( 2.07: 0.000) _attach_to_port try ip address "167.20.92.58" on port 17873
SMART_DEV ( 2.11: 0.000) _attach_to_port socket error on port 17873
SMART_DEV ( 2.14: 0.000) _attach_to_port try ip address "167.20.92.58" on port 14605
SMART_DEV ( 2.18: 0.000) _attach_to_port socket error on port 14605
SMART_DEV ( 2.22: 0.000) _attach_to_port try ip address "167.20.92.58" on port 17806
SMART_DEV ( 2.25: 0.000) _attach_to_port socket error on port 17806
SMART_DEV ( 2.29: 0.000) _attach_to_port try ip address "167.20.92.58" on port 10469
SMART_DEV ( 2.33: 0.000) _attach_to_port socket error on port 10469
SMART_DEV ( 2.37: 0.000) _attach_to_port try ip address "167.20.92.58" on port 16781
SMART_DEV ( 2.41: 0.000) _attach_to_port socket error on port 16781
SMART_DEV ( 2.45: 0.000) _attach_to_port try ip address "167.20.92.58" on port 9077
SMART_DEV ( 2.48: 0.000) _attach_to_port socket error on port 9077
SMART_DEV ( 2.52: 0.000) _attach_to_port try ip address "167.20.92.58" on port 21967
SMART_DEV ( 2.56: 0.000) _attach_to_port socket error on port 21967
SMART_DEV ( 2.60: 0.000) _attach_to_port try ip address "167.20.92.58" on port 30898
SMART_DEV ( 2.64: 0.000) _attach_to_port socket error on port 30898
SMART_DEV ( 2.68: 0.000) _attach_to_port try ip address "167.20.92.58" on port 13614
SMART_DEV ( 2.72: 0.000) _attach_to_port socket error on port 13614
SMART_DEV ( 2.75: 0.000) _attach_to_port try ip address "167.20.92.58" on port 25378
SMART_DEV ( 2.79: 0.000) _attach_to_port socket error on port 25378
SMART_DEV ( 2.83: 0.000) _attach_to_port try ip address "167.20.92.58" on port 28482
SMART_DEV ( 2.87: 0.000) _attach_to_port socket error on port 28482
SMART_DEV ( 2.90: 0.000) _attach_to_port try ip address "167.20.92.58" on port 29329
SMART_DEV ( 2.94: 0.000) _attach_to_port socket error on port 29329
SMART_DEV ( 2.98: 0.000) _attach_to_port try ip address "167.20.92.58" on port 17499
SMART_DEV ( 3.01: 0.000) _attach_to_port socket error on port 17499
SMART_DEV ( 3.05: 0.000) _attach_to_port try ip address "167.20.92.58" on port 27399
SMART_DEV ( 3.09: 0.000) _attach_to_port socket error on port 27399
SMART_DEV ( 3.12: 0.000) _attach_to_port try ip address "167.20.92.58" on port 13076
SMART_DEV ( 3.16: 0.000) _attach_to_port socket error on port 13076
SMART_DEV ( 3.19: 0.000) _attach_to_port try ip address "167.20.92.58" on port 30561
SMART_DEV ( 3.23: 0.000) _attach_to_port socket error on port 30561
SMART_DEV ( 3.27: 0.000) _attach_to_port try ip address "167.20.92.58" on port 27213
SMART_DEV ( 3.30: 0.000) _attach_to_port socket error on port 27213
SMART_DEV ( 3.34: 0.000) _attach_to_port try ip address "167.20.92.58" on port 11295
SMART_DEV ( 3.38: 0.000) _attach_to_port socket error on port 11295
SMART_DEV ( 3.41: 0.000) _attach_to_port try ip address "167.20.92.58" on port 12674
SMART_DEV ( 3.45: 0.000) _attach_to_port socket error on port 12674
SMART_DEV ( 3.49: 0.000) _attach_to_port try ip address "167.20.92.58" on port 24523
SMART_DEV ( 3.53: 0.000) _attach_to_port socket error on port 24523
SMART_DEV ( 3.57: 0.000) _attach_to_port try ip address "167.20.92.58" on port 28238
SMART_DEV ( 3.60: 0.000) _attach_to_port socket error on port 28238
SMART_DEV ( 3.64: 0.000) _attach_to_port try ip address "167.20.92.58" on port 29231
SMART_DEV ( 3.68: 0.000) _attach_to_port socket error on port 29231
SMART_DEV ( 3.72: 0.000) _attach_to_port try ip address "167.20.92.58" on port 18638
SMART_DEV ( 3.76: 0.000) _attach_to_port socket error on port 18638
SMART_DEV ( 3.80: 0.000) _attach_to_port try ip address "167.20.92.58" on port 29224
SMART_DEV ( 3.83: 0.000) _attach_to_port socket error on port 29224
SMART_DEV ( 3.87: 0.000) _attach_to_port try ip address "167.20.92.58" on port 8893
SMART_DEV ( 3.91: 0.000) _attach_to_port socket error on port 8893
SMART_DEV ( 3.95: 0.000) _attach_to_port try ip address "167.20.92.58" on port 29489
SMART_DEV ( 3.99: 0.000) _attach_to_port socket error on port 29489
SMART_DEV ( 4.02: 0.000) _attach_to_port try ip address "167.20.92.58" on port 23124
SMART_DEV ( 4.06: 0.000) _attach_to_port socket error on port 23124
SMART_DEV ( 4.10: 0.000) _attach_to_port try ip address "167.20.92.58" on port 23575
SMART_DEV ( 4.14: 0.000) _attach_to_port socket error on port 23575
SMART_DEV ( 4.18: 0.000) _attach_to_port try ip address "167.20.92.58" on port 31732
SMART_DEV ( 4.22: 0.000) _attach_to_port socket error on port 31732
SMART_DEV ( 4.26: 0.000) _attach_to_port try ip address "167.20.92.58" on port 12364
SMART_DEV ( 4.29: 0.000) _attach_to_port socket error on port 12364
SMART_DEV ( 4.33: 0.000) _attach_to_port try ip address "167.20.92.58" on port 13099
SMART_DEV ( 4.37: 0.000) _attach_to_port socket error on port 13099
SMART_DEV ( 4.41: 0.000) _attach_to_port try ip address "167.20.92.58" on port 15836
SMART_DEV ( 4.44: 0.000) _attach_to_port socket error on port 15836
SMART_DEV ( 4.48: 0.000) _attach_to_port try ip address "167.20.92.58" on port 31871
SMART_DEV ( 4.52: 0.000) _attach_to_port socket error on port 31871
SMART_DEV ( 4.56: 0.000) _attach_to_port try ip address "167.20.92.58" on port 12789
SMART_DEV ( 4.59: 0.000) _attach_to_port socket error on port 12789
SMART_DEV ( 4.63: 0.000) _attach_to_port try ip address "167.20.92.58" on port 15830
SMART_DEV ( 4.67: 0.000) _attach_to_port socket error on port 15830
SMART_DEV ( 4.71: 0.000) _attach_to_port try ip address "167.20.92.58" on port 17176
SMART_DEV ( 4.75: 0.000) _attach_to_port socket error on port 17176
SMART_DEV ( 4.78: 0.000) _attach_to_port try ip address "167.20.92.58" on port 23975
SMART_DEV ( 4.82: 0.000) _attach_to_port socket error on port 23975
SMART_DEV ( 4.86: 0.000) _attach_to_port try ip address "167.20.92.58" on port 12393
SMART_DEV ( 4.89: 0.000) _attach_to_port socket error on port 12393
SMART_DEV ( 4.93: 0.000) _attach_to_port try ip address "167.20.92.58" on port 28989
SMART_DEV ( 4.97: 0.000) _attach_to_port socket error on port 28989
SMART_DEV ( 5.00: 0.000) _attach_to_port try ip address "167.20.92.58" on port 26489
SMART_DEV ( 5.04: 0.000) _attach_to_port socket error on port 26489
SMART_DEV ( 5.07: 0.000) _attach_to_port try ip address "167.20.92.58" on port 17467
SMART_DEV ( 5.11: 0.000) _attach_to_port socket error on port 17467
SMART_DEV ( 5.15: 0.000) _attach_to_port try ip address "167.20.92.58" on port 21029
SMART_DEV ( 5.18: 0.000) _attach_to_port socket error on port 21029
SMART_DEV ( 5.22: 0.000) _attach_to_port try ip address "167.20.92.58" on port 23810
SMART_DEV ( 5.25: 0.000) _attach_to_port socket error on port 23810
SMART_DEV ( 5.29: 0.000) _attach_to_port try ip address "167.20.92.58" on port 23768
SMART_DEV ( 5.33: 0.000) _attach_to_port socket error on port 23768
SMART_DEV ( 5.36: 0.000) _attach_to_port try ip address "167.20.92.58" on port 28065
SMART_DEV ( 5.40: 0.000) _attach_to_port socket error on port 28065
SMART_DEV ( 5.44: 0.000) _attach_to_port try ip address "167.20.92.58" on port 29830
SMART_DEV ( 5.47: 0.000) _attach_to_port socket error on port 29830
SMART_DEV ( 5.51: 0.000) _attach_to_port try ip address "167.20.92.58" on port 29633
SMART_DEV ( 5.54: 0.000) _attach_to_port socket error on port 29633
SMART_DEV ( 5.58: 0.000) _attach_to_port try ip address "167.20.92.58" on port 14841
SMART_DEV ( 5.62: 0.000) _attach_to_port socket error on port 14841
SMART_DEV ( 5.65: 0.000) _attach_to_port try ip address "167.20.92.58" on port 18235
SMART_DEV ( 5.69: 0.000) _attach_to_port socket error on port 18235
SMART_DEV ( 5.72: 0.000) _attach_to_port try ip address "167.20.92.58" on port 15671
SMART_DEV ( 5.76: 0.000) _attach_to_port socket error on port 15671
SMART_DEV ( 5.80: 0.000) _attach_to_port try ip address "167.20.92.58" on port 17904
SMART_DEV ( 5.83: 0.000) _attach_to_port socket error on port 17904
SMART_DEV ( 5.87: 0.000) _attach_to_port try ip address "167.20.92.58" on port 21555
SMART_DEV ( 5.91: 0.000) _attach_to_port socket error on port 21555
SMART_DEV ( 5.94: 0.000) _attach_to_port try ip address "167.20.92.58" on port 23765
SMART_DEV ( 5.98: 0.000) _attach_to_port socket error on port 23765
SMART_DEV ( 6.02: 0.000) _attach_to_port try ip address "167.20.92.58" on port 22142
SMART_DEV ( 6.05: 0.000) _attach_to_port socket error on port 22142
SMART_DEV ( 6.09: 0.000) _attach_to_port try ip address "167.20.92.58" on port 28092
SMART_DEV ( 6.12: 0.000) _attach_to_port socket error on port 28092
SMART_DEV ( 6.16: 0.000) _attach_to_port try ip address "167.20.92.58" on port 9703
SMART_DEV ( 6.20: 0.000) _attach_to_port socket error on port 9703
SMART_DEV ( 6.23: 0.000) _attach_to_port try ip address "167.20.92.58" on port 27448
SMART_DEV ( 6.27: 0.000) _attach_to_port socket error on port 27448
SMART_DEV ( 6.30: 0.000) _attach_to_port try ip address "167.20.92.58" on port 9839
SMART_DEV ( 6.34: 0.000) _attach_to_port socket error on port 9839
SMART_DEV ( 6.38: 0.000) _attach_to_port try ip address "167.20.92.58" on port 21727
SMART_DEV ( 6.41: 0.000) _attach_to_port socket error on port 21727
SMART_DEV ( 6.45: 0.000) _attach_to_port try ip address "167.20.92.58" on port 14611
SMART_DEV ( 6.49: 0.000) _attach_to_port socket error on port 14611
SMART_DEV ( 6.52: 0.000) _attach_to_port try ip address "167.20.92.58" on port 12211
SMART_DEV ( 6.56: 0.000) _attach_to_port socket error on port 12211
SMART_DEV ( 6.59: 0.000) _attach_to_port try ip address "167.20.92.58" on port 26416
SMART_DEV ( 6.63: 0.000) _attach_to_port socket error on port 26416
SMART_DEV ( 6.67: 0.000) _attach_to_port try ip address "167.20.92.58" on port 30699
SMART_DEV ( 6.70: 0.000) _attach_to_port socket error on port 30699
SMART_DEV ( 6.74: 0.000) _attach_to_port try ip address "167.20.92.58" on port 21335
SMART_DEV ( 6.78: 0.000) _attach_to_port socket error on port 21335
SMART_DEV ( 6.82: 0.000) _attach_to_port try ip address "167.20.92.58" on port 20829
SMART_DEV ( 6.85: 0.000) _attach_to_port socket error on port 20829
SMART_DEV ( 6.90: 0.000) _attach_to_port try ip address "167.20.92.58" on port 22246
SMART_DEV ( 6.93: 0.000) _attach_to_port socket error on port 22246
SMART_DEV ( 6.97: 0.000) _attach_to_port try ip address "167.20.92.58" on port 12140
SMART_DEV ( 7.00: 0.000) _attach_to_port socket error on port 12140
SMART_DEV ( 7.04: 0.000) _attach_to_port try ip address "167.20.92.58" on port 29938
SMART_DEV ( 7.08: 0.000) _attach_to_port socket error on port 29938
SMART_DEV ( 7.11: 0.000) _attach_to_port try ip address "167.20.92.58" on port 27266
SMART_DEV ( 7.15: 0.000) _attach_to_port socket error on port 27266
SMART_DEV ( 7.19: 0.000) _attach_to_port try ip address "167.20.92.58" on port 10668
SMART_DEV ( 7.22: 0.000) _attach_to_port socket error on port 10668
SMART_DEV ( 7.26: 0.000) _attach_to_port try ip address "167.20.92.58" on port 21371
SMART_DEV ( 7.30: 0.000) _attach_to_port socket error on port 21371
SMART_DEV ( 7.33: 0.000) _attach_to_port try ip address "167.20.92.58" on port 28033
SMART_DEV ( 7.37: 0.000) _attach_to_port socket error on port 28033
SMART_DEV ( 7.40: 0.000) _attach_to_port try ip address "167.20.92.58" on port 12182
SMART_DEV ( 7.44: 0.000) _attach_to_port socket error on port 12182
SMART_DEV ( 7.48: 0.000) startup_on_demand Failed to allocate a random port

Last edited by theducks; 10-19-2013 at 06:51 PM. Reason: Wrapped long paste in Spoiler
wn1ytw is offline   Reply With Quote
Old 10-19-2013, 11:20 PM   #2
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 25,762
Karma: 4998511
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
You can control what interface the calibre server tries to listen on via

Preferences->Tweaks->What interfaces should the content server listen on

I dont recall if that also affects the wireless device driver, try it and see.
kovidgoyal is online now   Reply With Quote
 
Enthusiast
Old 10-20-2013, 06:24 AM   #3
chaley
"chaley", not "charley"
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 5,251
Karma: 821512
Join Date: Jan 2010
Location: France
Device: Many android devices
Something on your computer is telling calibre that the 167.20 IP address is what it should use. What that is, I cat say. I don't own and never use macs, so I don't know enough to give hints.

You can tell the wireless device plugin which interface to listen on by going to preferences / plugins / device interface plugins / smart device then pushing the configure plugin button.

Also make sure that you do not have any virtual private networks (VPNs) configured. They can confuse network interface selection because they appear to be valid networks but they are not.
chaley is offline   Reply With Quote
Old 10-20-2013, 07:38 AM   #4
wn1ytw
Member
wn1ytw began at the beginning.
 
Posts: 24
Karma: 10
Join Date: May 2011
Device: kindle
Ok, I did some fiddling this morning first thing, I'll check Kovid's suggestion next. As of now, my notes this morning:
odd, calibre content server worked this morning,.
imac was off, after boot I started calibre with content server first thing.

asus ubuntu box had been suspended, I opened li, opened firefox - NOT CHROME - typed "http://167.20.92.106:8080/" and it worked.
now to try chrome
and it worked in chrome. confusing- I tried ALL of this yesterday… I had different IP ad's showing and typed them, carefully confirming they were correct but they did not work and I had IP showing as different from network settings on iMac and calibre's Connect/share menu.

I am not getting the error today because I have wireless device off - tried that yesterday also. Scratching my head raw. Reboots and starting fresh yesterday did nothing. Calibre wants to start the wireless device at http://167.20.92.58:9090
I think this is the problem but how to fix??

-------------------------------
On for Kovid's suggestion
scott
wn1ytw is offline   Reply With Quote
Old 10-20-2013, 07:53 AM   #5
chaley
"chaley", not "charley"
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 5,251
Karma: 821512
Join Date: Jan 2010
Location: France
Device: Many android devices
Is it possible that in time past you set the wireless device ip address in the settings I mentioned above? I ask because what might have happened is that you got a new ip address from the router where before it always have back the same one. This can happen if the router is restarted and it forgets the allocation table.
chaley is offline   Reply With Quote
Old 10-20-2013, 07:53 AM   #6
wn1ytw
Member
wn1ytw began at the beginning.
 
Posts: 24
Karma: 10
Join Date: May 2011
Device: kindle
I found the tweak for 'content server' but not for 'wireless device' and calibre wants to start wireless device on an old IP that no longer works. I think this might be the root of my problem??
wn1ytw is offline   Reply With Quote
Old 10-21-2013, 08:26 AM   #7
wn1ytw
Member
wn1ytw began at the beginning.
 
Posts: 24
Karma: 10
Join Date: May 2011
Device: kindle
Quote:
Originally Posted by kovidgoyal View Post
You can control what interface the calibre server tries to listen on via

Preferences->Tweaks->What interfaces should the content server listen on

I dont recall if that also affects the wireless device driver, try it and see.
Kovid,
Thanks, It controls Content Server fine but NOT wireless device.
scott
wn1ytw is offline   Reply With Quote
Old 10-21-2013, 08:30 AM   #8
wn1ytw
Member
wn1ytw began at the beginning.
 
Posts: 24
Karma: 10
Join Date: May 2011
Device: kindle
Quote:
Originally Posted by chaley View Post
Is it possible that in time past you set the wireless device ip address in the settings I mentioned above? I ask because what might have happened is that you got a new ip address from the router where before it always have back the same one. This can happen if the router is restarted and it forgets the allocation table.
If it is router, I'm dead. This is a network I have no control over, when they reset the system, my devices must deal with it. Yes, Wireless Device once used that IP.scott
wn1ytw is offline   Reply With Quote
Old 10-21-2013, 09:36 AM   #9
chaley
"chaley", not "charley"
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 5,251
Karma: 821512
Join Date: Jan 2010
Location: France
Device: Many android devices
Have you looked at the setting I described in post 3?
chaley is offline   Reply With Quote
Old 10-25-2013, 08:24 AM   #10
wn1ytw
Member
wn1ytw began at the beginning.
 
Posts: 24
Karma: 10
Join Date: May 2011
Device: kindle
yes

Thanks! Just saw and changed it =Thank you, that fixed it!
scott
wn1ytw is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Browse Calibre content server from Kindle device? skidrash Amazon Kindle 5 10-15-2013 07:00 PM
Excited! But errors for headless server. apiontek Devices 3 08-25-2013 04:07 PM
0.9.36 related server errors khahoon Calibre 0 06-26-2013 03:26 PM
Stand alone server - Chrome errors robin58 Calibre 7 02-19-2013 11:29 PM
iPad Calibre errors wont add books to device stustaff Calibre 9 06-07-2010 06:10 AM


All times are GMT -4. The time now is 03:40 AM.


MobileRead.com is a privately owned, operated and funded community.