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

    Installing sudo or nano issues?

    Scheduled Pinned Locked Moved pfSense Packages
    pfsensece sudo
    13 Posts 7 Posters 386 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.
    • M
      MrWhatZitTooya666
      last edited by MrWhatZitTooya666

      Why does installing sudo or nano require these other packages be removed.

      [2.8.0-RELEASE]root: pkg install nano
      Updating pfSense-core repository catalogue...
      Fetching meta.conf: 0%
      Fetching data.pkg: 0%
      pfSense-core repository is up to date.
      Updating pfSense repository catalogue...
      Fetching meta.conf: 0%
      Fetching data.pkg: 0%
      pfSense repository is up to date.
      All repositories are up to date.
      The following 5 package(s) will be affected (of 0 checked):

      Installed packages to be REMOVED:
      bind-tools: 9.20.6
      pfSense: 2.8.0.1500029
      protobuf: 28.3,1
      protobuf-c: 1.4.1_7

      New packages to be INSTALLED:
      nano: 8.2 [pfSense]

      Number of packages to be removed: 4
      Number of packages to be installed: 1

      The operation will free 118 MiB.
      1 MiB to be downloaded.

      Proceed with this action? [y/N]: y
      [1/1] Fetching nano-8.2.pkg: 100% 1 MiB 1.1MB/s 00:01
      Checking integrity... done (0 conflicting)
      pkg: Cannot delete vital package: pfSense!
      pkg: If you are sure you want to remove pfSense,
      pkg: unset the 'vital' flag with: pkg set -v 0 pfSense

      patient0P GertjanG S 3 Replies Last reply Reply Quote 0
      • patient0P
        patient0 @MrWhatZitTooya666
        last edited by

        @MrWhatZitTooya666 not sure what you are seeing. What other packages have you installed?

        [2.8.0-RELEASE][root@pfSense.home.arpa]/root: pkg install sudo
Updating pfSense-core repository catalogue...
Fetching meta.conf:   0%
Fetching data.pkg:   0%
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
Fetching meta.conf:   0%
Fetching data.pkg:   0%
pfSense repository is up to date.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
        sudo: 1.9.16p2 [pfSense]

Number of packages to be installed: 1

The process will require 5 MiB more space.
2 MiB to be downloaded.

Proceed with this action? [y/N]: 

        [2.8.0-RELEASE][root@pfSense.home.arpa]/root: pkg install nano
Updating pfSense-core repository catalogue...
Fetching meta.conf:   0%
Fetching data.pkg:   0%
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
Fetching meta.conf:   0%
Fetching data.pkg:   0%
pfSense repository is up to date.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
        nano: 8.2 [pfSense]

Number of packages to be installed: 1

The process will require 3 MiB more space.
1 MiB to be downloaded.

Proceed with this action? [y/N]:
        M 1 Reply Last reply Reply Quote 0
        • GertjanG
          Gertjan @MrWhatZitTooya666
          last edited by

          @MrWhatZitTooya666

          Somewhat comparable with https://forum.netgate.com/topic/198047/main-pfsense-package-is-removed?_=1751879968327 ....

          No "help me" PM's please. Use the forum, the community will thank you.
          Edit : and where are the logs ??

          1 Reply Last reply Reply Quote 0
          • M
            MrWhatZitTooya666 @patient0
            last edited by MrWhatZitTooya666

            @patient0 I am seeing the stuff posted for both nano and sudo. I know I don't need nano just wanted to try and see if it would have the same problem as sudo and it does. Tried installing in GUI first but it failed too. Says I have to remove package pfsense, which would be dumb. I have suricata, system patches, acme, pfblockerng, service watchdog and ntopng installed

            From GUI:

            Installing pfSense-pkg-sudo...
            Updating pfSense-core repository catalogue...
            Fetching meta.conf:
            Fetching data.pkg:
            pfSense-core repository is up to date.
            Updating pfSense repository catalogue...
            Fetching meta.conf:
            Fetching data.pkg:
            pfSense repository is up to date.
            All repositories are up to date.
            Checking integrity... done (0 conflicting)
            The following 6 package(s) will be affected (of 0 checked):

            Installed packages to be REMOVED:
            bind-tools: 9.20.6
            pfSense: 2.8.0.1500029
            protobuf: 28.3,1
            protobuf-c: 1.4.1_7

            New packages to be INSTALLED:
            pfSense-pkg-sudo: 0.3_10 [pfSense]
            sudo: 1.9.16p2 [pfSense]

            Number of packages to be removed: 4
            Number of packages to be installed: 2

            The operation will free 115 MiB.
            Failed

            From SSH:
            /root: pkg install sudo
            Updating pfSense-core repository catalogue...
            Fetching meta.conf: 0%
            Fetching data.pkg: 0%
            pfSense-core repository is up to date.
            Updating pfSense repository catalogue...
            Fetching meta.conf: 0%
            Fetching data.pkg: 0%
            pfSense repository is up to date.
            All repositories are up to date.
            Checking integrity... done (0 conflicting)
            The following 5 package(s) will be affected (of 0 checked):

            Installed packages to be REMOVED:
            bind-tools: 9.20.6
            pfSense: 2.8.0.1500029
            protobuf: 28.3,1
            protobuf-c: 1.4.1_7

            New packages to be INSTALLED:
            sudo: 1.9.16p2 [pfSense]

            Number of packages to be removed: 4
            Number of packages to be installed: 1

            The operation will free 115 MiB.

            Proceed with this action? [y/N]:

            patient0P 1 Reply Last reply Reply Quote 0
            • patient0P
              patient0 @MrWhatZitTooya666
              last edited by

              @MrWhatZitTooya666 Mmmh, I wasn't able to reproduce that issue yet.

              Did you upgrade from CE 2.7.2 or is this a fresh installation of CE 2.8.0?

              M 1 Reply Last reply Reply Quote 0
              • S
                sysfredintech @MrWhatZitTooya666
                last edited by

                @MrWhatZitTooya666 I have the same problem installing the zeek package

                1 Reply Last reply Reply Quote 0
                • M
                  MrWhatZitTooya666 @patient0
                  last edited by MrWhatZitTooya666

                  @patient0 this was an upgrade from 2.7.2ce

                  S 1 Reply Last reply Reply Quote 0
                  • w0wW
                    w0w
                    last edited by

                    Diagnostics - Command Prompt copy/paste and hit execute

                    pkg -vv | awk '/^Repository/{repo=$2} /url/{print repo, $3}'

                    This should return two URLs for core 2.8 and base, both targeting netgate servers.
                    If you see some freebsd servers instead, something or somebody have changed repo.conf

                    johnpozJ M 2 Replies Last reply Reply Quote 0
                    • johnpozJ
                      johnpoz LAYER 8 Global Moderator @w0w
                      last edited by johnpoz

                      So just tested this on my 2.8 since I had it up testing other stuff for another thread. And installing sudo works normally via gui install.

                      >>> Installing pfSense-pkg-sudo...
