亚洲av成人无遮挡网站在线观看,少妇性bbb搡bbb爽爽爽,亚洲av日韩精品久久久久久,兔费看少妇性l交大片免费,无码少妇一区二区三区

Chinaunix

標題: 運行fastdfs_client_php_v1.6.tar.gz中的fdfs_test.php時遇到問題,請教版主 [打印本頁]

作者: xuexifdfs    時間: 2009-10-30 09:50
標題: 運行fastdfs_client_php_v1.6.tar.gz中的fdfs_test.php時遇到問題,請教版主
機器ubuntu9.04   fastdfs 版本為v1.22      tracker ip = 192.168.95.71
                                                             group1   2臺機器
                                         group2   2臺機器  192.168.95.72  192.168.95.75
                                                               group3   2臺機器

運行fastdfs_client_php_v1.6.tar.gz中的fdfs_test.php
按照文件名上傳文件成功,上傳到了group3的一臺機器上
按照文件內(nèi)容上傳文件也成功,上傳到了group1的ip為192.168.95.72的機器上
然后從192.168.95.72下載文件也成功,
最后刪除文件也成功。

查看72機器的data/sync/binlog.000 的內(nèi)容如下:
root@blade03:~/FastDFS# cat data/sync/binlog.000
1256865366 C M00/00/00/SF8mykrqPlYAAAAAAAASOSZePco50.php
1256865366 C M00/00/00/SF8mykrqPlYAAAAAAAASOSZePco50.php-m
1256865368 U M00/00/00/SF8mykrqPlYAAAAAAAASOSZePco50.php-m
1256865370 D M00/00/00/SF8mykrqPlYAAAAAAAASOSZePco50.php
1256865370 D M00/00/00/SF8mykrqPlYAAAAAAAASOSZePco50.php-m
說明程序運行是正確的。

但是遇到問題,文件被刪除的機器(也就是192.168.95.72)上的日志有以下內(nèi)容:
[2009-10-30 09:16:45] WARNING - file: storage_sync.c, line: 100, sync data file, file: /home/node03/FastDFS/data/00/00/SF8mykrqPlYAAAAAAAASOSZePco50.php not exists, maybe deleted later?
[2009-10-30 09:16:45] WARNING - file: storage_sync.c, line: 100, sync data file, file: /home/node03/FastDFS/data/00/00/SF8mykrqPlYAAAAAAAASOSZePco50.php-m not exists, maybe deleted later?
[2009-10-30 09:16:45] CRIT - file: fdfs_storaged.c, line: 281, catch signal 6, program exiting...

192.168.95.72機器上的fdfs_storaged 進程退出了。

請教版主,這是什么原因?

[ 本帖最后由 xuexifdfs 于 2009-10-31 10:02 編輯 ]
作者: happy_fish100    時間: 2009-10-30 14:19
標題: 回復 #1 xuexifdfs 的帖子
會不會是線程棧設(shè)置得太小造成的?
storage.conf中配置的thread_stack_size是多大呢?
作者: xuexifdfs    時間: 2009-10-30 14:26
標題: 回復 #2 happy_fish100 的帖子
# thread stack size, should > 512KB
# default value is 1MB
thread_stack_size=1MB

使用的是默認的值 我沒有修改  是否應該修改得大一些?
作者: happy_fish100    時間: 2009-10-30 14:45
標題: 回復 #3 xuexifdfs 的帖子
你改大到2MB試試?
作者: xuexifdfs    時間: 2009-10-30 15:32
標題: 回復 #4 happy_fish100 的帖子
[2009-10-30 15:30:44] WARNING - file: storage_sync.c, line: 100, sync data file, file: /home/node04/FastDFS/data/00/00/SV8mykrqlgQAAAAAAAASOVUJ8OI73.php not exists, maybe deleted later?
[2009-10-30 15:30:44] WARNING - file: storage_sync.c, line: 100, sync data file, file: /home/node04/FastDFS/data/00/00/SV8mykrqlgQAAAAAAAASOVUJ8OI73.php-m not exists, maybe deleted later?
[2009-10-30 15:30:44] CRIT - file: fdfs_storaged.c, line: 281, catch signal 6, program exiting...

