Sponsor:

Server and Web Integrator
Link:
Kloxo-MR logo
6.5.0 or 7.0.0
Click for "How to install"
Donation/Sponsorship:
Kloxo-MR is open-source.
Donate and or Sponsorship always welcome.
Click to:
Click Here
Please login or register. 2024-03-29, 13:26:10

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Kloxo-DR

Pages: [1] 2 3 ... 16
1
Hi alexo,

Kloxo-MR is buggy.

I CONFIRM THAT THIS IS A BUG, amongst many others, AND - UNTIL TODAY - REFRAINED TO PLACE THIS IN THIS FORUM! Mustafa lives in his little world of craze and believes that everything is fine with version 6.5.0f.

People who have not seen such a problem will not understand this. But I know what you are talking about.

Do the following:

1) Try to switch to any other php version from the control panel if it allows, and wait until it is finished and there is a message in the TINY LITTLE CORNER BELOW that it is finished.

Reboot to make sure that the new php version comes into effect.

2) If the php version 5.3.xx does not appear in the list, then try to manually install it through yum.

I did the listing by yum list php*. Then I installed php 5.3.3, I think.

One you install php version, you _MUST_ reboot.

Try to install through command line and reboot.

At some point, this problem will be gone.

Also try FIRST sh /script/cleanup. This will also try to insert reqpective entries in the table and correct it.

because Mustafa does not chase after each and every problem in depth when a user reports and modifies his scripts, although he gives an excellent support, the sh /script/cleanup also remains buggy. Further, this script is a gigntic invention of Mustafa that really works fantastic when it works. It does work for muost of the areas but fails to work on certain combination of environments or situations.

2
Hi Mustafa,

Why do you want everyone to confirm here?

My confirmation number is: 5D207650FG999322M.

3
Kloxo-MR Technical Helps / Re: remote ftp backup not working
« on: 2014-05-01, 19:20:55 »
Hi Mustafa,

1. Not work in innodb (also possible in Aria) storage-engine

Thats is true. But now, Kloxo-MR concentrates on MyISAM.

2. Need stop mysql server before zipped process and start again after that because to make sure integrity of data

We do not need to backup procedures and functions.

To make sure integrity of data:

Old Server:
...........There is no need to stop mysql server BEFORE THE TAR BEGINS to copy
...........and compress the data. The only negative situation may occur is when
...........the database tables are updated and very big.
...........This depends on the size of the database.
...........Here, one could issue a LOCK TABLE command.
...........This would be the same when one makes a dump or a a dir copy.
...........Time to lock until a directory is copied _IS_ FASTER to dump procedure.

Old Server:
...........There is no need to stop mysql server DURING THE COPY PROCESS is going on.

Old Server:
...........If you want a consistent dump and sure integrity of data of database
...........WHILE ITS BEING MODIFIED you need to use --single-transaction
...........(if you only backup innodb) or --lock-all-tables.
...........Stop mysql server is not necessary.

New Server:
...........There is no need to stop mysql server
...........WHILE KLOXO-MR CREATES A NEW ENTRY of database, if absent.

New Server:
...........There is no need to stop mysql server
...........BEFORE THE TAR BEGINS to copy
...........and UNCOMPRESS the data under /var/lib/mysql/db_name.

New Server: Last step
...........There is no need to stop mysql server
...........to RELOAD THE GRANT TABLES on new entry of database.
...........Thereafter, mysql will recognize the directory as a database.

In a nutshell, your ALT method is appropriate for recent condition of Kloxo-MR server installations everywhere. regardless of the kernel or bits, the ALT method SHALL FUNCTION efficiently without errors and fears.

Copy, tar and untar and simple linux functions. Now, if a directory appears under the /var/lib/mysql, then it does not disturb mysql at all until the directory is registered as a database. The only exception that would disturb mysql server would be if the name of this directory is mustafa. Then, mysql would crash.

