mudboy Posted September 11, 2017 Share Posted September 11, 2017 Getting this on the 6.4 RC8 release. Warning: Illegal string offset 'PK1334PEKDAGZS' in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 187 Fatal error: Uncaught Error: Cannot use string offset as an array in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php:187 Stack trace: #0 /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php(86): Get_JSON_Config_File() #1 /usr/local/emhttp/plugins/serverlayout/php/serverlayout_layout.php(2): require_once('/usr/local/emht...') #2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(378) : eval()'d code(1): include('/usr/local/emht...') #3 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(378): eval() #4 /usr/local/emhttp/plugins/dynamix/template.php(62): require_once('/usr/local/emht...') #5 {main} thrown in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 187 Not sure if that's a 6.4 beta issue, or something else, but thought I would mention it in case it's a 6.4 related issue. Quote Link to comment
themaxxz Posted September 21, 2017 Share Posted September 21, 2017 On 15-6-2017 at 10:44 PM, themaxxz said: Just noticed the same thing on my server, running identical versions. After switching my unRAID from virtualized to BM, and removing some usb keys that were giving 'errors', the layout is working again for me. Quote Link to comment
wgstarks Posted September 24, 2017 Share Posted September 24, 2017 I see a warning in my logs every time i connect to this plugin- Sep 24 08:37:28 Brunnhilde rc.diskinfo[16281]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 687 Sep 24 08:37:28 Brunnhilde rc.diskinfo[16281]: SIGHUP received, forcing refresh of disks info. Quote Link to comment
BobPhoenix Posted September 26, 2017 Share Posted September 26, 2017 I believe "rc.diskinfo" is part of the preclear plugin. You can disable diskinfo by typing "/etc/rc.d/rc.diskinfo --quit" and these messages will likely go away. Quote Link to comment
redeuxx Posted November 6, 2017 Share Posted November 6, 2017 I know I can clean up and print my server layout, but would it be possible to make a print friendly version of the page? Thanks! Quote Link to comment
Cessquill Posted December 21, 2017 Share Posted December 21, 2017 I'm getting the same stream of errors on the layout page as mentioned previously.. (starts with Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 126 Warning: array_key_exists() expects parameter 2 to be array,...) I'm running 6.4.0_rc16b and have unassigned devices installed. Has a source been found for this issue? The data tab also contains errors (can list if required), and Chrome's console has the following errors... serverlayout:1932 Uncaught SyntaxError: Unexpected token < serverlayout:2416 Uncaught ReferenceError: StartUp is not defined at serverlayout:2416 I'm running the latest version of the plugin in from CA. Quote Link to comment
itimpi Posted December 21, 2017 Share Posted December 21, 2017 I have a feeling this plugin is going to need updating to make it compatible with the latest 6.4 release. 1 Quote Link to comment
Squid Posted December 22, 2017 Share Posted December 22, 2017 (edited) 13 hours ago, itimpi said: I have a feeling this plugin is going to need updating to make it compatible with the latest 6.4 release. I've tagged the app as being incompatible with 6.4 since this issue has existed and been reported since July. I've issued a PR to @theone with the fix. But, in the meantime you can add this either to your go file or as a user script set to run at array start to fix the problem sed -i 's/\"DISK_DATA\" => \"\"/\"DISK_DATA\" => array()/' /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php Edited December 22, 2017 by Squid 3 4 Quote Link to comment
redeuxx Posted December 29, 2017 Share Posted December 29, 2017 I have a 20 bay case. But in addition to those 20 bays, I have two 2.5" mounts that are placed elsewhere in the case. Is it possible to create a separate layout for these two mounts? Quote Link to comment
trurl Posted December 29, 2017 Share Posted December 29, 2017 4 hours ago, redeuxx said: I have a 20 bay case. But in addition to those 20 bays, I have two 2.5" mounts that are placed elsewhere in the case. Is it possible to create a separate layout for these two mounts? You use an empty row or column to create space between different parts of the layout. Quote Link to comment
lewcass Posted January 13, 2018 Share Posted January 13, 2018 (edited) Just upgraded to unRAID 6.4 and now getting error when trying to access Server Layout. Quote Warning: Illegal string offset 'WD-WCC4M0484703' in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 187Fatal error: Uncaught Error: Cannot use string offset as an array in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php:187 Stack trace: #0 /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php(86): Get_JSON_Config_File() #1 /usr/local/emhttp/plugins/serverlayout/php/serverlayout_layout.php(2): require_once('/usr/local/emht...') #2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(379) : eval()'d code(1): include('/usr/local/emht...') #3 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(379): eval() #4 /usr/local/emhttp/plugins/dynamix/template.php(62): require_once('/usr/local/emht...') #5 {main} thrown in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 187 So am no longer able to access the layout at all. Was working OK yesterday on 6.3.5. Any suggestions? Edited January 13, 2018 by lewcass Quote Link to comment
remotevisitor Posted January 13, 2018 Share Posted January 13, 2018 (edited) Did you apply the work around Squid posted about 3 post back in the thread? Edited January 13, 2018 by remotevisitor Quote Link to comment
Squid Posted January 13, 2018 Share Posted January 13, 2018 2 minutes ago, lewcass said: Just upgraded to unRAID 6.4 and now getting error when trying to access Server Layout. So am no longer able to access the layout at all. Was working OK yesterday on 6.3.5. Any suggestions? Look up a couple of posts Quote Link to comment
lewcass Posted January 13, 2018 Share Posted January 13, 2018 Will do. Sorry I missed that! Thanks. Quote Link to comment
lowbiker Posted January 15, 2018 Share Posted January 15, 2018 Anyone else get an error like this? "Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 114382050000070232 bytes) in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 213" Quote Link to comment
Cessquill Posted January 15, 2018 Share Posted January 15, 2018 4 hours ago, lowbiker said: Anyone else get an error like this? "Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 114382050000070232 bytes) in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 213" Read up a few posts Quote Link to comment
CorneliousJD Posted January 23, 2018 Share Posted January 23, 2018 Any update on getting this integrated into the actual plugin and updated in CA? Would like to avoid the patch provided as I know I'll forget that it's there and stumble on it in 6 months asking myself "what the heck is this..." 1 Quote Link to comment
Squid Posted January 24, 2018 Share Posted January 24, 2018 19 hours ago, CorneliousJD said: Any update on getting this integrated into the actual plugin and updated in CA? Would like to avoid the patch provided as I know I'll forget that it's there and stumble on it in 6 months asking myself "what the heck is this..." The apply the patch via the user scripts plugin so you can also have a description. I've had the PR sitting there for @theone to approve since I posted the patch in December. Quote Link to comment
Cessquill Posted January 24, 2018 Share Posted January 24, 2018 19 minutes ago, Squid said: The apply the patch via the user scripts plugin so you can also have a description. I've had the PR sitting there for @theone to approve since I posted the patch in December. Thanks - I missed the bit about running it as a user script in your previous post. Sorts it out just fine. Quote Link to comment
theone Posted January 25, 2018 Author Share Posted January 25, 2018 Sorry for the delay. I have other things on my plate at the moment. Released update. 2018.01.25 - Updated for unRAID v6.4 - Thank you Squid Quote Link to comment
Squid Posted January 25, 2018 Share Posted January 25, 2018 Sorry for the delay. I have other things on my plate at the moment. Released update. 2018.01.25 - Updated for unRAID v6.4 - Thank you Squid I'll remove the incompatible flag in a couple of hours Quote Link to comment
Squid Posted January 25, 2018 Share Posted January 25, 2018 Anyone who applied the line to patch the plugin can now safely remove it after updating their plugin. Quote Link to comment
CorneliousJD Posted January 26, 2018 Share Posted January 26, 2018 7 hours ago, theone said: Sorry for the delay. I have other things on my plate at the moment. Released update. 2018.01.25 - Updated for unRAID v6.4 - Thank you Squid Thanks for the update, working great again now. Hope whatever is in your plate isn't bad stuff! Quote Link to comment
michael123 Posted January 26, 2018 Share Posted January 26, 2018 (edited) Hello I have m.2 flash used as a cache drive, it is internal mounted to the motherboard via pci adapter I see it listed together with other SATA devices I think it might be better to show it separately, similar to the way unraid usb stick is pictured Edited January 26, 2018 by michael123 Quote Link to comment
Cessquill Posted January 26, 2018 Share Posted January 26, 2018 2 hours ago, michael123 said: Hello I have m.2 flash used as a cache drive, it is internal mounted to the motherboard via pci adapter I see it listed together with other SATA devices I think it might be better to show it separately, similar to the way unraid usb stick is pictured On 12/29/2017 at 1:50 PM, trurl said: You use an empty row or column to create space between different parts of the layout. Not an ideal workaround, but it's what other people are doing. I have my parity and cache disks inside the case (the caches on PCI mounts). 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.