還是進程退出了  我改成了10M
作者: happy_fish100    時間: 2009-10-30 17:00
標題: 回復 #5 xuexifdfs 的帖子
有沒有生成coredump文件呢?
建議重新編譯一下程序fdfs_storaged
進入storage目錄,修改Makefile,將:
COMPILE = $(CC) -O3 ...
中的-O3替換為-g
然后執(zhí)行:
make clean; make

執(zhí)行
ulimit -c 10240
然后運行fdfs_storaged
這樣確保程序異常終止時,可以生成core dump文件。
有了core dump文件,就可以用gdb進行調(diào)試了。
作者: xuexifdfs    時間: 2009-10-31 09:56
我運行的是fastdfs_client_php_v1.6.tar.gz中的fdfs_test文件,昨天發(fā)帖子的時候誤說成FastDFS_v1.22\FastDFS\php_client\fastdfs_test.php了,現(xiàn)在把帖子改過來了,實在不好意思。

請問版主是否遇到過我帖子里面說的:運行fastdfs_client_php_v1.6.tar.gz中的fdfs_test.php,出現(xiàn)的問題。謝謝版主

[ 本帖最后由 xuexifdfs 于 2009-10-31 09:59 編輯 ]
作者: xuexifdfs    時間: 2009-10-31 10:12
請問版主,運行fastdfs_client_php_v1.6.tar.gz中的fdfs_test.php
是不是應該用:
#php fdfs_test.php

我用的方法是在/var/www/中創(chuàng)建FastDFS的符號鏈接,然后在瀏覽器中打開fdfs_test.php文件,我覺得出現(xiàn)錯誤可能是由于我這個錯誤操作造成的。
作者: happy_fish100    時間: 2009-10-31 10:54
標題: 回復 #8 xuexifdfs 的帖子
這個應該沒有關(guān)系的。
從你說的情況來看,是storage server程序退出了。
能否照我6樓的做法操作一下,定位一下問題所在。
作者: xuexifdfs    時間: 2009-10-31 11:14
標題: 回復 #9 happy_fish100 的帖子
每一個storage server上都要這樣修改嗎?
作者: happy_fish100    時間: 2009-10-31 11:22
標題: 回復 #10 xuexifdfs 的帖子
出問題的那臺storage server。
作者: xuexifdfs    時間: 2009-10-31 14:54
標題: 回復 #11 happy_fish100 的帖子
版主,我將幾個storage server都按照你說的配置了一次,然后再次在瀏覽器上運行fdfs_test.php文件。

同樣的問題,文件被刪除的那個storage server上的進程退出了,log如下:

