upgrade plone 3.3.6 to plone 4.0.7 File Error - migration

i tried to migrate plone 3.3.6 to a newer plone 4.0.7 version (and then to 4.3.x) but I ran in multiple errors:
Full traceback
2013-10-07 13:51:33 INFO ProgressHandler Process started (1842 objects to go)
2013-10-07 13:51:33 ERROR plone.app.upgrade Upgrade aborted. Error:
Traceback (most recent call last):
File "/Users/iie/Projects/plone4.0/rwa/eggs/Plone-4.0.7-py2.6.egg/Products/CMFPlone/MigrationTool.py", line 175, in upgrade
step['step'].doStep(setup)
File "/Users/iie/Projects/plone4.0/rwa/eggs/Products.GenericSetup-1.6.3-py2.6.egg/Products/GenericSetup/upgrade.py", line 142, in doStep
self.handler(tool)
File "/Users/iie/Projects/plone4.0/rwa/eggs/plone.app.upgrade-1.0.7-py2.6.egg/plone/app/upgrade/v40/betas.py", line 117, in updateIconMetadata
obj = brain.getObject()
File "/Users/iie/Projects/plone4.0/rwa/eggs/Zope2-2.12.18-py2.6-macosx-10.7-x86_64.egg/Products/ZCatalog/CatalogBrains.py", line 92, in getObject
target = parent.restrictedTraverse(path[-1])
File "/Users/iie/Projects/plone4.0/rwa/eggs/Zope2-2.12.18-py2.6-macosx-10.7-x86_64.egg/OFS/Traversable.py", line 310, in restrictedTraverse
return self.unrestrictedTraverse(path, default, restricted=True)
File "/Users/iie/Projects/plone4.0/rwa/eggs/Zope2-2.12.18-py2.6-macosx-10.7-x86_64.egg/OFS/Traversable.py", line 278, in unrestrictedTraverse
raise e
AttributeError: pa_20120810.pdf
If I delete "pa_20120810.pdf" another file throws an error, and so on ...
I hope you understand me and someone can help me
Thanks

Something to try: before migration use collective.catalogcleanup to remove broken references from your catalog. It's easy to use: add to your buildout, restart the site, go to /##collective-catalogcleanup?dry_run=false in your browser.
As collective.catalogcleanup's documentation states:
The goal is to get rid of outdated brains that could otherwise cause problems, for example during an upgrade to Plone 4.

Related

Tensorflow-gpu, has no attribute "python_io"

I am trying to create a custom TFrecords.
When I called a script that uses the tf.python_io.TFRecordWriter(..) as ...:
this error came up
log:
Traceback (most recent call last):
File "createtfrecordsbyother.py", line 105, in <module>
main(args)
File "createtfrecordsbyother.py", line 85, in main
num_shards=num_shards_train)
File "createtfrecordsbyother.py", line 45, in create_tfrecords
with tf.python_io.TFRecordWriter(output_filename) as tfrecord_writer:
AttributeError: module 'tensorflow' has no attribute 'python_io'
Switched to the tensorflow,ver1.15 .
After switching to that version that error is gone and replaced with a warning that states module is depreciated with a new name (io) instead of (python_io)
Note many modules also changed the name.
and downgrading tensorflow may require a updates of CUDA and Cudnn library.
It's not a complete solution to those who wanted to stay in Tensorflow2.0-gpu
But I will post this as a solution for those who are like me fine with downgrade to 1.15.
For uninstall tf,please refer to tf official documentation under install page.

Tensorboard error after upgrading to 1.4: trying to access flag before flags were parsed

