[SOLVED] Package installer incorrectly reporting failure
-
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.
-
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.
-
I'm seeing same behaviour in this morning's build.
-
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!
-
-
[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.
-
bump
-
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.
-
Would you please run: "pkg clean -ay" from the command line to clear the package cache?
-
Would you please run: "pkg clean -ay" from the command line to clear the package cache?
Done.
-
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?
-
Oops. Should have said - no, same behaviour after cleaning the cache. Will grab the updated php file and try again.
-
Assuming you mean commit 3985bb3 in github, that does make it report success. Thnx.
[Solved]
-
Cool. Thank you for testing.
We have passed the "pkg" bug report upstream.