2.0-RC1 (amd64) built on Tue Apr 5 Observations

Gloom

First I have to say thanks to whoever sorted out snort. This is the first upgrade in months that has left the rules and log intact. The block list is still cleared but I can live with that. Please don't regress this change.

Sadly NTPD is still broken.

I noticed this on the previous build from the 4th and it is still present, the dashboard displays
2.0-RC1 (amd64)
built on Tue Apr 5 21:27:23 EDT 2011

Unable to check for updates.

It breaks the packages listing as well so I've no idea if I'm running the latest package version. Updating from the command line is fine.

Memory usage has increased to 26% from a stable 8% usage over the last few months. It's not a problem for me on 12GB but might be for people running the 64bit with 4GB physical memory.

Gloom

Does anyone have any ideas on why I'm getting

2.0-RC1 (amd64)
built on Thu Apr 7 04:03:17 EDT 2011

Unable to check for updates.

and nothing listed under ports either. This problem is on both the 5th and 7th of April AMD builds.
If it's just me I'll rip it down and do a fresh build.

wallabybob

Concerning Unable to check for updates: I'm pretty sure I saw that when I wasn't getting a default route setup.

Gloom

Netstat -r is showing my default route fine.

Destination Gateway Flags Refs Use Netif Expire
default 9x.xxx.xx.x UGS 0 828039 bce0

Gloom

Oh well I just did an upgrade to the latest 64 bit build from yesterday evening and the box is now dead with it continually streaming link is up messages for the 3 nics and I'm miles away :(

mromero

Wish I could help, the only help we would get would be the "welcome to snapshotland " land refrain from Jimp…........

eri--

Can you try i386 snapshot and see if you get the same outcome?

jimp

@Gloom:

Oh well I just did an upgrade to the latest 64 bit build from yesterday evening and the box is now dead with it continually streaming link is up messages for the 3 nics and I'm miles away :(

bce NICs? We recently changed out the bce driver. Someone else had an issue that sounds like yours. I rolled those back out and the next new snapshot should have the old (working) drivers again.

Gloom

Thanks for that. I tried rebuilding with yesterdays release and had the same issue so rolled back to the release from the 7th which fixed the problem.