3. No other panel use this method (including MySQL Inc and MariaDB Inc) as 'alternative' method

Big companies do not use this method because they have to handle with different mysql versions and environment.

In that case, I would also not suggest to do anything like this.

In case of Kloxo-Mr, this fundamental pre-requisite is not there. All Kloxo-MR installation will have a standarized procedure of installlation and maintanence of the servers. Here, one can use a different approach than used by different companies.

If you do not implement, than thats fine. But if you do implement, it will not help me.

4
Kloxo-MR Technical Helps / Re: remote ftp backup not working
« on: 2014-05-01, 16:16:20 »
Hi Mustafa,
What's the 'raw method'?. So, what's different with method by Kloxo-MR (also Kloxo-MR)?.

Uh, I was perhaphs not very clear about this, as well as zenkul. Zenkul ment in his description of my psyedoname "Kloxo-DR", when he refered to RAW method.

Lets define both, the current method as "BACKUP method" and my suggestion as "RAW method", as zenkul proposed" the name (which is really very accurate description of the method). This is what happens:

1) BACKUP METHOD

Currently, backup function makes:

Code: [Select]
mysql> dump client_name_db_name;
When the backup function is executed, it will make an export to dump data from mysql server using the mysql functions. It will convert all the data in tables of the database and wrap it with (INSERT"") STATEMENTS. It can grow really very large, depending on the data inside table.fields.

Advantage:

a. It remains mysql version independent.
b. Many external programs are able to import such dumps.

We do not require both above.

2) RAW METHOD

Suggestion is:

tar -cpf client_name_db_name.tgz /var/lib/mysql/client_name_db_name

Here, there is no conversion of three files from mysql format to ASCII data with INSERT statements inside.

So there is no backup.

Thus, there is no restore.

One simply has do the following:

Create client_name_db_name from kloxo restore, if not exists.
Code: [Select]
if [[ ! -d  /var/lib/mysql/client_name_db_name]] ; then
   {
    mkdir /var/lib/mysql/client_name_db_name
    insert details in mysql about client_name_db_name
   }
   tar -zxf /tmp/backupTRgbvFGT/client_name_db_name.tgz /var/lib/mysql/client_name_db_name

Kloxo-MR does not export php files to ASCII but makes a tar from /home/dir. Use the same method for mysql data as well. This is possible now because the system of mysql has become very stable and backward compatible too.

Thats it.

5
Kloxo-MR Technical Helps / Re: remote ftp backup not working
« on: 2014-05-01, 12:59:37 »
Hi zenkul,

yes, there is some many option for backup/restore, depends on we condition
@MRatwork,
why stop development "raw backup" like Kloxo-DR method ?

In 2008, I had a bad fight with Ligesh about this aspect also, amonst my argument with him regarding security features.

By not implementing the RAW BACKUP method, he introduced an additional layer of problems that prevails even today.

If the mysql database was functional on the old server, keeping the mysql pre-requisites the same, it MUST function on the new server.

I argued with Ligesh and questioned him why he was "kind of exporting" to make a backup from those MYI/MYD files to re-contruct the database to the same MYI/MYD files in a new location.

With the reconstruction one gets into 100s of problems, where the table file name.MYI will be the same before in the old server and name.MYI after in the new server.

His only argument was that it is possible that there are different mysql versions and configurations.

What if not?

With the current state of Kloxo-MR, the architecture is reached to a way far more advanced level, although Mustafa creates his own little world with his scripts breaking the Linux integrity.

Thats why I also support you, and your request to Mustafa, to completely abolish the "backup/restore" method and implement the transfer oF EXACT COPIES IN COMPRESSED FORMAT OF ALL FILES OF MYSQL DATABASES without one single byte exported and imported.

Backup could also be done with php ---> ASCII and restore could be ASCII ---> php back again.

Backup could also be done with html ---> ASCII and restore could be ASCII ---> html back again.

Does this make sense?

