Updating Database failed! Failed to open stream!

Kevin Talbot · Nov 30, 2018, 2:06 PM

the node is 172.16.100.246
yes i was able to ftp to 172.16.100.246 using “fog” and the long password
the image is arriving on 172.16.100.246

Kevin Talbot · Nov 30, 2018, 2:10 PM

permissions on images and dev folder

george1421 · Nov 30, 2018, 2:11 PM

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

Kevin Talbot · Nov 30, 2018, 8:15 AM

@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

Kevin Talbot · Nov 30, 2018, 8:18 AM

@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 · Nov 30, 2018, 8:17 AM

@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 · Nov 30, 2018, 2:22 PM

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

Kevin Talbot · Nov 30, 2018, 2:29 PM

@george1421 I just dragged 54bf64334d40 folder to images with no issues

Kevin Talbot · Nov 30, 2018, 2:31 PM

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

george1421 · Nov 30, 2018, 2:32 PM

@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 · Nov 30, 2018, 2:37 PM

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

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?

Kevin Talbot · Nov 30, 2018, 2:37 PM

@george1421 I must be missing something very stupid somewhere…

Both ubuntu firewalls are off btw!

george1421 · Nov 30, 2018, 2:39 PM

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

Kevin Talbot · Nov 30, 2018, 3:00 PM

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

george1421 · Nov 30, 2018, 3:04 PM

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

Kevin Talbot · Nov 30, 2018, 3:19 PM

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

Kevin Talbot · Nov 30, 2018, 3:26 PM

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

george1421 · Nov 30, 2018, 3:42 PM

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

jeremyvdv · Dec 4, 2019, 10:21 AM

Hello

I do not understand …

I have this problem but I find the plugin rental customers?

Thank you

Updating Database failed! Failed to open stream!

160

12.0k

17.3k

155.2k