This is fixed in trunk, thanks for reporting.

This is fixed in trunk, thanks for reporting.

This was found and fixed. Basically, NOTHING could be saved, updated, edited, or tweaked, bad, but I suppose it was “EXTREMELY” safe.

@Tom-Elliott
after upgrade to 4105 :

[Tue Oct 06 14:14:15.158169 2015] [:error] [pid 20445] [client 192.168.39.235:44958] PHP Fatal error: Call to a member function isValid() on string in /var/www/fog/lib/fog/Host.class.php on line 833, referer: http://192.168.39.243/fog/management/index.php?node=host

after upgrade to 4106 : Everything works fine

I updated to the latest git version of FOG today, and whatever had been causing this issue is now gone. This thread can be marked as solved.

Confirmed! Ty again.

This has been fixed for a while. Please update.

You’re being modest.

Is fixed in current, sorry about missing it.

Thought I did … setting it again.

By build 4728, it is fixed. Ty!

@Tom-Elliott said:

@Wayne-Workman I don’t know what you mean.

They are currently synced properly.

gah… I had it backwards… I do apologize, that was confusing.

Change the FOG number every other time - till it’s in sync with the SVN number.

Right now the mobile page does not have a request desktop site. Some of this is because you can create a user who can only login using the mobile interface. I have found and fixed the issues described in the thread. The task page on mobile should not be a searching tool as it is designed to really only display the active tasks and allow you to force or cancel the task. I’ve also made the host page only display the search field rather than always say there are no results when you first look at it.

Then I’m going to solve the thread. As far as I can tell, all of the sources of reports of this horrendous problem are no more occurring on current trunk.

Thank you all for your patience with this.

Very good, I confirm, resolved 😉

@Mark-Shelton said:

Thanks for the info, it helped.
I have 3 nodes in total. One was an older version of ubuntu with an earlier SVN, and this was affecting the bandwidth monitor. I removed it and the 2 up-to-date nodes come up on the monitor. Thanks Wayne.

Thanks for the thanks, but you solved this one yourself. Props where it’s deserved, good job.

I see it occasionally the simple fix is to deploy the image expand the partition and run fixparts if needed then reupload.

Okay, it’s working now. Thanks again for all your help.

@midas1989 Your logs indicate this is for the legacy client. Mind posting this in a new thread?