migrate stalled out
jde
to have stalled out. I've been waiting about 35 minutes with no
change. Below is the command and output:
# php -d memory_limit=2G symfony propel:migrate /var/www/icaatom-1.1/
data/fixtures/datadump_20111214.yml
PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib64/
php/modules/imagick.so' - /usr/lib64/php/modules/imagick.so: undefined
symbol: php_set_error_handling in Unknown on line 0
PHP Warning: date(): It is not safe to rely on the system's timezone
settings. You are *required* to use the date.timezone setting or the
date_default_timezone_set() function. In case you used any of those
methods and you are still getting this warning, you most likely
misspelled the timezone identifier. We selected 'America/Los_Angeles'
for 'PST/-8.0/no DST' instead in /var/www/icaatom-1.2.0/vendor/symfony/
lib/config/sfRootConfigHandler.class.php on line 91
>> migrate Initial data version 62
Does it just take a long time, or should I be seeing something else by
now?
Also, if you have suggestions to resolve the warnings in the output
above, I'd be happy to hear those too.
Thank you,
Jill Earles
jde
>> migrate Data migrated to Release 1.1 v75
and then the path it was written to.
Does this mean it did not migrate to be compatible with
icaatom-1.2.0? I ran the command from my 1.2.0 directory, but with a
path to the data dump that was in the 1.1 directory.
David Juhasz
> Apparently it's still running. Just got additional output:
>>> migrate Data migrated to Release 1.1 v75
> and then the path it was written to.
>
> Does this mean it did not migrate to be compatible with
> icaatom-1.2.0? I ran the command from my 1.2.0 directory, but with a
> path to the data dump that was in the 1.1 directory.
No, that's perfect Jill, it's just a glitch in the output - Release 1.1
v75 = Release 1.2. :)
I'm surprised it took that long though, it usually only takes a few
minutes. Maybe you have a very large database?
As for the error messages (if you are still interested. I typed them up
in response to your first post):
What OS are you running? To get rid of the "imagick.so" error in Ubuntu
or Debian Linux you can install the PHP imagemagick library using:
sudo apt-get install php5-imagick
To get rid of the date warning you need to set a timezone in the php
configuration file, see
<http://php.net/manual/en/datetime.configuration.php>
Regards,
David
--
David Juhasz,
Software Engineer
Artefactual Systems Inc.
www.artefactual.com
jde
running after almost 3 hours.
This is running on Ubuntu 10.04. I'll try the things you mentioned
once the data load is complete.
Thank you!
Jill
jde
it and start again. The propel load data task has now been running
for about 2.5 hours, and when I check the database via phpmyadmin, I
can see that there are no records in any of the tables. I'm not
seeing any errors in the mysql or apache logs, and the output from the
data load command isn't showing anything.
The last command I issed was:
nohup php -d memory_limit=50000M symfony propel:data-load data/
fixtures/migrated_data_20111214125840.yml
nohup: appending output to `nohup.out'
And the output in nohup.out is:
PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib64/
php/modules/imagick.so' - /usr/lib64/php/modules/imagick.so: undefined
symbol: php_set_error_handling in Unknown on line 0
>> propel load data from "data/fixtures/migrated_data_20111214125840.yml"
Do you have any suggestions for how to determine what's wrong, or how
to get the migrated data into the database?
Thank you!
Jill
jde
It's RHEL 5.6.
jde
migrated_data_20111214125840.yml file is just under 63 MB.
David Juhasz
I recommend disabling the search index when doing the data load:
http://www.qubit-toolkit.org/wiki/index.php?title=Search#Disabling_the_search_index_for_Release_1.2
I've added a note to this effect to the upgrading documentation:
http://www.qubit-toolkit.org/wiki/index.php?title=Upgrading#Load_migrated_data
Regards,
David Juhasz
jde
I disabled the search index and tried loading the migrated data again.
MySQL crashed and could not restart, so I had to uninstall and
reinstall it again. This has happened a few times as I've attempted
this. Any idea what would cause this?
Regards,Jill
> I recommend disabling the search index when doing thedataload:http://www.qubit-toolkit.org/wiki/index.php?title=Search#Disabling_th...
>
> I've added a note to this effect to the upgrading documentation:http://www.qubit-toolkit.org/wiki/index.php?title=Upgrading#Load_migr...
> Regards,
> David Juhasz
>
> On 11-12-15 12:54 PM, jde wrote:
>
>
>
>
>
>
>
>
>
> > Also, in case it helps, the size of the
> > migrated_data_20111214125840.yml file is just under 63 MB.
>
> > On Dec 15, 12:33 pm, jde<jilldenaeear...@gmail.com> wrote:
> >> P.S. I was wrong about the OS (confused this with anotherserver).
> >> It's RHEL 5.6.
>
> >> On Dec 15, 12:30 pm, jde<jilldenaeear...@gmail.com> wrote:
>
> >>> it and start again. The propelloaddatatask has now been running
> >>> can see that there are no records in any of the tables. I'm not
> >>>dataloadcommand isn't showing anything.
> >>> nohup php -d memory_limit=50000M symfony propel:data-loaddata/
> >>> fixtures/migrated_data_20111214125840.yml
> >>> nohup: appending output to `nohup.out'
> >>> And the output in nohup.out is:
> >>> symbol: php_set_error_handling in Unknown on line 0
> >>>> Yes, it seems to be a very large database - thedataloadis still
> >>>> This is running on Ubuntu 10.04. I'll try the things you mentioned
> >>>> Jill
> >>>> On Dec 14, 1:23 pm, David Juhasz<da...@artefactual.com> wrote:
> >>>>> On 11-12-14 01:02 PM, jde wrote:
> >>>>>> Apparently it's still running. Just got additional output:
> >>>>>> Does this mean it did not migrate to be compatible with
> >>>>>> icaatom-1.2.0? I ran the command from my 1.2.0 directory, but with a
jde
https://groups.google.com/group/ica-atom-users/msg/2a25fa367d0bc0d9?hl=en,
that indicates that it might be. My YAML file for the migrated data
is close to 63M. That message says they needed 12G of RAM for a 53M
YAML file. Will I need that much RAM or more to get this to work?
On Jan 5, 10:07 am, jde <jilldenaeear...@gmail.com> wrote:
> Hi David,
> I disabled the search index and tried loading the migrateddataagain.
jde
Unable to execute INSERT statement. [wrapped: SQLSTATE[HY000]: General
error: 2006 MySQL server has gone away]
On Jan 5, 1:44 pm, jde <jilldenaeear...@gmail.com> wrote:
> Could this be a RAM issue? I saw something in this message:https://groups.google.com/group/ica-atom-users/msg/2a25fa367d0bc0d9?h...,
Jesús García Crespo
--
You received this message because you are subscribed to the Google Groups "ICA-AtoM Users" group.
To post to this group, send email to ica-ato...@googlegroups.com.
To unsubscribe from this group, send email to ica-atom-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/ica-atom-users?hl=en.
Jesús García Crespo,
Software Engineer, Artefactual Systems Inc.
http://www.artefactual.com | +1.604.527.2056