SQLSTATE[42S22]

[adukes40]

@Tom-Elliott Ok, updated all nodes, the Location can be set now, but still getting the SQLSTATE[42000] chainload issue

[Raymond Bell]

@adukes40 said in SQLSTATE[42S22]:

@Tom-Elliott Ok, updated all nodes, the Location can be set now, but still getting the SQLSTATE[42000] chainload issue

Confirm this issue … Guest stick in boot loop

[Tom Elliott]

Issue is now fixed, again, please update. This time it’s for sure. Last time the “fix” was to stop a die from occurring by simply removing the “die” element.

Now the die is left in place so queries can error straight to the user to allow us better finding of issues. Sorry about the issue this caused.

[adukes40]

@Tom-Elliott OK, updating now, be back in a few

[Raymond Bell]

@Tom-Elliott Confirm Boot is working now with rev 5723

[adukes40]

@adukes40 OK, the boot now goes through. However, the host screen now look different and there is a SQL error at the bottome of the page, can’t change location again. Here are some screenshots:

This is at the bottom of the above page:

SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘) ORDER BY LOWER(printers.pAlias) ASC’ at line 1 SQL: [103] SELECT pID FROM printers WHERE printers.pID NOT IN () ORDER BY LOWER(printers.pAlias) ASC Params: 0

And when changing the location I get this:

SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘) ORDER BY LOWER(modules.name) ASC’ at line 1 SQL: [89] SELECT * FROM modules WHERE modules.id IN () ORDER BY LOWER(modules.name) ASC Params: 0

[Raymond Bell]

@Tom-Elliott @adukes40 Confirm the issue with the host screen

[Tom Elliott]

Fixed. Again. Better. Faster. Stronger, or something.

[adukes40]

@Tom-Elliott Lol. OK, updating again.

[adukes40]

@Tom-Elliott Alright, my issues seems to be checking out now. All looks good so far. Thanks Tom!

[Tom Elliott]

Update again, I found another issue with imaging that it couldn’t find the right field.

This is now fixed, and I think imaging is more important than GUI. Hopefully all will be well.

[adukes40]

@Tom-Elliott I was getting ready to say that there was an error Attempting to checkin during deployment. Updating now.

[adukes40]

@Tom-Elliott OK, looks like imaging is running now. And the other parts still look good.

[Tom Elliott]

Safe to say this one is solved now?

[Roger Saffle]

im seeing some cert errors in my clients after doing all these updates. I went into our all group and hit the cert update button. Is that all I need to do? Doing latest update now.

[Tom Elliott]

@Roger-Saffle You mean invalid security token?

[Roger Saffle]

@Tom-Elliott yes

[Roger Saffle]

@Tom-Elliott the reboot problem is fixed, yes

[adukes40]

@Tom-Elliott Just set an image and came back to it in sleep mode. Checked machine and the snapins did not run. I found this in the log:

---

--------------------------------Authentication--------------------------------

6/21/2016 8:56 AM Client-Info Version: 0.9.12
6/21/2016 8:56 AM Middleware::Communication URL: http://10.103.72.49/fog/management/other/ssl/srvpublic.crt
6/21/2016 8:56 AM Middleware::Authentication ERROR: Could not get security token
6/21/2016 8:56 AM Middleware::Authentication ERROR: Could not find file ‘C:\Windows\system32\token.dat’.
6/21/2016 8:56 AM Data::RSA FOG Server CA cert found
6/21/2016 8:56 AM Data::RSA ERROR: Certificate validation failed
6/21/2016 8:56 AM Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. (NotTimeValid)
6/21/2016 8:56 AM Middleware::Authentication ERROR: Could not authenticate
6/21/2016 8:56 AM Middleware::Authentication ERROR: Certificate is not from FOG CA
6/21/2016 8:56 AM Service Sleeping for 120 seconds

[Tom Elliott]

@adukes40 reset encryption data.