pfSense Support Subscription

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Renato Botelho

Pages: [1] 2 3 4 5 ... 18
1
Post a bounty / Re: Slow Web GUI with many VLAN Interfaces - 300$
« on: November 06, 2017, 05:01:57 am »
Has this been fixed in 2.4.1?

not officially, my fixes should work.

Can you please submit a Pull Request on https://github.com/pfsense/pfsense so we can review and merge the fixes?

2
2.4 Development Snapshots / Re: Update issues
« on: October 06, 2017, 05:28:26 am »
I'm having the exact same problem. I'm currently on 2.4.0.r.20171003.1349. It says the Latest Base System is 2.4.0.r.20171004.0814. When cat /cf/conf/upgrade_log.txt, all it says is "2.4.0.r.20171004.0814 version of pfSense is available"

Attached is a capture of the console log when I try to update.

If your system is still in this state can you please run following commands and send me output?

# pkg -ddd upgrade -n
# pkg -ddd upgrade -Fn

Thanks

I ran those two commands and the output is attached.

If you didn't upgrade it, could you send me the content of /var/db/pkg from this machine? Files inside this directory don't contain sensitive data and maybe they could help me to reproduce it internally. If it's possible please send to my email renato at pfsense dot org

Thank you

3
2.4 Development Snapshots / Re: Update issues
« on: October 05, 2017, 03:21:16 pm »
I'm having the exact same problem. I'm currently on 2.4.0.r.20171003.1349. It says the Latest Base System is 2.4.0.r.20171004.0814. When cat /cf/conf/upgrade_log.txt, all it says is "2.4.0.r.20171004.0814 version of pfSense is available"

Attached is a capture of the console log when I try to update.

If your system is still in this state can you please run following commands and send me output?

# pkg -ddd upgrade -n
# pkg -ddd upgrade -Fn

Thanks

If you still have the possibility of run this test for me, please add an extra -d to have more debug. It's hard to reproduce the problem

# pkg -dddd upgrade -n
# pkg -dddd upgrade -Fn

4
2.4 Development Snapshots / Re: Update issues
« on: October 05, 2017, 10:58:00 am »
It works just fine over SSH.

Code: [Select]
Enter an option: 13

>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
The following 27 package(s) will be affected (of 0 checked):

Installed packages to be REMOVED:
        pecl-rrd-1.1.3_4

New packages to be INSTALLED:
        pecl-rrd1: 1.1.3 [pfSense]

Installed packages to be UPGRADED:
        unbound: 1.6.3 -> 1.6.6 [pfSense]
        strongswan: 5.5.3 -> 5.6.0 [pfSense]
        sqlite3: 3.20.0_1 -> 3.20.1_1 [pfSense]
        rrdtool: 1.6.0_1 -> 1.7.0_1 [pfSense]
        python27: 2.7.13_7 -> 2.7.14 [pfSense]
        postgresql95-client: 9.5.8_1 -> 9.5.9 [pfSense]
        pfSense-default-config: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core]
        pfSense-base: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core]
        pfSense: 2.4.0.r.20171003.1203 -> 2.4.0.r.20171004.0814 [pfSense]
        pear: 1.10.3 -> 1.10.5 [pfSense]
        nginx: 1.12.1,2 -> 1.12.1_1,2 [pfSense]
        mysql56-client: 5.6.37 -> 5.6.37_1 [pfSense]
        mpd5: 5.8_1 -> 5.8_2 [pfSense]
        libzmq4: 4.1.5 -> 4.2.2 [pfSense]
        libnghttp2: 1.23.1 -> 1.26.0 [pfSense]
        liblz4: 1.7.5,1 -> 1.8.0,1 [pfSense]
        libidn2: 2.0.3 -> 2.0.4 [pfSense]
        libiconv: 1.14_10 -> 1.14_11 [pfSense]
        libffi: 3.2.1 -> 3.2.1_1 [pfSense]
        isc-dhcp43-server: 4.3.5 -> 4.3.6_1 [pfSense]
        isc-dhcp43-relay: 4.3.5 -> 4.3.6 [pfSense]
        isc-dhcp43-client: 4.3.5 -> 4.3.6 [pfSense]
        glib: 2.50.2_3,1 -> 2.50.2_6,1 [pfSense]

