Monthly Archives: August 2015

Google Code Shutdown

As previously announced, most of Google Code will become read-only on August 25th, 2015.

We are still working with Google-affiliated projects (e.g., /p/chromium and /p/android) to get them migrated to other tools and make their projects read-only by the end of the year. These projects will remain read-write until we can transition all their data off of Google Code.

What will happen to the data?

Google Code data will still be accessible, just read-only. You will be able to search for and browse project issues, sync source data, and so on. The Export to GitHub feature will still work as advertised.

However, during this time you will not be able to modify projects. For example: create new issues, push code changes, or even modify admin settings. If you need some administrative action taken, such as deleting a project or setting up an automatic redirect URL, please contact us. (Instructions will also be linked from the /admin page of for project administrators.)

How long will the data remain available?

Google Code’s data will remain online for a long time.

Until January 2016 the Google Code Project Hosting service as it exists today will continue to be available. And you will still be able to use version control clients like git, hg, or svn to access project data.

After January 2016 you will no longer be able to access source code from a version control client; however project data will still be available. We will also be offering project data in more convenient formats for export such as JSON and .zip files. Archived project data will be available throughout 2016 and beyond.

Note that only public data will be archived. If your project has private data, such as issues with the Restrict-View-* label, you will no longer be able to browse those project resources next year. (Public downloads, issues, wikis, etc. will be available.)

Most importantly, project URLs (e.g. will continue to work, although links to raw source code like will not. But again, Google Code will continue to work as normal until at least January 2016.


If you have any questions, please contact [email protected].

How to mirror a FTP folder and subfolders – lftp

I had to copy almost 10Gb from one server to another.
Usually I use rsync but this time the user that I have on the remove server is just an FTP user.

My first and dumb option was to use wget to fetch the content! *DUMB!*.
After a few hours/day… I got Write failed: Broken pipe.

OK!, I’v decided to use lftp.
So… I needed to install simply by doing….

apt-get install lftp

Let’s go!

Connect to the server


Enter the username

user userexport

then enter the password…

and the the magic command!

mirroc -c -p

-c – resume option
-p – download files in parallel

HOORAY!, thats kinda it.

lftp [email protected]:~> mirror -c -p
Total: 2184 directories, 97729 files, 0 symlinks
New: 25548 files, 0 symlinks
9900721069 bytes transferred in 2750916 seconds (3.5 KiB/s)
lftp [email protected]:/>

First login @ the new server at kimsufi

First login @ the new server at kimsufi

[email protected]'s password:
Welcome to Ubuntu 15.04 (GNU/Linux 3.14.32-xxxx-grs-ipv6-64 x86_64)

* Documentation:
Ubuntu 15.04

server : 226969
ip :
hostname :

 System information as of Tue Aug 4 11:11:24 EDT 2015

System load: 0.0 Processes: 121
 Usage of /home: 0.0% of 897.05GB Users logged in: 0
 Memory usage: 1% IP address for eth0:
 Swap usage: 0%

Graph this data and manage this system at:

0 packages can be updated.
0 updates are security updates.

*** System restart required ***
Ubuntu 15.04
Linux 3.14.32-xxxx-grs-ipv6-64 #1 SMP Tue Jun 30 18:50:21 CEST 2015 x86_64 x86_64 x86_64 GNU/Linux

server : 225804
ip :
hostname :


Magic Quadrant for Cloud-Enabled Managed Hosting, North America

Cloud-enabled managed hosting brings cloudlike consumption and provisioning attributes to the traditional managed hosting market. It represents an evolution of a mature market in which the wide variety of offerings and capabilities means vendors must be chosen carefully.

 Text and image copied from

Continue reading Magic Quadrant for Cloud-Enabled Managed Hosting, North America

kimsufi – screen

On the 30th of July I’v ordered this server @ KS-4 in Canada…

  • CPU Core™ i5-3570S 4c / 4t 3.1 GHz+
  • RAM 16 GB
  • Disk 1 TB
  • 100 Mbps

Only today I got inside the kimsufi panel!
This is how it looks…



upstream sent too big header while reading response header from upstream

While I was running some scripts, of my new project, from time to time the PHP kinda had some breaks…. went to error.log and I saw the following error.

2015/08/02 19:42:19 [error] 25586#0: *8735692 upstream sent too big header while reading response header from upstream, client:, server:, request: "GET /worker/?action=runHTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "", referrer: ""

I had to edit my nginx domain.conf and add the lines in bold!

location ~ \.php$ {
 try_files $uri =404;
 fastcgi_split_path_info ^(.+\.php)(.*)$;
 fastcgi_pass unix:/var/run/php5-fpm.sock;
 fastcgi_index index.php;
 include fastcgi_params;
 fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
 access_log off;
 fastcgi_buffers 16 16k;
 fastcgi_buffer_size 32k;

Save it and restart nginx!
Should solve it! 🙂