2.0-BETA4 x86 64 BITS FULL Several problems (renamed topic due to ARCH)
-
Downloading package configuration file… done.
Saving updated package information... done.
Downloading OpenVPN Client Export Utility and its dependencies... done.
Checking for successful package installation... of p7zip-9.04 failed!Installation aborted.
:(
-
When reporting such problems on 2.0 you also need to tell us if you are using i386 or amd64. The package repositories are completely different.
-
Jim,
Forgive my rather blunt post without any comment!.
I posted this from a crapy laptop in a datacenter, while trying to tackle the problem.The platform is intel 64bits
At current we have (see my other posts in this forum section) a pfsense 2.0-BETA4 x64 in a setup
which has to go into production in a about a week or 2.I know pfsense 2.0 is not for ..
My collegeas had to fix a broken pfsense 1.3.2 and thougd, why not installed 2.0 … while i was in hospital.
After that because the developers where working on the farm behind it, i got the honor of trying to get it running as it was ..Ah.. now i must say 2.0 xx has some really kewl enhancements and new features, which once used to you don;t want to go back to 1.3.2. But allthough bsd itself feels and handles stable the gui -> system is not.
Just to sum op the issues i ran into:
- Relayd (vs the former sldb): nice, more scalable, more options. but buggy.
I get gui parse error's and the online / offline view doesn't work
Loadbalancer log (in logs view) seems completly broken, does nothingLast 250 Load Balancer log entries
Aug 18 19:13:47 relayd[54535]: reloading configuration(and has really been changed many times since that)
-
Vpn: (all of them) seem non-functional, libexso .. something error, parse error's
OpenVPN only seemed to gave gui-error's but skipped debugging due to time. -
This package, from this post
-
Aliases: A strange but small bug in aliases, making one of my hosts not getting parsed to hosts file in bsd itself.
this hosts appears in dnsfilter.conf, the works of that is beyond my scope for now (due to lack of time)
I get frequent "entry to long / parse error" more then 63 characters .. (i have only short aliases with valid char.)
- Nat/Rules: Again parse / charac. error's
I have no log-entry's for that right now since the log-time i quit short when getting loaded with error's like apinger ..
- RRD broken ..
Apinger going nuts over RRD :)
_apinger: Error while feeding rrdtool: Broken pipe
apinger: /usr/local/bin/rrdtool respawning too fast, waiting 300_sKeep up the good work! ;D
-
I am not sure you are on latest snapshot.
-
as in "are you on..?" no definetlly not the latest:
2.0-BETA4 (amd64)
built on Thu Aug 12 09:20:36 UTC 2010
FreeBSD xxxxxxx 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Thu Aug 12 08:05:47 UTC 2010 sullrich@FreeBSD_8.0_pfSense_2.0-AMD64.snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense.8 amd64mmhhhh it doesn't really show a build ID does it just a date? 12 aug.
Anyone got experience with updating the snapshots?
-
I wonder if the same builds for 32 bits are more stable/mature (mostly regarding the libs)
if so i could allways try to switch to 32B before going back to 1.3.2 as a last resortA new version is now available
Current version: 2.0-BETA4
Built On: Thu Aug 12 09:20:36 UTC 2010
New version: Sun Aug 22 23:46:20 UTC 2010Update source: http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/amd64/pfSense_HEAD/.updaters/
I feel a bit nerveous about updating beta's .. worst case: i have to drive 40 miles to the datacenter to restore it
-
Updated to latest build (22/08)
php: /status_rrd_graph_settings.php: RRD create failed exited with 1, the error is: /libexec/ld-elf.so.1: /usr/local/lib/libfreetype.so.9: unsupported file layout
php: /status_rrd_graph_img.php: rrdcolors.inc.php for theme pfsense_ng does not exist, using defaults!
Aug 25 23:22:00 php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: /libexec/ld-elf.so.1: /usr/local/lib/libfreetype.so.9: unsupported file layout/usr/bin/nice -n20 /usr/local/bin/rrdtool graph /tmp/system-processor.rrd-year.png –start 1262214000 --end 1293750000 --vertical-label "utilization, number" --color SHADEA#eeeeee --color SHADEB#eeeeee --title "
hostname- System :: Processor - 1 year - 1 day average" --height 200 --width 620 DEF:"user=/var/db/rrd/system-processor.rrd:user:AVERAGE" DEF:"nice=/var/db/rrd/system-processor.rrd:nice:AVERAGE" DEF:"system=/var/db/rrd/system-processor.rrd:system:AVERAGE" DEF:"interrupt=/var/db/rrd/system-processor.rrd:interrupt:AVERAGE" DEF:"processes=/var/db/rrd/system-processor.rrd:processes:AVERAGE" AREA:"user#990000:user" AREA:"nice#a83c3c:nice:STACK" AREA:"system#b36666:system:STACK" AREA:"interrupt#bd9090:interrupt:STACK" LINE2:"processes#cccccc:processes" COMMENT:"\n" COMMENT:" minimum average maximum -
There were error(s) loading the rules: /tmp/rules.debug:190: rule label too long (max 63 chars)
pfctl: Syntax error in config file: pf rules not loaded The line in question reads [190]: pass in quick on $OpenVPN from any to any keep state label "USER_RULE: OpenVPN Remote *************** wizard rules." -
There were error(s) loading the rules: /tmp/rules.debug:190: rule label too long (max 63 chars)
pfctl: Syntax error in config file: pf rules not loaded The line in question reads [190]: pass in quick on $OpenVPN from any to any keep state label "USER_RULE: OpenVPN Remote *************** wizard rules."This should be fixed now. OpenVPN description should have been limited to 30 chars. That is now enforced, and there is another check to prevent the rule descr from being too long as well.
-
php: /status_rrd_graph_settings.php: RRD create failed exited with 1, the error is: /libexec/ld-elf.so.1: /usr/local/lib/libfreetype.so.9: unsupported file layout
Did you install ntop by chance? I don't get that error on my amd64 vm on the same snapshot.
php: /status_rrd_graph_img.php: rrdcolors.inc.php for theme pfsense_ng does not exist, using defaults!
That should be fixed now
-
I feel a bit nerveous about updating beta's .. worst case: i have to drive 40 miles to the datacenter to restore it
Then you shouldn't be running a BETA there ;D
Most of the time the updates are fine, but I generally test them in a VM before putting them on a live machine.
-
jimp: when new update x64?
Is ntop now OK/working?
-
There is a snapshot building now. There was a problem with a module on x64 that was preventing it from building. It's been worked around for now.
We made a lot of changes to the nop build yesterday but I don't believe it's all correct yet. It's worth trying though.
-
Jim you are so right ;D
A know i posted a lot of garble, but what's up with the lib9.so thing? (i could just google offcourse)
M.
-
Jim you are so right ;D
A know i posted a lot of garble, but what's up with the lib9.so thing? (i could just google offcourse)
I haven't seen that before, which is why I asked if you had installed packages. The error message might imply that the library is the wrong format (e.g. 32-bit library when it expects 64-bit)
-
MMmhhh, that does give me hope. I'll look into it some more and will post my findings.
-
Unable to communicate with www.pfsense.com. Please verify DNS and interface configuration, and that pfSense has functional Internet connectivity. DNS is OK and interet is working. What is the problem.
i have:
2.0-BETA4 (amd64)
built on Fri Aug 27 01:09:19 UTC 2010
FreeBSD 8.1-RELEASEYou are on the latest version.
-
Jim,
Just upgraded to 2.0-BETA4 (amd64) built on Mon Aug 30 05:08:19 UTC 2010
FreeBSD 8.1-RELEASE FreeBSD 8.1-RELEASE #1: Mon Aug 30 04:56:22 UTC 2010 sullrich@FreeBSD_8.0_pfSense_2.0-AMD64.snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense.8 amd64I am happy to report that:
- RRD works again
- Open VPN seems to work again
- Loadbalancer seems to work (didn't start …)
