Common errors in CentOS FASTDFS configuration

Fastdfs FAQ

Q:/fdfs_trackerd:error while loading shared libraries:libevent-1.4.so.2:cannot open Shared object file:no such file or Directory

A:export ld_library_path=/usr/loal/lib (libevent installation path, can be found by find)

Q:command ' Ifconfig ' is available in '/sbin/ifconfig '
The command could not being located because '/sbin ' is not included in the PATH environment variable.
This is most likely caused by the lack of administrative priviledges associated with your user account.
Ifconfig:command not found

A:export path= $PATH:/sbin

q:nginx@ubuntu:~/fastdfs/bak$./run_nginx.sh
/home/nginx/nginx/sbin/nginx:error while loading shared libraries:libfastcommon.so:cannot open Shared object File:no s Uch file or directory

A: The Fastdfs library file was not found because the export ld_library_path=/usr/loal/lib was previously executed, so in order to make it easy to use, put all the needed lib together:

CP Libf*.so/usr/local/lib
Ls-l/usr/local/lib/libf* If there is no link map, you need to do one or four files all over.
sudo ln-sf/home/nginx/fastdfs/lib/libfastcommon.so.1/usr/local/lib/libfastcommon.so
sudo ln-sf/home/nginx/fastdfs/lib/libfdfsclient.so.1/usr/local/lib/libfdfsclient.so

Note: When doing soft links need to add an absolute path, otherwise there will be a black hint.

q:400 Badrequest
[2011-12-12 15:24:21] Error-file:/TMP/FASTDFS-NGINX-MODULE/SRC/COMMON.C, line:561, logic file:m00/00/00/ Wkgbnu7lqyjzjz4maa4crxl5scq670.jpg NOT EXISTS
2011/12/12 15:24:21 [ERROR] 14147#0: *1 open () "/home/nginx/nginx/html/favicon.ico" failed (2:no such file or directory) client:192.168.1.123, Server:localhost, Request: "Get/favicon.ico http/1.1", Host: "192.168.1.53:8090"

A: Modify/fastdfs/conf/mod_fastdfs.conf
Inside Url_have_group_name = True

Q: report such errors in the tracker log
ERROR-FILE:TRACKER_MEM.C, line:1406, the format of the file "/home/bstar/dfs_data/data/storage_sync_timestamp.dat" is Invalid, group:group3, row count:1 > Server count:0

A: Modify the Storage_sync_timestamp.dat inside the data, delete the Group3 information, and then restart Tracker

Q: This type of error occurs when tracker is started:
Error-file:.. /COMMON/FDFS_HTTP_SHARED.C, line:128, param "http.mime_types_filename" not exist or are empty

A: Modify the tracker.conf inside, change the # #include http.conf to #include http.conf, then reboot

Q:ERROR-FILE:TRACKER_HTTP_CHECK.C, line:132, HTTP check alive, connect to HTTP server 192.168.1.53:8888 fail, errno:1 One, the error info:connection refused

A: The port is not right. To configure storage and Nginx Port consistency/

Q:error-file:/HOME/NGINX/INSTALL/FASTDFS-NGINX-MODULE/SRC/COMMON.C, line:561, logic file:m00/00/00/ Wkgbnu7wrbrcayguaaloprgj7yq668.jpg NOT EXISTS

A:apache and Nginx Extension module versions v1.06 and above, you need to set the storage path information for storage server in the configuration file/etc/fdfs/fastdfs_mod.conf.
An example is shown below:
Store_path_count=1
Store_path0=/home/yuqing/fastdfs
Both Store_path_count and store_path# need to be set correctly and must be identical to the corresponding configuration in storage.conf

Q:DEBUG-FILE:TRACKER_PROTO.C, line:48, server:192.168.1.51:22122, response status 28!= 0
Tracker_query_storage fail, error no:28, error info:no space left on device

A: Insufficient space

Q:EBUG-FILE:STORAGE_DISK_RECOVERY.C, line:699, disk recovery:begin recovery data path:/home/nginx/fastdfs ...

A: This is the problem after data migration, the number of previously configured Sub_dir is consistent.

Q: When you start storage server, you are always in a zombie state.
Starting storage Server,storage will connect to tracker server and will retry if it is not connected. Until the connection is successful, the boot is not really finished.
If this occurs, check the reason why the tracker server is not connected.

A: After V2.03, tracker server does a time check at startup to determine whether 4 system files need to be synchronized from another tracker server.
The trigger time is after the first storage server connects to tracker server and initiates a join request.
If there are 2 tracker servers in the cluster, and one of the tracker does not start, the storage server may be in a zombie state.

