[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[LDM #VPO-816759]: LDM won't start through systemd or cron(reboot)
- Subject: [LDM #VPO-816759]: LDM won't start through systemd or cron(reboot)
- Date: Thu, 28 Jun 2018 11:03:33 -0600
John,
The following steps should do it. If any one of them fails, then stop and tell
me.
1. Become the LDM user in their home-directory
2. If the LDM is running, then stop it with the command
ldmadmin stop
3. Get and unpack the distribution by executing the following commands
verbatim:
rm -rf bin include lib runtime share src
wget ftp://ftp.unidata.ucar.edu/pub/ldm/ldm-6.13.6.tar.gz
gunzip -c ldm-6.13.6.tar.gz | pax -r '-s:/:/src/:'
cd ldm-6.13.6/src
4. Verify that the current working directory is the top-level LDM
source-directory with the command
ls configure.ac || echo Report that this did not work and stop here
5. Configure the build and install the package by executing the following
commands verbatim:
./configure --disable-root-actions >configure.log 2>&1 && echo Configured
make install >install.log 2>&1 && echo Installed
6. Finish the installation by performing the actions that require root
privileges with a command like
sudo make root-actions
or
su -c 'make root-actions'
7. Go the LDM user's home directory
cd
8. Verify that all's well by sending me the output of the command
ls -l
> I did away with that first try with PAX and the other option on your site
> didn't create the structure needed either. I'm sure I messed something up.
> Here's what you asked for.
>
> 1.
> ldm@tornado:~$ head /home/ldm/ldm-6.13.6/config.log
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
>
> It was created by LDM configure 6.13.6, which was
> generated by GNU Autoconf 2.68. Invocation command line was
>
> $ ./configure --enable-logging=local0
>
> ## --------- ##
> ## Platform. ##
>
> 2.
> ldm@tornado:~$ ls bin/
> afos ensureLdmhomeLinks ensureSyslogEntry feedtest hupsyslog ldmd
> ldmsend notifyme pqact pqcopy pqing pqsend pqutil
> regutil scour ulogger
> ddplus ensureRpcEntry ensureVar hds ids ldmfail
> netcheck plotMetrics pqcat pqcreate pqinsert pqsurf
> refresh_logging rpmUserActions syscheck wasReceived
> dds ensureServicesEntry feedme hrs ldmadmin ldmping
> newlog pps pqcheck pqexpire pqmon pq_test_insert regex
> rtstats uldbutil
>
> ldm@tornado:~$ ls include/
> abbr.h autoshift.h error.h feedTime.h h_clnt.h ldm5_clnt.h
> ldm.h md5.h peer_info.h prod_class.h requester6.h
> savedInfo.h timestamp.h UpFilter.h
> alrm.h down6.h fbits.h fsStats.h inetutil.h ldmalloc.h
> ldmprint.h mkdirs_open.h pq.h RegularExpressions.h rpc
> setenv.h uldb.h xdr_data.h
> atofeedt.h DownHelp.h fdnb.h globals.h lcm.h ldm_clnt_misc.h
> ldm_xlen.h pattern.h priv.h remote.h rpcutil.h
> statsMath.h ulog.h
>
> ldm@tornado:~$ ls lib/
> libldm.a libldm.la libldm.so libldm.so.0 libldm.so.0.0.0
>
> ldm@tornado:~$ ls runtime/
> acinclude.m4 CHANGE_LOG config.status ensureLdmhomeLinks ensureVar
> fileIngest html ldmping lib Makefile misc pq
> pqcopy pqinglib pqsurf README rpc scripts TODO
> aclocal.m4 config.h configure ensureRpcEntry extractDecls
> gempak hupsyslog ldmsend libtool Makefile.am mldm_sender
> pqact pqcreate pqinsert pqutil regex rpmUserActions src
> uldbutil
> BACKLOG config.h.in configure.ac ensureServicesEntry fauxPq
> grib2 ldm-50x50.xpm ldm.spec log Makefile.in noaaport
> pqcat pqexpire pqmon protocol registry rtstats stamp-h1
> ulogger
> build-aux config.log COPYRIGHT ensureSyslogEntry feedme
> gribinsert ldmd ldm.spec.in m4 mcast_lib notifyme
> pqcheck pqing pqsend protocol2 regutil scour test
>
> ldm@tornado:~$ ls share/
> doc man
Regards,
Steve Emmerson
Ticket Details
===================
Ticket ID: VPO-816759
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.