System unable to startup after upgrade to 1.0.1 with squid installed
-
rm /usr/local/etc/rc.d/squid* will keep it from starting.
-
'Love you! Thanks a lot man!!
I'm going to test and if I don't post anymore consider my problem as solved! ;)
Thanks again! 8) -
Hem ;D
I need your help again :-[
I've tried many ways to delete these files but each time I've got the same problem :
It says me that I "Cannot write to read-only filesystem" :-X
I understand the message but I don't know how to bypass this problem in a easy way ? ???
Many thanks and sorry again but my home network is locked since 2 weeks because of that problem :'( :) -
read-only filesystem? are you running an embedded install? and why did you install squid on this? embedded systems don't have package support.
with the following commands you can set the filesystem rw and ro:
/etc/rc.conf_mount_rw
/etc/rc.conf_mount_rohowever, this only should be needed on embedded systems.
Maybe a reinstal is in order and something is hosed.
-
Strange so! Because I've installed PfSense on a (old) computer using the LiveCD installer by choosing the 99 option making then a permanent installation on the hard-disk of the computer :-X
So, you're right, I've installed (cause I can) the package named squid and this one seems to cause my system freezing during startup.
And when I try to do "rm /usr/local/etc/rc.d/squid*" in recovery options I've got the message I wrote before this post :)
Maybe you can see where is the problem with this informations but as I'm not friendly at all with linux I don't know how to operate to execute this command.
Command I must execute to start at least one time my old PfSense installation to backup all my settings/rules before reinstall it :)
Many thanks for all your work and your patience team! (with linux-n00bz like me ;D) ;)(Sorry for my poor english, if there's something you don't understand, don't hesitate to ask me more! ;) )
-
The currently available squid package shoudl "just work"
-
The currently available squid package shoudl "just work"
On a recent snapshot that is. I fixed a bug from 1.0.1 that would halt the packages from starting on bootup.
Scott
-
Ok, thanks for the informations. :)
Anyway I still have my box down because even if PfSense can now boot up succesfully, I'm not able to login into my webGUI. I don't kow why.
So I've reinstalled PfSense on another disk and for now I'm trying to "force" importation of my rules from disk1 to disk2. But the problem is : where are they ? ;D
Are the rules (for each interfaces) and the alias created stored somewhere (Like a conf file or anything else) ?
And do you think that a brutal import will work ? I'd like to have your opinion on that :)
Thanks in advance :) -
The complete configuration is stored at /conf/config.xml. Try to cut it down to just the rule block and do a partitial diagnostics>backup/restore of only the parts you need or you might end up with the same situation that you have already on the old install.
-
I had uninstall the squid package and install the new beta 2.6.5_1-p15 but the same error still happened. any way to stop and squid the service properly?
system stopped
Executing rc.d items
Stopping /usr/local/etc/rc.d/proxy_monitor.sh…... -
I had uninstall the squid package and install the new beta 2.6.5_1-p15 but the same error still happened. any way to stop and squid the service properly?
system stopped
Executing rc.d items
Stopping /usr/local/etc/rc.d/proxy_monitor.sh…...This question has been asked atleast 15 times now. Update to the latest snapshot from: http://snapshots.pfsense.com/FreeBSD6/RELENG_1/