RC21 - Can't Deploy Images From GUI. "Image does not exist on any node"


  • Testers

    Server
    • FOG Version: RC21
    • OS: Cent OS 7 x64
    Client
    • Service Version:
    • OS:
    Description

    I go to deploy my base image on a new host and I just get his “Image does not exist on any node” error. I made sure it was set proper in other parts of the gui and it is. It shows its size on the server and everything in the gui. I check on the server and the file is there on the main server and on the storage node.
    my apache error log with newest on top

    [Tue Nov 08 14:27:11.377153 2016] [core:notice] [pid 9489] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
    [Tue Nov 08 14:27:11.377107 2016] [mpm_prefork:notice] [pid 9489] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips PHP/7.0.12 configured -- resuming normal operations
    [Tue Nov 08 14:27:11.337102 2016] [lbmethod_heartbeat:notice] [pid 9489] AH02282: No slotmem from mod_heartmonitor
    [Tue Nov 08 14:27:11.335873 2016] [auth_digest:notice] [pid 9489] AH01757: generating secret for digest authentication ...
    AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using ::1. Set the 'ServerName' directive globally to suppress this message
    [Tue Nov 08 14:27:11.285230 2016] [suexec:notice] [pid 9489] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
    [Tue Nov 08 14:25:58.828060 2016] [mpm_prefork:notice] [pid 6186] AH00170: caught SIGWINCH, shutting down gracefully
    [Tue Nov 08 14:25:53.875911 2016] [:error] [pid 6193] [client 192.168.100.144:61029] PHP Warning: PDO::__construct(): MySQL server has gone away in /var/www/html/fog/lib/db/pdodb.class.php on line 151
    [Tue Nov 08 14:25:51.904220 2016] [:error] [pid 7292] [client 192.168.9.151:50550] PHP Warning: PDO::__construct(): MySQL server has gone away in /var/www/html/fog/lib/db/pdodb.class.php on line 151
    [Tue Nov 08 14:25:51.861942 2016] [:error] [pid 6197] [client 192.168.9.151:62462] PHP Warning: PDO::__construct(): MySQL server has gone away in /var/www/html/fog/lib/db/pdodb.class.php on line 151
    [Tue Nov 08 14:25:51.853218 2016] [:error] [pid 7272] [client 192.168.9.151:58260] PHP Warning: PDO::__construct(): MySQL server has gone away in /var/www/html/fog/lib/db/pdodb.class.php on line 151
    [Tue Nov 08 14:25:51.840651 2016] [:error] [pid 12056] [client 192.168.9.151:50549] PHP Warning: PDO::__construct(): MySQL server has gone away in /var/www/html/fog/lib/db/pdodb.class.php on line 151
    [Tue Nov 08 14:25:51.816007 2016] [:error] [pid 6556] [client 192.168.9.151:62461] PHP Warning: PDO::__construct(): MySQL server has gone away in /var/www/html/fog/lib/db/pdodb.class.php on line 151
    [Tue Nov 08 14:25:51.773648 2016] [:error] [pid 6198] [client 192.168.9.151:58259] PHP Warning: PDO::__construct(): MySQL server has gone away in /var/www/html/fog/lib/db/pdodb.class.php on line 151
    [Tue Nov 08 14:25:51.738900 2016] [:error] [pid 6195] [client 192.168.9.151:58258] PHP Warning: PDO::__construct(): MySQL server has gone away in /var/www/html/fog/lib/db/pdodb.class.php on line 151
    [Tue Nov 08 14:25:51.737949 2016] [:error] [pid 6194] [client 192.168.9.151:62460] PHP Warning: array_combine(): Both parameters should have an equal number of elements in /var/www/html/fog/lib/fog/fogbase.class.php on line 936
    [Tue Nov 08 14:25:51.730574 2016] [:error] [pid 6194] [client 192.168.9.151:62460] PHP Warning: PDOStatement::execute(): Error reading result set's header in /var/www/html/fog/lib/db/pdodb.class.php on line 533
    [Tue Nov 08 14:25:51.730523 2016] [:error] [pid 6194] [client 192.168.9.151:62460] PHP Warning: PDOStatement::execute(): MySQL server has gone away in /var/www/html/fog/lib/db/pdodb.class.php on line 533
    [Tue Nov 08 14:25:51.708590 2016] [:error] [pid 12058] [client 192.168.9.151:50548] PHP Warning: array_combine(): Both parameters should have an equal number of elements in /var/www/html/fog/lib/fog/fogbase.class.php on line 936
    [Tue Nov 08 14:25:51.708448 2016] [:error] [pid 12058] [client 192.168.9.151:50548] PHP Warning: PDOStatement::execute(): Error reading result set's header in /var/www/html/fog/lib/db/pdodb.class.php on line 533
    

    I was able to upload a new image without any issue. It was a completely separate image. However, that gave me an idea and I just tested it. If I switch the host to the new image I just created from the host it gets the same error, so this is not an error for just my one image.


  • Senior Developer

    @Tom-Elliott Confirmation was made.

    RC-22 officially released. Please update and all should be much more betterer.


  • Senior Developer

    I believe I can now (fairly assuredly) state this is solved. Those with hosts defined to no location but with the location plugin enabled were seeing the issue.

    Waiting on confirmation though.



  • @Tom-Elliott Yep, both have the location plugin installed.


  • Senior Developer

    @RobTitian16 It’s possible. Did your “remote site” also have lcoation plugin installed? It shouldn’t have been required for it, but…



  • @theWizard I can confirm my location was also left blank for the system I was trying to image with Tom earlier. Perhaps this is the culprit?



  • @Tom-Elliott
    Unfortunately i have to chime in and say i am also experiencing this issue, i can not launch an image task unless i have open slots on my main fog server and i set the host location to mainbox, if i leave host location blank like i always do it give me image does not exist in any node.


  • Senior Developer

    So we remoted with one another and all seems to have worked properly, although the image does not exist was still problematic.

    The fix, is a work around at the moment for functionality speaking. We are just forcing the checking to return true.

    Mind you deploying is working properly from the UK site, this seems to be specific to the US site only.


  • Senior Developer

    @RobTitian16 How many nodes do you have? If I recall, you’re running from the UK to the US, correct?

    Maybe try an even longer available timeout? Just a suggestion. I created the 500 millisecond as it seemed to work perfectly for my testing and for most will work fine. I made it a user adjustable value for the fact that my environment is NOT what everybody will experience.

    Please also try a longer available timeout (though it will likely cause issues if you go longer than 20 seconds.)



  • @Tom-Elliott This FOG server only has the default storage node, and the web gui does say it’s there. When browsing to /images/ I can also see it listed (can provide screenshots of anything if it helps).


  • Senior Developer

    @RobTitian16 Is it possible the image doesn’t exist on any of the nodes as it’s suggesting then?



  • @Tom-Elliott Still the same, unfortunately, even after going through the steps suggested.


  • Senior Developer

    @RobTitian16 Before just updating files, please look in FOG Configuration Page -> FOG Settings -> General Settings.

    Look near the bottom of that section. YOu should see three new timeout values.

    The AVAILABLE timeout should display as 500. Try changing this to 1200. (1.2 seconds) as that should be plenty enough time even on a crowded network.

    If it still causes issue, then update your files with:

    wget -O /var/www/fog/lib/fog/fogurlrequests.class.php https://raw.githubusercontent.com/FOGProject/fogproject/ba2ba4fcf16a0940a443eca4ec622f3cc30dfa29/packages/web/lib/fog/fogurlrequests.class.php
    wget -O /var/www/html/fog/lib/fog/fogurlrequests.class.php https://raw.githubusercontent.com/FOGProject/fogproject/ba2ba4fcf16a0940a443eca4ec622f3cc30dfa29/packages/web/lib/fog/fogurlrequests.class.php
    

    Then see if it starts working for you.



  • @JJ-Fullmer When does RC22 go live? I’m currently running into this issue as well.
    I tried updating but I’m still on RC21 and I attempted to use the files mentioned in the link to no avail.


  • Testers

    Solved in working RC22. Something in these magical code lines https://github.com/FOGProject/fogproject/commit/42f104080e0f6a22df1890fe14f20fa2f4231de6
    got it back up and running. Because @Tom-Elliott is amazing.


  • Senior Developer

    This post is deleted!

  • Moderator

    This post is deleted!

  • Testers

    Edited the title. I just tested and confirmed that I can still deploy from the pxe menu without issue.
    So this issue is only in the GUI.


Log in to reply
 

401
Online

39210
Users

10856
Topics

103346
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.