Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Freeradius not start

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    4 Posts 2 Posters 4.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      max_ens
      last edited by

      Mon Jan 10 22:32:50 2011 : Info: Using deprecated naslist file.  Support for this will go away soon.
      Mon Jan 10 22:32:50 2011 : Info: Using deprecated naslist file.  Support for this will go away soon.
      Mon Jan 10 22:32:50 2011 : Error: There appears to be another RADIUS server running on the authentication port 1812
      Mon Jan 10 22:32:50 2011 : Info: rlm_exec: Wait=yes but no output defined. Did you mean output=none?
      Mon Jan 10 22:32:51 2011 : Info: Ready to process requests.
      Mon Jan 10 22:32:52 2011 : Info: Reloading configuration files.

      ever i restart the server pfsense the package freeradius start like the log so i need change the port and restart the service to can use. this is normal or exist an other way to work fine.
      this the same in x86 and x64 i use in both and its the same error.

      1 Reply Last reply Reply Quote 0
      • N
        Nachtfalke
        last edited by

        This is a problem posted in several other posts.
        freeRADIUS package is started several time on startup, so the radiusd ist startet twice.

        When I used it in the past I used the cosole and killall radiusd and then restart it. Then you do not need to change the port.

        Error: There appears to be another RADIUS server running on the authentication port 1812
        

        Hope this helps

        1 Reply Last reply Reply Quote 0
        • M
          max_ens
          last edited by

          thanks i try, this i thik works, but i think its better try fix in RC or not?

          1 Reply Last reply Reply Quote 0
          • N
            Nachtfalke
            last edited by

            Of course a fix would be better - this is just a workaround.
            But I am not sure who is responsible for this package - I don't think the pfsense builders are.

            I only know that I do not have the skills to do that ;)

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.