RE: [Arches] Upgrading to a specific version of Arches - 4.4.1 (not the latest 4.4.2 version)
Hi Alexei, Yes I set "DEBUG=False" in settings.py file but python manage.py migrate still failed with a memory error. Thanks Tom Shewring GIS Systems Developer IMT Development Centre 07748 182134 IMT Development and Programmes: Together, we enable the celebration of England’s historic environment by empowering our customers and the public through technology and innovation. From: Alexei Peters [mailto:apet...@fargeo.com] Sent: 07 October 2019 18:10 To: Shewring, Tom Cc: Cyrus Hiatt; Adam Cox; Arches Project Subject: Re: [Arches] Upgrading to a specific version of Arches - 4.4.1 (not the latest 4.4.2 version) Tom, Did you set "DEBUG=False" in your settings.py file? If you don't Django will keep a record of all you sql statements called. That may be causing your out of memory error. -Alexei Director of Web Development - Farallon Geographics, Inc. - 971.227.3173 On Fri, Oct 4, 2019 at 1:18 AM Shewring, Tom mailto:tom.shewr...@historicengland.org.uk>> wrote: Hi, Thank you for you your replies. I took a snapshot of the server before I started the upgrade process. I will roll back to the snapshot and follow the process Cyrus has detailed. Before I do so, would you be able to comment on the process I followed and the error I encountered - 1) Upgrade Yarn and Node.js to 1.13.0 and 10.15.2 respectively (this brings the versions of this software up to the same level as the our other working 4.4.1 environments) 2) python -m pip install --upgrade pip 3) pip install arches==4.4.1 --upgrade --no-binary :all: (this completed successfully, upgrading directly from 4.1.1) 4) python manage.py migrate – (errors encountered) – is this due to a lack of memory on the server? – (see final error massage - django.db.utils.DatabaseError: out of memory for query result) Operations to perform: Apply all migrations: admin, auth, contenttypes, guardian, models, oauth2_provider, sessions Running migrations: Applying models.2293_recent_edits... OK Applying models.2974_provisionaledits_in_editlog... OK Applying models.3098_custom_map_markers... OK Applying models.3199_graphmodel_color... OK Applying models.3201_remove_node_and_nodetype_branches... OK Applying models.3210_card_components... OK Applying models.3314_graphmodel_jsonldcontext... OK Applying models.3201_replace_node_and_nodetype_branches... OK Applying models.3201_second_removal_of_node_nodetype_branch... OK Applying models.deserialize_provisional_edits...Traceback (most recent call last): File "manage.py", line 29, in execute_from_command_line(sys.argv) File "c:\obap\env4.1.1\lib\site-packages\django\core\management\__init__.py", line 364, in execute_from_command_line utility.execute() File "c:\obap\env4.1.1\lib\site-packages\django\core\management\__init__.py", line 356, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "c:\obap\env4.1.1\lib\site-packages\django\core\management\base.py", line 283, in run_from_argv self.execute(*args, **cmd_options) File "c:\obap\env4.1.1\lib\site-packages\django\core\management\base.py", line 330, in execute output = self.handle(*args, **options) File "c:\obap\env4.1.1\lib\site-packages\django\core\management\commands\migrate.py", line 204, in handle fake_initial=fake_initial, File "c:\obap\env4.1.1\lib\site-packages\django\db\migrations\executor.py", line 115, in migrate state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial) File "c:\obap\env4.1.1\lib\site-packages\django\db\migrations\executor.py", line 145, in _migrate_all_forwards state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial) File "c:\obap\env4.1.1\lib\site-packages\django\db\migrations\executor.py", line 244, in apply_migration state = migration.apply(state, schema_editor) File "c:\obap\env4.1.1\lib\site-packages\django\db\migrations\migration.py", line 129, in apply operation.database_forwards(self.app_label, schema_editor, old_state, project_state) File "c:\obap\env4.1.1\lib\site-packages\django\db\migrations\operations\special.py", line 193, in database_forwards self.code(from_state.apps, schema_editor) File "c:\obap\env4.1.1\lib\site-packages\arches\app\models\migrations\deserialize_provisional_edits.py", line 13, in forwards_func for tile in tiles: File "c:\obap\env4.1.1\lib\site-packages\django\db\models\query.py", line 250, in __iter__ self._fetch_all() File "c:\obap\env4.1.1\lib\site-packages\django\db\models\query.py", line 1118, in _fetch_all self._result_cache = list(self._iterable_class(self)) File "c:\obap\env4.1.1\lib\site-packages\django\db\models\query.py", line 53, in __iter__ results = compiler.execute_sql(chunked_fetch=self.chunked_fetch) File "c:\obap\env4.1.1\lib\site-packages\django\db\models\sql\compiler.py", line 899, in execute_sql raise original_exception
Re: [Arches] Upgrading to a specific version of Arches - 4.4.1 (not the latest 4.4.2 version)
Tom, Did you set "DEBUG=False" in your settings.py file? If you don't Django will keep a record of all you sql statements called. That may be causing your out of memory error. -Alexei Director of Web Development - Farallon Geographics, Inc. - 971.227.3173 On Fri, Oct 4, 2019 at 1:18 AM Shewring, Tom < tom.shewr...@historicengland.org.uk> wrote: > Hi, > > > > Thank you for you your replies. I took a snapshot of the server before I > started the upgrade process. I will roll back to the snapshot and follow > the process Cyrus has detailed. Before I do so, would you be able to > comment on the process I followed and the error I encountered - > > 1) Upgrade Yarn and Node.js to 1.13.0 and 10.15.2 respectively (this > brings the versions of this software up to the same level as the our other > working 4.4.1 environments) > > 2) python -m pip install --upgrade pip > > 3) pip install arches==4.4.1 --upgrade --no-binary :all: (this > completed successfully, upgrading directly from 4.1.1) > > 4) python manage.py migrate – (errors encountered) – is this due to > a lack of memory on the server? – (see final error massage - > django.db.utils.DatabaseError: out of memory for query result) > > > > Operations to perform: > > Apply all migrations: admin, auth, contenttypes, guardian, models, > oauth2_provider, sessions > > Running migrations: > > Applying models.2293_recent_edits... OK > > Applying models.2974_provisionaledits_in_editlog... OK > > Applying models.3098_custom_map_markers... OK > > Applying models.3199_graphmodel_color... OK > > Applying models.3201_remove_node_and_nodetype_branches... OK > > Applying models.3210_card_components... OK > > Applying models.3314_graphmodel_jsonldcontext... OK > > Applying models.3201_replace_node_and_nodetype_branches... OK > > Applying models.3201_second_removal_of_node_nodetype_branch... OK > > Applying models.deserialize_provisional_edits...Traceback (most recent > call last): > > File "manage.py", line 29, in > > execute_from_command_line(sys.argv) > > File > "c:\obap\env4.1.1\lib\site-packages\django\core\management\__init__.py", > line 364, in execute_from_command_line > > utility.execute() > > File > "c:\obap\env4.1.1\lib\site-packages\django\core\management\__init__.py", > line 356, in execute > > self.fetch_command(subcommand).run_from_argv(self.argv) > > File > "c:\obap\env4.1.1\lib\site-packages\django\core\management\base.py", line > 283, in run_from_argv > > self.execute(*args, **cmd_options) > > File > "c:\obap\env4.1.1\lib\site-packages\django\core\management\base.py", line > 330, in execute > > output = self.handle(*args, **options) > > File > "c:\obap\env4.1.1\lib\site-packages\django\core\management\commands\migrate.py", > line 204, in handle > > fake_initial=fake_initial, > > File > "c:\obap\env4.1.1\lib\site-packages\django\db\migrations\executor.py", line > 115, in migrate > > state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, > fake_initial=fake_initial) > > File > "c:\obap\env4.1.1\lib\site-packages\django\db\migrations\executor.py", line > 145, in _migrate_all_forwards > > state = self.apply_migration(state, migration, fake=fake, > fake_initial=fake_initial) > > File > "c:\obap\env4.1.1\lib\site-packages\django\db\migrations\executor.py", line > 244, in apply_migration > > state = migration.apply(state, schema_editor) > > File > "c:\obap\env4.1.1\lib\site-packages\django\db\migrations\migration.py", > line 129, in apply > > operation.database_forwards(self.app_label, schema_editor, old_state, > project_state) > > File > "c:\obap\env4.1.1\lib\site-packages\django\db\migrations\operations\special.py", > line 193, in database_forwards > > self.code(from_state.apps, schema_editor) > > File > "c:\obap\env4.1.1\lib\site-packages\arches\app\models\migrations\deserialize_provisional_edits.py", > line 13, in forwards_func > > for tile in tiles: > > File "c:\obap\env4.1.1\lib\site-packages\django\db\models\query.py", > line 250, in __iter__ > > self._fetch_all() > > File "c:\obap\env4.1.1\lib\site-packages\django\db\models\query.py", > line 1118, in _fetch_all > > self._result_cache = list(self._iterable_class(self)) > > File "c:\obap\env4.1.1\lib\site-packages\django\db\models\query.py", > line 53, in __iter__ > > results = compiler.execute_sql(chunked_fetch=self.chunked_fetch) > > File > "c:\obap\env4.1.1\lib\site-packages\django\db\models\sql\compiler.py", line > 899, in execute_sql > > raise original_exception > > django.db.utils.DatabaseError: out of memory for query result > > > > Thank you > > > > Tom Shewring > > GIS Systems Developer > > IMT Development Centre > > 07748 182134 > > > > IMT Development and Programmes: Together, we enable the celebration of > England’s historic environment by empowering our customers and the public > through technology and innovation. > > > > *From:* Cyrus Hiatt
