You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently got 4 new identical nodes for our cluster running CentOS. I've installed webmin in the past without issue, I've installed successfully this time on 3 of the 4 Nodes. The 4th one though doesn't seem to be working.
After much googling debugging, looking through logs, I still can't get this going. The exact error message is: Warning! In order to have System Information displayed you will need to enable System Status module in user settings.
There are exactly 3 results in google concerning this error without any real solution to the problem or even direction where I should be looking to see a error message or something.
Before this point miniserv.error was reporting a missing Authen::PAM module. Fixed that, now everything seems to be working ok.
[15/Nov/2017:16:23:31 +0100] miniserv.pl started
[15/Nov/2017:16:23:31 +0100] IPv6 support cannot be enabled without the Socket6 perl module
[15/Nov/2017:16:23:31 +0100] Using MD5 module Digest::MD5
[15/Nov/2017:16:23:31 +0100] PAM authentication enabled
I'm getting the exact screenshot and problem as this post: https://www.virtualmin.com/node/53053
I can login, but don't have any options available to me other than to logout or refresh in the Dashboard view.
I even manually added a second user from the commandline, same thing. I tried remote management and added it to the server list on the other nodes. When I try to connect to it I get either RPC error : Invalid user for RPC or Login to RPC server as root rejected depending on the user I setup.
I'd really like to get this working but haven't been able to make any progress beyond this point.
The text was updated successfully, but these errors were encountered:
ok, just checked, I don't even have that file in my system. I've made a copy of the file from the other system and now it seems to be working.
Thank you very much. This still doesn't explain why using the same install steps from the same repos and files on 4 identical machines didn't deliver the same result.
That means something went wrong during installation. There may be other problems. webmin.acl is a really core file...there's no way for it to be missing if something didn't go wrong during installation or Webmin or possibly something that may have deleted it later (I have no idea what that might have been).
Check the install log on the problem server for clues, or just start over on that server and watch the install closely for errors next time...it's probably got other issues.
We recently got 4 new identical nodes for our cluster running CentOS. I've installed webmin in the past without issue, I've installed successfully this time on 3 of the 4 Nodes. The 4th one though doesn't seem to be working.
After much googling debugging, looking through logs, I still can't get this going. The exact error message is:
Warning! In order to have System Information displayed you will need to enable System Status module in user settings.
There are exactly 3 results in google concerning this error without any real solution to the problem or even direction where I should be looking to see a error message or something.
Before this point miniserv.error was reporting a missing Authen::PAM module. Fixed that, now everything seems to be working ok.
I'm getting the exact screenshot and problem as this post: https://www.virtualmin.com/node/53053
I can login, but don't have any options available to me other than to logout or refresh in the Dashboard view.
I even manually added a second user from the commandline, same thing. I tried remote management and added it to the server list on the other nodes. When I try to connect to it I get either
RPC error : Invalid user for RPC
orLogin to RPC server as root rejected
depending on the user I setup.I'd really like to get this working but haven't been able to make any progress beyond this point.
The text was updated successfully, but these errors were encountered: