Thanks for the suggestions.
My cardano-node process runs and I don’t see any errors or anything with it during run time that would make me suspect that there is a configuration issue, etc…
What it seems like is that sometimes it takes awhile for cardano-node to create the socket file.
I guess my assumption is someone writing code for a network service would have it create it’s socket file immediately before it does any other work. I suspect that is not the case with cardano-node. Maybe cardano-node does some sort of data integrity check before it starts it’s network services?..but not sure I’m convinced about that because I do see it logging network related messages even though the socket file isn’t created upon startup, don’t remember exactly what those messages were. I had to back off on the default logging verbose because it was making giant syslog files.
I’ll have to do a restart and time how long it takes a few times to see if it’s consistent or has something to do with the amount of data cardano-node is processing at start up. I’m going to make a guestimate that it takes longer to create the socket file every time I restart the service because the process is still syncing since it’s a new server.
Either that or I am doing something wrong and the node.socket file should get created immediately upon startup every time.