Now, with Kloxo-MR with an advanced level of data exchanges features with FTPs, and those install and fix scripts harmonizing through yum repos, it is really non-sense to use the "backup/restore" method.

Then, after abolishing, everyone can ofcourse use the "backup/restore" method on mysql level when they want, should the pre-requisites of environment changes.

After implementing the "RAW METHOD", Kloxo-MR will achieve the highest form of integrety in transfer of data between datacebters or servers and and archiving the data.

6
Kloxo-MR Technical Helps / Re: remote ftp backup not working
« on: 2014-05-01, 08:36:33 »
Hi Mustafa,
I think we must back to topic.

Did you mean to say that my solution is wrong?

If file database backup already exists in server, many options to restore:

There are even more options to use a dump. The method you suggested is not the only one.

But I can certainly read your thoughts between the lines. It can be avoided tell people "how to use an extra layer" of problems.

Mysql dump, backup and restore is helpful when there is a purpose. Creating mysql dump, it simply makes a file with SQL statements in ASCII format. One can compress it for certain reasons.

Mysql dump with SQL statements in ASCII format is necessary when one should make a version upgrade from Mysql 4--- > 5 or technical pre-requisites changes like INNODB ---> MyISAM.

When all pre-requisites between two servers are equal and a manual transfer is in question, there is no reason for a mysql dump, backup and restore. Why?

Under the mysql database directory /var/lib/mysql there are files with extensions like MYI, MYD, etc. in mysql format. These files will operate under any name of the database under the same mysql server architecture and driver connecting it.

THESE MYSQL FILES ARE NOT SERVER DEPENDENT AND ARE PORTABLE TO ANY SERVER.

So one converts these files to a text file inserting SQL INSERT statements and make one file 10 - 100 times bigger. Then one transfers to a different server. And then one reconverts it back again.

This is a step that can be completely avoided. There are many tutorials available for such a process with php scripts, also interactive. So ofcourse one can use method of back/restore. One can ofcourse give solution to this, when necessary. But this is not always necessary.

Young webmasters will not realize this. There are experts reading such exchanges and your messages are evaluated by the international community. There are journalists writing articles on Kloxo-MR...

7
Hi Spacedust,
Buy something like this: https://i-hosting.co/overstock - it costs only $7 and it's a perfect server for slave test server.

For a test server is $ 7 very expensive. It should be $ 0.007!

You can order a test server with www.DigitalOcean.com and pay per hour for the test server.

When you are finished with the test, you only pay for the hour. Make an image in your account and lest it remain. This means you park the server and DO NOT PAY FOR IT on mnthly charges.

When you need one more hour, then create a server "droplet" and pay for one more hour.

In one month they bill for maximum 620 hours and costs $ 5.

So testing a server for 62 hours it would costs $ 0.50!

You can test it in Los Sngeles, Amsterdam, Singapore and New York.

By the way, I liked your creative title making competence "and bug on welcome". You made me laugh...

8
HI,
i have 10gbps network

I have an LTE connection and thats sufficient to upload a couple of hundred megabytes within minites.

During my stay in asia before a couple of months, I saw how horrible state of internet is. Just nightmare.

Before a couple of months, I read post by Mustafa about his slow internet connection. He declared that he had a nightmare to upload 2 GB of data.

Not in every country people have an extraordinary internet connection speeds like you and myself.

Thats the reason why it is necessary to use Kloxo-MR FTPs for the direct transfer of data with SSl.

Many times this does not work due to several reasons, which may be in the scripts but MAY NOT BE. Now due to the introduction of CSRF token system, it may not function on certain systems.

Here an alternatve is necessary for using the data from old server to new server.

In this case, ofcourse kloxo-mr is the best, but when it does not function, one _MUST_ be able to come forward with an extra option WITHOUT ANY ADDITIONAL LAYER OF PROBLEMS, residing in any script, connection, etc.

