View Issue Details

IDProjectCategoryView StatusLast Update
0001787RackTablesdefaultpublic2017-10-23 22:47
ReporterrdinoffAssigned To 
PrioritynormalSeveritymajorReproducibilityalways
Status newResolutionopen 
PlatformCentOS release 6.9 (Final)OSOS Version
Product Version0.20.14 
Target VersionFixed in Version 
Summary0001787: Argument 'bypass' of value '(NULL)' is invalid
DescriptionWe have upgraded from 0.20.11 to 0.20.14 hoping that this would fix the "Argument 'bypass' of value '(NULL)' is invalid" error but it has not.
Clicking on Objects gives the following error:
 
 https://racktables/index.php?page=depot
 Internal error
 Argument 'bypass' of value '(NULL)' is invalid (must be specified for the given page name).

 Looks like a similar issues was reported in 2013 and resolution was fixed (http://bugs.racktables.org/view.php?id=823)
Steps To ReproduceClicking on Objects
TagsNo tags attached.

Activities

infrastation

infrastation

2017-10-23 16:22

administrator   ~0003747

Does this installation of RackTables list any issues under reports/data integrity?
rdinoff

rdinoff

2017-10-23 16:35

reporter   ~0003749

no issues listed .... "No integrity violations found"
infrastation

infrastation

2017-10-23 16:45

administrator   ~0003751

Could you add the following to the secret.php file and if it prints a stack trace instead of the original error message, copy it here?

$debug_mode = TRUE;
rdinoff

rdinoff

2017-10-23 17:34

reporter   ~0003753

Uncaught exception: InvalidArgException

Argument 'bypass' of value '(NULL)' is invalid (must be specified for the given page name). (0)
at file /var/www/RackTables-0.20.14/wwwroot/inc/functions.php, line 2961

/var/www/RackTables-0.20.14/wwwroot/inc/interface.php:2422 mkA('row#', 'row', NULL)
renderDepot(NULL)
/var/www/RackTables-0.20.14/wwwroot/index.php:35 call_user_func('renderDepot', NULL)
Parameters:

GET

page depot
POST

COOKIE

PHPSESSID 28nsg83p844f1027lj5r1jb576
infrastation

infrastation

2017-10-23 22:47

administrator   ~0003755

Thank you for the update. This issue is not a duplicate as far as I can tell. Looks like it is caused by invalid data coming from the function getMountInfo(); that function has not changed for at least 5 years but I don't remember any similar reports.

If the root cause is discrepancies in the database, the fact the integrity report does not detect them is a bug itself. If I have the time to look into this, I will request more debugging information and provide means to retrieve it.

Issue History

Date Modified Username Field Change
2017-09-15 00:24 rdinoff New Issue
2017-10-23 16:22 infrastation Note Added: 0003747
2017-10-23 16:35 rdinoff Note Added: 0003749
2017-10-23 16:45 infrastation Note Added: 0003751
2017-10-23 17:34 rdinoff Note Added: 0003753
2017-10-23 22:47 infrastation Note Added: 0003755