Error on fresh install
-
- Posts: 3
- Joined: 09 Aug 2016 11:53
Error on fresh install
Hello all,
I just created a LightSail instance on AWS with CentOS 7 minimal. I updated the OS, installed the NetworkManager package and restarted the server.
Then I ran the following command: curl -sSL https://install.efa-project.org | bash
No errors happened and I restarted the machine. When reconnecting to the server, I started the first configuration and did it as I always did on other occasions. However when I finished and the system started to perform the tasks, I saw the following errors:
[eFa] - Starting MariaDB and Configuring
Dropping the database is potentially a very bad thing to do.
Any data stored in the database will be destroyed.
Do you really want to drop the 'test' database [y/N] Database "test" dropped
ERROR 1064 (42000) at line 20: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'firstseen TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP,
lastsent TIMESTAMP NOT ' at line 11
[eFa] - Configure timezone
[eFa] - Configuring razor
nextserver: Bootstrap discovery failed. Giving up.
nextserver: Bootstrap discovery failed. Giving up.
chmod: cannot access ‘/var/spool/postfix/.razor/identity-*’: No such file or directory
[eFa] - Error initializing system! Please try again...
The installation was aborted. Is there any way to fix this? Is it possible to configure another version (like stable) that is not showing configuration errors? Any other references to follow with the installation?
Thanks
Andre
I just created a LightSail instance on AWS with CentOS 7 minimal. I updated the OS, installed the NetworkManager package and restarted the server.
Then I ran the following command: curl -sSL https://install.efa-project.org | bash
No errors happened and I restarted the machine. When reconnecting to the server, I started the first configuration and did it as I always did on other occasions. However when I finished and the system started to perform the tasks, I saw the following errors:
[eFa] - Starting MariaDB and Configuring
Dropping the database is potentially a very bad thing to do.
Any data stored in the database will be destroyed.
Do you really want to drop the 'test' database [y/N] Database "test" dropped
ERROR 1064 (42000) at line 20: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'firstseen TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP,
lastsent TIMESTAMP NOT ' at line 11
[eFa] - Configure timezone
[eFa] - Configuring razor
nextserver: Bootstrap discovery failed. Giving up.
nextserver: Bootstrap discovery failed. Giving up.
chmod: cannot access ‘/var/spool/postfix/.razor/identity-*’: No such file or directory
[eFa] - Error initializing system! Please try again...
The installation was aborted. Is there any way to fix this? Is it possible to configure another version (like stable) that is not showing configuration errors? Any other references to follow with the installation?
Thanks
Andre
- shawniverson
- Posts: 3780
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Error on fresh install
One of our mirrors must be behind. These issues have been fixed grrr...
Re: Error on fresh install
Hi, I am trying to install EFA 4.0 and I have just received the same error. What do I do now? Can I re-launch the installation wizard (how?) and see if it connects to a working mirror?
- shawniverson
- Posts: 3780
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Error on fresh install
Working on it. You can work around the issue for now by ensuring that NetworkManager is enabled prior to building.
Code: Select all
sudo systemctl enable NetworkManager
Re: Error on fresh install
Hi
With apologies for replying to a thread from a few months ago, but I've just hit this same issue.
Attempted the workaround with the command "sudo systemctl enable NetworkManager" then reboot and login as root to start the config off again, but it still fails.
Am I doing something wrong?
Ian
With apologies for replying to a thread from a few months ago, but I've just hit this same issue.
Attempted the workaround with the command "sudo systemctl enable NetworkManager" then reboot and login as root to start the config off again, but it still fails.
Am I doing something wrong?
Ian
Re: Error on fresh install
Further info - I reverted my snap to the server-built stage.
ran sudo systemctl enable NetworkManager
install eFa "sudo su" "curl -sSL https://install.efa-project.org | bash"
reboot
login as root, run the configure. same error
nextserver: Bootstrap discovery failed. Giving up
nextserver: Bootstrap discovery failed. Giving up
chmod: cannot access '/var/spool/postfix/.razor/identity-*' : no such file or directory
ran sudo systemctl enable NetworkManager
install eFa "sudo su" "curl -sSL https://install.efa-project.org | bash"
reboot
login as root, run the configure. same error
nextserver: Bootstrap discovery failed. Giving up
nextserver: Bootstrap discovery failed. Giving up
chmod: cannot access '/var/spool/postfix/.razor/identity-*' : no such file or directory
- shawniverson
- Posts: 3780
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Error on fresh install
Are you blocking DNS, by chance?
Re: Error on fresh install
Confirmed not blocking DNS - have allowed $server to be able to talk to the outside to world to everywhere on everything. Checked FW logs and it's talking DNS so it's not that
Yesterday I seemed to get further but today I am stuck at the Razor error again
Code: Select all
[eFa] - Configure timezone
[eFa] - Configuring razor
nextserver: Bootstrap discovery failed. Giving up.
nextserver: Bootstrap discovery failed. Giving up.
chmod: cannot access ‘/var/spool/postfix/.razor/identity-*’: No such file or directory
[eFa] - Error initializing system! Please try again...
Code: Select all
curl -sSL https://install.efa-project.org | bash
Re: Error on fresh install
I must've done something stupid to my server, I rebuilt it , minimal install, allowed it to talk out to anywhere on any port and it works. My bad.
-
- Posts: 1
- Joined: 13 Oct 2021 11:20
Re: Error on fresh install
Was there a fix for this?
I've just gone to build a new eFa server by simply running the 'curl -sSL https://install.efa-project.org | bash' command however I'm getting the following:
I've made sure NetworkManager is enabled and that it has full access to the internet on all ports, however it seems to set the following in resolv.conf and removes current DNS config so it then can't talk out.
Any help would be greatly appreciated. I had this previously all configured through puppet and this was failing so testing the default install script also seems to fail.
I've just gone to build a new eFa server by simply running the 'curl -sSL https://install.efa-project.org | bash' command however I'm getting the following:
Code: Select all
+----[SHA256]-----+
[eFa] - Configure timezone
[eFa] - Configuring razor
nextserver: Bootstrap discovery failed. Giving up.
nextserver: Bootstrap discovery failed. Giving up.
chmod: cannot access ‘/var/spool/postfix/.razor/identity-*’: No such file or directory
[eFa] - Error initializing system! Please try again...
Code: Select all
nameserver 127.0.0.1
nameserver ::1
Re: Error on fresh install
Hi
No, I never got to the bottom of what was wrong with my first attempt. I think I'd broken it somehow by trying to be clever. I had done all sorts like install webmin before installing efa - in the end I scrapped it, went for a minimum install, let it get to anywhere on any port in my edge firewall and then everything was fine.
Good luck!
No, I never got to the bottom of what was wrong with my first attempt. I think I'd broken it somehow by trying to be clever. I had done all sorts like install webmin before installing efa - in the end I scrapped it, went for a minimum install, let it get to anywhere on any port in my edge firewall and then everything was fine.
Good luck!
Re: Error on fresh install
I had the same issue with firewalls running GEO Fencing.
The Razor servers were in Sweden and my GEO Fencing only allows US connectivity.
I allowed Sweden and he installation worked fine, then removed Sweden
The Razor servers were in Sweden and my GEO Fencing only allows US connectivity.
I allowed Sweden and he installation worked fine, then removed Sweden