Updating Database failed! Failed to open stream!



  • Hi Guys please help!

    Master Fog on VM Running Version 1.4.4 SVN Revision: 6077and single Node on pc, both running Ubuntu server 16.04.3

    Recently physically moved the Node to new building and subnet. Renamed the node and re-ip’d it.

    Also put a bigger Hard Drive in the Node

    DEPLOY WORKS FINE FROM NODE !!!

    But on Capture at 100% - Getting Database failed! Failed to open stream: no such file or directory

    ran the following on the node and rebooted:

    sudo chmod -R 777 /images

    Also just changed all the passwords to match in the following locations and rebooted both:

    Web Interface -> Storage Management -> [Your storage node] -> Management Username & Management Password
    Web Interface -> FOG Configuration -> FOG Settings -> TFTP Server -> FOG_TFTP_FTP_USERNAME & FOG_TFTP_FTP_PASSWORD
    The local ‘fog’ user’s password on the Linux FOG server
    Server file: /opt/fog/.fogsettings -> password (For recent FOG Trunk versions only. 1.2.0 does not have this setting. 1.3.0 will though.)
    Server file: /opt/fog/.fogsettings -> username (For recent FOG Trunk versions only. 1.2.0 does not have this setting. 1.3.0 will though.)

    But now getting:

    Updating Database failed! Login incorrect

    Please help as I think I am making it worse?


  • Moderator

    @Kevin-Talbot correct without the location plugin and locations being defined all target computers will use the main fog server for image capture. If you want to capture and deploy from storage nodes you need the location plugin, then assign the storage node and target computers to that location so everything stays local to the storage node.



  • @george1421 if I delete the one location will it just go by the image storage group default?



  • @george1421 said in Updating Database failed! Failed to open stream!:

    s it should have been working…

    Always the way George unfortunately but we go there many thanks for your help!


  • Moderator

    @Kevin-Talbot Well this is one for the record books.

    As always, its the last place you looked is where the problem is found. We should have started looking in the last place first. ;-)

    I’m glad you have it sorted out. Everything was pointing towards it should have been working…



  • @george1421 said in Updating Database failed! Failed to open stream!:

    proper storage nodes?

    George you are the HERO thankyou !!!

    So a long time ago we did use locations but stopped using them.

    However, it appears a colleague has added a new location with the new node name attached and ticked the: Use inits and kernels from this node box…grrrrrr

    I added the location to the host and restarted the capture and bingo all sorted!!!

    Sorry to waste your time!


  • Moderator

    @Kevin-Talbot We may need to turn this back over to the developers since it should not be doing what its doing.

    Just for clarity, are you using the location plugin to direct the clients to the proper storage nodes?



  • @george1421 I must be missing something very stupid somewhere…

    Both ubuntu firewalls are off btw!

    0_1543588613404_node.JPG


  • Moderator

    @Kevin-Talbot said in Updating Database failed! Failed to open stream!:

    @george1421 the original error appears to indicate it is trying to move 54bf64334d40 on the 172.16.220.246 though?0_1543588313701_error.JPG

    Ah that explains the not able to find the stream error. I’m looking at the kernel parameters from your post. I don’t see where its referencing 172.16.220.246. From the kernels parameters it should be interacting with 172.16.100.246

    Can you post a screen shot of the storage node configuration for this remote node?


  • Moderator

    @Kevin-Talbot well this is a good one. It “should be” working.

    In the storage node configuration for this remote node. The image path and ftp path point to /images?



  • @george1421 the original error appears to indicate it is trying to move 54bf64334d40 on the 172.16.220.246 though?0_1543588313701_error.JPG



  • @george1421 I just dragged 54bf64334d40 folder to images with no issues0_1543588149440_drag.JPG


  • Moderator

    @Kevin-Talbot what about selinux status?

    The permissions look ok? Did you try to drag and drop a mac address directory from /images/dev to /images logged in with the fog account?


  • Moderator

    @Kevin-Talbot Ok that raised another question. Why don’t we see the directories with mac addresses like you posted with the screen shot? Never mind I see that is a different host



  • @george1421 for the node (172.16.100.246)

    itsupport@259-fog:~$ ls -la /images
    total 100
    drwxrwxrwx 22 fog  root  4096 Nov 30 10:53 .
    drwxr-xr-x 27 root root  4096 Nov 30 10:53 ..
    drwxrwxrwx  6 fog  root  4096 Nov 30 10:53 dev
    drwxrwxrwx  2 fog  root  4096 Jun  7 10:17 Latitude3540Win7-Office2013-i3
    drwxrwxrwx  2 fog  root  4096 Jul  4 11:37 Latitude3570Win7-NoOffice-i5
    drwxrwxrwx  2 fog  root  4096 Apr 11  2018 Latitude3580Win7-NoOffice-i5
    drwxrwxrwx  2 fog  root  4096 Oct 26 21:06 Latitude3590-Win10
    drwxrwxrwx  2 fog  root  4096 Oct 11 12:04 Latitude5490-Win10-k1
    drwxrwxrwx  2 fog  root  4096 Apr 17  2018 LatitudeE5530Win7-NoOffice-HD3000
    drwxrwxrwx  2 fog  root  4096 Jul  4 14:21 LatitudeE5540Win7-Office2013-i3
    drwxrwxrwx  2 fog  root  4096 Jul  5 10:20 LatitudeE5540Win7-Office2013-i5
    drwxrwxrwx  2 fog  root  4096 Jan  2  2018 LatitudeE5550Win7-NoOffice-i5
    drwxrwxrwx  2 fog  root  4096 Feb  6  2018 LatitudeE5570Win7-Office2016-i5
    drwxrwxrwx  2 fog  root 16384 Sep 24 14:13 lost+found
    -rwxrwxrwx  1 fog  root     0 Sep 24 16:55 .mntcheck
    drwxrwxrwx  2 fog  root  4096 Jul  6 17:04 Optiplex3020MWin7-Workshop
    drwxrwxrwx  2 fog  root  4096 Jan  4  2018 Optiplex3030Win7-NoOffice
    drwxrwxrwx  2 fog  root  4096 Aug 17 10:27 Optiplex3240Win7-NoOffice
    drwxrwxrwx  2 fog  root  4096 Mar 22  2018 Optiplex380Win7-NoOffice
    drwxrwxrwx  2 fog  root  4096 Nov 28  2017 Optiplex380Win7-Office2007
    drwxrwxrwx  2 fog  root  4096 Nov 28  2017 Optiplex380Win7-Office2010
    drwxrwxrwx  2 fog  root  4096 Oct  4 11:52 Optiplex5250Win10
    drwxrwxrwx  2 fog  root  4096 Nov 30 10:53 postdownloadscripts
    
    itsupport@259-fog:~$ ls -la /images/dev
    total 24
    drwxrwxrwx  6 fog root 4096 Nov 30 10:53 .
    drwxrwxrwx 22 fog root 4096 Nov 30 10:53 ..
    drwxrwxrwx  2 fog root 4096 Nov 14 07:25 54bf642068ae
    drwxrwxrwx  2 fog root 4096 Nov 30 14:13 54bf64334d40
    drwxrwxrwx  2 fog root 4096 Oct 26 12:06 54bf64495fa7
    -rwxrwxrwx  1 fog root    0 Nov 27  2017 .mntcheck
    drwxrwxrwx  2 fog root 4096 Nov 30 10:53 postinitscripts
    itsupport@259-fog:~$
    


  • @george1421 For the master (172.16.220.246)

    itsupport@fog-server:~$ ls -la /images
    total 64
    drwxrwxrwx 16 fog  root 4096 Nov 30 13:18 .
    drwxr-xr-x 26 root root 4096 Nov 30 13:01 ..
    drwxrwxrwx  3 fog  root 4096 Nov 30 10:14 dev
    drwxr-xr-x  2 fog  fog  4096 Nov 30 13:53 Latitude3570Win7-NoOffice-i5
    drwxr-xr-x  2 fog  fog  4096 Nov 30 13:21 Latitude3580Win7-NoOffice-i5
    drwxr-xr-x  2 fog  fog  4096 Nov 30 13:53 LatitudeE5530Win7-NoOffice-HD3000
    drwxr-xr-x  2 fog  fog  4096 Nov 30 13:53 LatitudeE5540Win7-Office2013-i3
    drwxr-xr-x  2 fog  fog  4096 Nov 30 13:53 LatitudeE5550Win7-NoOffice-i5
    drwxr-xr-x  2 fog  fog  4096 Nov 30 13:53 LatitudeE5570Win7-Office2016-i5
    -rwxrwxrwx  1 fog  root    0 Nov 26  2017 .mntcheck
    drwxr-xr-x  2 fog  fog  4096 Nov 30 13:53 Optiplex3020MWin7-Workshop
    drwxr-xr-x  2 fog  fog  4096 Nov 30 13:54 Optiplex3030Win7-NoOffice
    drwxr-xr-x  2 fog  fog  4096 Nov 30 13:54 Optiplex3240Win7-NoOffice
    drwxr-xr-x  2 fog  fog  4096 Nov 30 13:54 Optiplex380Win7-Office2007
    drwxr-xr-x  2 fog  fog  4096 Nov 30 13:23 Optiplex380Win7-Office2010
    drwxr-xr-x  2 fog  fog  4096 Nov 30 13:54 Optiplex5250Win10
    drwxrwxrwx  2 fog  root 4096 Nov 26  2017 postdownloadscripts
    
    itsupport@fog-server:~$ ls -la /images/dev
    total 12
    drwxrwxrwx  3 fog root 4096 Nov 30 10:14 .
    drwxrwxrwx 16 fog root 4096 Nov 30 13:18 ..
    -rwxrwxrwx  1 fog root    0 Nov 26  2017 .mntcheck
    drwxrwxrwx  2 fog root 4096 Nov 26  2017 postinitscripts
    itsupport@fog-server:~$
    

    [Mod note] I fixed the post for readability -Geo


  • Moderator

    @Kevin-Talbot well this isn’t exactly what I asked, but from filezilla logged in as fog, can you move one of the mac directories from /images/dev to /images?

    For what I asked about with permissions run these commands on both the main fog server and on the remote storage node.

    ls -la /images
    ls -la /images/dev
    sestatus|grep -e "SELinux status"| awk '{print $3}'

    Hint: If you use putty to ssh into the fog servers you can copy and paste these commands and the output.



  • @george1421

    1. permissions on images and dev folder1_1543586972596_images.JPG 0_1543586972595_devper.JPG


  • @george1421

    1. the node is 172.16.100.246
    2. yes i was able to ftp to 172.16.100.246 using “fog” and the long password
    3. the image is arriving on 172.16.100.2460_1543586762996_dev.JPG

  • Moderator

    @Kevin-Talbot OK let make sure we understand a few things (building a truth table).

    1. The storage node in question is 172.16.220.246?
    2. You were able to ftp to that storage node using the user name of fog and that long password from storage node page?
    3. The image is arriving on the 172.16.220.246 server in /images/dev/<mac_address> directory?
    4. We see the failed to update database message
    5. The actions were it failed are in the FTP section of the code.

    Here is where I’m going:

    1. What does the permissions look like on the /images and /images/dev directory?
    2. Does the linux user fog have rights to move/create files?
    3. Do the permissions on these directories match the FOG Master Server’s directories?

    I believe where the process is falling down is when the target computer connects to the fog server (node) using FTP. At this point it needs to move the images from /images/dev/<mac_address> to /images/<image_name>. It should do that with the ftp mv command. One should be able to do the same steps from a FTP client connected to the remote storage node.


Log in to reply
 

572
Online

5.8k
Users

13.1k
Topics

123.2k
Posts