9
Kloxo-MR Technical Helps / Re: remote ftp backup not working
« on: 2014-04-30, 22:18:09 »
Hi cmdman,

Why the hell you want to restore?

You do not make any "backups". So there is no option or suggestion of "restore".

In the above solution, one already has the database uncompressed under the root directory /root/download. With this one has "kind of restored" in a different location

You simply have to create a new database from kloxomr with any name and copy as follows:

cp /root/download/db_name /var/lib/mysql/old_or_new_db_name

Then all the database files for mysql will appear under the new database (with same or new name) in the new server.

Where is the question of "restore" here?

When people started to use calculators they forgot to calculate. And thats the question you are asking me.

Before you make such rubbish comments "use less is useless", apply your intelligence and inform yourself in advance to talk like this.

10
Hi Mella,
121MB of gzipped DB isn't considered big :) Could sound like it's PHP that's timing out as the default script execution time is 30s.
 

Living is a developed world both of us may experience different kind of speeds of internet connections.

For someone in  developing country, 121 MB is huge data to upload.

While it is ofcourse better to increase execution time out any way, in any other solution there is a download and upload.

Many times I use wget. Sometimes I use Midnight commander to make an ftp connection depending on if I require secure or not. Because wget uses https, it is easier and faster.

The solution I suggested, which I use it daily, is a data transfer between servers directly, regardless of midnight commander or wget. It is 10 times faster compared to upstream of a private upstream capacity.

11
Kloxo-MR Technical Helps / Re: remote ftp backup not working
« on: 2014-04-30, 15:54:17 »
Hi cmdman,

It has been 15 years I have been using the above solution. I have written several shell scripts for all kinds  for transfers of data between servers and use them daily.

Any other method is not as good as reliable than above.

In any method other than server to server transfers, one uses ones own computer to download and upload.

Wget and ftps and basically no different. Both work with SSL.

It is a joke to say that this is a useless solution.

Next time when I see your post, I will avoid giving any solution.

No problem. Sorry for wasting my time for you.

12
Kloxo-MR Technical Helps / Re: installation Failed
« on: 2014-04-30, 09:17:10 »
Hi uzer,

full of errors.. :(

The install script is buggy or does not work on many systems. In the installation, you will find /usr/local/lxlabs/kloxo/install/setup.sh that is not executable.

I have seen this error many times and found that it occurs when setup.sh was not properly executed.
Do the following:

Code: [Select]
cd /usr/local/lxlabs/kloxo/install
chmod +x setup.sh
rpm -Va --nofiles --nodigest
sh ./setup.sh
sh /script/upcp

Then you may also have problems later at the stage when it will give a mysql connection error.

If this happens, do the following:

Code: [Select]
sh /script/reset-mysql-root-password
sh /script/reset-mysql-root-password root

Mustafa,

I suggest that you break the setup process into three, one pre-installation to prepare server for kloxomr installation, one normal setup for kloxomr and one post installation setup specific to user and server.

In the post installation, you can have the process of setup under an interactive installation procedure.

13
Hi jure12,

FOR BIG DATABASES
AVOID EXPORT MYSQL ---> DOWNLOAD ---> UPLOAD ---> IMPORT
USE PACK ---> HIGH SPEED TRANSFER BETWEEN DATACENTERS ---> UNPACK

Anything to do with export from mysql has given many problems. I do a transfer by archiving it and unpacking the archive, a method that is reliable.

FOR THIS YOU DO NOT NEED TO DOWNLOAD THE BACKUP FILE TO YOUR COMPUTER!

#####################################
Do the following:

1) OLD SERVER: PREPARE FOR TRANSFER AND PACK
Make a tar of the corresponding database from # shell and make it accessable on the internet.

Code: [Select]
mkdir /home/clientname/domain.com/download_dir_name
cd /home/clientname/domain.com/download_dir_name
tar -zpcf backup.tgz /var/lib/mysql/db_name

