[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDD #UZP-358176]: [ldm-problem] "couldn't reset LDM registry"



Franke,

What happens when the LDM user executes the command "regutil -R"?

> I recently noticed that the ldm server keeps to send the warning mail to me. 
> The information is showing below.
> 
> From address@hidden  Tue Jun  7 11:51:01 2016
> Return-Path: <address@hidden>
> X-Original-To: ldm
> Delivered-To: address@hidden
> Received: by xxx.xxx.xxx (Postfix, from userid 1003)
> id E0774988061; Tue,  7 Jun 2016 11:51:01 -0500 (CDT)
> From: "(Cron Daemon)" <address@hidden>
> To: address@hidden
> Subject: Cron <address@hidden> /home/ldm/bin/ldmadmin addmetrics
> Content-Type: text/plain; charset=UTF-8
> Auto-Submitted: auto-generated
> Precedence: bulk
> X-Cron-Env: <XDG_SESSION_ID=14559>
> X-Cron-Env: <XDG_RUNTIME_DIR=/run/user/1003>
> X-Cron-Env: <LANG=en_US.UTF-8>
> X-Cron-Env: <SHELL=/bin/sh>
> X-Cron-Env: <HOME=/home/ldm>
> X-Cron-Env: <PATH=/usr/bin:/bin>
> X-Cron-Env: <LOGNAME=ldm>
> X-Cron-Env: <USER=ldm>
> Message-Id: <address@hidden>
> Date: Tue,  7 Jun 2016 11:51:01 -0500 (CDT)
> 
> Couldn't reset LDM registry
> 
> 
> I believe my ldm server is running, by using ldmadmin watch, the information 
> shows like below
> 
> address@hidden:~/var/logs$ ldmadmin watch
> (Type ^D when finished)
> 20160607T165409.157577Z pqutil[113747] INFO pqutil.c:1181:display_watch()     
>    236 20160607205811.778294 IDS|DDPLUS 175098801  SAKU31 NCRG 072100
> 20160607T165409.157649Z pqutil[113747] INFO pqutil.c:1181:display_watch()     
>    103 20160607205811.772476 IDS|DDPLUS 175098802  SAAT31 TQPF 072057
> 20160607T165409.157686Z pqutil[113747] INFO pqutil.c:1181:display_watch()     
>     95 20160607205811.772579 IDS|DDPLUS 175098803  SAVG31 TVSV 072100
> 20160607T165409.157764Z pqutil[113747] INFO pqutil.c:1181:display_watch()     
>    147 20160607205811.772621 IDS|DDPLUS 175098804  UANT01 CWAO 072057
> 20160607T165409.157807Z pqutil[113747] INFO pqutil.c:1181:display_watch()     
>    256 20160607205812.011678 IDS|DDPLUS 37012687  SFAB58 KWAL 072057
> 20160607T165409.157852Z pqutil[113747] INFO pqutil.c:1181:display_watch()     
>    158 20160607205812.005908 IDS|DDPLUS 37012688  SXXX03 KWAL 072057
> 20160607T165409.157891Z pqutil[113747] INFO pqutil.c:1181:display_watch()     
>    105 20160607205812.005985 IDS|DDPLUS 37012690  SXXX03 KWAL 072058
> 20160607T165409.157927Z pqutil[113747] INFO pqutil.c:1181:display_watch()     
>    740 20160607205812.006037 IDS|DDPLUS 37012691  SXXX03 KWAL 072057
> 20160607T165409.157959Z pqutil[113747] INFO pqutil.c:1181:display_watch()     
>    155 20160607205812.006078 IDS|DDPLUS 37012692  SXXX03 KWAL 072057
> 20160607T165409.157994Z pqutil[113747] INFO pqutil.c:1181:display_watch()     
>    162 20160607205812.005947 IDS|DDPLUS 37012689  SXXX03 KWAL 072057
> 20160607T165409.158028Z pqutil[113747] INFO pqutil.c:1181:display_watch()     
>    162 20160607205812.006121 IDS|DDPLUS 37012693  SXXX03 KWAL 072057
> 20160607T165409.158061Z pqutil[113747] INFO pqutil.c:1181:display_watch()     
>    135 20160607205812.011569 IDS|DDPLUS 37012694  SRFL20 KWAL 072057
> 20160607T165409.158093Z pqutil[113747] INFO pqutil.c:1181:display_watch()     
>    121 20160607205812.011642 IDS|DDPLUS 37012695  SXXX03 KWAL 072058
> 
> 
> Here is the information I used the command regutil.
> 
> address@hidden:~/var/logs$ regutil
> /delete-info-files : 0
> /hostname : xxx.xxx.xxx
> /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 : /home/ldm/var/logs/metrics.txt
> /metrics/files : /home/ldm/var/logs/metrics.txt*
> /metrics/netstat-command : /usr/bin/netstat -A inet -t -n
> /metrics/top-command : /usr/bin/top -b -n 1
> /log/count : 7
> /log/file : /home/ldm/var/logs/ldmd.log
> /log/rotate : 1
> /pqsurf/config-path : /home/ldm/etc/pqsurf.conf
> /pqsurf/datadir-path : /home/ldm/var/data
> /scour/config-path : /home/ldm/etc/scour.conf
> /surf-queue/path : /home/ldm/var/queues/pqsurf.pq
> /surf-queue/size : 2M
> /server/config-path : /home/ldm/etc/ldmd.conf
> /server/enable-anti-DOS : TRUE
> /server/ip-addr : 0.0.0.0
> /server/max-clients : 256
> /server/max-latency : 3600
> /server/port : 388
> /server/time-offset : 3600
> /queue/path : /home/ldm/var/queues/ldm.pq
> /queue/size : 500M
> /queue/slots : default
> /pqact/config-path : /home/ldm/etc/pqact.conf
> /pqact/datadir-path : /home/ldm/var/data
> 
> 
> I guessed this is because the error I read through from the ldm log file. it 
> looks like
> 
> 20160520T205219.132074Z xxx.xxx.xxx[66094] NOTE requester6.c:588:req6_new() 
> LDM-6 desired product-class: 20160520195219.132029 TS_ENDT {{IDS|DDPLUS, 
> ".*"},{NONE, "SIG=4505a6334c29e9c811d4f271e72b83a5"}}
> 20160520T205219.136466Z xxx.xxx.xxx[66094] NOTE error.c:236:err_log() 
> Upstream LDM didn't reply to FEEDME request; RPC: Unable to receive; errno = 
> Connection reset by peer
> 20160607T165757.544876Z xxx.xxx.xxx[105865] NOTE requester6.c:588:req6_new() 
> LDM-6 desired product-class: 20160607155757.544835 TS_ENDT {{IDS|DDPLUS, 
> ".*"},{NONE, "SIG=4505a6334c29e9c811d4f271e72b83a5"}}
> 20160607T165757.549147Z xxx.xxx.xxx[105865] NOTE error.c:236:err_log() 
> Upstream LDM didn't reply to FEEDME request; RPC: Unable to receive; errno = 
> Connection reset by peer
> 
> 
> Do you have any idea about what caused this problem?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: UZP-358176
Department: Support LDM
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.



NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.