Hi,
I just did the upgraded to 0.5.36 and received a blank screen after logging in -
did:
and saw:
I Can see this has happened previous and a quick fix is:
Hope this helps someone else.
Hi,
I just did the upgraded to 0.5.36 and received a blank screen after logging in -
did:
and saw:
I Can see this has happened previous and a quick fix is:
Hope this helps someone else.
Clearing your cache should also do that trick.
Would that solve the missing folder?
I tried 3 browsers and Chrome incognito - No cache.
You´re correct. that fixed just the first error. After login i also receive a blank screen.
It is running. You get to the login page, type in your credentials and then you get a blank screen.
Yes, and after creating the symlink it also shows the page correctly - as I wrote.
I opened up a bugreport:
http://bugtracker.openmediavault.org/view.php?id=997
Upgrade to 5.37. I think Volker probably fixed it already.
ZitatWithdrawing this: (Can't use
TEXTfor some reason)
Seems to have done the trick - Upgrade went fine, page loads as expected.
Quick fix - Thanks.
Could be because of the symlink that stayed it continued to work. On my way to sleep so wont have time to test.
Nope. 0.5.37 does not fix it. At least not at my VM. Have not tried it at my productive.
This is path error on something updated. I don't know if old path from .4 or new path from .6 was in Volker's head. He should fix it soon.
I am also experiencing the same issue I tried the sym link and get the same result a blank page but the error changes see below
I sent message to Volker on this issue.
That might be a typo in the sabnzbd installation using Miller's script.
**edit - can't find it there either...
Just updated to the newest version and got the blank page too.
But thanks to the first post and the command "ln -s /var/www/openmediavault/js/omv /var/www/openmediavault/OMV" i got it fixed for now
Thanks to the OP, but of course to the team of OMV too. Use this since some weeks now and it's great!
When it is fixed we will tell you to delete the symmlink.
Just updated to 0.5.37 and not having the problem. Did a recursive grep through all of the OMV source and I don't see anything pointing to /var/www/openmediavault/OMV. Not sure what is causing the problem.
Maybe just ppl that upgraded to .5.36 are having this issue. WastlJ, did you upgrade to .5.36??? before you did .5.37?
Ryeco, did you look at Volker's edits so we could have them fix manually?
Okay so it is directly connected to openmediavault-sabnzbd when using Miller testing repository I remove sabnzbd using "apt-get remove openmediavault-sabnzbd" and was able to log in and get the status page again.
hmmm..... so not volker's fault?
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!