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)
tar -xzvf fuse-2.9.7.tar.gz
rm -f fuse-2.9.7.tar.gz
mv fuse-2.9.7 fuse
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)
git clone https://github.com/s3fs-fuse/s3fs-fuse.git
sudo make install
6. If there were no errors along the way, this should return the s3fs-fuse version (currently 1.80)
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-126.96.36.199-1.el5.rf.x86_64 (rpmforge)
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
--> Running transaction check
---> Package rpmforge-release.x86_64 0:0.5.3-1.el5.rf will be erased
--> Finished Dependency Resolution
Package Arch Version Repository Size
rpmforge-release x86_64 0.5.3-1.el5.rf @rpmforge 13 k
Remove 1 Package(s)
Installed size: 13 k
Is this ok [y/N]: y
Running Transaction Test
Transaction Test Succeeded
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
[[email protected] boot]#
After that the standard yum install git will work just fine!
Three days ago Laravel 5.4 was released, so I have decided to give it a try. I have made a new Laravel 5.4 project and just when I was about to run the default auth migrations that are shipped with the Laravel almost without any other changes, I got these two red errors:
SQLSTATE: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes (SQL: alter table `users` add unique `users_email_unique`(`email`))
SQLSTATE: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes
What the hell is going on!?!? I have checked the migrations file and everything was okay there unchanged compared to Laravel 5.3. But, according to Laravel Documentation one thing changed:
Laravel 5.4 uses the
utf8mb4 character set by default, which includes support for storing “emojis” in the database. If you are upgrading your application from Laravel 5.3, you are not required to switch to this character set.
And, according to their documentation the problem is that I’m running version of MySQL prior to 5.7.7 or MariaDB prior to 10.2.2 (my case). In case you are running versions of MySQL or MariaDB greater than these than most probably that you won’t have this problem at all.
In case you are having this problem – here are the possible solutions:
1. Upgrade MariaDB / MySQL
To update MariaDB on Mac using Brew, first you need to unlink the current one using:
brew unlink mariadb
and then install a dev one using
brew install mariadb --devel
That will install MariaDB version 10.2.3 that works fine. Remember that after installation is done you need to stop/start the service:
brew services stop mariadb
brew services start mariadb
2. Stick with utf8
In case you don’t want to use the utf8mb4 (that is now setup by default in Laravel 5.4) – instead you want to stick with utf8 that was in use in Laravel 5.3 and all versions before, simply edit /config/database.php and find these two lines in mysql driver:
'charset' => 'utf8mb4',
'collation' => 'utf8mb4_unicode_ci',
and replace them with with
'charset' => 'utf8',
'collation' => 'utf8_unicode_ci',
That will stop using the utf8mb4 and will change back to utf8. The good thing about this is that you’ll be able to fit 25% more characters into the same columns in database compared with utf8mb4 and that you’ll be able to use existing databases and projects without the need of converting them if you don’t want to. And the downside is that some characters will not be able to be saved to database like this mac command character ⌘ or some emojis. Utf8 can only store Plane Unicode while utf8mb4 can store any unicode character. Utf8mb4 is also 100% backwards compatible with utf8.
3. Use utf8mb4 without MySQL/MariaDB upgrade
In case you want to use utf8mb4 but you don’t want to or simply can’t upgrade your MySQL/MariaDB there is a simple solution proposed by Laravel documentation. All you need to do is edit AppServiceProvider located at App\Providers\AppServiceProvider.php and add the following line to the boot() method and load the Schema facade:
* Bootstrap any application services.
* @return void
public function boot()
What that will do is actually change the default maximum field length in the database and actually shorten your maximum string length from 255 to maximum of 191 characters (utf8 uses 3 bytes per character while utf8mb4 uses 4 bytes per character your field can now hold 25% less characters 255 * 75% = 191.25). So if you don’t set the string field by hand in the migration the new default will be 191. You can increase the length if you need it manually by defining it:
But this will not be possible on indexed fields since these can’t be longer than 191 characters. So keep this in mind in case you’re planing to use utf8mb4.
In case you want to convert the database from utf8 to utf8mb4 for any existing projects or if you are upgrading from Larvel 5.3 or older to Laravel 5.3 this is the code you need to run for every database, table and column:
Make sure you have the database backups before making these changes!!!!
# For each database:
ALTER DATABASE database_name CHARACTER SET = utf8mb4 COLLATE = utf8mb4_unicode_ci;
# For each table:
ALTER TABLE table_name CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
# For each column:
ALTER TABLE table_name CHANGE column_name column_name VARCHAR(191) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
# (Don’t just blindly copy-paste this! The exact statement depends on the column type, maximum length, and other properties. The above line is just an example for a `VARCHAR` column.)
Once again: when converting from utf8 to utf8mb4, the maximum length of a column or index key is unchanged in terms of bytes but since utf8mb4 uses 25% more bytes per character your columns can now accept less characters. Therefore, it is smaller in terms of characters, because the maximum length of a character is now four bytes instead of three.
For example, a TINYTEXT column can hold up to 255 bytes, which correlates to 85 three-byte or 63 four-byte characters. Let’s say you have a TINYTEXT column that uses utf8 but must be able to contain more than 63 characters. Given this requirement, you can’t convert this column to utf8mb4 unless you also change the data type to a longer type such as TEXT — because if you’d try to fill it with four-byte characters, you’d only be able to enter 63 characters, but not more.
The same goes for index keys. The InnoDB storage engine has a maximum index length of 767 bytes, so for utf8 or utf8mb4 columns, you can index a maximum of 255 or 191 characters, respectively. If you currently have utf8 columns with indexes longer than 191 characters, you will need to index a smaller number of characters when using utf8mb4.
If you plan on using utf8mb4 make sure to setup your MySQL server accordingly by editing /etc/my.cnf file accordingly:
default-character-set = utf8mb4
default-character-set = utf8mb4
character-set-client-handshake = FALSE
character-set-server = utf8mb4
collation-server = utf8mb4_unicode_ci
If your application won’t use any special characters or emojis or languages such as Chinese, Japanese, and Korean you’re most probably fine sticking with utf8. But if you can – you should move to utf7mb4 since that will stop you from loosing 4-byte characters when a user ads these in comments or in message or whenever you store these in your database. You should always strive to full unicode support everywhere in your apps and updating your database and code might take some time but it’s definitely worth the time and effort.
While I was working on my referral traffic spam article today, I have noticed one more form of spam in my Google Analytics statistics. It’s called a language spam and in this case it had something to do with Trump LOL.
Here’s the language spam volume:
When I filter it by country I can again see that these bots are coming from Russia (same as with referral spam). Now, apparently, someone from Russia (actually the guy behind this is Vitaly Popov, a well-known Analytics spammer) wants me to open this url: secret.ɢoogle.com and to vote for Donald Trump ?!?!? Mind blowing, really… As, you can clearly see that it’s again multi-byte domain, and that the letter G is multi-byte letter, and that it’s clearly a fake url/domain so don’t open it!
This spam actually just hits your Google Analytics, and no bot traffic is sent to your site, so all you need to do is to simply filter out these fake languages. To make things perfectly clear this kind of spam can’t harm your SEO or Rankings because there are no real backlinks or traffic to your site and Google also deosn’t use data from your Google Analytics for website ranking. The only one this spam is affecting is you! You are the only one who can see it while you’re checking your Google Analytics, and you should block it so your statistics are accurate and you can make some good decisions based on them.
Here’s the best way how to block the language spam: go to Google Analytics, and click Admin. Now under your account click All Filters:
and then click on Add filter and make a filter like this (follow my arrows from top to bottom of the picture):
- Filter Name: write something descriptive so you know what’s this filter for: blocks language spam is a good name
- Filter Type: pick Custom
- Filter Field: search for and pick Language Settings
- Filter Pattern: enter \.
- Apply Filter to Views: select views that you want to apply this filter on and click Add (moves them from left to right into selected views list)
- Click Save
That’s it! You have created a filter that will discard any language containing a dot (basically a domain name). This should remove your language spam from future Google Analytics stats.
However if you would like to filter current data and see the correct stats without the language spam hits you’ll have to create a new segment like this: on just about any report in Google Analytics click on +Add Segment:
and now click on red button +New Segment:
Now enter some meaningful name, for the language pick does not contain and just add a single dot in the filed right to it and press save above:
Here you can see the result of this filter with before and after charts:
This way you can filter data on any report. Just click add segment and search for the new segment we created (so it’s important to add a meaningful name to the segment so you can easily locate it anytime you need it).
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.