OpenSSL also wants to be secure, so it makes the "secret" data readable only by the current user. The short solution is to just chmod them after the files have been created. We can fix the scripts on our end, but there's likely work to do on the RedHat packages, too. Please also file a bug report with them and reference this one. See also commit 29add13 , which fixed this. At this point, there's nothing more to do on our end.
Your certificate file permissions are set incorrectly, as the error says. Skip to content. Star 1. First of all enable the sql , rest and sqlcounter modules:. Once you have configured properly an SQL server, e. Refer to the sql module documentation for the available configuration values.
The sqlcounter module is used to enforce session limits. We need enable the sqlcounter in a special way. The modules section of radiusd. This is because of a bug in freeradius. This should be solved in a future release of freeradius. Remember you need to add your freeradius server IP address in openwisp freeradius allowed hosts settings. If the freeradius server IP is not in allowed hosts, all requests to openwisp radius API will return It became even worse never start at re boot when upgrading to 2.
Note that the in the original clean install of 2. I experience the exact same issue with a fresh install of pfSense 2. Well, not exactly fresh install: I did have to upgrade from pfSense 2. Service will only start if I save a file on the GUI no changes necessary or start manually from command line as described in this post. I notice this now so I have nothing yet to provide in addition to what was already posted. As mentioned, starting in debug mode provides no additional clue as start-up manually works flawlessly.
Errors in system logs are already provided I those are the ones I see. We were struggling with the same problem, but on a fresh, pristine 2. So far we have found this strange behavior on logs as shown on snapshot1 The server is stopping the radius servce instead of starting it up at the boot process. The logs shown was taken on a clean boot so we're sure there is some error on php-fm rc.
By now the workaround was to install Watchdog package and mark FreeRadius for monitor and start up when found stopped or crashed. It's usefull for other purposes :P. After looking at the code, it seems that it is the way the package is handling a resync.
During a resync it is restarting the service about 9 times as bg calls and confusing the service. This is done by pfSctl -c 'service reload packages'. For me this leads to a always stopped radiusd. All the technical details are way beyond my knowledge.
Since the last upgrade the Freeradius problems are gone and Freeradius is re starting as it should after a reboot of pfSense. Great I don't have to start it manually anymore. I'm on pfSense 2. Since this is a Race Condition the Problem will hit only some users. It depends on the Hardware you are running pfSense on. I like to see this Problem solved in the freeradius2 Package, because now I have to manually patch this every time a new pfSense Version or freeradius2 Package is installed.
I can create a Pull Request against freeradius. Asked 6 years, 6 months ago. Active 1 year, 7 months ago. Viewed 12k times. Improve this question. Add a comment. Active Oldest Votes. You seem to be on Windows. Here you need to use forward slashes! Improve this answer. And the file must exist in the given location and it must be readable by the mysql process.
0コメント