Checking in...Error on GIT 4728
-
When attempting to image, we get an error that simply states “Checking In…” with a counting timer that just keeps going up.
Per Tom’s request, I’ve included the last few entries of log files from httpd’s error_log .
-
@Marcus-Allen What is your Max Connections setting for your storage node set to?
-
2 Nodes, 1 Master. Both are set at 10 connections.
-
Can you try updating again and then tail the apache error log when a system is stuck in the “Checking in” state? I modified a little bit yesterday to try to rid the “headers already sent message” though I don’t think this is directly the problem you’re seeing.
-
-
Here is the tailed file. 10.1.1.28 is a storage node, .24 is the main fog server, .22 is the storage master.
13.249 is the client.
-
the latest require_once error you’re seeing was a mistake
I’m pushing a fix for that right now.The only thing that loads the page is gui side, so at worst you would have seen everything, but had logs filling with that error.
-
Both of these issues (the require_once and the getClientNode) are now fixed please update and try again, keep me posted.
-
Thanks a bunch! You got the imaging going. There is still the can’t modify header information error, but I don’t look at the logs too often, so it doesnt bother me as much! I included them just in case you’d like to check it out though!
-
The header sent messages should be fixed (if you update again) though I don’t know how I like the approach. My approach, currently, is to just check if the headers have already been sent, if not send the headers I want. However, as your output of the log already shows, the headers are already sent before then so the headers I would prefer to be sent may not ever actually get sent.
For now, I’d recommend upgrading just so your server isn’t getting spammed with these errors.
-
Upgraded! Thanks again sir for all of your hard work! It really is appreciated.
-
@Tom-Elliott Jumping on the wagon a bit right here. I’m still having the issue as well. I just upgraded the GIT version and am still having the checking in timeout and tried the SVN version as well and it has the same issue.
-
@Killklli I need details. As @Marcus-Allen has stated this is now fixed, we need more details from your particular use case. Error logs as described and displayed in this thread would be very useful.
-
@Tom-Elliott I think you want the error log? error.log Its while two machines are stuck trying to download an image. All of the other files on this thread just seem to be renditions of that file as far as I can tell.
-
I have the same issue, after installing the latest git and svn. I also have a worse issue that started on version 4457 where the web interface is all screwed up, different things are all over the place, but it was still working, until the latest git / svn where I get this “Checking in” error
I’m running FOG using DNSMASQ on ubuntu 14.04.3 LTS Server on VM … thanks.
-
Please try updating again.
I know this issue is fixed, and has been fixed for a little bit now, but those that keep seeing the issues, please update and try again.
-
@Tom-Elliott Even as is with updating multiple times since then. (Both on Git and SVN) I’m still having the issue.
-
@Killklli
I would suggest starting fresh then to see if it comes up. You are also updating your storage nodes, correct? I’m not sure if you need to update the storage, but it wouldn’t hurt to try. -
@Killklli So every error that is in your attached error log is still occurring?
What does the version in the cloud on you system say? You say you updated, but the Page::sendHeaders() message you seem to be getting hasn’t been in for at least the last 10 or so revisions. The “using $this” out of context message you’re seeing is not possible unless the server that is currently showing under FOG Configuration->FOG Settings->Web Server->FOG_WEB_HOST is not the same as the server you typically use to access your GUI. It’s this particular server (THE FOG_WEB_HOST) that needs to be updated as this is what’s called to do Checking in.
If you can provide more details, such as the error logs, when you update and still “see the same problem”. I ask this because I have had cases of people not realizing that the entries in the logs had not been updated.
-
Well, my issue is back after updating to build 4743.
See attached error log. error_log
I updated yesterday to build 4743 and it stopped working, so I updated again today to 4752 and it still is not working.
