Oi Thaisy,
ldmadmin tail passou a responder. É que Selinux estava barrando. Agora está
apresentando o problema de timed out..
ldmadmin tail
Mar 24 20:10:42 gempak idd.cptec.inpe.br[2695] WARN: Couldn't connect to LDM on
idd.cptec.inpe.br using either port 388 or portmapper; : RPC: Remote system
error - Connection timed out
Mar 24 20:10:47 gempak idd.cptec.inpe.br[2691] WARN: Couldn't connect to LDM on
idd.cptec.inpe.br using either port 388 or portmapper; : RPC: Remote system
error - Connection timed out
Mar 24 20:10:47 gempak idd.cptec.inpe.br[2689] WARN: Couldn't connect to LDM on
idd.cptec.inpe.br using either port 388 or portmapper; : RPC: Remote system
error - Connection timed out
Mar 24 20:10:47 gempak idd.cptec.inpe.br[2690] WARN: Couldn't connect to LDM on
idd.cptec.inpe.br using either port 388 or portmapper; : RPC: Remote system
error - Connection timed out
Mar 24 20:10:47 gempak idd.cptec.inpe.br[2698] WARN: Couldn't connect to LDM on
idd.cptec.inpe.br using either port 388 or portmapper; : RPC: Remote system
error - Connection timed out
Mar 24 20:10:47 gempak idd.cptec.inpe.br[2700] WARN: Couldn't connect to LDM on
idd.cptec.inpe.br using either port 388 or portmapper; : RPC: Remote system
error - Connection timed out
Mar 24 20:10:47 gempak idd.cptec.inpe.br[2696] WARN: Couldn't connect to LDM on
idd.cptec.inpe.br using either port 388 or portmapper; : RPC: Remote system
error - Connection timed out
Mar 24 20:10:47 gempak idd.cptec.inpe.br[2692] WARN: Couldn't connect to LDM on
idd.cptec.inpe.br using either port 388 or portmapper; : RPC: Remote system
error - Connection timed out
Mar 24 20:10:47 gempak idd.cptec.inpe.br[2693] WARN: Couldn't connect to LDM on
idd.cptec.inpe.br using either port 388 or portmapper; : RPC: Remote system
error - Connection timed out
Mar 24 20:10:47 gempak tigge-ldm.cptec.inpe.br[2702] WARN: Couldn't connect to
LDM on tigge-ldm.cptec.inpe.br using either port 388 or portmapper; : RPC:
Remote system error - Connection timed out
Mar 24 20:11:42 gempak idd.cptec.inpe.br[2697] NOTE: LDM-6 desired
product-class: 20140324191142.313 TS_ENDT {{CONDUIT, "prod/gfs.*[49]$"}}
Mar 24 20:11:42 gempak idd.cptec.inpe.br[2694] NOTE: LDM-6 desired
product-class: 20140324191142.313 TS_ENDT {{CONDUIT, "prod/gfs.*[16]$"}}
Mar 24 20:11:42 gempak idd.cptec.inpe.br[2699] NOTE: LDM-6 desired
product-class: 20140324191142.313 TS_ENDT {{EXP, "^ww_"}}
Mar 24 20:11:42 gempak idd.cptec.inpe.br[2701] NOTE: LDM-6 desired
product-class: 20140324191142.313 TS_ENDT {{EXP, "(wrf|wrf2).gem$"}}
Mar 24 20:11:42 gempak idd.cptec.inpe.br[2695] NOTE: LDM-6 desired
product-class: 20140324191142.315 TS_ENDT {{CONDUIT, "prod/gfs.*[27]$"}}
Mar 24 20:11:47 gempak idd.cptec.inpe.br[2689] NOTE: LDM-6 desired
product-class: 20140324191147.313 TS_ENDT {{IDS|DDPLUS, ".*"}}
Mar 24 20:11:47 gempak idd.cptec.inpe.br[2691] NOTE: LDM-6 desired
product-class: 20140324191147.313 TS_ENDT {{UNIWISC, "GOES"}}
Mar 24 20:11:47 gempak idd.cptec.inpe.br[2690] NOTE: LDM-6 desired
product-class: 20140324191147.313 TS_ENDT {{HDS, ".*"}}
Mar 24 20:11:47 gempak idd.cptec.inpe.br[2692] NOTE: LDM-6 desired
product-class: 20140324191147.317 TS_ENDT {{NIMAGE, "NHEM"}}
Mar 24 20:11:47 gempak idd.cptec.inpe.br[2693] NOTE: LDM-6 desired
product-class: 20140324191147.317 TS_ENDT {{CONDUIT, "prod/gfs.*[05]$"}}
Mar 24 20:11:47 gempak idd.cptec.inpe.br[2700] NOTE: LDM-6 desired
product-class: 20140324191147.317 TS_ENDT {{EXP, "^ll20.*.grb"}}
O ldmadmin watch continua sem responder.
atenciosamente,
Márcio Fialho
Técnico Pesquisador / TI
CREA - MA 9040D-MA
NUGEO- UEMA
Tel: (98) 3244-0915
Em Segunda-feira, 24 de Março de 2014 19:06, Marcio Fialho
<help_fialho@xxxxxxxxxxxx> escreveu:
Oi Thaisy,
Como falei o ldmadmin wacth e o tail não respondem. O pqmon apresenta a
seguinte mensagem:
pqmon -i 5
Mar 24 19:25:54 pqmon NOTE: Starting Up (12936)
Mar 24 19:25:54 pqmon NOTE: nprods nfree nempty nbytes maxprods
maxfree minempty maxext age
Mar 24 19:25:54 pqmon NOTE: 0 1 122069 0 0
1 122069 500002816 0
Mar 24 19:25:59 pqmon NOTE: 0 1
122069 0 0 1 122069 500002816 0
Mar 24 19:26:04 pqmon NOTE: 0 1 122069 0 0
1 122069 500002816 0
Mar 24 19:26:09 pqmon NOTE: 0 1 122069 0 0
1 122069 500002816 0
Mar 24 19:26:14 pqmon NOTE: 0 1 122069
0 0 1 122069 500002816 0
Mar 24 19:26:19 pqmon NOTE: 0 1 122069 0 0
1 122069 500002816 0
Mar 24 19:26:24 pqmon NOTE: 0 1 122069 0 0
1 122069 500002816 0
Mar 24 19:26:29 pqmon NOTE: 0 1 122069 0
0 1 122069 500002816 0
Segue em anexo a resposta do regutil da minha instalação. Outro problema é que
o ldmd.log está vazio, mesmo com o ldmadmin sendo executado.
262149 -rw-r--r--. 1 ldm unidata 0 Mar 11 18:26 ldmd.log
Grato pela atenção.
Márcio Fialho
Técnico Pesquisador / TI
CREA - MA 9040D-MA
NUGEO- UEMA
Tel: (98) 3244-0915/delete-info-files : 0
/hostname : gempak.uema.br
/insertion-check-interval : 300
/reconciliation-mode : do nothing
/check-time/enabled : 1
/check-time/limit : 10
/check-time/warn-if-disabled : 1
/check-time/ntpdate/command : /usr/sbin/ntpdate
/check-time/ntpdate/servers : ntp.ucsd.edu ntp1.cs.wisc.edu ntppub.tamu.edu
otc1.psu.edu timeserver.unidata.ucar.edu
/check-time/ntpdate/timeout : 5
/metrics/count : 4
/metrics/file : /usr/local/ldm/var/logs/metrics.txt
/metrics/files : /usr/local/ldm/var/logs/metrics.txt*
/metrics/netstat-command : /bin/netstat -A inet -t -n
/metrics/top-command : /usr/bin/top -b -n 1
/log/count : 7
/log/file : /usr/local/ldm/var/logs/ldmd.log
/log/rotate : 1
/pqsurf/config-path : /usr/local/ldm/etc/pqsurf.conf
/pqsurf/datadir-path : /usr/local/ldm/var/data
/scour/config-path : /usr/local/ldm/etc/scour.conf
/surf-queue/path : /usr/local/ldm/var/queues/pqsurf.pq
/surf-queue/size : 2M
/server/config-path : /usr/local/ldm/etc/ldmd.conf
/server/ip-addr : 0.0.0.0
/server/max-clients : 256
/server/max-latency : 3600
/server/port : 388
/server/time-offset : 3600
/queue/path : /usr/local/ldm/var/queues/ldm.pq
/queue/size : 500M
/queue/slots : default
/pqact/config-path : /usr/local/ldm/etc/pqact.conf
/pqact/datadir-path : /usr/local/ldm/var/data