[2009-10-31 11:26:49] INFO - FastDFS v1.22, base_path=/home/node03/FastDFS, store_path_count=1, subdir_count_per_path=256, group_name=group1, network_timeout=60s, port=23000, bind_addr=, max_connections=256, heart_beat_interval=30s, stat_report_interval=60s, tracker_server_count=2, sync_wait_msec=200ms, sync_interval=0ms, sync_start_time=00:00, sync_end_time: 23:59, allow_ip_count=-1, file_distribute_path_mode=0, file_distribute_rotate_count=100, fsync_after_written_bytes=0, sync_log_buff_interval=10s, sync_binlog_buff_interval=60s, thread_stack_size=10240 KB, check_file_duplicate=0, FDHT group count=0, FDHT server count=0, FDHT key_namespace=, FDHT keep_alive=0
[2009-10-31 11:26:49] INFO - HTTP supported: server_port=8888, http_trunk_size=262144, default_content_type=application/octet-stream, anti_steal_token=0, token_ttl=0s, anti_steal_secret_key length=0, token_check_fail content_type=, token_check_fail buff length=0
[2009-10-31 11:26:49] INFO - file: tracker_client_thread.c, line: 191, successfully connect to tracker server 192.168.95.71:22122
[2009-10-31 11:26:49] INFO - file: tracker_client_thread.c, line: 191, successfully connect to tracker server 192.168.95.79:22122
[2009-10-31 11:26:49] INFO - file: storage_sync.c, line: 1701, successfully connect to storage server 192.168.95.75:23000
[2009-10-31 14:35:50] INFO - file: storage_sync.c, line: 1701, successfully connect to storage server 192.168.95.75:23000
[2009-10-31 14:45:50] WARNING - file: storage_sync.c, line: 100, sync data file, file: /home/node03/FastDFS/data/00/00/SF8mykrr3RgAAAAAAAASOUOT8cI61.php not exists, maybe deleted later?
[2009-10-31 14:45:50] WARNING - file: storage_sync.c, line: 100, sync data file, file: /home/node03/FastDFS/data/00/00/SF8mykrr3RgAAAAAAAASOUOT8cI61.php-m not exists, maybe deleted later?
[2009-10-31 14:45:50] CRIT - file: fdfs_storaged.c, line: 281, catch signal 6, program exiting...

出問題的機器上的storage里沒有發(fā)現(xiàn)coredump文件。還請問版主,這又是為何?
看log提示,好像是與75那臺機器同步數(shù)據(jù)的時候出的問題,但是我看過之前的帖子,版主你說過這2個warning可以不管它,但是奇怪的就是這臺機器上的storaged進程退出了

[ 本帖最后由 xuexifdfs 于 2009-10-31 15:04 編輯 ]
作者: xuexifdfs    時間: 2009-10-31 15:18
版主你好,我分析了一下log

這應該是一個同步異常問題,也就是說72機器上的文件file: /home/node03/FastDFS/data/00/00/SF8mykrr3RgAAAAAAAASOUOT8cI61.php
還沒有與同組的75機器同步,就已經(jīng)被刪除了,所以在75與72同步數(shù)據(jù)的時候就出現(xiàn)這樣的warning,然后程序執(zhí)行退出操作。

請問版主我的分析是否正確? 新手上路還請多多指教
作者: xuexifdfs    時間: 2009-10-31 17:29
版主你好,后來我又做了一個測試,使用命令刪除文件
即: /usr/local/bin/fdfs_test /etc/fdfs/client.conf delete group1 文件

刪除了組內(nèi)其中一臺機器上的文件,但是刪除完畢以后,這臺機器上的storaged進程還是退出了,情況和執(zhí)行fdfs_test.php文件造成的結(jié)果一樣的。

對于這個問題我比較迷惑,向版主請教了!謝謝
作者: happy_fish100    時間: 2009-10-31 18:30
標題: 回復 #14 xuexifdfs 的帖子
從日志文件可以看出,storage server的最大連接數(shù)是缺省配置的256。
你把storage.conf中的max_connections配置小一些試試呢?比如配置為32試試。
另外,最好照我上面的操作步驟,程序異常退出時,讓系統(tǒng)生成core dump文件,這樣就便于定位問題所在了。

