Fastdfs Frequently Asked Questions

Fastdfs Frequently Asked Questions

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 through 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.
Likely caused by the lack of administrative priviledges associated with your user account.
Ifconfig:command not found

A:export path= $PATH:/sbin

Q:[email protected]:~/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 could not be found because the export ld_library_path=/usr/loal/lib was executed earlier, so in order to make it easy to use, we put together all the Lib needed:

CP Libf*.so/usr/local/lib
Ls-l/usr/local/lib/libf* If you don't have a link map, you need to do one yourself or copy all four files.
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 you do a soft link, you need to add an absolute path, or a black hint will appear.

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: * 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: Such errors are reported in Tracker's 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 data inside the Storage_sync_timestamp.dat, delete the Group3 information, and then restart the tracker

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

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

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, error info:connection refused

A: The port is not correct. 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 modules version 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 match the corresponding configuration in the 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 a data migration problem, which requires the same number of Sub_dir that were previously configured.

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 not connected. Until the connection is successful, the startup is truly complete.
If this occurs, check why the connection is not on tracker server.

A: From V2.03 onwards, multi-tracker server will do time detection at startup to determine if 4 system files need to be synchronized from another tracker server.
The trigger time is the first Storage server connection on tracker server, and a join request is initiated.
If there are 2 tracker servers in the cluster, and one of the tracker does not start, it may cause storage server to remain in a zombie state.

Q: The server returned error number 2 when executing fdfs_test or fdfs_test1 upload file

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

Q: How do I remove 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 state of the storage server that is being deleted is active, that is, the storage server is also in the service online, it cannot be deleted.

Q:nginx and Apache extensions correspond to Fastdfs server versions

A: Extension Module 1.05: For Fastdfs server v2.x, requires server version greater than or equal to v2.09
Extension modules 1.07 and later: for Fastdfs server v3.x

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

A: The error code 28 is returned, indicating that there is not enough disk space. Note that there is a concept of reserved space in the Fastdfs, set in tracker.conf, the configuration entry is: Reserved_storage_space, the default value is 4GB, which is reserved 4GB space. Please set the Reserved_storage_space parameter as appropriate, for example, can be set to about 20% of the total disk space.

Q:nginx extension Module, the problem of not displaying pictures properly

A: In 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 service, we can see Tracker and storage communication status by Fdfs_monitor command, and find storage status is always offline.

A: Check the logs of tracker and storage to see if there is a problem with the service, and if the logs are displayed properly, it is possible that the cache files of tracker or storage party have been removed during the operation, 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 tile set information will be lost.

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

A: In the distributed graph process, when uploading tiles to fastdfs storage, the number of ports that occupy increases may reach the upper limit of the number of ports on the local operating system, so this problem occurs. This can be circumvented by the following ways:
Windows System

Run "Regedit.exe", open the registry, locate the "hkey_local_machinesystemcurrentcontrolsetservicestcpipparameters" location, add " TcpTimedWaitDelay ", the type is DWORD, the value is 30," MaxUserPort "is added, the type is DWORD, and the value is 20000 (the number of available ports on the system is adjusted).
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 let the parameters take effect.

Q: After installing Fastdfs and fastdht, why can't I find the 3 commands for Fdfs_trackerd, fdfs_storaged and FDHTD in the/usr/local/bin directory?

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

Q: When you start the FASTDHT service, the "segment error" is prompted, what is the reason?

A: This is because FDHTD requires a dependent libdb-5.3.so that is not properly installed or is pointing 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 dependency that is displayed is not version 5.3, first confirm whether the installation path is specified as/usr when installing db. If it is installed under the/USR path, but still does not rely on libdb.5.3.so correctly, you will need to manually create a libdb.so symbolic link in the/lib64 directory, pointing to the dynamic library of BDB 5.3.

The Q:fastdfs and FASTDHT services are fine, but the Add Graph task fails to view the debug version of Iserver.log, and the log shows "storageserver when uploading data tileset_names to Fastdfs, tion, the exception information is: Getstorestorage fail, errno code:28 ", what is the reason?

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

Reference Address: http://blog.rekfan.com/articles/442.html

Fastdfs Frequently Asked Questions