Austin, > I haven't intentionally started LDM as any user other than ldm. Do you have any idea how those log files got to be owned by root? > There > are two executables in bin/ owned by root and setuid: hupsyslog and > rpc.ldmd. The files in the bin/ directory that are owned by root should be owned by root: that's normal. > I changed all files in logs/ to ldm:ldmusers and started up LDM again, > logged in as user ldm. After a few hours there is still no new data. At > the moment no one process is eating up 100% cpu, but rtstats, pqact and > two instances of rpc.ldmd are hovering around 50% each. For now at least > all files in logs/ are still owned by ldm. I started the LDM this morning. The LDM timed-out trying to connect to the portmapper (which is running). Apparently, the TCP connection is being established, but the TCP data packets either aren't getting to the portmapper or aren't getting back to the LDM. Would you please check the system log file /var/log/messages for relevant messages. I noticed a bunch of VMware stuff. Is this a Windows system on which you're running Linux? > Austin > > -- > Austin Cross > Graduate Student / Research Assistant > International Arctic Research Center > University of Alaska Fairbanks > Phone: 907-474-2415 Regards, Steve Emmerson Ticket Details =================== Ticket ID: FKC-383851 Department: Support LDM Priority: Normal Status: On Hold
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.