Ok, config for SELinux has been changed, did a reboot for testing, looking good so far.
Even if I still do not know, how the SELinux got enabled at all, it looks like the issue is solved.
Thank you very much to all of you guys who helped with the issue.
Cheers Nuit
Yay…that kinda did it.
The setenforce 0 and restarting the FTP did the trick.
So question is, what went wrong on the SELinux.
I am actually not aware, that I ever fiddled with it on the Debian machine to start with.
Is there any possibilty to keep this permissive mode for good, so I do not to redo it manually every time I reboot the VM ?
Or would there be any prime reason to actually fix the config for vsftpd and get it back up running again ?
Thanks a lot so far for the fix.
Cheers, Nuit
Ok here is the vsftpd.conf (looks the same as mentioned in the Wiki):
and the SELinux status:
FTP Service has been restarted several times by now.
But it looks like the status has even gone worse now.
I guess since the resyncing of the fog service account password. I can no longer do anything via FTP since then.
I can still log in using the “fog” user. But that’s about it. Can change directories but not even list anything anymore:
Hi,
that was one of the first things I did when recognising this was some sort of permission problem.
“/images” ownership and all subfolders is set to fog:root
and full permissions on everything are set:
As you can see in the screenshot, the whole thing worked til December.
As mentioned before the problem seems not really to be located on folder/file level.
If I do login to the console using the “fog” user I can create/move files and folders between “/image” and any subfolders without problems.
But if I do login via FTP using the “fog” user I no longer can (getting Error 550 when trying to create a Folder and Error 553 when trying to create a file (using put command).
If I stay in the “fog” users home folder the FTP commands do work.
So I get the impression, that something with “/images” folder and it’s setting with the FTP service or the permissions of the “fog” user regarding FTP is broken.
One little add: this “permission problem” seems to be somewhat connected with the FTP function.
When loggin onto the CentOS console with the “fog” user, the user can actually copy and move files within the “/images” and “/dev” folders (the file permissions are somewhat reduced) but the copy/move works.
Hi,
thanks for the reply.
Yes, I did the resync too. But that did not change anything.
Regarding this, when running the reinstall of Fog for finishing the resync, there is a request to “Update the Database Scheme” via the Web Console before continuing.
Is there anything else needed doing this appart from validating the info in the Web Console?
Is there any actual function for “updating the database scheme” in the Web-Console ?
Cheers, Nuit
Hey there,
running Fog 1.4.2 on Debian CentOS-7.1511 (the whole thing is a VM running on ESXi 5.5)
and have one of these quite common problems with the image capture not getting finished:
Searched the forum and went trough the according Wiki: Troubleshoot FTP - FOG Project
Still does not work.
So what’s the thing at:
The images get captured and are found in “/images/dev” (under their MAC address) but no named folder for the image is created in “/images” and the files are not moved if a new image is captured or if an existing image should be overwritten, the overwrite does not happen.
So the task in FOG never finishes and the client is ending with the error pictured above.
Ran some tests on FTP availability (going there from a Windows machine).
Loging in with the standard FOG user, works fine, puts me to the “/home/fog” folder, where I can create subfolders, put, get, del files etc.
But when I move over to the “/images” folder no creating folders, files or whatsoever anymore:
Giving the results, I’d assume there is some permission problem somewhere, so the question is what did I miss ?
Stupid side fact: The whole thing worked til December like a charm. We were deploying images during the last few month just fine. Only found out about the error when trying to update the images recently. And no one here remembers having changed anything about the server (as usual).
Any help would be appreciated.
Cheers Nuit