New answers tagged configuration
From "BOSPROD9", try to connect with the mongoshell to the other serves: $ mongo --host 10.235.96.12 --port 27017 $ mongo --host 10.235.96.13 --port 27017 (Telnet is not the same.) If this doesn't work, it might be firewall or BindIP. Check bind_ip (should be 0.0.0.0, change in mongodb.conf is it's 127.0.0.1): $ netstat -nap | grep :27017 | grep LISTEN ...
Your bind-address needs to be 0.0.0.0 or at the very least the IP address of the interface you will be connecting to from your remote machine. If you set it to 127.0.0.1 only loopback connections from the server can be made.
Just a misunderstanding I guess. The unit for the given number is blocks (or buffers), not 1 kb like you assume. Quoting the manual for shared_buffers: Each buffer is 8192 bytes, unless a different value of BLCKSZ was chosen when building the server. Bold emphasis mine. SELECT pg_size_pretty(327680 * 8192::numeric); pg_size_pretty -------------- ...
Expanding on what @mustaccio said, the answer for me was the SELinux context on the new logpath and dbpath. I ran the following commands and all was well: sudo chcon -Rv --type=mongod_log_t $logpath sudo chcon -Rv --type=mongod_var_lib_t $dbpath (this was on RHEL 7.1 btw)
Also, is the Services section in SQL Server Configuration Manager just a "shell" of the full Services screen, which is limited to SQL Server related services? Yes, SQL SCM is the SQLServerManager10.msc file that is opened as a snap-in Windows Management Console (mmc.exe). Is there any reason not to stop and start SQL Server services from the full ...
Top 50 recent answers are included