New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Web Gui not responding. #78

Open
SupperCraft5000 opened this Issue Apr 2, 2018 · 4 comments

Comments

Projects
None yet
4 participants
@SupperCraft5000

SupperCraft5000 commented Apr 2, 2018

When i save a setting in the web gui than there is a communication failure every time.

http://prntscr.com/izpklb
http://prntscr.com/izpksr
http://prntscr.com/izpl1s

@votdev

This comment has been minimized.

Collaborator

votdev commented Apr 3, 2018

Please execute the following CLI commands to identify the problem:

# monit stop omv-engined
# omv-engined -d -f

After that repeat your UI actions and check the console output for errors.

@votdev votdev added the 4.x label Apr 3, 2018

@damianperera

This comment has been minimized.

damianperera commented Apr 6, 2018

Came across this issue once in v3.x post initial setup, when intially setting up the filesystems. Managed to fix it after googling.

@NeroBurner

This comment has been minimized.

NeroBurner commented Apr 7, 2018

@damianperera please write down how you fixed it. Then everyone with the same problem can fix it too when stumbling about this issue. Thanks in advance

@damianperera

This comment has been minimized.

damianperera commented Apr 7, 2018

@NeroBurner my issue was directly related to filesystems and was documented by another user in this thread and raised in the previous bug tracker (deprecated). Unfortunately I don't remember how I fixed it, but I might be able to help out here.

@SupperCraft5000 a communication failure in OMV generally occurs when the OMV frontend was not able to execute a linux command successfully (either the command fails or a timeout occurs). If you can login to the CLI of your OMV instance and execute the command you were trying to apply in the web app, you will be able to see more detailed a info/error output.

You can also directly view the console output via the CLI by following the procedure outlined by @votdev.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment