Ticket #264 (assigned problem)

Opened 5 months ago

Last modified 4 weeks ago

Set up netdrms02 at NSO

Reported by: niles Owned by: niles
Priority: highest Milestone:
Component: NSO Servers Version:
Severity: blocker Keywords:


The NSO machine needs to be set up as a backup to the netdrms01 machine. Hopefully we can use it to try remote SUMS.

The external RAID has been set up (with a technical note about how to do that).

Currently waiting on disks to populate internal RAID.

Change History

comment:1 Changed 5 months ago by alisdair

  • Component changed from (unfiled) to NSO Servers

comment:2 Changed 4 months ago by alisdair

  • Owner changed from Niles to niles
  • Status changed from new to assigned

comment:3 Changed 2 months ago by niles

Got netdrms-9.2 compiled. Have to set up the database as per


Also note that the default encoding now seems to be UTF8 rather than LATIN1 in postgres. We should be fine with it

comment:4 Changed 7 weeks ago by niles

I'm working on this, but it's got to a stage where I need some input from Art who is out until next week. I'll pick it up again when he's back.

comment:5 Changed 4 weeks ago by niles

I now have the code compiled and the SUMS database set up. After I got rpcbind running with the -i option ("i" for insecure, ho-hum) the sum_start.NetDRMS actually works, but in fact that is an out-of-date method to start things. The new way does not involve RPC (yay) but Art has been preoccupied with recent JSOC database calamities and has not updated the documentation yet. As I'd rather emerge from this with good documentation, I'm waiting for that to happen.

I may edit the old start and stop scripts at NSO so that they simply print a message directing the user to the new way of doing things and then exit. They still have to be around as they are still in use at the JSOC, but at a remote site they are confusing.

Note: See TracTickets for help on using tickets.