Cannot connect to installer daemon
-
@stephenw10 where can I find the installer logs in /var/log ?
-
Yes, there and also in /var/log
-
@stephenw10 here you have a example of all logs that I belive make sense.
daemon.log
root@pfSense-install:/var/log # cat daemon.log Jun 18 20:20:00 pfSense-install newsyslog[1700]: logfile first created Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: Starting Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: Version: v1.0-RC Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: argv[0]: /usr/local/libexec/installer/pfSense-init Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: argv[1]: -M Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: argv[2]: unknown Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: /usr/local/libexec/installer/pfSense-init exited with status: 0 Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: init: error: 0 Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: argv[0]: /usr/local/libexec/installer/pfSense-if-up Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: argv[1]: -i Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: argv[2]: igb0 Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: /usr/local/libexec/installer/pfSense-if-up exited with status: 0 Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: if_set_up: error: 0 Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: argv[0]: /usr/local/libexec/installer/pfSense-if-up Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: argv[1]: -i Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: argv[2]: igb1 Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: /usr/local/libexec/installer/pfSense-if-up exited with status: 0 Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: if_set_up: error: 0 Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: argv[0]: /usr/local/libexec/installer/pfSense-if-up Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: argv[1]: -i Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: argv[2]: igb2 Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: /usr/local/libexec/installer/pfSense-if-up exited with status: 0 Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: if_set_up: error: 0 Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: argv[0]: /usr/local/libexec/installer/pfSense-if-up Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: argv[1]: -i Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: argv[2]: igb3 Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: /usr/local/libexec/installer/pfSense-if-up exited with status: 0 Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: if_set_up: error: 0 Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: nic_addr_set: addr: 192.168.1.1/24 Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: argv[0]: /usr/local/libexec/installer/pfSense-pf Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: argv[1]: -d Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec output [2]: pfctl: pf not enabled Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec output [1]: Warning: Cannot disable the pf firewall. Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: /usr/local/libexec/installer/pfSense-pf exited with status: 0 Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: nic_pf_disable: error: 0 Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: argv[0]: /usr/local/libexec/installer/pfSense-copy-configxml Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec output [1]: Searching configuration backups on the installation media... Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec output [1]: Looking for config.xml on da0s3: Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec output [1]: [found msdos] Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec output [1]: [no config.xml on da0s3] Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec output [1]: Could not locate a msdos partition. Done. Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec output [1]: Searching for configuration files in the existing disks... Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec output [1]: Could not locate an existing XML configuration. Done. Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: /usr/local/libexec/installer/pfSense-copy-configxml exited with status: 0 Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: cfg_copy_configxml: error: 0 Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: argv[0]: /usr/local/libexec/installer/pfSense-ready Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: argv[1]: -M Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: argv[2]: unknown Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: exec: /usr/local/libexec/installer/pfSense-ready exited with status: 0 Jun 18 20:20:01 pfSense-install pfSense-installer[1851]: ready: error: 0 root@pfSense-install:/var/log #
auth.log
root@pfSense-install:/var/log # cat auth.log Jun 18 20:20:00 pfSense-install newsyslog[1700]: logfile first created Jun 18 20:20:02 pfSense-install sshd[1953]: Server listening on :: port 22. Jun 18 20:20:02 pfSense-install sshd[1953]: Server listening on 0.0.0.0 port 22. Jun 18 20:20:02 pfSense-install login[1970]: login on ttyu0 as root Jun 18 20:20:02 pfSense-install login[1962]: login on ttyv0 as root Jun 18 20:20:02 pfSense-install login[1981]: login on ttyv3 as root root@pfSense-install:/var/log #
messages
Attached as file.
messages.txtCan you find some clues in these logs? I do not find anything suspicus...
-
Hmm, no errors shown there but the daemon log should have a lot more in it....
The only time I've ever seen that is after restarting the installer without rebooting. But I assume you are rebooting here between attempts?
-
@stephenw10 yes I am rebooting between the attempts.
Looks like the issue is with the pfsense-installerd.sh it should bring up a webservice which do not seem to be accessible through nginx. I get ssl issues and can not bypass that.
Ideas?
-
Hmm, do you have a good system time? Some time ago there was a bug that caused the installer to generate a cert that was then seen as expired once ntp kicked in. That should be fixed but perhaps you're hitting some variant.
-
@stephenw10 yes I have a good system time and date it might diff a few seconds, but that is it.
More ideas?
Is it possible to download an older image 2.6.x or 2.7.x just to verify if I get a different behaivour?
-
Yes you can get the legacy installers for 2.7.2 here.
Those definitely won't hit this because the installer code itself is completely different. But you can test upgrading to 2.8.
-
@stephenw10 I tried to install 2.7.2 and it worked fine the install as you expected.
But I hit another issue and that is firefox generates SSL_ERROR_BAD_MAC_READ when I try to connect to pfsense 2.7.2 after inital install at https://192.168.1.1.
So I am not able to connect to the GUI at all. I logged in via the console to the shell and executed the command below but this did not help.
pfSsh.php playback generateguicert
I also tested to install Opnsense 25.1 and it just works very well. As well as FreeBSD 14.
So ideas on what to test or how to resolve this situation.
It is quite clear that the new pfsense 2.8 installer is not as compatible as the old 2.7.2.
Any ideas or tests you can think of would be appricated since I want to run pfsense on my box.
-
@stephenw10 I did some further test on SSL_ERROR_BAD_MAC_READ.
I fund out that I had the same issue on a live cd of Debian 12 as well.I then ran memtest86 test suite and found out that it seems to be an issue with my RAM memory. I will exchange the RAM memory during next week and retest to install pfsense 2.7.2.
I do not belive that pfsense 2.8 installation issues is caused by the RAM memory, but I will retest this as well.
I will reach out here with an update and some advise from you if I am not successful in my endeavor.
-
Huh. Well that would not be anything I'd have suspected! Let us know if that allows it to run the installer.