Image task not going through

[Sebastian Roth]

@tom-elliott said in Image task not going through:

Red icon is just “Ping Hosts” this has no bearing on the ability to image.

See what Tom said about the red icon. Nothing to do with imaging.

So what error exactly do you get now? As you seem to have registered the client, just schedule a task for it and reboot to see what’s happening. Post a picture in case you run into an error.

[JackieJack]

@sebastian-roth Yes sir, doing that right now. (I am racists against red exclamation marks lol). Will give you an update first thing tomorrow (Partclone is taking a while)

[JackieJack]

@jackiejack

[JackieJack]

@jackiejack

If you want more/closer screenshots lemme no

[Sebastian Roth]

@JackieJack Well now there is something wrong with your FTP account that is used in the background to move the image files from /images/dev/ to /images/ after upload. Be careful when using the fog user account for administration as well. This is intended as sort of “internal FOG account”.

Please follow this: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP

[JackieJack]

@sebastian-roth Right, I completed this as per george’s instructions:

Should I do them over? I mean I ftp to my fog server normal user account regularly. Upload and download files.

[JackieJack]

@jackiejack Did it over, everything seems to be fine.
It asked to update mysql but when I went to the fog site nothing to update. No button. Other than that, all is well.

[JackieJack]

That root user owner on the second line is okay? Running chown -R fog:root /images solve problem?

[Tom Elliott]

@jackiejack The second line refers to the “parent” directory (/) so yes it’s perfectly fine. A chown -R fog:root /images won’t solve the problem if you’re still having problems as, based on what I can tell, the permissions are already setup as fog:root.

[JackieJack]

@tom-elliott

Change interface from n to enp5s0 on storage management?

[Tom Elliott]

@jackiejack You can though that should only impact the fog services and multicast (more particularly).

[JackieJack]

@tom-elliott what about that php file line 1046 error? I don’t think I saw those before I did george passwd reset.

[Tom Elliott]

@jackiejack The only thing I can think of here is the 1046 error you’re seeing is in regards to FTP. The line your file is referencing is literally:

            if ($fields[3]) {

What this tells me is the field it’s working on isn’t defined, so it’s more a warning than an error. If I had to guess, however, your password for the storage node is not accurate and you should really be seeing something to the tune of “Unable to authenticate.” I base this on the fact that it’s showing the host/username but failing to show the password.

I suppose it’s also possible the /home/fog folder is missing?

[JackieJack]

@tom-elliott /home/fog is there and empty.

I went to storage management and then on DefaultMember and pasted the password from the .fogconfig file twice. The second time using private browsing. I am thinking to do over george’s stuff again but change the password on the .fogconfig to something really stupidly simple.

[JackieJack]

but interface is enp5s0

is that okay? click y (I changed the password to something simple.)

[Tom Elliott]

@jackiejack Change the interface setting in the /opt/fog/.fogsettings file to match that of the interface for your device.

[JackieJack]

@tom-elliott ooookay so what I did was hit N for no, then changed .fogsettings to enp5s0
re ran installer, now went to
http://192.168.26.110/fog/management
to update database

nothing there, so came back to terminal and keep hitting enter but nothing is happening. It’s hanging right there.

[Tom Elliott]

@jackiejack Click in the terminal, then press enter.

When you see the button right Rectangle that’s not all black, it means the window is currently not focused, at least not directly.

[JackieJack]

@tom-elliott sir it’s black, that screenshot not focused. Hit enter how many times no work

[Tom Elliott]

@jackiejack What changed between when you ran it before to now? It seems maybe you could close the terminal, and open a new one? Then try? I’m only guessing. Nothing from fog’s installer perspective has changed.