Package synchronization stuck

[sadortun]

Hi !

I've added a package from a repository where Repman do not have access, and the sync is stuck, and there is no way to delete the package.

Have a good day,
Samuel

[akondas]

Is the consumer runnig? You need to run

bin/console messenger:consume async

[sadortun]

Yes, it's running

[akondas]

Ok then i have to reproduce it. Normally it is so that if an error occurred during synchronization it is displayed on the package list.

[akondas]

Normally in such a situation something like what I shared on this screen follows:

Are you able to share application logs? Or did it happen on our public instance?

[sadortun]

@akondas Yes, i saw this message on later packages due tu access issues.

During the first addition of the package it might be possible that the message consumer was not running.

Sorry, i dont have any logs.

[sadortun]

Ill close this since it's probably only an issue with my incorect initial setup.

[akondas]

consumer was not running

This should not be a problem, when you start the consumer, all the work that was in the queue resumes.

You can try to run:

bin/console messenger:failed:show

[akondas]

@sadortun have you tried bin/console messenger:failed:show? If yes, and still no errors then can we close this? (because at the moment it's difficult to reproduce)

[sadortun]

No i did not. I think we can close this anyway, until we get a better way to reproduce the issue

[sadortun]

Same issue occured again

[akondas]

The next step is the nginx and/or php-fpm logs:

• /var/log/nginx/app_error.log
• /var/log/php7.4-fpm.log

[akondas]

Hey @sadortun, can we also check:

• message consumer logs var/log/consumer.log
• supervisor logs /var/log/supervisor/message-consumer_00-stderr ...

I would like to solve this problem 😉

[akondas]

Thanks @sadortun for your time with. I think we can close it for now. All helpful information on where to look for errors will be included in the new documentation tab: repman-io/repman-docs-pages#13

In case of further news, please feel free to open this issue or create a new one.