Dashboard what's going on?
-
Everytime I upgrade lately I loose the dashboard. I tinker with it and re-install or reload the part of it and it starts working. Any ideas?
RC ???
-
When you do a firmware upgrade, it replaces index.php with a fresh copy.
In order for the Dashboard to work, you need to reinstall the dashboard package so it can replace index.php with its own custom copy.
pfSense used to automatically reinstall all packages after every update, but now the proper compatibility features are in the kernel so that is no longer needed (and it took quite a long time to happen, too, if you had squid or snort)
There had been some issues with the dashboard package not reinstalling properly, but those should be sorted out now. Some people may have to reinstall the Dashboard package twice, but after that it will only need once. (The broken uninstaller was used from the cached copy of the package config on the hdd… it takes one update to get rid of that... then another for a proper install to happen)
-
re-installed half a more times and still not working. any ideas?
RC -
Not sure. It's been working for me as I've been tracking snapshots.
After it reboots from loading the new image, I go to the packages page and reinstall it, then it works fine.
You might try to delete /usr/local/www/index.php and then reinstall the dashboard if all else fails.
-
Removing that index file did the trick.
RC -
I'm not sure why that still happens now and then. It used to happen to me all the time, but lately with the changes I've made to the dashboard installer it has cleared up on my test systems.
And as usual, if I can't reproduce the error, it's impossible to know if I've really found a fix.
-
Hmm just a suggestion.
Why not simply remove index.php as a part of reinstall process?
If for some reason it can't be removed then you probably should abort the install and write something to log as to why the file deletion failed.
That way I think it will be easier to reproduce the problem and at least you will have some indication of the failure. -
Hmm just a suggestion.
Why not simply remove index.php as a part of reinstall process?
If for some reason it can't be removed then you probably should abort the install and write something to log as to why the file deletion failed.
That way I think it will be easier to reproduce the problem and at least you will have some indication of the failure.At some point I had tried that and I don't recall why it didn't work. It does try it again now, as of the version I committed yesterday afternoon.
Part of the problem is that lately it no longer misbehaves on any of my systems…
-
For months I'd have to re-install twice to get the 2.0 Dashboard back. Now with the latest snapshots I just reinstall it and it comes back normally. :)
Eventually when PfSense 2.0 goes gold it won't be an issue since Dashboard 2.0 will be part of it.
Darkk
-
For months I'd have to re-install twice to get the 2.0 Dashboard back. Now with the latest snapshots I just reinstall it and it comes back normally. :)
Yeah, I think I finally got it sorted out. PHP's APC cache was holding the old index.php in memory, and I was removing it with an exec call to rm, which didn't update the cache. I replaced that with a PHP unlink() call and that seems to make it handle the transition.