Since upgrading to TF 1.4 I am getting this error when I try to run tensorboard:
Traceback (most recent call last):
File "/opt/python/3.6.3/bin/tensorboard", line 11, in <module>
sys.exit(main())
File "/opt/python/3.6.3/lib/python3.6/site-packages/tensorboard/main.py", line 39, in main
return program.main(default.get_plugins(),
File "/opt/python/3.6.3/lib/python3.6/site-packages/tensorboard/default.py", line 71, in get_plugins
debugger = debugger_plugin_loader.get_debugger_plugin()
File "/opt/python/3.6.3/lib/python3.6/site-packages/tensorboard/plugins/debugger/debugger_plugin_loader.py", line 46, in get_debugger_plugin
if FLAGS.debugger_data_server_grpc_port is None:
File "/opt/python/3.6.3/lib/python3.6/site-packages/absl/flags/_flagvalues.py", line 509, in __getattr__
raise _exceptions.UnparsedFlagAccessError(error_message)
absl.flags._exceptions.UnparsedFlagAccessError: Trying to access flag --debugger_data_server_grpc_port before flags were parsed.
I am getting this error even when just typing tensorboard with no --logdir specified but also when I do specify a log dir. I notice this has been reported in github as of 5 days ago (https://github.com/tensorflow/nmt/issues/176), but I am surprised not to see more folks reporting this.
I also noticed that I was not able to run a Tensorflow RNN tutorial for the same reason last week, with the error also indicating flags were accessed before being parsed. Has anyone run into this and can you tell me if there's a fix?
As instructed in this Github issue, the quick fix is to upgrade Tensorboard to the nightly build:
pip install --upgrade tb-nightly
As also explained this issue will be fixed as soon as soon as TensorFlow nightly 20171122 is released though.

UnsupportedMethod error when deploy scrapy project in EC2

I was trying to deploy my Scrapy code to AWS by using scrapyd, but I got into this issue I could not figure out. It has been two days. I saw similar problems on the web, but did not find any helpful solution to fix this issue.
2016-02-15 08:41:20+0000 [HTTPChannel,1,xx.xxx.x.xxx] Unhandled Error
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/twisted/web/http.py", line 1730, in allContentReceived
req.requestReceived(command, path, version)
File "/usr/lib/python2.7/dist-packages/twisted/web/http.py", line 826, in requestReceived
self.process()
File "/usr/lib/python2.7/dist-packages/twisted/web/server.py", line 189, in process
self.render(resrc)
File "/usr/lib/python2.7/dist-packages/twisted/web/server.py", line 238, in render
body = resrc.render(self)
--- <exception caught here> ---
File "/usr/local/lib/python2.7/dist-packages/scrapyd/webservice.py", line 17, in render
return JsonResource.render(self, txrequest)
File "/usr/local/lib/python2.7/dist-packages/scrapyd/utils.py", line 19, in render
r = resource.Resource.render(self, txrequest)
File "/usr/lib/python2.7/dist-packages/twisted/web/resource.py", line 249, in render
raise UnsupportedMethod(allowedMethods)
twisted.web.error.UnsupportedMethod: ['HEAD', 'object', 'POST']
I have tried to run the scrapy code alone in both my macbook, and EC2 server. It works in both cases. It's just not working when I use my macbook to schedule a job in EC2.
These are the steps I followed to set things up.

Indexing of pdf and word docs with Plone4 and Windows

I followed an instruction for indexing pdf on Plone(4) (and Windows 2008) , that was originaly written for Plone3:
http://plone.org/documentation/kb/enable-indexing-of-pdf-and-word-docs-with-windows-in-five-steps-occurs-three-minutes-without-problems
I got an error on he fiths step "Add Transform; Enter in ID: pdf_to_text", when I tried to add the Module: Products.PortalTransforms.transforms.pdf_to_text.
Here is the Report:
Traceback (innermost last):
Module ZPublisher.Publish, line 127, in publish
Module ZPublisher.mapply, line 77, in mapply
Module ZPublisher.Publish, line 47, in call_object
Module Products.PortalTransforms.TransformEngine, line 487, in manage_addTransform
Module Products.PortalTransforms.TransformEngine, line 254, in _mapTransform
Module Products.MimetypesRegistry.MimeTypesRegistry, line 220, in lookup
- __traceback_info__: ("'BROKEN'", 'BROKEN')
Module Products.MimetypesRegistry.MimeTypesRegistry, line 457, in split
MimeTypeException: Malformed MIME type (BROKEN)
Well, that is very old.
On Windows, the word indexing "Just Works" in Plone 4 if you have MS Office installed. PDF still needs xpdf.
Is pdftotext.exe on your PATH? It won't work if it isn't. Remember, if you have added it to the system-wide environment, you are still going to have to stop/start Zope to have the Zope process pick up the changed PATH: run Zope in the foreground, from a command window that you know has pdftotext on the path, and see what happens.

Upgrade from trac 0.10.3 to 0.12 mod_python database error

I´m trying to upgrade trac! from 0.10.3 to 0.12. Need help, i basiclally did steps shown here
http://trac.edgewall.org/wiki/TracUpgrade
So i went through this commands without errors:
todasana:~# easy_install —upgrade Trac0.12 Searching for Trac0.12
todasana:~# trac-admin /usr/local/apache2/htdocs/trac_catw3 upgrade
todasana:~# trac-admin /usr/local/apache2/htdocs/trac_catw3 wiki upgrade
todasana:~# trac-admin /usr/local/apache2/htdocs/trac_catw3 repository resync ‘*’
Didn´t do Step 5 Refresh static resources, because i did not understand it, and i think it does not apply to me: trac-admin /path/to/env deploy /deploy/path
then i
restarted apache:
/etc/init.d/apache2 restart
got this error in the browser now:
Mod_python error: "PythonHandler trac.web.modpython_frontend"
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/mod_python/apache.py", line 299, in HandlerDispatch
result = object(req)
File "/var/lib/python-support/python2.4/trac/web/modpython_frontend.py", line 87, in handler
gateway.run(dispatch_request)
File "/var/lib/python-support/python2.4/trac/web/wsgi.py", line 87, in run
response = application(self.environ, self._start_response)
File "/var/lib/python-support/python2.4/trac/web/main.py", line 377, in dispatch_request
env = _open_environment(env_path, run_once=run_once)
File "/var/lib/python-support/python2.4/trac/web/main.py", line 58, in _open_environment
env_cache[env_path] = open_environment(env_path)
File "/var/lib/python-support/python2.4/trac/env.py", line 435, in open_environment
if env.needs_upgrade():
File "/var/lib/python-support/python2.4/trac/env.py", line 315, in needs_upgrade
if participant.environment_needs_upgrade(db):
File "/var/lib/python-support/python2.4/trac/env.py", line 373, in environment_needs_upgrade
raise TracError, 'Database newer than Trac version'
TracError: Database newer than Trac version
got Python 2.4.4 (#2, Jan 24 2010, 11:19:18)
mysql: Server version: 5.0.32-Debian_7etch11-log Debian etch distribution
IT OCCOURS TO ME THAT SOMETHING SHOULD BE DONE WITH THE DATABASE OR CONFIG FILES, BUT NOT SURE WHAT BECAUSE THERE IS NOTHING IN THE DOCS ABOUT IT!
Guys have a great day!!
It sounds like the version of Trac being run by Apache is the older version and not the version you just installed. Verify that the version of Trac you are running is the version you think you are running.