Installed packages to be REINSTALLED:
        pkg-1.10.1_1 [pfSense]
        pfSense-Status_Monitoring-1.7.2 [pfSense] (direct dependency changed: pecl-rrd1)

Number of packages to be removed: 1
Number of packages to be installed: 1
Number of packages to be upgraded: 23
Number of packages to be reinstalled: 2

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

**** WARNING ****
Reboot will be required!!
Proceed with upgrade? (y/N) y
>>> Downloading upgrade packages...
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
Checking for upgrades (25 candidates): .......... done
Processing candidates (25 candidates): .......... done
Checking integrity... done (1 conflicting)
  - pecl-rrd1-1.1.3 [pfSense] conflicts with pecl-rrd-1.1.3_4 [installed] on /usr/local/lib/php/20131226/rrd.so
Checking integrity... done (0 conflicting)
The following 26 package(s) will be affected (of 0 checked):

Installed packages to be REMOVED:
        pecl-rrd-1.1.3_4

New packages to be INSTALLED:
        pecl-rrd1: 1.1.3 [pfSense]

Installed packages to be UPGRADED:
        unbound: 1.6.3 -> 1.6.6 [pfSense]
        strongswan: 5.5.3 -> 5.6.0 [pfSense]
        sqlite3: 3.20.0_1 -> 3.20.1_1 [pfSense]
        rrdtool: 1.6.0_1 -> 1.7.0_1 [pfSense]
        python27: 2.7.13_7 -> 2.7.14 [pfSense]
        postgresql95-client: 9.5.8_1 -> 9.5.9 [pfSense]
        pfSense-default-config: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core]
        pfSense-base: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core]
        pfSense: 2.4.0.r.20171003.1203 -> 2.4.0.r.20171004.0814 [pfSense]
        pear: 1.10.3 -> 1.10.5 [pfSense]
        nginx: 1.12.1,2 -> 1.12.1_1,2 [pfSense]
        mysql56-client: 5.6.37 -> 5.6.37_1 [pfSense]
        mpd5: 5.8_1 -> 5.8_2 [pfSense]
        libzmq4: 4.1.5 -> 4.2.2 [pfSense]
        libnghttp2: 1.23.1 -> 1.26.0 [pfSense]
        liblz4: 1.7.5,1 -> 1.8.0,1 [pfSense]
        libidn2: 2.0.3 -> 2.0.4 [pfSense]
        libiconv: 1.14_10 -> 1.14_11 [pfSense]
        libffi: 3.2.1 -> 3.2.1_1 [pfSense]
        isc-dhcp43-server: 4.3.5 -> 4.3.6_1 [pfSense]
        isc-dhcp43-relay: 4.3.5 -> 4.3.6 [pfSense]
        isc-dhcp43-client: 4.3.5 -> 4.3.6 [pfSense]
        glib: 2.50.2_3,1 -> 2.50.2_6,1 [pfSense]

Installed packages to be REINSTALLED:
        pfSense-Status_Monitoring-1.7.2 [pfSense] (direct dependency changed: pecl-rrd1)

Number of packages to be removed: 1
Number of packages to be installed: 1
Number of packages to be upgraded: 23
Number of packages to be reinstalled: 1

The process will require 3 MiB more space.
Upgrade is complete.  Rebooting in 10 seconds.

Broadcast Message from admin@pfSense.home
        (/dev/pts/0) at 21:19 BST...

Upgrade is complete.  Rebooting in 10 seconds.

*** Welcome to pfSense 2.4.0-RC (amd64) on pfSense ***

 WAN (wan)       -> pppoe0     -> v4/PPPoE: **.***.**.***/**
 LAN (lan)       -> igb1       -> v4: ***.***.*.*/**
                                  v6/t6: ****:****:****:****:***:****:****:****/**
 PROTONVPN (opt1) -> ovpnc2     -> v4: **.*.*.*/**

 0) Logout (SSH only)                  9) pfTop
 1) Assign Interfaces                 10) Filter Logs
 2) Set interface(s) IP address       11) Restart webConfigurator
 3) Reset webConfigurator password    12) PHP shell + pfSense tools
 4) Reset to factory defaults         13) Update from console
 5) Reboot system                     14) Disable Secure Shell (sshd)
 6) Halt system                       15) Restore recent configuration
 7) Ping host                         16) Restart PHP-FPM
 8) Shell

