Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

    [SOLVED] Package installer incorrectly reporting failure

    2.3-RC Snapshot Feedback and Issues - ARCHIVED
    3
    14
    1458
    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.
    • P
      PantsManUK last edited by

      Running 2.3-ALPHA 20151021, after every package install I've tried thus far, the GUI reports failure, while the package log shows success.

      (Loving the new GUI BTW)
      ![Screen Shot 2015-10-26 at 11.27.29.png](/public/imported_attachments/1/Screen Shot 2015-10-26 at 11.27.29.png)
      ![Screen Shot 2015-10-26 at 11.27.29.png_thumb](/public/imported_attachments/1/Screen Shot 2015-10-26 at 11.27.29.png_thumb)

      1 Reply Last reply Reply Quote 0
      • P
        phil.davis last edited by

        My test system is running 2.3-ALPHA (amd64) built on Sat Oct 24 00:24:51 CDT 2015

        I just installed the same arping package and got success everywhere.

        Renato was doing a bunch of work on that in the last week - I guess the 20151021 snapshot had code in a not-so-good state. I would try a newer snapshot.

        By the way, there was some code just committed that makes the package installer work correctly for the reinstall-all case as well. So it would be good to use a snapshot that was built within the last few hours or later.

        As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
        If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

        1 Reply Last reply Reply Quote 0
        • P
          PantsManUK last edited by

          @phil.davis:

          By the way, there was some code just committed that makes the package installer work correctly for the reinstall-all case as well. So it would be good to use a snapshot that was built within the last few hours or later.

          Will do Phil. Thnx for the reply.

          1 Reply Last reply Reply Quote 0
          • P
            PantsManUK last edited by

            I'm seeing same behaviour in this morning's build.

            1 Reply Last reply Reply Quote 0
            • S
              Steve_B Developer Netgate last edited by

              I have not been able to reproduce this either.

              Would you mind running another installation please and then posting the last few lines from the files:

              • /tmp/webgui-log.txt

              • /tmp/webgui-log.json

              That should provide some clues.

              Thanks!

              Als ik kan

              1 Reply Last reply Reply Quote 0
              • P
                PantsManUK last edited by

                [2.3-ALPHA][root@pfSense.pantsmanuk.org]/root: tail /tmp/webgui-log.txt 
                	pfSense-pkg-AutoConfigBackup: 1.29 [pfSense]
                
                The process will require 49 KiB more space.
                10 KiB to be downloaded.
                Fetching pfSense-pkg-AutoConfigBackup-1.29.txz: . done
                Checking integrity... done (0 conflicting)
                [1/1] Installing pfSense-pkg-AutoConfigBackup-1.29...
                [1/1] Extracting pfSense-pkg-AutoConfigBackup-1.29: ......... done
                >>> Cleaning up cache... done.
                __RC=0
                
                
                [2.3-ALPHA][root@pfSense.pantsmanuk.org]/root: tail /tmp/webgui-log.json 
                { "type": "INFO_PROGRESS_TICK", "data": { "current": 3, "total" : 0}}
                { "type": "INFO_PROGRESS_TICK", "data": { "current": 4, "total" : 0}}
                { "type": "INFO_PROGRESS_TICK", "data": { "current": 5, "total" : 0}}
                { "type": "INFO_PROGRESS_TICK", "data": { "current": 6, "total" : 0}}
                { "type": "INFO_PROGRESS_TICK", "data": { "current": 7, "total" : 0}}
                { "type": "INFO_PROGRESS_TICK", "data": { "current": 8, "total" : 0}}
                { "type": "INFO_PROGRESS_TICK", "data": { "current": 9, "total" : 0}}
                { "type": "INFO_PROGRESS_TICK", "data": { "current": 9, "total" : 0}}
                { "type": "INFO_EXTRACT_FINISHED", "data": { "pkgname": "pfSense-pkg-AutoConfigBackup", "pkgversion": "1.29"}}
                { "type": "INFO_INSTALL_FINISHED", "data": { "pkgname": "pfSense-pkg-AutoConfigBackup", "pkgversion": "1.29", "message": ""}}
                

                Note: This was against a brand new install of today's build of full memstick i386 (2015-10-27T02:26). Same behaviour exhibited.

                1 Reply Last reply Reply Quote 0
                • P
                  PantsManUK last edited by

                  bump

                  1 Reply Last reply Reply Quote 0
                  • S
                    Steve_B Developer Netgate last edited by

                    Thanks for that. The problem is that for some reason your system is reporting that 9 steps of 0 required have been completed:

                    { "type": "INFO_PROGRESS_TICK", "data": { "current": 9, "total" : 0}}

                    and the code is looking for $current == $total to call it a success.

                    We will investigate.

                    Als ik kan

                    1 Reply Last reply Reply Quote 0
                    • S
                      Steve_B Developer Netgate last edited by

                      Would you please run:  "pkg clean -ay" from the command line to clear the package cache?

                      Als ik kan

                      1 Reply Last reply Reply Quote 0
                      • P
                        PantsManUK last edited by

                        @Steve_B:

                        Would you please run:  "pkg clean -ay" from the command line to clear the package cache?

                        Done.

                        1 Reply Last reply Reply Quote 0
                        • S
                          Steve_B Developer Netgate last edited by

                          Did it help?

                          We think this may be a bug in the pkg system. I have just made a change to pkg_mgr_install.php to accommodate it.

                          Would you please test before and after syncing?

                          Als ik kan

                          1 Reply Last reply Reply Quote 0
                          • P
                            PantsManUK last edited by

                            Oops. Should have said - no, same behaviour after cleaning the cache. Will grab the updated php file and try again.

                            1 Reply Last reply Reply Quote 0
                            • P
                              PantsManUK last edited by

                              Assuming you mean commit 3985bb3 in github, that does make it report success. Thnx.

                              [Solved]

                              1 Reply Last reply Reply Quote 0
                              • S
                                Steve_B Developer Netgate last edited by

                                Cool. Thank you for testing.

                                We have passed the "pkg" bug report upstream.

                                Als ik kan

                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post