# Nach Migration über Console, Fehler bei messagequeue.sh

**URL:** <https://forum.shopware.com/t/nach-migration-ueber-console-fehler-bei-messagequeue-sh/103163>\
**Category:** Shopware 6 (German)\
**Created:** [29. Februar 2024 um 10:59 UTC](https://forum.shopware.com/t/nach-migration-ueber-console-fehler-bei-messagequeue-sh/103163 "2024-02-29T10:59:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marc\_E](https://avatars.discourse-cdn.com/v4/letter/m/3e96dc/32.png) [@Marc\_E](https://forum.shopware.com/u/Marc_E)\
**Post date:** [29. Februar 2024 um 10:59 UTC](https://forum.shopware.com/t/nach-migration-ueber-console-fehler-bei-messagequeue-sh/103163/1 "2024-02-29T10:59:04Z")

</div>

Hallo,  
nachdem ich eine Migration der Kunden und Bestellung von SW5 auf SW6 über die Console ausgeführt habe bekommen wir über den Cronjob messagequeue.sh im Minutentakt folgende Fehlermeldung:

```auto
[OK] Consuming messages from transport "default".                              

 // The worker will automatically exit once it has exceeded 512M of memory, been
 // running for 55s or received a stop signal via the messenger:stop-workers    
 // command.                                                                    

 // Quit the worker with CONTROL-C.                                             

 // Re-run the command with a -vv option to see logs about consumed messages.   

10:16:25 WARNING [messenger] Error thrown while handling message SwagMigrationAssistant\Migration\MessageQueue\Message\ProcessMediaMessage. Sending for retry #1 using 1000 ms delay. Error: "Handling "SwagMigrationAssistant\Migration\MessageQueue\Message\ProcessMediaMessage" failed: Media for id 018dea2461f6737eaf0d60cdf5723602 not found." ["class" => "SwagMigrationAssistant\Migration\MessageQueue\Message\ProcessMediaMessage","retryCount" => 1,"delay" => 1000,"error" => "Handling "SwagMigrationAssistant\Migration\MessageQueue\Message\ProcessMediaMessage" failed: Media for id 018dea2461f6737eaf0d60cdf5723602 not found.","exception" => Symfony\Component\Messenger\Exception\HandlerFailedException { …}]
10:16:25 CRITICAL [console] Error thrown while running command "messenger:consume default --time-limit=55 --memory-limit=512M". Message: "Malformed UTF-8 characters, possibly incorrectly encoded" ["exception" => Symfony\Component\Serializer\Exception\NotEncodableValueException { …},"command" => "messenger:consume default --time-limit=55 --memory-limit=512M","message" => "Malformed UTF-8 characters, possibly incorrectly encoded"]

In JsonEncode.php line 52:
                                                            
  Malformed UTF-8 characters, possibly incorrectly encoded  
                                                            

messenger:consume [-l|--limit LIMIT] [-f|--failure-limit FAILURE-LIMIT] [-m|--memory-limit MEMORY-LIMIT] [-t|--time-limit TIME-LIMIT] [--sleep SLEEP] [-b|--bus BUS] [--queues QUEUES] [--no-reset] [--] [<receivers>...]

```

Kann mir jemand vielleicht sagen was das ist und wie man den Fehler ggf. beheben kann?

---

<div class="post-metadata">

**Author:** ![Marc\_E](https://avatars.discourse-cdn.com/v4/letter/m/3e96dc/32.png) [@Marc\_E](https://forum.shopware.com/u/Marc_E)\
**Post date:** [4. März 2024 um 07:46 UTC](https://forum.shopware.com/t/nach-migration-ueber-console-fehler-bei-messagequeue-sh/103163/2 "2024-03-04T07:46:13Z")

</div>

Mein Provider hat das memory\_limit von 512 auf 1024 angegeben und gleichzeitig habe ich die Warteschlage der noch ausstehenden Aufgaben zurückgesetzt, jetzt kommt der Fehler nicht mehr.