No Web Interface on Thu May 29 08:48:37 CDT 2014
-
This is confirmed for memstick version x86 and x64.
Boot hangs after cron, webgui won't come up though.After the snapshot to fix this, is there some way to update without the GUI or fresh install?
-
I can confirm that. Fresh (today's) snapshot doesn't complete booting for me: on the console, it stops here:
Starting webConfigurator ... done. Configuring CRON ... done. Starting DNS forwarder ... done. Starting NTP time client ... done Starting DHCP service ... done. Starting DHCPv6 service ... done. Configuring Firewall ... done. Generating RRD graphs ... done. Starting syslog ... done. Starting CRON ... done.
Though I can ^C out of that to /bin/sh and look around. check_reload_status does not dump core, so that's an improvement. The VM can ping, and be pinged, on the LAN. Looks like it may be hanging in /etc/rc, right after starting CRON. If I comment out the rest of the commands in /etc/rc and reboot, the boot continues and I get the console menu.
Still no web server at that point, and as before, sshd can't be started.
-
After the snapshot to fix this, is there some way to update without the GUI or fresh install?
Perhaps the easiest would be to save your configuration and do a fresh install. To get your config file, boot into single user mode and get it from /cf/conf/config.xml (and older copies from the backup directory if you want).
Alternately you can hack /etc/rc as I described above (commenting out everything past cron); this will get you to the console menu where you can choose item 13 "Upgrade from Console"
-
After the snapshot to fix this, is there some way to update without the GUI or fresh install?
Perhaps the easiest would be to save your configuration and do a fresh install. To get your config file, boot into single user mode and get it from /cf/conf/config.xml (and older copies from the backup directory if you want).
Alternately you can hack /etc/rc as I described above (commenting out everything past cron); this will get you to the console menu where you can choose item 13 "Upgrade from Console"
How does one "comment out" as you explained?
After I select "upgrade from console", how do I upgrade? As before with a usb thumbdrive? -
Config from last install borks a fresh install from an earlier version.
Is sad.
-
-
-
Is the same on "amd64-20140529-1554" snapshot (no webconfigurator, boot stuck at starting Cron…), but i was able to login via SSH and perform a "upgrade" ;)
login as: root Using keyboard-interactive authentication. Password for root@pfsense.d510: *** Welcome to pfSense 2.2-ALPHA-pfSense (amd64) on pfsense *** WAN (wan) -> pppoe0 -> v4/PPPoE: 1.1.1.1/32 LAN (lan) -> re1 -> v4: 192.168.1.254/24 GEST (opt1) -> re0 -> v4: 172.20.254.6/29 W311U (opt2) -> run0_wlan1 -> v4: 192.168.0.1/24 0) Logout (SSH only) 8) Shell 1) Assign Interfaces 9) pfTop 2) Set interface(s) IP address 10) Filter Logs 3) Reset webConfigurator password 11) Restart webConfigurator 4) Reset to factory defaults 12) pfSense Developer Shell 5) Reboot system 13) Upgrade from console 6) Halt system 14) Disable Secure Shell (sshd) 7) Ping host 15) Restore recent configuration Enter an option: 13 Starting the pfSense console firmware update system.. 1) Update from a URL 2) Update from a local file Q) Quit Please select an option to continue: 1 Enter the URL to the .tgz or .img.gz update file. Type 'auto' to use http://snapshots.pfsense.org/FreeBSD_stable/10/amd64/pfSense_HEAD/.updaters//latest.tgz > http://snapshots.pfsense.org/FreeBSD_stable/10/amd64/pfSense_HEAD/updates/pfSense-Full-Update-2.2-DEVELOPMENT-amd64-20140526-1601.tgz Fetching file size... File size: 80085938 Fetching file... looking up snapshots.pfsense.org connecting to snapshots.pfsense.org:80 requesting http://snapshots.pfsense.org/FreeBSD_stable/10/amd64/pfSense_HEAD/updates/pfSense-Full-Update-2.2-DEVELOPMENT-amd64-20140526-1601.tgz remote size / mtime: 80085938 / 1401202722 /root/firmware.tgz 6% of 76 MB 106 kBps 11m34s
edit: fix code tag ;)
-
You can update through console or ssh (this one have ssh)
Option 13 -> 1 -> "auto"
-
@mais_um:
You can update through console or ssh (this one have ssh)
Option 13 -> 1 -> "auto"
I've already done this, but for the sake of knowing…
If I get stuck at the loader where it get stuck at cron, how do I access the console? -
As Charlie said, hit ^C (Control-C).
Steve
-
Is sad.
No, it's alpha
Thank you, Captain Obvious.
We're all aware it's Alpha.
Yes, but it sounded (to me) like you were expecting more from alpha.
To keep this post somewhat on-topic, I noticed an option in the installation menu to "rescue config.xml":
< quick/easy install > < custom install > < rescue config.xml > < reboot > < exit >
I haven't tried to use it, but perhaps it would be easier for some rather than using the other methods described in this thread.
-
Has anyone downloaded the last snapshot from today at 23:36?
-
I updated to amd64-20140529-1755, issue is still present. Tried updating again from SSH, didn't fix it. Restarting webConfigurator from SSH doesn't fix it. Routing and firewall functionality seems to be unaffected.
-
Mmm, the most recent update file is still far too small, <1MB for the Nano 1G update.
Steve
-
Playing with this mornings amd-64 snapshot, as a fresh install in a VM. As noted earlier, the boot hangs after 'Starting CRON'. Seems that the guilty line is in /etc/rc:
/usr/local/sbin/fcgicli -f /etc/rc.start_packages
If you comment out only that line in /etc/rc, then the boot completes and goes to the console menu.
Run that line at a console prompt in a recent snapshot, it hangs until you ^C out of it. But run that line in an earlier, working snapshot, and it completes and returns to the shell. Note that I'm testing without any packages installed, so the command should not actually do anything for me.
This explains the hanging boot, and may be related to the missing webgui, but I haven't dug that far yet.
As a side note, if you do a fresh install, you can run /etc/sshd by hand to generate the keys. sshd won't start up until keys are present.
[edit: noted as amd-64 arch]
-
The following cases all show a missing webgui and boot hang symptoms described above:
- amd-64, fresh install, 30-May image
- i386, fresh install, 30-May image
- amd-64, fresh install 23-May image (confirmed working and completed the wizard) and then confirmed failing when auto-upgraded to 30-May update
-
Still no go for web interface on amd64-20140530-1557.
EDIT: I can get the bootup to complete by running:
ps aux | grep -i rc
Then finding the PID of /usr/local/sbin/fcgicli -f /etc/rc.start_packages and running:
kill -9 xxxxx
Where xxxxx is the PID of the process. This doesn't bring up the web interface though.
-
I am running the 30th snapshot on i386 and sshd works for me after running it manually the last time I booted to create the sshd keys. The GUI doesn't work for me though.
I noticed the same /usr/local/sbin/fcgicli -f /etc/rc.start_packages command in the process list apparently stuck. I killed it and then a few more with different rc scripts specified as arguments were launched by minicron I think. Those are stuck now too.
I ran the tracing command truss manually on one of the command lines and it appears to lock up around the time of writting to /var/run/php-fpm.socket. php-fpm is running.
truss /usr/local/sbin/fcgicli -f /etc/rc.update_alias_url_data
connect(3,{ AF_UNIX "/var/run/php-fpm.socket" },106) = 0 (0x0) __sysctl(0xbfbfe6c4,0x2,0xbfbfe708,0xbfbfe6c0,0x0,0x0) = 0 (0x0) __sysctl(0xbfbfe6c4,0x2,0xbfbfe808,0xbfbfe6c0,0x0,0x0) = 0 (0x0) __sysctl(0xbfbfe6c4,0x2,0xbfbfe908,0xbfbfe6c0,0x0,0x0) = 0 (0x0) __sysctl(0xbfbfe6c4,0x2,0xbfbfea08,0xbfbfe6c0,0x0,0x0) = 0 (0x0) __sysctl(0xbfbfe6c4,0x2,0xbfbfeb08,0xbfbfe6c0,0x0,0x0) = 0 (0x0) madvise(0x28804000,0x1000,0x5,0x281c15f8,0xbfbfe4f4,0x28120ccf) = 0 (0x0) madvise(0x28816000,0x1000,0x5,0x281c15f8,0xbfbfe4f4,0x28120ccf) = 0 (0x0) madvise(0x28818000,0x1000,0x5,0x281c15f8,0xbfbfe56c,0x28120ccf) = 0 (0x0) madvise(0x28803000,0x3000,0x5,0x281c15f8,0xbfbfe57c,0x28120ccf) = 0 (0x0) write(3,"\^A\^A\0\^A\0\b\0\0\0\^A\0\0\0\0"...,263) = 263 (0x107)
It just sits there forever. Any /usr/local/sbin/fcgicli command executed even by hand gets stuck there.
-