Magento integrator – "Killed"

Hi there!

We’re having a bit of a problem with the Magento integrator. We set up an API user with all privileges, installed the Bridge through Magento Connect, verified the installation and set up a channel with an according integration.

It verifies the API credentials just fine and lets us pick the store (i.e. it’s connected correctly), but whenever doing a sync (we picked the 1st of december as we have A LOT of customers and orders), the following is output (this is the output from the console with the -vvv flag, which is the same as in the WebUI in the jobs queue)

[Warning] Attempt number 1 with 5 sec delay. [Warning] Attempt number 2 with 10 sec delay. [Warning] Attempt number 3 with 20 sec delay. Looking for batch Filter applied: website_id key=in; value=1 Filter applied: created_at key=to; value=2014-12-01 00:00:00 Killed

1 2 3 4 5 6 7 8 9

[Warning] Attempt number 1 with 5 sec delay. [Warning] Attempt number 2 with 10 sec delay. [Warning] Attempt number 3 with 20 sec delay. Looking for batch Filter applied: website_id key=in; value=1 Filter applied: created_at key=to; value=2014-12-01 00:00:00 Killed

We didn’t touch it at all; it’s not due to ^C or ^D that it gets killed.

Did you experience anything like this?

Topic

[denckerParticipant]

We’re using Magento CE 1.7.0.2, OroCRM 1.4.1 and Bridge 1.1.4.4. Oro_Api does indeed show up under Settings > Advanced

[Yevhen ShyshkinParticipant]

Hello, dencker.

That’s odd – look’s like sync process was killed directly by your kernel. Possible reason – not enough memory. Please, check your memory limit in php.ini (should be at least 512M, but not -1), and check whether your system has enough free memory.

To check list of processes killed by kernel see /var/log/kern.log or similar file in /var/log. These articles might be helpful:
http://unix.stackexchange.com/questions/10077/where-can-i-see-a-list-of-kernel-killed-processes
http://stackoverflow.com/questions/1853884/when-a-process-is-killed-is-this-information-recorded-anywhere
http://stackoverflow.com/questions/624857/finding-which-process-was-killed-by-linux-oom-killer

[denckerParticipant]

That was what I suspected – apparently I was kinda tired at the time of writing. What I did was just making a 4G swap-file and upping the memory-limit to 1024M. Works like a charm now!

Thank you for your competent answer, Yevhen!

[Author]

Replies