Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Once I get on the page on Drupal Reoprts->Brightcove Status Overview clicking on Synch All having an issue:
An error has occurred.
Please continue to the error page
An AJAX HTTP error occurred.
HTTP Result Code: 500
Debugging information follows.
Path: /batch?id=55&op=do_nojs&op=do
StatusText: Internal Server Error
ResponseText:
See attached:
| Comment | File | Size | Author |
|---|---|---|---|
| #13 | brightcove-2858601-13.patch | 3.53 KB | manojapare |
| #11 | sync-api-2858601-11.patch | 1.76 KB | douggreen |
| synch1.jpg | 57.14 KB | nick.prusov | |
| synch.jpg | 132.65 KB | nick.prusov |
Comments
Comment #2
BoobaaCould you please post the relevant parts of your logs? This "500 Internal Server Error" is so generic that we cannot pinpoint your problem.
Comment #3
nick.prusov CreditAttribution: nick.prusov commentedplease advise the path where the logs can be checked
Comment #4
nick.prusov CreditAttribution: nick.prusov commentedComment #5
jan.mashat CreditAttribution: jan.mashat at Pronovix for BrightCove commentedThat depends on the environment, but you're looking for the web server error logs.
On Debian-based systems they can found under: /var/log/apache2/error.log
Comment #6
douggreen CreditAttribution: douggreen at Appnovation for Pfizer, Inc. commentedI get this same error when synchronizing the api client and subscription via the Drupal sync directory, and somewhere along the process, the api key is deleted, but the subscription key is left around. The attached patch solves the problem for me.
Comment #7
douggreen CreditAttribution: douggreen at Appnovation for Pfizer, Inc. commentedUpdated patch doesn't throw an exception on error, because the exception causes the config import to fail hard instead of gracefully.
Comment #8
jribeiro CreditAttribution: jribeiro for Pfizer, Inc. commentedJust a patch re-roll.
Comment #9
douggreen CreditAttribution: douggreen at Appnovation for Pfizer, Inc. commented-8 is the better roll that doesn't assume other patches.
This re-roll assumes other patches that we're applying. I think 7 is still the best choice.Comment #10
douggreen CreditAttribution: douggreen at Appnovation for Pfizer, Inc. commentedWe're having problems apply the 4 Brightcove patches needed, so the following attached patch rolls two of them together. You should probably still use -8 above. See #2902537: Can't synchronize subscription
Comment #11
douggreen CreditAttribution: douggreen at Appnovation for Pfizer, Inc. commentedUpdated patch to latest head.
Comment #12
douggreen CreditAttribution: douggreen at Appnovation for Pfizer, Inc. commentedComment #13
manojapare CreditAttribution: manojapare as a volunteer and commentedPatch which worked for me, module version 8.x-1.3.
Comment #14
yce CreditAttribution: yce at Pronovix for BrightCove commentedIs it still an issue? The subscriptions are no longer config entities, so they won't get exported to configuration.
Also in the latest dev version the queues are getting cleared when an API client is deleted, so there shouldn't be any null references left when synching the entities.
Comment #15
yce CreditAttribution: yce at Pronovix for BrightCove commentedClosing as there is no feedback, cannot reproduce.