Enter an option:

It then terminated the putty session, rebooted the box - and afterwards hadn't upgraded again. Still saying update available

It's hard to reproduce but if your system is still in this state can you run the following command and send me the output?

# pkg -ddd upgrade -n

Thanks

I just forgot to ask you to run a 2nd command as well:

# pkg -ddd upgrade -Fn

5
2.4 Development Snapshots / Re: Update issues
« on: October 05, 2017, 09:36:01 am »
I'm having the exact same problem. I'm currently on 2.4.0.r.20171003.1349. It says the Latest Base System is 2.4.0.r.20171004.0814. When cat /cf/conf/upgrade_log.txt, all it says is "2.4.0.r.20171004.0814 version of pfSense is available"

Attached is a capture of the console log when I try to update.

If your system is still in this state can you please run following commands and send me output?

# pkg -ddd upgrade -n
# pkg -ddd upgrade -Fn

Thanks

6
2.4 Development Snapshots / Re: Update issues
« on: October 05, 2017, 09:33:30 am »
It works just fine over SSH.

Code: [Select]
Enter an option: 13

>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
The following 27 package(s) will be affected (of 0 checked):

Installed packages to be REMOVED:
        pecl-rrd-1.1.3_4

New packages to be INSTALLED:
        pecl-rrd1: 1.1.3 [pfSense]

Installed packages to be UPGRADED:
        unbound: 1.6.3 -> 1.6.6 [pfSense]
        strongswan: 5.5.3 -> 5.6.0 [pfSense]
        sqlite3: 3.20.0_1 -> 3.20.1_1 [pfSense]
        rrdtool: 1.6.0_1 -> 1.7.0_1 [pfSense]
        python27: 2.7.13_7 -> 2.7.14 [pfSense]
        postgresql95-client: 9.5.8_1 -> 9.5.9 [pfSense]
        pfSense-default-config: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core]
        pfSense-base: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core]
        pfSense: 2.4.0.r.20171003.1203 -> 2.4.0.r.20171004.0814 [pfSense]
        pear: 1.10.3 -> 1.10.5 [pfSense]
        nginx: 1.12.1,2 -> 1.12.1_1,2 [pfSense]
        mysql56-client: 5.6.37 -> 5.6.37_1 [pfSense]
        mpd5: 5.8_1 -> 5.8_2 [pfSense]
        libzmq4: 4.1.5 -> 4.2.2 [pfSense]
        libnghttp2: 1.23.1 -> 1.26.0 [pfSense]
        liblz4: 1.7.5,1 -> 1.8.0,1 [pfSense]
        libidn2: 2.0.3 -> 2.0.4 [pfSense]
        libiconv: 1.14_10 -> 1.14_11 [pfSense]
        libffi: 3.2.1 -> 3.2.1_1 [pfSense]
        isc-dhcp43-server: 4.3.5 -> 4.3.6_1 [pfSense]
        isc-dhcp43-relay: 4.3.5 -> 4.3.6 [pfSense]
        isc-dhcp43-client: 4.3.5 -> 4.3.6 [pfSense]
        glib: 2.50.2_3,1 -> 2.50.2_6,1 [pfSense]

Installed packages to be REINSTALLED:
        pkg-1.10.1_1 [pfSense]
        pfSense-Status_Monitoring-1.7.2 [pfSense] (direct dependency changed: pecl-rrd1)

Number of packages to be removed: 1
Number of packages to be installed: 1
Number of packages to be upgraded: 23
Number of packages to be reinstalled: 2

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

**** WARNING ****
Reboot will be required!!
Proceed with upgrade? (y/N) y
>>> Downloading upgrade packages...
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
Checking for upgrades (25 candidates): .......... done
Processing candidates (25 candidates): .......... done
Checking integrity... done (1 conflicting)
  - pecl-rrd1-1.1.3 [pfSense] conflicts with pecl-rrd-1.1.3_4 [installed] on /usr/local/lib/php/20131226/rrd.so
Checking integrity... done (0 conflicting)
The following 26 package(s) will be affected (of 0 checked):

