Updating Database failed! Failed to open stream!

[Kevin Talbot]

Can anyone help please?

[Sebastian Roth]

@Kevin-Talbot Have you checked the error logs as suggested?

Rereading your initial post I noticed that you say you moved to a different subnet as well. Meaning IPs of master and storage node have changed as well?

Check all the IPs you have in /var/www/html/fog/lib/fog/config.class.php and /opt/fog/.fogsettings

[george1421]

@Kevin-Talbot This thread is almost 1 month old. I take it, its still an issue?

Can you take a clear screen shot of the error so we can see the context of the error? It sounds like the linux user fog’s account password was changed/is out of sync with the webui. I have a tutorial on how to get everything back in alignment here: https://forums.fogproject.org/topic/11203/resyncing-fog-s-service-account-password

The fog service account should exist on the fog master node the storage node should have their own service account too.

[Kevin Talbot]

@george1421 Hi yes very much still an issue thanks for replying!

I can deploy from and capture to the master fog server perfectly fine.

I can deploy from but NOT capture to the node

Struggling to get the screenshot to upload fails at 97% grrr…

[Kevin Talbot]

@Sebastian-Roth said in Updating Database failed! Failed to open stream!:

and storage node have changed as well?

Thanks for the reply Sebastian!

Only the node subnet has changed, I re-ip’d it as per the book!

[george1421]

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

I can deploy from but NOT capture to the node

You can’t normally capture to a storage node. Only the master node in a storage group can be used to capture images. I just want to make sure we are on the same page here.

[Kevin Talbot]

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

node. Only the master node in a storage group can be used to capture im

I’ve always captured to a node, I have a separate storage group with one node in it which is the master for that storage group!

But I think you may have just nailed the problem…when I moved the node I renamed it and re-ip’d it and something tells me I may have deleted the old “named” node and added the newly “named” node but not clicked “master”

[Sebastian Roth]

@Kevin-Talbot Have you checked the storage node settings in the web UI?

[Kevin Talbot]

@Kevin-Talbot I just made the node a master but that has not cured the problem!

[Kevin Talbot]

@Sebastian-Roth yes and master was not ticked! I have ticked it but that has not cured the issue!

[Kevin Talbot]

This post is deleted!

[Kevin Talbot]

@george1421 whats the size limit on uploading an image to the forum please?

[george1421]

@Kevin-Talbot your image didn’t upload but lets try this.

In the storage node definition for the remote storage node in question. There is a management user account and password. From your windows computer, can you ftp to that remote storage node using those credentials? Those credentials should match the contents of the /opt/fog/.fogsettings on the remote storage node.

[Kevin Talbot]

@george1421 Yes I can FTP with Filezilla to the node using “fog” and the very long generated password!

The DEV folder has the images under folders named by the mac addresses as it should do but clearly cannot rename and move them to the IMAGES folder?

[Kevin Talbot]

@Sebastian-Roth said in Updating Database failed! Failed to open stream!:

/var/www/html/fog/lib/fog/config.class.php and /opt/fog/.fogsettings

“Check all the IPs you have in /var/www/html/fog/lib/fog/config.class.php and /opt/fog/.fogsettings”

these check out fine!

[Kevin Talbot]

@george1421

[george1421]

@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.

[Kevin Talbot]

@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.246

[Kevin Talbot]

@george1421

1. permissions on images and dev folder

[george1421]

@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.