 |
What is the message above the URL that you open? |
 |
when I entered http://<node>/racktables it redirected me to racktables/wwwroot/?module=installer |
|
|
There are a few strange things about this issue. 1. When RackTables prompts to install or to upgrade, it does not redirect. It returns a page with a message and a link and it is up to the user whether to follow the link. 2. When RackTables URI is "/racktables/", it will never redirect a user to "/racktables/wwwroot/". 3. The installer always starts at step 1. 4. After the upgrade RackTables never prompts to run the installer (unless the upgrade involved removing secret.php). It would help if you double-checked everything and provided exact steps to reproduce the problem. |
|
|
As the upgrade instruction consisted of: # How to upgrade RackTables 0. **Backup your database** and check the release notes below before actually starting the upgrade. 1. Remove all existing files except configuration (the `inc/secret.php` file) and local plugins (in the `plugins/` directory). 2. Put the contents of the new tar.gz/zip archive into the place. 3. Open the RackTables page in a browser. The software will detect version mismatch and display a message telling to log in as admin to finish the upgrade. 4. Do that and report any errors to the bug tracker or the mailing list. The easiest way to remove all the existing files was just rename the racktable directory, create a new one, restore the inc/secret.php file and the plugins directory. Then, place the contents of the new release into the racktables directory. |
|
|
One actual bug I can confirm is that in RackTables 0.20.14 at installer step 4 if the code fails to require secret.php (after the user has likely adjusted the permissions as advised on the previous page) it ends ups in a blank page and an error in the log file: PHP Fatal error: require_once(): Failed opening required '/usr/local/racktables/wwwroot/inc/secret.php' (include_path='.:/usr/share/php') in /usr/local/racktables/wwwroot/inc/pre-init.php on line 48 But in the first place the installer does not start when secret.php is present. |
|
|
Looking in the web server log, I do see the PHP Fatal error that you mentioned - any idea how to resolve it? Maybe try 0.21.0? |
|
|
To resolve the failure to require secret.php it would help to make the file readable (as much as the web-server process is concerned, specifically). To understand other issues mentioned here it would help to read my comment 4 comments before and provide the specific information it requests. |
|
|
What information are you asking for? I provided the steps taken for the upgrade. |
|
|
changing the protection to 755 on secret.php resulted in the login being displayed - in version 0.20.10 I did not have to do this....in any case, the problem is resolved. |
- Anonymous