Installed packages to be REMOVED:
        pecl-rrd-1.1.3_4

New packages to be INSTALLED:
        pecl-rrd1: 1.1.3 [pfSense]

Installed packages to be UPGRADED:
        unbound: 1.6.3 -> 1.6.6 [pfSense]
        strongswan: 5.5.3 -> 5.6.0 [pfSense]
        sqlite3: 3.20.0_1 -> 3.20.1_1 [pfSense]
        rrdtool: 1.6.0_1 -> 1.7.0_1 [pfSense]
        python27: 2.7.13_7 -> 2.7.14 [pfSense]
        postgresql95-client: 9.5.8_1 -> 9.5.9 [pfSense]
        pfSense-default-config: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core]
        pfSense-base: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core]
        pfSense: 2.4.0.r.20171003.1203 -> 2.4.0.r.20171004.0814 [pfSense]
        pear: 1.10.3 -> 1.10.5 [pfSense]
        nginx: 1.12.1,2 -> 1.12.1_1,2 [pfSense]
        mysql56-client: 5.6.37 -> 5.6.37_1 [pfSense]
        mpd5: 5.8_1 -> 5.8_2 [pfSense]
        libzmq4: 4.1.5 -> 4.2.2 [pfSense]
        libnghttp2: 1.23.1 -> 1.26.0 [pfSense]
        liblz4: 1.7.5,1 -> 1.8.0,1 [pfSense]
        libidn2: 2.0.3 -> 2.0.4 [pfSense]
        libiconv: 1.14_10 -> 1.14_11 [pfSense]
        libffi: 3.2.1 -> 3.2.1_1 [pfSense]
        isc-dhcp43-server: 4.3.5 -> 4.3.6_1 [pfSense]
        isc-dhcp43-relay: 4.3.5 -> 4.3.6 [pfSense]
        isc-dhcp43-client: 4.3.5 -> 4.3.6 [pfSense]
        glib: 2.50.2_3,1 -> 2.50.2_6,1 [pfSense]

Installed packages to be REINSTALLED:
        pfSense-Status_Monitoring-1.7.2 [pfSense] (direct dependency changed: pecl-rrd1)

Number of packages to be removed: 1
Number of packages to be installed: 1
Number of packages to be upgraded: 23
Number of packages to be reinstalled: 1

The process will require 3 MiB more space.
Upgrade is complete.  Rebooting in 10 seconds.

Broadcast Message from admin@pfSense.home
        (/dev/pts/0) at 21:19 BST...

Upgrade is complete.  Rebooting in 10 seconds.

*** Welcome to pfSense 2.4.0-RC (amd64) on pfSense ***

 WAN (wan)       -> pppoe0     -> v4/PPPoE: **.***.**.***/**
 LAN (lan)       -> igb1       -> v4: ***.***.*.*/**
                                  v6/t6: ****:****:****:****:***:****:****:****/**
 PROTONVPN (opt1) -> ovpnc2     -> v4: **.*.*.*/**

 0) Logout (SSH only)                  9) pfTop
 1) Assign Interfaces                 10) Filter Logs
 2) Set interface(s) IP address       11) Restart webConfigurator
 3) Reset webConfigurator password    12) PHP shell + pfSense tools
 4) Reset to factory defaults         13) Update from console
 5) Reboot system                     14) Disable Secure Shell (sshd)
 6) Halt system                       15) Restore recent configuration
 7) Ping host                         16) Restart PHP-FPM
 8) Shell

Enter an option:

It then terminated the putty session, rebooted the box - and afterwards hadn't upgraded again. Still saying update available

It's hard to reproduce but if your system is still in this state can you run the following command and send me the output?

# pkg -ddd upgrade -n

Thanks

7
Just to make sure you are using the proper keys. What is the content of /usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406 ?

