I installed DevKinsta earlier this week and was able to pull my site from Kinsta. Since then, I’ve rebooted, and now, I’m unable to pull the site from Kinsta again. I always get the “Something Bad Happened” error.
In the main.log file, the error is: failed to open exclude file /tmp/rsync/rsync_exclude_pull_2a8b0a20bd474be4b9dd23a6c0039cc4.tmp: Permission denied (13) rsync error: error in file IO (code 11) at exclude.c(1481) [client=3.2.7]
I’ve verified that /tmp, /tmp/rsync and the file in question seem to have appropriate permissions and are owned by my user. I’ve also verified that the file gets written properly since it is full of the excluded files when I tried to exclude them.
I’ve tried running DevKinsta as root, but that caused more issues. I’ve also tried excluding files from the pull, removing the file and not excluding anything, but I get the same error each time.
Thank you for sending this in.
We would like to investigate this further, can you please provide the following information?
DevKinsta Version: OS Version: Docker Desktop Version:
Can you also send me the DevKinsta main.log file via direct message and send it to @Adrian_L, @VladimirM, and @Andrew as well? You can get the main.log file by clicking on the “Reveal log file in File Manager” under the Help and Support page in DevKinsta.
I know that Fedora isn’t officially supported, but I’ve been using DevKinsta on it for a while. I had to reinstall it and this newer version is the first time I’ve had an issue. It was also working earlier in the week. I have a feeling it’s docker related, but I can’t narrow it down.
Hi @landyman! Thank you for your reply and for sending the main.log file!
I have reviewed the log file further. I also am seeing that failed to open exclude file error you mentioned. I understand that you are running DevKinsta on Fedora 44 which as you mentioned isn’t officially supported. While support for this type of installation is outside the scope of our support, as a courtesy we certainly want to do what we can here to help!
The permission denied error could be indicating some other system level protection is preventing the file from being opened. I would like to check if it’s possible an SELinux policy is preventing this file from being opened by DevKinsta or any of the related Docker containers.
To check for this could you please perform the following steps?
Attempt to pull the site again. This likely will fail and is expected.
Immediately after the failure has occurred please run the following commands in a terminal window:
ls -laZ /tmp/rsync/
and look for anything referencing user_tmp_t for the /tmp/rsync/rsync_exclude_pull*files.
Also run:
sudo ausearch -m avc -ts recent
and look for anything related to the /tmp/rysnc temp file as well.
If you do see anything related to the temp file after running these commands if you could please DM me, @Adrian_L, @VladimirM, @jackirish and @merineth with the details (or screenshots) of the terminal window displaying that information that will help us in our investigation and in determining the best next step forward.
Hi @Andrew - Thanks for the help, I appreciate it.
I had previously tried, but apparently unsuccessfully, to allow these to run through SELinux. Today, when I temporarily disabled it (setenforce 0), the pull ran, but there were quite a few SELinux messages. I’ve attached all those to a DM along with the original CLI output, which did include user_tmp_t in the output.
I’m not very well versed in SELinux, so I’ll have to do some digging and hopefully get it all working without needing to disable it every time.
I am not sure if there is anything more we can suggest, since the Fedora 44 OS isn’t officially supported. But could you also DM me, @merineth, @VladimirM, and @jackirish with this latest information?
I’ve attached all those to a DM along with the original CLI output, which did include user_tmp_t in the output.
We can continue to review it while @Andrew is away.
Hi @Adrian_L - No worries, I think I’m probably good from here on out. I thought I had DM’d those files earlier today. I just sent another DM with the CLI output and the SELinux output.
Plus, I think you guys nailed it with the problem being SELinux. I’m not sure why I wasn’t getting the error earlier in the week.
Very well, we’re glad that we could help. For what it’s worth, I also upgraded the Docker Engine to 29.6.0 on my test Ubuntu machine and can confirm that DevKinsta continues to work, especially the Push and Pull actions, right out of the box. So it appears likely that the issue is between Fedora and the latest version of the Docker Engine.