Another update another lost access storage.
-
@Tom-Elliott
I understand about the mentality but if it breaks on nightly updates then is not beneficial as the error just keep coming back. I understand about debugging as well, it is just counter productive when the same error keep reappearing, wouldn’t you agree?
It is hard to provide details when I am totally unsure what are you looking for.
Apache error.log with tail command
[Thu Jun 18 16:58:20.278610 2015] [:error] [pid 7926] [client 192.168.1.111:17100] PHP Warning: current() expects parameter 1 to be array, string given in /var/www/fog/lib/fog/Image.class.php on line 146, referer: http://192.168.1.133/fog/management/index.php?node=group&sub=edit&id=10
[Thu Jun 18 16:58:20.304759 2015] [:error] [pid 7926] [client 192.168.1.111:17100] PHP Warning: current() expects parameter 1 to be array, string given in /var/www/fog/lib/fog/Image.class.php on line 146, referer: http://192.168.1.133/fog/management/index.php?node=group&sub=edit&id=10
[Thu Jun 18 16:58:20.354456 2015] [:error] [pid 7926] [client 192.168.1.111:17100] PHP Warning: current() expects parameter 1 to be array, string given in /var/www/fog/lib/fog/Image.class.php on line 146, referer: http://192.168.1.133/fog/management/index.php?node=group&sub=edit&id=10
[Thu Jun 18 16:58:20.408619 2015] [:error] [pid 7926] [client 192.168.1.111:17100] PHP Warning: current() expects parameter 1 to be array, string given in /var/www/fog/lib/fog/Image.class.php on line 146, referer: http://192.168.1.133/fog/management/index.php?node=group&sub=edit&id=10
[Thu Jun 18 17:14:31.313708 2015] [:error] [pid 8198] [client 192.168.1.111:17521] PHP Warning: current() expects parameter 1 to be array, string given in /var/www/fog/lib/fog/Image.class.php on line 146, referer: http://192.168.1.133/fog/management/index.php?node=group
[Thu Jun 18 17:14:31.314278 2015] [:error] [pid 8198] [client 192.168.1.111:17521] PHP Fatal error: Call to a member function get() on a non-object in /var/www/fog/lib/pages/ImageManagementPage.class.php on line 101, referer: http://192.168.1.133/fog/management/index.php?node=group
[Thu Jun 18 17:15:59.447887 2015] [:error] [pid 10795] [client 192.168.1.111:17559] PHP Warning: current() expects parameter 1 to be array, string given in /var/www/fog/lib/fog/Image.class.php on line 146, referer: http://192.168.1.133/fog/management/index.php?node=storage&sub=edit&id=3
[Thu Jun 18 17:15:59.448462 2015] [:error] [pid 10795] [client 192.168.1.111:17559] PHP Fatal error: Call to a member function get() on a non-object in /var/www/fog/lib/pages/ImageManagementPage.class.php on line 101, referer: http://192.168.1.133/fog/management/index.php?node=storage&sub=edit&id=3
[Thu Jun 18 17:16:07.008015 2015] [:error] [pid 7082] [client 192.168.1.111:17560] PHP Warning: current() expects parameter 1 to be array, string given in /var/www/fog/lib/fog/Image.class.php on line 146, referer: http://192.168.1.133/fog/management/index.php?node=storage&sub=edit&id=3
[Thu Jun 18 17:16:07.008583 2015] [:error] [pid 7082] [client 192.168.1.111:17560] PHP Fatal error: Call to a member function get() on a non-object in /var/www/fog/lib/pages/ImageManagementPage.class.php on line 101, referer: http://192.168.1.133/fog/management/index.php?node=storage&sub=edit&id=3The image page is displaying totally blank.
-
What same error?
-
@Tom-Elliott
At the surface it seems to be the same error. When a deployment task is being created I get the image needs to be uploaded before creating a deployment task. It is almost as if the storage keep dropping every time an updated is done in the server.I am thinking to stay in one version and won’t upgrade any longer.
-
I’m still confused. When was this occurring before? Did I fix it at any point? Is it a particular set of sequences?
-
Yes, it was fixed previously and it was running as normal. Today the new SVN was downloaded and installed and the page for Image Management is now blank. All the permission are the same and has not changed. It is the only page that it is not working that I have noticed so far.
-
Discovering more errors in the error logs while searching through:
[Thu Jun 18 17:39:01.387369 2015] [:error] [pid 15195] [client 192.168.1.111:19252] PHP Fatal error: Call to a member function get() on a non-object in /var/www/fog/lib/pages/ImageManagemephp on line 101, referer: http://192.168.1.133/fog/management/index.php?node=group&sub=add
[Thu Jun 18 17:40:38.262594 2015] [:error] [pid 7926] [client 192.168.1.111:19297] PHP Warning: Invalid argument supplied for foreach() in /var/www/fog/lib/fog/FOGPage.class.php on line 11http://192.168.1.133/fog/management/index.php?node=printer&sub=edit&id=1
[Thu Jun 18 17:41:31.916370 2015] [:error] [pid 14931] [client 192.168.1.111:19356] PHP Warning: current() expects parameter 1 to be array, string given in /var/www/fog/lib/fog/Image.class146, referer: http://192.168.1.133/fog/management/index.php
[Thu Jun 18 17:41:31.916939 2015] [:error] [pid 14931] [client 192.168.1.111:19356] PHP Fatal error: Call to a member function get() on a non-object in /var/www/fog/lib/pages/ImageManagemephp on line 101, referer: http://192.168.1.133/fog/management/index.php
[Thu Jun 18 17:42:30.600227 2015] [:error] [pid 15537] [client 192.168.1.111:19390] PHP Warning: current() expects parameter 1 to be array, string given in /var/www/fog/lib/fog/Image.class146, referer: http://192.168.1.133/fog/management/index.php?node=task&sub=scheduled
[Thu Jun 18 17:42:30.600806 2015] [:error] [pid 15537] [client 192.168.1.111:19390] PHP Fatal error: Call to a member function get() on a non-object in /var/www/fog/lib/pages/ImageManagemephp on line 101, referer: http://192.168.1.133/fog/management/index.php?node=task&sub=scheduled
[Thu Jun 18 17:42:49.338161 2015] [:error] [pid 14931] [client 192.168.1.111:19393] PHP Warning: array_merge(): Argument #1 is not an array in /var/www/fog/lib/pages/ReportManagementPage.cine 915, referer: http://192.168.1.133/fog/management/index.php?node=report&sub=pend-mac
[Thu Jun 18 17:42:50.915890 2015] [:error] [pid 7926] [client 192.168.1.111:19394] PHP Warning: asort() expects parameter 1 to be array, null given in /var/www/fog/lib/pages/ReportManagemephp on line 625, referer: http://192.168.1.133/fog/management/index.php?node=report&sub=snapin-log
[Thu Jun 18 17:42:53.682164 2015] [:error] [pid 15195] [client 192.168.1.111:19395] PHP Fatal error: Undefined class constant ‘FOG_REPORT_HTML’ in /var/www/fog/management/reports/Hosts and line 62, referer: http://192.168.1.133/fog/management/index.php?node=report&sub=vir-hist
[Thu Jun 18 17:43:00.905470 2015] [:error] [pid 7926] [client 192.168.1.111:19394] PHP Fatal error: Undefined class constant ‘FOG_REPORT_HTML’ in /var/www/fog/management/reports/Hosts and line 62, referer: http://192.168.1.133/fog/management/index.php?node=report&sub=vir-hist -
@Tom-Elliott
Is it possible to go back to a previous version? -
I actually have a suspicion as to your particular issue. And am about to push a potential fix if you’d be willing to update.
-
@Tom-Elliott
I am ready is you are. I am all game at this point. -
@DarkEnergy 3573
-
@Tom-Elliott
No dice, still a blank page -
Yep, I found that out.
It’s because the ImagePartitionType isn’t set for that image. Ultimately, if it’s not set, it should auto set to be an “everything” type.
-
@DarkEnergy Should be fixed, at least for the line 102 issue, can you test and let me know? SVN 3574
-
@Tom-Elliott
Sorry, while I understand what you mean, I am not an experience programmer.
How would like me to proceed? What changes need to be made to the code? -
@DarkEnergy I’ll do the work, I just like to express the issue so others happening can understand the problem. I don’t expect you to do anything with it. It’s just a way of speaking out loud if you will.
-
@Tom-Elliot
Totally understand!!! Selftalks are the best way to communicate. I do that a lot in my everyday admin position. -
If you have multiple storage nodes within one storage group, not having one set as “master” would cause something like this. Also, Some users have experienced their /etc/exports getting written over, and only having one storage node wrote back instead of them all.
But from the sound of it, I think that this is not the case, and Tom is working on the actual problem… I just wanted to chime in for future readers where these things might be the case.
-
This should be fixed as of latest svn.
-
@cml
Can you please provide the latest SVN number? The issue was after updating the last version before yesterday.@Wayne-Workman
All my storage nodes are local and the default storage is set as master as well. I did my homework before coming for help. -
@DarkEnergy If you go to your /svn/trunk directory,
To get the latest revision, all you have to type is
[CODE]svn up[/CODE]