[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[LDM #AHC-351489]: Couldn't lock LDM lock-file (was: ldm)
- Subject: [LDM #AHC-351489]: Couldn't lock LDM lock-file (was: ldm)
- Date: Sun, 04 Oct 2015 12:14:37 -0600
Patrick,
I can't get log on from zero.unidata.ucar.edu [128.117.140.56]:
~: ssh -v ldm@...
OpenSSH_6.7p1, OpenSSL 1.0.1l 15 Jan 2015
debug1: Reading configuration data /home/steve/.ssh/config
debug1: Reading configuration data /etc/ssh_config
debug1: Connecting to ... [...] port 22.
debug1: Connection established.
debug1: identity file /home/steve/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/steve/.ssh/id_rsa-cert type -1
debug1: identity file /home/steve/.ssh/id_dsa type 2
debug1: key_load_public: No such file or directory
debug1: identity file /home/steve/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/steve/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/steve/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/steve/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/steve/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.7
^C
~:
> bash -l -c 'ldmadmin addmetrics'
>
> was in cron before, but had been remmed out.. so it "should not" have
> interfered with ldm processes...
>
> The .ldmadmin.lck error no longer seems to be an issue... my steps to correct
> where
> 1. update all packages on the system
> 'sudo aptitude update'
> 'sudo aptitude safe-upgrade'
>
> 2. install the latest ldm per your usual instructions
>
> 3. execute make root-actions just to be sure everything is kosier
> 'su root -c 'make root-actions'
>
> 4. restart rsyslog for the same reason
> '/etc/init.d/rsyslog restart'
>
> The .ldlmadmin.lck error no longer shows up.. however the no server running
> issue still appears, and this is the latest ldm
>
> i.e.
> ldm@crad1:~$ ldmadmin watch
> There is no LDM server running
>
> But the server is actually running
>
> This is the box that you have access too, so you are more than welcome to
> shell in and play.. there are some active products still on this box, so
> don't go too crazy please :)
>
> Fyi here is the output from the latest ldm config
>
> ldm@crad1:~$ ldmadmin config
>
> hostname: "removed by me"
> os: Linux
> release: 3.2.0-4-amd64
> ldmhome: /home/ldm
> LDM version: 6.12.14
> PATH:
> /home/ldm/ldm-6.12.14/bin:/bin:/usr/bin:/usr/sbin:/home/ldm/decoders:/home/ldm/util:/home/ldm/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
> LDM conf file: /home/ldm/etc/ldmd.conf
> pqact(1) conf file: /home/ldm/etc/pqact.conf
> scour(1) conf file: /home/ldm/etc/scour.conf
> product queue: /ramdisk/queue/ldm.pq
> queue size: 8G bytes
> queue slots: default
> reconciliation mode: do nothing
> pqsurf(1) path: /home/ldm/var/queues/pqsurf.pq
> pqsurf(1) size: 2M
> IP address: 0.0.0.0
> port: 388
> PID file: /home/ldm/ldmd.pid
> Lock file: /home/ldm/.ldmadmin.lck
> maximum clients: 256
> maximum latency: 3600
> time offset: 3600
> log file: /home/ldm/var/logs/ldmd.log
> numlogs: 7
> log_rotate: 1
> netstat: /bin/netstat -A inet -t -n
> top: /usr/bin/top -b -n 1
> metrics file: /home/ldm/var/logs/metrics.txt
> metrics files: /home/ldm/var/logs/metrics.txt*
> num_metrics: 4
> check time: 1
> delete info files: 0
> ntpdate(1): /usr/sbin/ntpdate
> ntpdate(1) timeout: 5
> time servers: ntp.ucsd.edu ntp1.cs.wisc.edu ntppub.tamu.edu
> otc1.psu.edu timeserver.unidata.ucar.edu
> time-offset limit: 10
Regards,
Steve Emmerson
Ticket Details
===================
Ticket ID: AHC-351489
Department: Support LDM
Priority: Normal
Status: Closed