SQLSTATE[42S22]
-
@Tom-Elliott Confirm Boot is working now with rev 5723
-
@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] SELECTpID
FROMprinters
WHEREprinters
.pID
NOT IN () ORDER BY LOWER(printers
.pAlias
) ASC Params: 0And 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 * FROMmodules
WHEREmodules
.id
IN () ORDER BY LOWER(modules
.name
) ASC Params: 0 -
@Tom-Elliott @adukes40 Confirm the issue with the host screen
-
Fixed. Again. Better. Faster. Stronger, or something.
-
@Tom-Elliott Lol. OK, updating again.
-
@Tom-Elliott Alright, my issues seems to be checking out now. All looks good so far. Thanks Tom!
-
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.
-
@Tom-Elliott I was getting ready to say that there was an error Attempting to checkin during deployment. Updating now.
-
@Tom-Elliott OK, looks like imaging is running now. And the other parts still look good.
-
Safe to say this one is solved now?
-
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.
-
@Roger-Saffle You mean invalid security token?
-
@Tom-Elliott yes
-
@Tom-Elliott the reboot problem is fixed, yes
-
@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 -
@adukes40 reset encryption data.
-
@adukes40 Yep that the exact error I was talking about just now. I did a reset on all. Did not seem to make a diff. I went into our all group and hit the big button. Is that what you are asking us to do?
-
@Roger-Saffle time not valid is a bit concerning. That isn’t anything I can help server side. Check you clients times to make sure they’re within the time of the certificate period.
-
@Tom-Elliott
Im sorry I did not see that on his error. Mine does not have a time error. Just the below.--------------------------------Authentication--------------------------------
6/21/2016 12:43 PM Client-Info Version: 0.9.10
6/21/2016 12:43 PM Middleware::Communication URL: http://10.95.95.100/fog/management/other/ssl/srvpublic.crt
6/21/2016 12:43 PM Data::RSA FOG Server CA cert found
6/21/2016 12:43 PM Data::RSA ERROR: Certificate validation failed
6/21/2016 12:43 PM Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: The signature of the certificate cannot be verified. (NotSignatureValid)
6/21/2016 12:43 PM Middleware::Authentication ERROR: Could not authenticate
6/21/2016 12:43 PM Middleware::Authentication ERROR: Certificate is not from FOG CA
6/21/2016 12:43 PM Service Sleeping for 120 seconds -
@Roger-Saffle I think a new thread would be good. This is now leading in an entirely different direction as what the problem was with this thread.