[ 本帖最后由 happy_fish100 于 2009-10-31 18:32 編輯 ]
作者: xuexifdfs    時間: 2009-10-31 19:00
標題: 回復 #15 happy_fish100 的帖子
我已經(jīng)按照你的方法重新配置了storage,但是程序進程退出后,沒有生成core dump文件。
作者: happy_fish100    時間: 2009-10-31 19:06
標題: 回復 #16 xuexifdfs 的帖子
運行fdfs_storaged前,要執(zhí)行ulimit -c 10240設(shè)置要生成coredump文件。
執(zhí)行:
sysctl -a | grep core
把輸出的信息貼一下。
作者: xuexifdfs    時間: 2009-10-31 20:14
標題: 回復 #17 happy_fish100 的帖子
root@blade03:/# sysctl -a |grep core
error: permission denied on key 'net.ipv4.route.flush'
kernel.core_uses_pid = 0
kernel.core_pattern = core
net.core.wmem_max = 131071
net.core.rmem_max = 131071
net.core.wmem_default = 124928
net.core.rmem_default = 124928
net.core.dev_weight = 64
net.core.netdev_max_backlog = 1000
net.core.message_cost = 5
net.core.message_burst = 10
net.core.optmem_max = 20480
net.core.xfrm_aevent_etime = 10
net.core.xfrm_aevent_rseqth = 2
net.core.xfrm_larval_drop = 0
net.core.xfrm_acq_expires = 30
net.core.somaxconn = 128
net.core.netdev_budget = 300
net.core.warnings = 1
error: permission denied on key 'net.ipv6.route.flush'
root@blade03:/#
作者: happy_fish100    時間: 2009-10-31 20:27
標題: 回復 #18 xuexifdfs 的帖子
生成的core文件名應該就是core吧。
程序異常退出,不應該不生成core文件。∧銍栏裾瘴艺f的步驟操作的么?

剛才看了一下程序,你修改一下源程序:fdfs_storaged.c,將157行:
sigaction(SIGABRT, &act, NULL) < 0 || \
刪除,然后重新編譯試試看能否生成core文件。

如何才能生出core文件,參見如下文章:《淺析Linux下core文件》,文章鏈接:
http://bowen.blog.51cto.com/136148/96867

[ 本帖最后由 happy_fish100 于 2009-10-31 20:33 編輯 ]
作者: xuexifdfs    時間: 2009-10-31 20:44
標題: 回復 #19 happy_fish100 的帖子
找到了生成的core文件了 原來就在我的根目錄下面 ,沒有注意看 我試驗了4次 一共有4個"core.xxx"文件
作者: happy_fish100    時間: 2009-10-31 20:55
標題: 回復 #20 xuexifdfs 的帖子
用gdb看一下。
gdb  fdfs_storaged   <corefile>

例如:
gdb  fdfs_storaged   core.1234

進去后可以看到調(diào)用堆棧。把函數(shù)堆棧貼一下吧,謝謝!
作者: xuexifdfs    時間: 2009-10-31 21:05
標題: 回復 #21 happy_fish100 的帖子
root@blade03:/# gdb fdfs_storaged core.30777
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...

