Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Mike Chadwick 32 posts 131 karma points
    1 week ago
    Mike Chadwick
    0

    Response status code does not indicate success: 500 (Internal Server Error).

    Hi Kevin,

    I've been using uSync Complete with my clients solution very happily. Its a great tool. Recently its started throwing this error when trying to publish anything from development to staging:

    Response status code does not indicate success: 500 (Internal Server Error).

    I'm struggling a little to debug the cause of this and see what the issue is from the exception below.

    I'm wondering if something is failing or perhaps its timing out. Can you recommend a way I can debug this and find the cause?

    Much appreciated, thanks,

    Mike


    Full Error:
    Response status code does not indicate success: 500 (Internal Server Error). at uSync.Publisher.Publishers.SyncRealTimeStepPublisher.

  • Kevin Jump 1818 posts 11658 karma points MVP 4x c-trib
    1 week ago
    Kevin Jump
    0

    Hi Mike,

    that doesn't sound ideal :(

    when its a 500 error it is likely coming from the staging server (and being passed through to you on dev) so the error is probably in the logs on the stage server.

    as its a 500 there should be something logged in the umbraco logs - but if you can't find anything you can turn the logging level up to debug

    if you add the following to the config/serilog.config file

    <add key="serilog:minimum-level:override:uSync" value="Debug" />
    

    you will get more of logging (you might have to restart the site, as just changing this log file doesn't trigger a reloading of umbraco)

  • Mike Chadwick 32 posts 131 karma points
    1 week ago
    Mike Chadwick
    0

    Thanks Kevin! Will have to continue to dig :-)

  • Mike Chadwick 32 posts 131 karma points
    1 week ago
    Mike Chadwick
    0

    Hi Kevin,

    So I managed to get it running again, I added an executionTimeout to httpRuntime in web.config and it stopped throwing 500 error.

    However, it is now running but it reports everytime I try to publish something that nothing needs to be updated and is completely in sync when it clearly isn't. We're on v8.6.3.0.

    Can you recommend a way to reset it, any procedure we can do, work arounds or advice to resolve?

    Thanks in advance,

    Mike

  • Kevin Jump 1818 posts 11658 karma points MVP 4x c-trib
    1 week ago
    Kevin Jump
    0

    Hi Mike,

    There isn't really a reset process, each publish process is self contained so there are no files reused etc :(

    for tidyness you could take a look at the health checkes, there should be some uSync health checks that will clean up failed publishes, but these won't affect new ones.

    With timeouts i would suggest you try a smaller publish, maybe with fewer options, unchecking include dependencies? or unselecting "Delete missing items" will have the largest impact on times.

    this is something we've are worked on for the next release (uSync.Complete 8.9-rc) which is in release candidate stage - i wouldn't say put it on a live site, but if you have a place to test this might help./

  • Mike Chadwick 32 posts 131 karma points
    1 week ago
    Mike Chadwick
    0

    Hi Kevin,

    Thanks for you response. I resolved the timeout issue by adding

    But my question was more asking if you've seen before the publisher saying nothing needs to be imported when it actually does? Its doing everything right apart from its gets to the final publish bit and it says nothing needs to be updated? Very odd indeed.

    If you have seen before and have any advice that would be great. I'm also checking everything infrastructure and configuration wise...

    Thanks in advance!

    Mike

  • Mike Chadwick 32 posts 131 karma points
    1 week ago
    Mike Chadwick
    101

    Hi Kevin,

    Good news. It turned out that after some investigation the infrastructure team had configured multiple instances on azure webapps on the development and staging environments, not realising the impact that would have. By scaling back down to 1 instance on each environment problem solved.

    Thanks for you help!

    Mike

  • Kevin Jump 1818 posts 11658 karma points MVP 4x c-trib
    1 week ago
    Kevin Jump
    1

    Oh, that sounds tricksy .

    the base uSync package already detects if it is running loadbalnaced (and not the master) maybe we should do this for publisher too? we could return something then. like 'the site is loadbalanced, so nothing will be updated '.

  • Mike Chadwick 32 posts 131 karma points
    1 week ago
    Mike Chadwick
    0

    Yeah good idea or maybe flag a warning. It must have been creating the package to upload, uploading it to the filesystem somewhere and then switching to another random instance to upload it and nothing there.

    Umbraco backoffice doesn't like to be load balanced either :-)

    Glad to resolve it anyway.

    Cheers

    Mike

Please Sign in or register to post replies

Write your reply to:

Draft