Unsolved
This post is more than 5 years old
1 Rookie
•
9 Posts
0
1625
September 21st, 2012 10:00
Errors in gstd log file
In NMC, Libraries, right click on on Networker Servers and choose refresh I get an error. Could not update library information ...: Connection Failure. I do see the NS and 4 libraries connected so it was working.
I get the following for all 4 of my Storage Nodes in the gstd.raw logs:
0 1348249473 2 0 0 7976 7704 0 hqbackup04c.corp.domain.com gstd 2 %s 1 0 88 poll: error (Unable to connect to server) querying server DCBACKUP02c.corp.domain.com
0 1348249473 2 0 0 7976 7704 0 hqbackup04c.corp.drugstore.com gstd 2 %s 1 0 60 RPC service 390109 (vers 2) not registered on 192.168.40.168
0 1348249473 2 0 0 7976 7704 0 hqbackup04c.corp.drugstore.com gstd 2 %s 1 0 60 RPC service 390109 (vers 2) not registered on 192.168.40.168
0 1348249473 2 0 0 7976 7704 0 hqbackup04c.corp.drugstore.com gstd 2 %s 1 0 34 ERROR generated: file null line #0
0 1348249473 2 0 0 7976 7704 0 hqbackup04c.corp.drugstore.com gstd 2 %s 1 0 43 ERROR generated: file gt_server.c line #157
0 1348249473 2 0 0 7976 7704 0 hqbackup04c.corp.drugstore.com gstd 2 %s 1 0 34 ERROR generated: file null line #0
0 1348249473 2 0 0 7976 7704 0 hqbackup04c.corp.drugstore.com gstd 2 %s 1 0 43 ERROR generated: file gt_server.c line #159
There are no firewalls between them, of the Storage Nodes is on the same network segment as the Networker Server.
Thanks for any insight.
ble1
4 Operator
•
14.3K Posts
0
September 21st, 2012 16:00
RPC 390109 is nsrstat (the only UDP thingy NW uses) and it looks like it could not connect to that RPC port on 192.168.40.168. Not sure why IP is used instead on name, but name resolution in place is likely required for this to work. You can do test from gst server and do rpcinfo -t 192.168.40.168 390113 2.
EDIT: On second thought, that might not be good example as -r does TCP connect, but I just tried it and it works:
[root@foo ~]# rpcinfo -t bar 390109 2
program 390109 version 2 ready and waiting