WOW… What at turd!
-
You have to wonder why are they on 2.2.4? and not 2.2.6 if they are so worried about updating?
If this is a production environment, where was the test of the upgrade, was there change control? You would upgrade your production wan router/firewall without testing? Without simple easy backout plan? Like already having install media at hand to clean install, or for that matter even taking an image of the machine before so you could just reimage it.
If this is a production environment, why is there not a carp setup.. And you could always just break the carp, upgrade, test ok let everyone use this one.. Upgrade the other one, then redo the carp. There are plenty of ways to actually roll out an upgrade in a production environment that prevents this sort of thing from ever even being an issue.
I just love how your complete an utter lack of any planning or forethought on what could and might go wrong and how to prevent it is pfsense problem?? Or why anyone here should give 2 shits at all? More than happy to help someone fix something, but its just plain hard to fix stupid..
JFC even on my home network I have backup plan if something goes wrong.. I run vm, so I have an image I can easy roll back too. But if something is wrong with the image, and that doesn't restore I always have the new media and current media to install from. And if my hardware decides that during the upgrade is the best time to take a shit, I always have my old school soho routers I could put in place until get the esxi host fixed up, etc.
Its fine your frustrated - but who you should be frustrated with is yourself for how you could let something like this ever become anything other than a minor blip on some monitoring of your wan connectivity being down for a few minutes. And if this really a production environment not only should you have your peepee slapped, your boss should have his slapped as well and their boss as well for a complete and utter lack on any sort of planning or contingency for when shit happens..
How this thread should of gone is.. Hey had a problem with the upgrade. Got xyz for errors, here is screen shot and logs.. My hardware is ABC, with packages 123 installed. I got it booted, but X didn't work, or could not get it booted at all. I tried X and Y and finally had to fallback to original setup.. What do you guys think the problem could be - and then exchange of more info, some questions asked and answered and if think problem found give it another go, etc..
The other thing that just blows my mind, is how is this even in the forums.. If this really is a "production" setup for actual company how do you not have support, and would be dealing with them directly for such a problem vs coming to a forum that is community supported and calling the product a turd.. I have to agree really just points to some troll trying to get some lulz..
-
^ agreed, if he really did what he says he did in a production environment, I would have fired him. I've never seen any of my employees act so stupidly, even with home networks. You don't drop brand new software on a production machine with no snapshots/backups or spare images around, especially when you're apparently too cheap for commercial support, double-especially with zero testing in your environment first
-
+1
-
I had no issue with the upgrade. I wiped and did a fresh install and restored using my 2.2.6 backup and all works like a charm.
-
the upgrade from 2.2.6 > 2.3-release also worked without any issues for me. the only package i had installed was mailreport. upgraded and back online in less than 5 minutes. great job, guys (and gals)!
-
Don't take this the wrong way, but considering you couldn't even find the 2.2.4 ISO's in a directory that had about 5 of them, perhaps you should consider a new career outside of IT? Sounds like it might be a little too challenging for you
A couple of things to consider. This did not happen on a "production" system, it happened at home, but that does not make it less important for those using it. Secondly, most of the code I've developed over the last 10 years actually lives embedded in over 50% of all cablemodems in use today. I've actually got some code in pfSense, not a ton but a few fixes and improvements here and there. So, no, I'm not an "IT" guy, nor would I ever consider a career in IT, the pay is too low.
Mea culpa. I wish I had taken a deep breath and calmed down before dashing off that original post, starting this shit storm of pontification. Lesson learned….
-
Mea culpa. I wish I had taken a deep breath and calmed down before dashing off that original post, starting this shit storm of pontification. Lesson learned….
-
You have to wonder why are they on 2.2.4? and not 2.2.6 if they are so worried about updating?
Here's the thing. 2.2.5 didn't work well for me. No problem, just restore the full backup of 2.2.4 using the built-in capability that's been available since what seems like forever.
After reading the release notes for 2.3, where there was no mention of this deleted functionality, I figured the same approach would be fine with at most half an hour of down time. The rest is history….
-
2.3 killed two of my wifi routers. WTF!
Can't connect to anything on port 80. 443 works fine.
Good thing I'm running on a SAN, just reverted back to a snapshot.
-
Upgraded to 2.3. lost dns resolution… can't restore full backup.
Way to go guys... not!
Locking thread, it's pointless. Multiple people tried to help here, PEBKAC
-
Yeah this thread is completely unproductive. If OP had started answering questions, I would have made sure his problem was addressed a lot faster than the hours he was screwing with it. I did free phone and screen share sessions with a couple people yesterday who were having issues, I would have done same with OP if he had any interest in actually trying to troubleshoot the problem.
If you're having an issue post-upgrade, start a new thread describing what you're seeing. Or pop into our IRC channel, ##pfsense on Freenode, for potentially more immediate help. I'm watching there and helping in such cases as well. If you're a support customer, please start a support case - we don't dock incidents for cases that are the result of a software problem.