Updating pfSense-core repository catalogue...
Fetching meta.conf: 
Fetching data.pkg: 
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
Fetching meta.conf: 
Fetching data.pkg: 
pfSense repository is up to date.
All repositories are up to date.
The following 2 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
	pfSense-pkg-sudo: 0.3_10 [pfSense]
	sudo: 1.9.16p2 [pfSense]

Number of packages to be installed: 2

The process will require 5 MiB more space.
2 MiB to be downloaded.
[1/2] Fetching pfSense-pkg-sudo-0.3_10.pkg: . done
[2/2] Fetching sudo-1.9.16p2.pkg: .......... done
Checking integrity... done (0 conflicting)
[1/2] Installing sudo-1.9.16p2...
[1/2] Extracting sudo-1.9.16p2: .......... done
[2/2] Installing pfSense-pkg-sudo-0.3_10...
[2/2] Extracting pfSense-pkg-sudo-0.3_10: ........ done
Saving updated package information...
done.
Loading package configuration... done.
Configuring package components...
Loading package instructions...
Custom commands...
Executing custom_php_install_command()...done.
Executing custom_php_resync_config_command()...done.
Menu items... done.
Writing configuration... done.
>>> Cleaning up cache...done.
Success

                      And nano installed fine as well

                      
[2.8.0-RELEASE][admin@test.mydomain.tld]/root: pkg install nano
Updating pfSense-core repository catalogue...
Fetching meta.conf:   0%
Fetching data.pkg:   0%
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
Fetching meta.conf:   0%
Fetching data.pkg:   0%
pfSense repository is up to date.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
        nano: 8.2 [pfSense]

Number of packages to be installed: 1

The process will require 3 MiB more space.
1 MiB to be downloaded.

Proceed with this action? [y/N]: y
[1/1] Fetching nano-8.2.pkg: 100%    1 MiB   1.1MB/s    00:01    
Checking integrity... done (0 conflicting)
[1/1] Installing nano-8.2...
[1/1] Extracting nano-8.2: 100%
[2.8.0-RELEASE][admin@test.mydomain.tld]/root:

                      My 2.8 vm was a upgrade from 2.7.2

                      An intelligent man is sometimes forced to be drunk to spend time with his fools
                      If you get confused: Listen to the Music Play
                      Please don't Chat/PM me for help, unless mod related
                      SG-4860 24.11 | Lab VMs 2.8, 24.11

                      1 Reply Last reply Reply Quote 0
                      • C
                        chrcoluk
                        last edited by

                        My install already had nano on it on 2.7.2, I did the upgrade keeping all packages, no errors, and nano still works as well.

                        pfSense CE 2.8.0

                        1 Reply Last reply Reply Quote 0
                        • M
                          MrWhatZitTooya666 @w0w
                          last edited by MrWhatZitTooya666

                          @w0w this is what I got

                          /root: pkg -vv | awk '/^Repository/{repo=$2} /url/{print repo, $3}'
                          "pkg+https://pkg.pfsense.org/pfSense_v2_8_0_amd64-core",
                          "pkg+https://pkg.pfsense.org/pfSense_v2_8_0_amd64-pfSense_v2_8_0",

                          I have a snapshot on proxmox from right before I updated to 2.8 if I can't figure out this problem.

                          w0wW 1 Reply Last reply Reply Quote 1
                          • S
                            sysfredintech @MrWhatZitTooya666
                            last edited by

                            @MrWhatZitTooya666 yes it is

                            1 Reply Last reply Reply Quote 0
                            • w0wW
                              w0w @MrWhatZitTooya666
                              last edited by

                              @MrWhatZitTooya666 said in Installing sudo or nano issues?:

                              "pkg+https://pkg.pfsense.org/pfSense_v2_8_0_amd64-core",
                              "pkg+https://pkg.pfsense.org/pfSense_v2_8_0_amd64-pfSense_v2_8_0",

                              looks good.

                              Try Forced pkg Reinstall

                              https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html

                              To forcefully reinstall all packages, take the following steps:

                              • Make a backup
                              • Clean the repository and forcefully reinstall pkg, repo data, and the upgrade script:
                              pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade
                              • Force a reinstall of everything:
                              pkg-static upgrade -f

                              • Review the list of changes and enter y to proceed

                              • Manually reboot the firewall

                              1 Reply Last reply Reply Quote 0
                              • First post
                                Last post
                              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.