Code: [Select]
[2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: cat /usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406
function: sha256
fingerprint: 30be9cc2e7b2b3ba1ff3b2be1795f3f0719ab9a65322695703dc7b8f004035a8

Interesting, you have CE keys but your system is configured to use factory repositories. I just don't know how this key ended up there. Did you make any custom change on this system? Is it expected to be a factory system or CE?

CE is community edition, I'm guessing.

pfSense was installed when I got this box (Netgate APU2).

Does that answer?

Yes, CE is community edition.

If you are using Netgate hardware you are supposed to be running factory. Now the question is how the CE key ended up on your system. Did you install any package manually? changed anything while testing?

I'll send you factory public key.

8
Just to make sure you are using the proper keys. What is the content of /usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406 ?

Code: [Select]
[2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: cat /usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406
function: sha256
fingerprint: 30be9cc2e7b2b3ba1ff3b2be1795f3f0719ab9a65322695703dc7b8f004035a8

Interesting, you have CE keys but your system is configured to use factory repositories. I just don't know how this key ended up there. Did you make any custom change on this system? Is it expected to be a factory system or CE?

9
Do you have key files in /usr/local/share/pfSense/keys/pkg/trusted/?

You should have, for example, pkg.pfsense.org.20160406 and beta.pfsense.org.20151223 in there.

Code: [Select]
[2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: ls -l  /usr/local/share/pfSense/keys/pkg/trusted
total 1
-rw-r--r--  1 root  wheel  95 Jul 19  2016 beta.pfsense.org.20151223
-rw-r--r--  1 root  wheel  95 Mar 30 11:34 pkg.pfsense.org.20160406

Do you see any error messages when you run 'pkg update -f'? No need to use pkg-static now since the empty file that was causing the crash was removed.

If you see the errors, run 'pkg -dd update -f' and share the output

Here we go

Code: [Select]
[2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: pkg -dd update -f
DBG(1)[50590]> pkg initialized
Updating pfSense-core repository catalogue...
DBG(1)[50590]> PkgRepo: verifying update for pfSense-core
pkg: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory
DBG(1)[50590]> PkgRepo: need forced update of pfSense-core
DBG(1)[50590]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
DBG(1)[50590]> Fetch: fetching from: https://www.firmware.netgate.com/pkg/pfSense_factory-v2_3_3_amd64-core/meta.txz with opts "i"
meta.txz                                 : 100%  944 B     0.9kB/s    00:01   
DBG(1)[50590]> PkgRepo: extracting meta of repo pfSense-core
DBG(1)[50716]> PkgRepo: extracting signature of repo in a sandbox
pkg: No trusted public keys found
repository pfSense-core has no meta file, using default settings
DBG(1)[50590]> Fetch: fetching from: https://www.firmware.netgate.com/pkg/pfSense_factory-v2_3_3_amd64-core/packagesite.txz with opts "i"
packagesite.txz                          : 100%    2 KiB   2.3kB/s    00:01   
DBG(1)[50590]> PkgRepo: extracting packagesite.yaml of repo pfSense-core
DBG(1)[50987]> PkgRepo: extracting signature of repo in a sandbox
pkg: No trusted public keys found
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
DBG(1)[50590]> PkgRepo: verifying update for pfSense
pkg: Repository pfSense load error: access repo file(/var/db/pkg/repo-pfSense.sqlite) failed: No such file or directory
DBG(1)[50590]> PkgRepo: need forced update of pfSense
DBG(1)[50590]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
DBG(1)[50590]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_factory-v2_3_3_amd64-pfSense_factory-v2_3_3/meta.txz with opts "i"
meta.txz                                 : 100%  944 B     0.9kB/s    00:01   
DBG(1)[50590]> PkgRepo: extracting meta of repo pfSense
DBG(1)[51205]> PkgRepo: extracting signature of repo in a sandbox
pkg: No trusted public keys found
repository pfSense has no meta file, using default settings
DBG(1)[50590]> Fetch: fetching from: https://firmware.netgate.com/pkg/pfSense_factory-v2_3_3_amd64-pfSense_factory-v2_3_3/packagesite.txz with opts "i"
packagesite.txz                          : 100%  119 KiB 121.8kB/s    00:01   
DBG(1)[50590]> PkgRepo: extracting packagesite.yaml of repo pfSense
DBG(1)[51295]> PkgRepo: extracting signature of repo in a sandbox
pkg: No trusted public keys found
Unable to update repository pfSense
Error updating repositories!
[2.3.2-RELEASE][admin@bast.int.unixathome.org]/root:

Just to make sure you are using the proper keys. What is the content of /usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406 ?

10
Do you have key files in /usr/local/share/pfSense/keys/pkg/trusted/?

You should have, for example, pkg.pfsense.org.20160406 and beta.pfsense.org.20151223 in there.

Code: [Select]
[2.3.2-RELEASE][admin@bast.int.unixathome.org]/root: ls -l  /usr/local/share/pfSense/keys/pkg/trusted
total 1
-rw-r--r--  1 root  wheel  95 Jul 19  2016 beta.pfsense.org.20151223
-rw-r--r--  1 root  wheel  95 Mar 30 11:34 pkg.pfsense.org.20160406

Do you see any error messages when you run 'pkg update -f'? No need to use pkg-static now since the empty file that was causing the crash was removed.

If you see the errors, run 'pkg -dd update -f' and share the output

11

Hi Dan,

I suspect I know what is causing that. Can you please run 'truss pkg update -f' and send me the result?

Send directly via email @FreeBSD.org

It's exactly what I suspected. There is a bug in pkg that causes this crash. You can see details here:

https://github.com/freebsd/pkg/pull/1586

We already fixed it in pfSense before submit the patch to upstream, and based on truss output we can see:


openat(AT_FDCWD,"/usr/local/share/pfSense/keys/pkg/revoked/.empty",O_RDONLY,00) = 8 (0x8)
fstat(8,{ mode=-rw-r--r-- ,inode=140382,size=0,blksize=4096 }) = 0 (0x0)
close(8)                = 0 (0x0)
SIGNAL 11 (SIGSEGV)
process killed, signal = 11 (core dumped)


The presence of the empty file /usr/local/share/pfSense/keys/pkg/revoked/.empty is the cause. I suspect there is a /usr/local/share/pfSense/keys/pkg/trusted/.empty file too. Just remove them and it will work as expected. As soon as you update pkg to latest version bug will be fixed.

12
Well:

Code: [Select]
$ lldb -c pkg-static.core
(lldb) target create --core "pkg-static.core"
Core file '/usr/home/dan/pkg-static.core' (x86_64) was loaded.
(lldb) bt

thread #1: tid = 100238, 0x000000000045014f, name = 'pkg-static', stop reason = signal SIGSEGV
frame #0: 0x000000000045014f
frame #1: 0x000000000044f1e0
frame #2: 0x000000000044f3ec
frame #3: 0x000000000044f00c
frame #4: 0x000000000044d791
frame #5: 0x00000000005adcd0
frame #6: 0x000000000041108d
frame #7: 0x0000000000409abb
frame #8: 0x000000000040ad50
frame #9: 0x000000000040032f
(lldb)

Hi Dan,

I suspect I know what is causing that. Can you please run 'truss pkg update -f' and send me the result?

13
Portuguese / Re: Dificuldade para baixar plugin pf2ad
« on: July 11, 2017, 04:33:37 pm »
Antes de fechar essa thread gostaria apenas de esclarecer um ponto:

- Mantive este projeto sozinho e ainda com rejeição pelo equipe
oficial de PFSense;

Esse projeto é algo particular e não tem nenhuma relação com o pfSense. Quando algum usuário faz a instalação do mesmo está fazendo por sua conta e risco e o resultado do sistema após a modificação é algo que nem mesmo deve ser considerado um pfSense.

Vou manter a thread fechada pois como esse não é algo suportado oficialmente, não deve ser discutido em um canal oficial.

14
General Questions / Re: Source Code
« on: June 12, 2017, 09:32:41 am »
You will not be able to reach our internal staging servers, you would need to have your own. The build process is not trivial and we do not offer support for it, but the code is not incomplete, it's all there and it's all we use to build our images. You just need to read the code and figure out what needs to be done.

15
I've pushed a fix, it's on pfSense-upgrade 0.19.

pfSense-upgrade was considering its new version as a new firmware version. The issue is harmless and if you finish the upgrade nothing bad will happen.

Fix is on version 0.19. As soon as it's available it's safe to manually run 'pkg upgrade pfSense-upgrade' on console to go to latest verssion.

This issue is being tracked at https://redmine.pfsense.org/issues/7343

Sorry for the inconvenience

Pages: [1] 2 3 4 5 ... 18