In case you have CentOS 6.8 server (or DigitalOcean droplet/vps) and you want to install s3fs-fuse the proposed way you’ll run into a problem: the s3fs-fuse requires fuse library version 2.8.4 or higher, but your yum install fuse fuse-devel will install you fuse 2.8.3. If you are running CentOS 7 you won’t have this problem at all, since by default, yum will install fuse 2.9.2.
To fix this problem you need to remove the fuse and install it manually.
1. Remove fuse installed by yum
yum remove fuse fuse* fuse-devel
2. Install some dependencies (for both fuse and s3fs-fuse)
yum install automake gcc-c++ git libcurl-devel libxml2-devel make openssl-devel
3. Download and install latest fuse library (version 2.9.7)
cd /usr/local/src
wget https://github.com/libfuse/libfuse/releases/download/fuse-2.9.7/fuse-2.9.7.tar.gz
tar -xzvf fuse-2.9.7.tar.gz
rm -f fuse-2.9.7.tar.gz
mv fuse-2.9.7 fuse
cd fuse/
./configure --prefix=/usr
make
make install
export PKG_CONFIG_PATH=/usr/lib/pkgconfig:/usr/lib64/pkgconfig/
ldconfig
4. Test that fuse is installed (should return “2.9.7″)
pkg-config --modversion fuse
5. Install the s3fs-fuse (using the default instructions from github)
cd /usr/local/src
git clone https://github.com/s3fs-fuse/s3fs-fuse.git
cd s3fs-fuse
./autogen.sh
./configure
make
sudo make install
6. If there were no errors along the way, this should return the s3fs-fuse version (currently 1.80)
s3fs --version
Hopefully, this will help you successfully install s3fs-fuse on your system. For details on how to use it please refer to documentation at the github page. Please do not hesitate to leave your comments below! Thank you.
Today I had to install git on one server running on CentOS 6, but yum install git returned the following error:
Error: Package: git-1.7.12.4-1.el5.rf.x86_64 (rpmforge)
Requires: libcurl.so.3()(64bit)
To fix this bug you have to run this command:
and then confirm the removal of that package:
Loaded plugins: fastestmirror, security
Setting up Remove Process
Resolving Dependencies
--> Running transaction check
---> Package rpmforge-release.x86_64 0:0.5.3-1.el5.rf will be erased
--> Finished Dependency Resolution
Dependencies Resolved
=============================================================================================================================================================================================================================================
Package Arch Version Repository Size
=============================================================================================================================================================================================================================================
Removing:
rpmforge-release x86_64 0.5.3-1.el5.rf @rpmforge 13 k
Transaction Summary
=============================================================================================================================================================================================================================================
Remove 1 Package(s)
Installed size: 13 k
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Erasing : rpmforge-release-0.5.3-1.el5.rf.x86_64 1/1
Verifying : rpmforge-release-0.5.3-1.el5.rf.x86_64 1/1
Removed:
rpmforge-release.x86_64 0:0.5.3-1.el5.rf
Complete!
[root@hosted-by boot]#
After that the standard yum install git will work just fine!
After cPanel upgrade from EasyApache3 to EasyApache4 all my CodeIgniter installations just broke on that server, returning just a white page without any error message. I spent more than one hour trying to figure out what the problem is. While testing out I noticed empty files named like these “0bce68a7a37e584ace98f0fd242a237d1662613e” or “296eed9bfb533552b0c3a9c8fdd784067eea216d” (without any extension) started popping in my project folder. I figured out that these must be session paths so something is wrong with that.
I tried enabling php error logging but it didn’t help since it didn’t log anything since all code is right and it was working before but it just stopped after I started using EasyApache4.
So I went and enabled CodeIgniter logging that proved to be a better idea. To enable it open config.php for editing, locate
$config['log_threshold'] = 0;
And change that value to 4. That will enable internal logging system and logs will be saved in /application/logs folder. What I found out just conf
ERROR - 2016-11-29 22:36:29 --> Severity: Warning --> mkdir(): Invalid path Session_files_driver.php 117
ERROR - 2016-11-29 22:36:29 --> Severity: error --> Exception: Session: Configured save path '' is not a directory, doesn't exist or cannot be created. Session_files_driver.php 119
My session save path at config.php was set to null:
$config['sess_save_path'] = NULL;
Once I got it changed to default (alternatively you can set it up to any other folder you want locally, so you can have full control over your sessions):
$config['sess_save_path'] = sys_get_temp_dir();
everything started working again! Now this is second time I have similar quiet errors with CodeIgniter where it reports absolutely nothing – instead it just gives white screen and this can be really frustrating to debug.
Today I wanted to install Git on a server with cPanel/WHM and have got the following result:
yum install git
Resolving Dependencies
--> Running transaction check
---> Package git.x86_64 0:1.7.1-4.el6_7.1 will be installed
--> Processing Dependency: perl-Git = 1.7.1-4.el6_7.1 for package: git-1.7.1-4.el6_7.1.x86_64
--> Processing Dependency: perl(Git) for package: git-1.7.1-4.el6_7.1.x86_64
--> Processing Dependency: perl(Error) for package: git-1.7.1-4.el6_7.1.x86_64
--> Finished Dependency Resolution
Error: Package: git-1.7.1-4.el6_7.1.x86_64 (base)
Requires: perl-Git = 1.7.1-4.el6_7.1
Error: Package: git-1.7.1-4.el6_7.1.x86_64 (base)
Requires: perl(Git)
Error: Package: git-1.7.1-4.el6_7.1.x86_64 (base)
Requires: perl(Error)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Then I did some research and have found out that Gis is already installed on cPanel as of version 11.36 but the problem is – it’s installed on this path:
/usr/local/cpanel/3rdparty/bin/git
So for ease of use I advise you to make a simple symlink:
ln -s /usr/local/cpanel/3rdparty/bin/git /usr/bin/git
so you don’t have to remember the path above and you can simply use it like you got used.
Note: In order for user to be able to login to SSH, it must be allowed in WHM first at Account Functions > Manage Shell Access and there just switch from Disabled Shell to Jailed Shell.
Happy Gitting!
If your /boot partition is running out of disk space this is probably because you got bunch of old Linux kernels that got stockpiled there and are no longer in use or needed for system to function normally. If you’re running a WHM/cPanel you’ll get an email with subject: DISKWARN blocks: Mount Point “/boot”
Usually on a system update, if there is a new Linux Kernel it will get downloaded and initialized while the last one will be kept for just in case the first one fails for any reason. In couple of months or years you could already have 5-6 of them while only the latest Linux kernel would be in use and the previous one will be kept as a backup. Removing these by hand is possible but an mistake could end up with a system that won’t boot.
To prevent that and free up disk space at /boot partition on Red Hat Linux or CentOS Linux all you need to do is simply to execute this command:
sudo yum install yum-utils && sudo package-cleanup --oldkernels --count=2
This will remove all your old kernels keeping just the last two (latest one and the previous one just in case) so you won’t get these emails or notifications anymore and you’ll keep your /boot partition with enough free space for a new kernel to be installed once released.