warning: Can't read pathname for load map: Input/output error.
Reading symbols from /usr/lib/libevent-1.4.so.2...done.
Loaded symbols for /usr/lib/libevent-1.4.so.2
Reading symbols from /lib/libpthread.so.0...done.
Loaded symbols for /lib/libpthread.so.0
Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/libnsl.so.1...done.
Loaded symbols for /lib/libnsl.so.1
Reading symbols from /lib/librt.so.1...done.
Loaded symbols for /lib/librt.so.1
Reading symbols from /lib/libresolv.so.2...done.
Loaded symbols for /lib/libresolv.so.2
Reading symbols from /lib/ld-linux-x86-64.so.2...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Core was generated by `/usr/local/bin/fdfs_storaged /etc/fdfs/storage.conf'.
Program terminated with signal 6, Aborted.
[New process 31038]
[New process 30777]
[New process 31037]
[New process 31036]
[New process 31035]
[New process 31034]
[New process 31033]
[New process 31032]
[New process 31031]
[New process 31030]
[New process 31029]
[New process 31028]
[New process 31027]
[New process 31026]
[New process 31025]
[New process 31024]
[New process 31023]
[New process 31022]
[New process 31021]
[New process 31020]
[New process 31019]
[New process 31018]
[New process 31017]
[New process 31016]
[New process 31015]
[New process 31014]
[New process 31013]
[New process 31012]
[New process 31011]
[New process 31010]
[New process 31009]
[New process 31008]
[New process 31007]
[New process 31006]
[New process 31005]
[New process 31004]
[New process 31003]
[New process 31002]
[New process 31001]
[New process 31000]
[New process 30999]
[New process 30998]
[New process 30997]
[New process 30996]
[New process 30995]
[New process 30994]
[New process 30993]
[New process 30992]
[New process 30991]
[New process 30990]
[New process 30989]
[New process 30988]
[New process 30987]
[New process 30986]
[New process 30985]
[New process 30984]
[New process 30983]
[New process 30982]
[New process 30981]
[New process 30980]
[New process 30979]
[New process 30978]
[New process 30977]
[New process 30976]
[New process 30975]
[New process 30974]
[New process 30973]
[New process 30972]
[New process 30971]
[New process 30970]
[New process 30969]
[New process 30968]
[New process 30967]
[New process 30966]
[New process 30965]
[New process 30964]
[New process 30963]
[New process 30962]
[New process 30961]
[New process 30960]
[New process 30959]
[New process 30958]
[New process 30957]
[New process 30956]
[New process 30955]
[New process 30954]
[New process 30953]
[New process 30952]
[New process 30951]
[New process 30950]
[New process 30949]
[New process 30948]
[New process 30947]
[New process 30946]
[New process 30945]
[New process 30944]
[New process 30943]
[New process 30942]
[New process 30941]
[New process 30940]
[New process 30939]
[New process 30938]
[New process 30937]
[New process 30936]
[New process 30935]
[New process 30934]
[New process 30933]
[New process 30932]
[New process 30931]
[New process 30930]
[New process 30929]
[New process 30928]
[New process 30927]
[New process 30926]
[New process 30925]
[New process 30924]
[New process 30923]
[New process 30922]
[New process 30921]
[New process 30920]
[New process 30919]
[New process 30918]
[New process 30917]
[New process 30916]
[New process 30915]
[New process 30914]
[New process 30913]
[New process 30912]
[New process 30911]
[New process 30910]
[New process 30909]
[New process 30908]
[New process 30907]
[New process 30906]
[New process 30905]
[New process 30904]
[New process 30903]
[New process 30902]
[New process 30901]
[New process 30900]
[New process 30899]
[New process 30898]
[New process 30897]
[New process 30896]
[New process 30895]
[New process 30894]
[New process 30893]
[New process 30892]
[New process 30891]
[New process 30890]
[New process 30889]
[New process 30888]
[New process 30887]
[New process 30886]
[New process 30885]
[New process 30884]
[New process 30883]
[New process 30882]
[New process 30881]
[New process 30880]
[New process 30879]
[New process 30878]
[New process 30877]
[New process 30876]
[New process 30875]
[New process 30874]
[New process 30873]
[New process 30872]
[New process 30871]
[New process 30870]
[New process 30869]
[New process 30868]
[New process 30867]
[New process 30866]
[New process 30865]
[New process 30864]
[New process 30863]
[New process 30862]
[New process 30861]
[New process 30860]
[New process 30859]
[New process 30858]
[New process 30857]
[New process 30856]
[New process 30855]
[New process 30854]
[New process 30853]
[New process 30852]
[New process 30851]
[New process 30850]
[New process 30849]
[New process 30848]
[New process 30847]
[New process 30846]
[New process 30845]
[New process 30844]
[New process 30843]
[New process 30842]
[New process 30841]
[New process 30840]
[New process 30839]
[New process 30838]
[New process 30837]
[New process 30836]
[New process 30835]
[New process 30834]
[New process 30833]
[New process 30832]
[New process 30831]
[New process 30830]
[New process 30829]
[New process 30828]
[New process 30827]
[New process 30826]
[New process 30825]
[New process 30824]
[New process 30823]
[New process 30822]
[New process 30821]
[New process 30820]
[New process 30819]
[New process 30818]
[New process 30817]
[New process 30816]
[New process 30815]
[New process 30814]
[New process 30813]
[New process 30812]
[New process 30811]
[New process 30810]
[New process 30809]
[New process 30808]
[New process 30807]
[New process 30806]
[New process 30805]
[New process 30804]
[New process 30803]
[New process 30802]
[New process 30801]
[New process 30800]
[New process 30799]
[New process 30798]
[New process 30797]
[New process 30796]
[New process 30795]
[New process 30794]
[New process 30793]
[New process 30792]
[New process 30791]
[New process 30790]
[New process 30789]
[New process 30788]
[New process 30787]
[New process 30786]
[New process 30785]
[New process 30784]
[New process 30783]
[New process 30782]
[New process 30781]
[New process 30780]
[New process 30779]
[New process 30778]
#0  0x00007fa79b9bdfb5 in raise () from /lib/libc.so.6
(gdb) where
#0  0x00007fa79b9bdfb5 in raise () from /lib/libc.so.6
#1  0x00007fa79b9bfb55 in abort () from /lib/libc.so.6
#2  0x00007fa79b9fd228 in ?? () from /lib/libc.so.6
#3  0x00007fa79ba8a2c7 in __fortify_fail () from /lib/libc.so.6
#4  0x00007fa79ba88170 in __chk_fail () from /lib/libc.so.6
#5  0x00007fa79ba877ab in __vsnprintf_chk () from /lib/libc.so.6
#6  0x00007fa79ba8767b in __snprintf_chk () from /lib/libc.so.6
#7  0x000000000041aa3d in storage_sync_delete_file ()
#8  0x000000000041cc9d in storage_sync_thread_entrance ()
#9  0x00007fa79bd043ba in start_thread () from /lib/libpthread.so.0
#10 0x00007fa79ba70fcd in clone () from /lib/libc.so.6
#11 0x0000000000000000 in ?? ()
(gdb) Quit

看來是storage_sync_delete_file ()和storage_sync_thread_entrance ()這里出了問題
作者: happy_fish100    時間: 2009-10-31 21:09
標題: 回復 #22 xuexifdfs 的帖子
非常感謝!你安裝的版本是V1.22吧?

修改Makefile,編譯時帶上-g參數(shù),然后重新編譯fdfs_storaged。
make clean; make

這樣用gdb就可以定位到代碼行了,謝謝!
作者: xuexifdfs    時間: 2009-10-31 21:18
>>非常感謝!你安裝的版本是V1.22吧?
是的 我安裝的是1.22版本

>>修改Makefile,編譯時帶上-g參數(shù),然后重新編譯fdfs_storaged。
make clean; make 這樣用gdb就可以定位到代碼行了,謝謝!

我按照版主你在6樓說的方法進行了操作,修改Makefile然后重新編譯,得到了core dump文件
作者: happy_fish100    時間: 2009-10-31 21:21
標題: 回復 #24 xuexifdfs 的帖子
如果編譯時帶上了 -g參數(shù),gdb中可以看到源碼文件名和代碼所在行數(shù)的。
你確認運行的fdfs_storaged是重新編譯后的吧?

只要gdb把出錯時的代碼行數(shù)打印出來,就可以直接定位到問題所在。

[ 本帖最后由 happy_fish100 于 2009-10-31 21:27 編輯 ]
作者: xuexifdfs    時間: 2009-11-01 01:02
標題: 回復 #25 happy_fish100 的帖子
謝謝版主,我按照你6樓說的方法重新編譯了fdfs_storaged,然后將其拷到/usr/local/bin下面,最后執(zhí)行fdfs_storaged。

然后我通過瀏覽器再次執(zhí)行了fdfs_test.php文件,這下沒有出現(xiàn)文件被刪除的機器上的進程退出的問題了,而且文件刪除以后,同組的其他機器也及時同步了。

非常感謝版主不厭其煩的解答,以后研究FastFDS過程中遇到問題再來向版主請教!




歡迎光臨 Chinaunix (http://www.72891.cn/) Powered by Discuz! X3.2