Migration from v4 to v5 memory problems

After migration we have many problems with allocated memory for PHP, a problem with DB same, was exceeded max limit of memory and we fix this. But now we have problems with queu_workers when we trying to migrate. At some point, migration fails and stops. After it on new version Invoices and clients are ok, but credits and payments are not full. Error in logs are:

2022-02-01T15:54:00+00:00] Execution #61 output:
app_1 | No scheduled commands are ready to run.
app_1 | [2022-02-01 15:54:57][62] Processed: App\Jobs\Util\StartMigration
app_1 | 2022-02-01 15:54:58,070 INFO exited: queue-worker_00 (exit status 12; not expected)
app_1 | 2022-02-01 15:54:59,076 INFO spawned: ‘queue-worker_00’ with pid 536
app_1 | Processing Event: ver:3.0 server:supervisor serial:0 pool:shutdown poolserial:0 eventname:PROCESS_STATE_EXITED len:87
app_1 | 2022-02-01 15:54:59,080 WARN received SIGQUIT indicating exit request
app_1 | 2022-02-01 15:54:59,082 INFO waiting for shutdown, php-fpm, queue-worker_00, queue-worker_01, scheduler to die
app_1 | 2022-02-01 15:54:59,087 INFO stopped: scheduler (terminated by SIGTERM)
db_1 | 2022-02-01T15:54:59.107731Z 6 [Note] Aborted connection 6 to db: ‘ninja’ user: ‘ninja’ (Got an error reading communication packets)
app_1 | 2022-02-01 15:54:59,108 INFO stopped: queue-worker_01 (terminated by SIGTERM)
app_1 | [2022-02-01 15:54:59][64] Processing: App\Jobs\Util\VersionCheck
app_1 | [2022-02-01 15:55:00][64] Processed: App\Jobs\Util\VersionCheck
app_1 | 2022-02-01 15:55:02,330 INFO waiting for shutdown, php-fpm, queue-worker_00 to die
app_1 | 2022-02-01 15:55:05,335 INFO waiting for shutdown, php-fpm, queue-worker_00 to die
app_1 | 2022-02-01 15:55:08,339 INFO waiting for shutdown, php-fpm, queue-worker_00 to die
app_1 | 2022-02-01 15:55:09,340 WARN killing ‘queue-worker_00’ (536) with SIGKILL
app_1 | 2022-02-01 15:55:09,350 INFO stopped: queue-worker_00 (terminated by SIGKILL)
db_1 | 2022-02-01T15:55:09.361266Z 68 [Note] Aborted connection 68 to db: ‘ninja’ user: ‘ninja’ (Got an error reading communication packets)
app_1 | [01-Feb-2022 15:55:09] NOTICE: Terminating …
app_1 | [01-Feb-2022 15:55:09] NOTICE: exiting, bye-bye!
app_1 | 2022-02-01 15:55:09,387 INFO stopped: php-fpm (exit status 0)
app_1 | 2022-02-01 15:55:09,389 INFO stopped: shutdown (terminated by SIGTERM)
app_1 | 2022-02-01T15:55:11Z [INFO] [Entrypoint]: Initialising Invoice Ninja…
app_1 | Configuration cache cleared!
app_1 | Configuration cached successfully!
app_1 | Configuration cache cleared!
app_1 | Configuration cached successfully!
app_1 | Route cache cleared!
app_1 | Routes cached successfully!
app_1 | Files cached successfully!
app_1 | Nothing to migrate.

| 2022-02-01 15:55:15,347 WARN For [program:php-fpm], redirect_stderr=true but stderr_logfile has also been set to a filename, the filename has been ignored
app_1 | 2022-02-01 15:55:15,347 WARN For [program:scheduler], redirect_stderr=true but stderr_logfile has also been set to a filename, the filename has been ignored
app_1 | 2022-02-01 15:55:15,348 WARN For [program:queue-worker], redirect_stderr=true but stderr_logfile has also been set to a filename, the filename has been ignored
app_1 | 2022-02-01 15:55:15,348 WARN For [program:queue-worker], redirect_stderr=true but stderr_logfile has also been set to a filename, the filename has been ignored
app_1 | 2022-02-01 15:55:15,353 INFO supervisord started with pid 1
app_1 | 2022-02-01 15:55:16,358 INFO spawned: ‘shutdown’ with pid 72
app_1 | 2022-02-01 15:55:16,363 INFO spawned: ‘php-fpm’ with pid 73
app_1 | 2022-02-01 15:55:16,368 INFO spawned: ‘queue-worker_00’ with pid 74
app_1 | 2022-02-01 15:55:16,373 INFO spawned: ‘queue-worker_01’ with pid 75
app_1 | 2022-02-01 15:55:16,392 INFO spawned: ‘scheduler’ with pid 76
app_1 | READY
app_1 | [01-Feb-2022 15:55:16] NOTICE: [pool www] ‘user’ directive is ignored when FPM is not running as root
app_1 | [01-Feb-2022 15:55:16] NOTICE: [pool www] ‘user’ directive is ignored when FPM is not running as root
app_1 | [01-Feb-2022 15:55:16] NOTICE: [pool www] ‘group’ directive is ignored when FPM is not running as root
app_1 | [01-Feb-2022 15:55:16] NOTICE: [pool www] ‘group’ directive is ignored when FPM is not running as root
app_1 | [01-Feb-2022 15:55:16] NOTICE: fpm is running, pid 73
app_1 | [01-Feb-2022 15:55:16] NOTICE: ready to handle connections
app_1 | Schedule worker started successfully.
app_1 | 2022-02-01 15:55:18,027 INFO success: shutdown entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
app_1 | 2022-02-01 15:55:18,027 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
app_1 | 2022-02-01 15:55:18,028 INFO success: queue-worker_00 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
app_1 | 2022-02-01 15:55:18,029 INFO success: queue-worker_01 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
app_1 | 2022-02-01 15:55:18,029 INFO success: scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

Looking for help, thank you!

Hi,

@david do you have any thoughts?

1 Like