Q: When performing fdfs_test or fdfs_test1 upload files, the server returns the error number 2

A: Error number 2 indicates an storage server that does not have an active state. You can perform Fdfs_monitor view server status.

Q: How do I delete an invalid storage server?

A: You can use Fdfs_monitor to delete. The command line is as follows:
/usr/local/bin/fdfs_monitor Delete
For example:
/usr/local/bin/fdfs_monitor/etc/fdfs/client.conf Delete group1 192.168.0.100
Note: If the status of the deleted storage server is active, which means that the storage server is still online, it cannot be deleted.

Q:nginx and Apache extension modules correspond to the FASTDFS server version

A: Extending module 1.05: For Fastdfs server v2.x, the server version is required to be greater than or equal to v2.09
Extension Module 1.07 and above: for Fastdfs server v3.x

Q: Upload file failed, return error code 28, what's going on?

A: Return error code 28, indicating insufficient disk space. Note that there is a reservation in the FASTDFS concept, set in the tracker.conf, configuration items are: Reserved_storage_space, the default value is 4GB, that is, 4GB space reserved. Please set reserved_storage_space this parameter as appropriate, for example, you can set the total disk space of about 20%.

Q:nginx expansion module, the problem of not displaying pictures properly

A: In the configuration file/etc/fdfs/mod_fastdfs.conf, the default setting is this: Http.need_find_content_type=false This parameter needs to be set to true in Nginx. should be set to False in Apache

Q: After starting the Fastdfs tracker and storage services, the Fdfs_monitor command to view the tracker and storage communication status, found that storage status is always offline, how to do?

A: Check the tracker and storage logs to see if there is a problem with the service, and if the log appears to be normal, it may be during the operation that the cache file for tracker or storage is deleted, resulting in a cache mismatch. At this point, turn off the tracker and storage services, delete the data files in the Base_path directory specified in tracker.conf and storage.conf, and restart the service.
Note: If you delete the files in the FASTDHT Base_path directory, the Slice set information will be lost.

Q: When distributing Chettu, why does the console prompt "No buffer space available (maximum connections reached?): Connect"?

A: In the distributed mapping process, when uploading slices to fastdfs, the number of ports used is increased, which may reach the upper limit of the port number of the local operating system, so this problem occurs. You can circumvent the following methods:
Windows System

Run "Regedit.exe", open the registry, locate the "hkey_local_machinesystemcurrentcontrolsetservicestcpipparameters" location, add " TcpTimedWaitDelay ", the type is DWORD, the value is 30; add" MaxUserPort ", the type is DWORD, the value is 20000 (increase the number of available ports on the system).
Linux System

Run "vi/etc/sysctl.conf", edit the file, and add the following:
Net.ipv4.tcp_syncookies = 1
Net.ipv4.tcp_tw_reuse = 1
Net.ipv4.tcp_tw_recycle = 1
Net.ipv4.tcp_fin_timeout = 30

Then execute "/sbin/sysctl-p" to allow the parameters to take effect.

Q: After installing Fastdfs and FASTDHT, why not find the 3 commands for Fdfs_trackerd, fdfs_storaged, and FDHTD under the/usr/local/bin directory?

A: This problem occurs because the Libevent version of the system is too low to cause FASTDFS compilation to fail. Please check that the libevent version is 1.4.x or above.

Q: When starting the FASTDHT service, the prompt "paragraph error", what is the reason?

A: This is because the FDHTD need to rely on libdb-5.3.so not properly installed or directed to the link. You can use the command ldd/usr/local/bin/fdhtd to view the dependencies of the FDHTD command, and if the Libdb dependencies shown are not version 5.3, first verify that the install path is specified as the/USR directory when installing db. If you are installed under the/USR path but still do not rely on libdb.5.3.so correctly, you will need to manually create a libdb.so symbolic link in the/lib64 directory and point to the dynamic library of BDB 5.3.

Q:fastdfs and FASTDHT services are normal, but the Add Map task fails, view the debug version of the Iserver.log, log display "to Fastdfs storageserver upload data tileset_names, occurs MYEXCEP tion, the exception message is: Getstorestorage fail, errno code:28 ", what is the reason?"

A: Error code 28 indicates No space left on device. Fastdfs can set the RESERVED_STORAGE_SAPCE parameter in the tracker.conf configuration file, that is, the storage reserved storage space size, default is 10%. If the reservation space is less than the setting value, a 28 error occurs.