Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    Linux proget "Feeds_SetLastSyncDate does not exist"

    Scheduled Pinned Locked Moved Support
    postgresqlprogetlinux
    2 Posts 1 Posters 13 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ? This user is from outside of this forum
      Guest
      last edited by

      Running Linux proget 4.6.7, when attempting to configure replication from an external feed returns a 500 error, pasted below. I don't see this mentioned in any release notes so I haven't upgraded yet to find out if there's an existing fix.

      When it comes to upgrading proget using the docker container, will a new container spinning up perform all necessary DB updates? In that case, should all other hosts be shut down prior to launching a new version of the container? I don't see any specific guidance on how to correctly perform an upgrade other than shutting down one container and spinning up another. Let me know if this should be a separate question, but I know I'll need to perform that to apply any fix.

      Npgsql.PostgresException
      42883: function Feeds_SetLastSyncDate(@Feed_Id => integer, @LastSync_Date => timestamp without time zone, session_user_name => text) does not exist
      
      Description: HTTP 500.Error processing request.
      Details: Non-web exception. Exception origin (name of application or object): mscorlib.
      Exception stack trace:
        at Npgsql.NpgsqlConnector.DoReadMessage (Npgsql.DataRowLoadingMode dataRowLoadingMode, System.Boolean isPrependedMessage) [0x000bc] in <4985dea8374f4819bebb7847d95ad483>:0 
        at Npgsql.NpgsqlConnector.ReadMessageWithPrepended (Npgsql.DataRowLoadingMode dataRowLoadingMode) [0x00056] in <4985dea8374f4819bebb7847d95ad483>:0 
      --- End of stack trace from previous location where exception was thrown ---
        at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <8f2c484307284b51944a1a13a14c0266>:0 
        at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <8f2c484307284b51944a1a13a14c0266>:0 
        at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <8f2c484307284b51944a1a13a14c0266>:0 
        at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <8f2c484307284b51944a1a13a14c0266>:0 
        at System.Runtime.CompilerServices.TaskAwaiter.GetResult () [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0 
        at System.Web.TaskAsyncResult.Wait (System.IAsyncResult result) [0x0003a] in <79d7580b4e46487286a5f8386a98413d>:0 
        at System.Web.HttpTaskAsyncHandler.System.Web.IHttpAsyncHandler.EndProcessRequest (System.IAsyncResult result) [0x00000] in <79d7580b4e46487286a5f8386a98413d>:0 
        at Inedo.Web.Handlers.AsyncHandlerWrapper.EndProcessRequest (System.IAsyncResult result) [0x00000] in <23fdb4c7144946fa87eea57c7dd622b3>:0 
        at System.Web.HttpApplication.async_handler_complete_cb (System.IAsyncResult ar) [0x0001e] in <79d7580b4e46487286a5f8386a98413d>:0 
      

      Product: ProGet
      Version: 4.6.7

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        Thanks for the bug report. This will be fixed in v4.7.2, which should be released today.

        To upgrade, see the "Upgrading to a new version" section of this KB article:

        http://inedo.com/support/kb/1100/getting-started-with-proget-for-linux

        Basically though, when the container starts up it makes sure the database schema version is current, so all you really need to do is run the new container and point to the same data.

        1 Reply Last reply Reply Quote 0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        • 1 / 1
        • First post
          Last post
        Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation