This helped me. I changed the bind-address from my IP to 0.0.0.0
Significantly less secure I think, but it worked.
I was on 3396. Looked it up in my records.
This helped me. I changed the bind-address from my IP to 0.0.0.0
Significantly less secure I think, but it worked.
I was on 3396. Looked it up in my records.
Also for what it’s worth, the same error message shows up on everyone in line. So the Waiting on X other clients always has zero for the value no matter how many in line.
scratch the deploy slots comment. I played with some settings and it is working. Still get this error message though.
When deploying images to multiple computers from storage nodes I get an uncaught exception error if there are other image deploys in progress. It also seems to limit me to one deploy at a time. I have available deploy slots. Attached is a pic of the error.
After the deploys to other computers finish, it continues on just as it did previously.
For what it’s worth, when updating, sometimes that step times out and sometimes it doesn’t. It seems to be an internet connectivity issue on either my end or the other end. I had this when updating to 5592
@Tom-Elliott Thanks Tom. Just pulled and installed and it’s working for me too.
When creating a new image in Image Management on the latest SVN, if I choose a different Storage Group and submit the form, the Storage Group selection doesn’t reflect on the image definition. It switches to default storage group. If I upload to that image it also uses the default storage group.
Currently, I am only seeing notifications from the fog client if I am logged in as an administrator level user. So scheduled shutdowns just shut the computer off if a standard user is logged in. Is this a misconfiguration on my part? I’m running client 0.9.5 and server version 5124
@Tom-Elliott Thanks for all your work on fog. Long time user. I’m on 5124 and CPU utilization looks good. I echo @Trevelyan 's concern about the user tracker report. CPU utilization goes high and then comes back down after the 500 error is sent to the browser. I know you said you’d fix it when you got to work. Is there a way for me to find out what version fixes it? Then I won’t bother posting this question in the forum.
Thanks,
Mark
This helped me. I changed the bind-address from my IP to 0.0.0.0
Significantly less secure I think, but it worked.
I was on 3396. Looked it up in my records.
I just pulled via git and am running the install script. At the upgrade database step I refresh my fog host and click the button to do the schema update. After that I get a blank page. Apache.error shows a lot of couldn’t fect mysqli in …Mysql.class.php on line 63 preceeded by two HY000/2002 errors.
My understanding is that this means that it’s not connecting to the database. Any pointers on this one?
This was an upgrade from a previous svn ~3300 or so…