Nmap-6.40_2 pkg v1.2 - Failing to Install


  • Banned

    nmap-6.40_2 pkg v1.2

    This is happening on 2 (so far) systems upgrading from 2.1.1 to 2.1.2. One system is x86, other is x64, both 2G NanoBSD VGA.

    When packages try to install on first boot, Nmap fails, other packages install ok.

    After system is done doing initial upgrade stuff and rebooted, Nmap install still fails.

    Issue seems to be that nmap.inc does not end up in /usr/local/pkg.

    If nmap.inc is manually placed (SCP) in /usr/local/pkg after GUI package install attempt (which leaves filesystem mounted as RW anyhow, so you don't need to manually remount) and do an XML GUI components reinstall for Nmap, everything works as expected.

    If not, on next reboot the package tries to reinstall / fix itself, fails to find nmap.inc, and eventually bails and removes any Nmap components that were installed.



  • @ky41083:

    nmap-6.40_2 pkg v1.2

    This is happening on 2 (so far) systems upgrading from 2.1.1 to 2.1.2. One system is x86, other is x64, both 2G NanoBSD VGA.

    When packages try to install on first boot, Nmap fails, other packages install ok.

    After system is done doing initial upgrade stuff and rebooted, Nmap install still fails.

    Issue seems to be that nmap.inc does not end up in /usr/local/pkg.

    If nmap.inc is manually placed (SCP) in /usr/local/pkg after GUI package install attempt (which leaves filesystem mounted as RW anyhow, so you don't need to manually remount) and do an XML GUI components reinstall for Nmap, everything works as expected.

    If not, on next reboot the package tries to reinstall / fix itself, fails to find nmap.inc, and eventually bails and removes any Nmap components that were installed.

    I'm not the package maintainer for nmap, but I can hazard a guess as to what is wrong.  There is most likely an error in the nmap.xml file that should be part of the package.  This file contains a list of all the files required for the GUI package, and has the path on the firewall where they should be stored.  Use your trick to get a successful nmap install and then go look in the file /usr/pkg/nmap.xml (I'm guessing about the exact file name).  That may give you some clues to post on the redmine bug reporting site for pfsense-packages.  That would help the package maintainer fix it.

    Bill


  • Banned

    @bmeeks:

    I'm not the package maintainer for nmap, but I can hazard a guess as to what is wrong.  There is most likely an error in the nmap.xml file that should be part of the package.  This file contains a list of all the files required for the GUI package, and has the path on the firewall where they should be stored.  Use your trick to get a successful nmap install and then go look in the file /usr/pkg/nmap.xml (I'm guessing about the exact file name).  That may give you some clues to post on the redmine bug reporting site for pfsense-packages.  That would help the package maintainer fix it.

    Bill

    Doing exactly that is how I fixed the package ;) There are (as far as I can tell) a few correct references to 1 file in the nmap.xml. It references the correct location (both filesystem and https download) for the nmap.inc file that I had to manually install.


  • Banned

    Also, I'm waiting to see how many others have / comment on having the same issue before going to Redmine.

    The last few legitimate bugs I've reported, I've had to spend more effort arguing that they are indeed bugs, than the effort to actually fix them would have taken.

    Because I was the first person to notice them? Maybe.

    Because the dev(s) that responded seem more concerned with arguing in paragraphs about how they don't exist, rather than actually committing a few lines of code to fix them? Probably.

    Unfortunate as it is, I have more faith in someone noticing it here and just fixing it, or them submitting a ticket, than taking it to Redmine myself, and taking on the role of prosecuting attorney (again) in a courtroom where the defense attorney and judge are one in the same.

    Sad state of development indeed.


  • Rebel Alliance Developer Netgate

    What's the exact set of error(s) that are displayed during the package install process?
    I just completely removed nmap from a VM, made sure the .inc file was gone, and then reinstalled it and it was fine.

    If we can't reproduce a problem, the burden is on the reporter to show that a general problem exists or at least some condition we can replicate and verify.


  • Banned

    No worries, upgrading to 2.1.3 has fixed the issue. Must have been something that got changed in the package or the package system.

    Thanks!

    Edit: Not sure if it matters, but the error message said something pertaining to a missing nmap.inc, install failed, then the install would gracefully back out and perform the nmap uninstall, removing all nmap components. If I can get the exact error message from an un-updated install I will before I update it.