2) NEW SERVER: CONNECT AND DOWNLOAD BY WGET METHOD AND UNPACK

You can use the following to download the backup by following:

Code: [Select]
mkdir /root/download
cd /root/download
wget https://domain.com/download_dir_name/backup.tgz --no-check-certificate
tar -zxvf backup.tgz

Then you are done.
#####################################

In the above step, the database is made available for download via internet. You can add password protection to download_dir_name or backup.tgz, or do without it.

If you add password protection to download_dir_name, then you must make the wget  connection with username and Password.
If you add Password protection to backup.tgz, then you must give it during unpacking by tar -zxvf.

When you download the file to your computer, then you use the download speed of your internet connection of downloadstream. When you upload this file, you use 8 times slower internet connection speed of upstream.

When you make a secure wget connection, you use 10-30 times faster connection from new server to old server for download and transfer the file in compressed format depending the network card attached to both servers and load on the servers.

The advantage of this method is that you DOWNLOAD THE FILE USE HIGH SPEED TRANSFER BETWEEN DATACENTERS.

---------------------------------------------------------

You should have created a db_name under the client in new server. Simply copy contents of the archive uncompressed under /root/download to the respective /var/lib/mysql/db_name. Then you are done.

14
Kloxo-MR Technical Helps / Re: remote ftp backup not working
« on: 2014-04-30, 08:45:58 »
Hi cmdman,

FOR BIG DATABASES
AVOID EXPORT MYSQL ---> DOWNLOAD ---> UPLOAD ---> IMPORT
USE PACK ---> HIGH SPEED TRANSFER BETWEEN DATACENTERS ---> UNPACK

Anything to do with export from mysql has given many problems. I do a transfer by archiving it and unpacking the archive, a method that is reliable.

FOR THIS YOU DO NOT NEED TO DOWNLOAD THE BACKUP FILE TO YOUR COMPUTER!

#####################################
Do the following:

1) OLD SERVER: PREPARE FOR TRANSFER AND PACK
Make a tar of the corresponding database from # shell and make it accessable on the internet.

Code: [Select]
mkdir /home/clientname/domain.com/download_dir_name
cd /home/clientname/domain.com/download_dir_name
tar -zpcf backup.tgz /var/lib/mysql/db_name

2) NEW SERVER: CONNECT AND DOWNLOAD BY WGET METHOD AND UNPACK

You can use the following to download the backup by following:

Code: [Select]
mkdir /root/download
cd /root/download
wget https://domain.com/download_dir_name/backup.tgz --no-check-certificate
tar -zxvf backup.tgz

Then you are done.
#####################################

In the above step, the database is made available for download via internet. You can add password protection to download_dir_name or backup.tgz, or do without it.

If you add password protection to download_dir_name, then you must make the wget  connection with username and Password.
If you add Password protection to backup.tgz, then you must give it during unpacking by tar -zxvf.

When you download the file to your computer, then you use the download speed of your internet connection of downloadstream. When you upload this file, you use 8 times slower internet connection speed of upstream.

When you make a secure wget connection, you use 10-30 times faster connection from new server to old server for download and transfer the file in compressed format depending the network card attached to both servers and load on the servers.

The advantage of this method is that you DOWNLOAD THE FILE USE HIGH SPEED TRANSFER BETWEEN DATACENTERS.

15
Spamdyke and iptables would be the next step to look at, had you managed to change the DNS servers.

Because you had a fresh install, that area Spamdyke  was not in the list of suggestions.  Spamdyke by default does not block anything.

I have asked Mustafa to make a better configuration possibility for SSL and Spamdyke. He gave a deaf ear to my requests.

Good that you got things managed. Good luck.




Pages: [1] 2 3 ... 16

Top 10 Social Networking:    Facebook    Twitter    LinkedIn    Pinterest    Google Plus    Tumblr    Instagram    VK    Flickr    Vine

Page created in 0.038 seconds with 20 queries.

web stats analysis