Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 2 subscribers
  • Views 1315 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

7.1 Update - no user authentication

brugger
On Friday, I updated our firmware from 7.011 to 7.1. Everything worked fine. This morning (Monday) everyone is being continuously prompted for authentication and then receive a "Authentication Failed" message. I have tried to use the back-up/restore page on the web portal to restore to a previous backup but the firmware remains at 7.1.

Any Ideas?


This thread was automatically locked due to age.
  • 0
    You can't roll back firmware versions... a reinstall would be in order to go back to 7.011.  NOt sure why you're getting that authentication error, that is wierd.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

  • 0 in reply to BrucekConvergent
    I had a similar issue after upgrading to 7.1. It ended up being the lack of an entry in the > Network> DNS> Request Routing>  "Add an entry for your Active Directory Server..
  • 0
    Are you using Active Directory?
    Do you have a HA/Cluster setup?

    Kind Regards,
    Daniel
  • 0 in reply to anonymous_02
    Yes, we are using Active Directory.

    I just worked with Astaro support, finally got a contact back, and they got it working again.  Never found out why it was doing it, but it is back up now.
  • 0 in reply to brugger
    I'd ask what they did to fix it.  I had one system that had a problem with an old winbindd.pid file that was keeping winbindd from starting... just curious if that was it.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

  • 0 in reply to BrucekConvergent
    I'd ask what they did to fix it.  I had one system that had a problem with an old winbindd.pid file that was keeping winbindd from starting... just curious if that was it.


    I saw your post in the other thread about this issue, thought that might have been my problem. Turned out to be something else. Try posing the procedure for correcting the PID issue so others can try...

    Regards,
  • 0 in reply to Igor.DeCamps
    sure...

    First, a disclaimer for you folks that have purchased maintenance... this could void your warrantly unless Astaro Support asks you to do this; now, with that out of the way, try:

    1) Disabling the HTTP Proxy
    2) Log into the shell (console or SSH)
    3) look for a winbindd.pid file in the /var/locks/ directory
    4) If present, delete the file
    5) Re-enable the HTTP Proxy
    6) log out of the shell

    This should kick things off if your problem was the same as mine; a corrupt / out of date .pid file (happened during the upgrade).  You could also try rebooting after this procedure if you'd like, but re-enabling the proxy was enough in my case.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

Cookie Information Banner