Blogs

Why the Removal?

Amazon is always striving to improve its products, and that includes keeping software packages up-to-date and secure. The apache-, php, and php-pecl- packages were removed from Amazon Linux 2023 due to outdated software and compatibility issues. As technology advances, it's essential to stay on top of these changes to ensure the best possible experience.

For me, new year started with one discovery.

As you know, holidays do traffic and server load peaks. So, my common job is to watch for problems. And be ready to solve them. (Yes, I do work at holidays.)

So, I noticed that "traffic" graph was disappear from my OVH dashboard. Hm, it was strange. So, I asked support "WTF?". My server monitoring tools show increased traffic and it was very nervous situation. I would expect OVH traffic counter to disable my server or limit channel capacity. And it is in best Rush Hour in the season!

But, in few hours I received answer from OVH.

My dedicated was upgraded with "UNLIMITED" amount of transferred data!!!

What a relive and surprise!!!

THANK YOU OVH!!!. Looking forward to work with you in new year.

When you do security there are no such term as "low risk".

Example - Linode.com. Somebody install phpBB and Linode just got two step attack.

Get out everyone by falser report
Attack old forum - got it.

So, questions are:

• Linode employes doesn't have notebooks?
• remote administration in 2014 is something they don't know?
• Linode don't have any remote administration?
• Linode operate from ONE office?
• how about different datacenters? are they affected?

So, again decentralization is good as never!

Just be notice, before you un-comment line:

geoip GEOIP_STANDARD /usr/share/GeoIP/GeoIP.dat

you should install Geo::IP perl module and for debian it is best to be done via package manager:

sudo aptitude install libgeo-ip-perl

Thanks for perl GeoIP library package interface Debian Perl Group.

When inspecting why nginx logs wasn't rotated, I did little strange discover

# uncomment this if you want your log files compressed
# compress

so, by default rotated logs are not compressed. Perhaps there are admins which process rotated logs, but I am not one them. I use pre-rotate hook to process logs before rotate them. So, I really expected logrotate to compress by default. And yes, my bad - I didn't checked default configuration in /etc/logrotate.conf

Now I did change default to compress and wouldn't have to use in per service logrotate configuration.

PS: and don't forget

sudo /usr/sbin/logrotate -f /etc/logrotate.conf

Lets see, you install new PHP app and get bunch of warnings. It is sad, commonly you need PHP knowledge to understand them and fix. Probably you can request help from you hosting support, but they reject such problems saying "We don't fix your php applications".

You want to grant free small regions for your customers and get money for bigger? it is simple with GPix.

• setup price for you regions
• set yes for "Allow free and paid regions" option
• define maxim free area"Maximum square for free region" - for example 300 (3 blocks with 10x10)
• review your get pixels page

Here you can see how administration settings need to look:

Here you can see what you can expect as visible result:

Well, it is nice when your project to group and it mean not only more money, but more server resources. And if you didn't start to receive money it will be normal if you will start to search for options without increasing monthly payments.

How you detect trends? how you follow mainstream? and do we need Zeitgeist?

May be you see news? may be you read opinions and conclusion from analytics? Well, every one have goal, my own goal is to be clear how I can get what I want and mainstream can help me in my goal.

With version 1.4, GPix have "Advaced settings" which provide you control over advanced features. You can leave them as is and GPix will work, but you can research them and choose to change for your special case.