I am trying to set up a graylog-server by their docs
I installed everything , turned on elastic search , installed mongo , configurated files , added name / passwd hashed and yet when i visit localhost:9000 is still unable to connect.
I tried to start up everything again
sudo service elasticsearch start
sudo service mongodb start
sudo service graylog-server start
sudo service rsyslog start
sudo service apache2 start
but it didnt work
Has anyone met with similliar problem? I am trying to make it work for few hours but nothing works. Thanks
You also need to make port 12900 available, because this is the port of the REST API which the web interface uses to connect to. You can find more information about this here.
Related
I have installed hadoop (HDP ) in the google cloud vm instance , after sometime when i tried to connect the machine again, it is showing error :
"We are unable to connect to VM on port 22" .
To get additional debug logs try to SSH using verbose flag using the following command:
$ gcloud compute ssh INSTANCE_NAME --zone ZONE --ssh-flag="-vvv"
If the above step doesn’t help, connect to the instance using the serial console of the affected instance and check if this issue has to do with open port as Abhinav mentioned.
You find additional SSH troubleshooting information in the Help Center Article.
I was trying to set up mongo server on Windows 10.
It looked like everything alright and the service was listening on 27017.
However on another command prompt, mongo failed to connect and the screen just froze as follow
I've checked the firewall rule, port 27017 is open. And ping 127.0.0.1 is responding.
Any idea why the connection would get stuck?
Try running mongo.exe with verbose mode
c:\mongodb\bin>mongo.exe --verbose
This will help you diagnose this further.
I have just got this situation.
Solution: Edit mongo configuration
mongodb.conf
linux: sudo nano /etc/mongodb.conf
and disable auth=true. Then restart mongo server service.
linux: sudo service mongodb restart
Incorrect config authentication steps lead to this hanging in mongo shell.
After that, config following this link: https://medium.com/#matteocontrini/how-to-setup-auth-in-mongodb-3-0-properly-86b60aeef7e8
Then re-enable auth=true
I created a new AWS account and started a new tier 2 instance. So I did following things afterward :
Created elastic IP and associated it with the instance.
Configured the inbound security groups for http, https and custom TCP rule:8080
Installed tomcat7 using "sudo yum install tomcat7"
Started tomcat using "sudo service tomcat7 start"
Finally, i tried to check the tomcat, by hitting http://elastic-ip:8080 from the browser but a blank page comes up.
I guess this is a 404 error. Please help me which part have i missed.
I am trying to set up a redis sentinel as a windows service on a Azure VM (IaaS).
I am using the MS OpenTech port of Redis for Windows and running the following command...
redis-server --service-install --service-name rdsent redis.sentinel.conf --sentinel
This command installs the service on my system but when I try to start this service either through the services control panel or through the following command...
redis-server --service-run --service-name rdsent redis.sentinel.conf --sentinel
Then the service fails to start with the following error...
HandleServiceCommands: system error caught. error code=1063, message = StartServiceCtrlDispatcherA failed: unknown error
Am I missing something here?
Please someone help me start this service make it work properly.
I had the same problem, and mine was related to my sentinel config. A number of articles I have found have some incorrect examples, so my service install would not work until the configuration was correct. Anyway, here is what you need at a minimum for your sentinel config (for Windows Redis 2.8.17):
sentinel monitor <name of redis cache> <server IP> <port> 2
sentinel down-after-milliseconds <name of redis cache> 4000
sentinel failover-timeout <name of redis cache> 180000
sentinel parallel-syncs <name of redis cache> 1
Once you have that setup, the original Redis service command above will work.
According to MSOpenTech, the following command should install Redis Sentinel as a service:
redis-server --service-install --service-name Sentinel1 sentinel.1.conf --sentinel
But when I used that command the installed service wouldn't start: it would immediately fail with error 1067, "The process terminated unexpectedly." Looking at service entry I'm guessing the problem is that the --service-name parameter isn't being filtered and ends up as part of the service executable path.
What I did find to work is installing the service manually with the SC command:
SC CREATE Sentinel1 binpath= "\"C:\Program Files\Redis\redis-server.exe\" --service-run sentinel.1.conf --sentinel"
Don't forget the required space after "binpath=", and obviously that path will have to reflect where you've installed redis-server.exe. Also after the service installed I edited the service entry so Redis Sentinel would run under the Network Service account.
I am using v3.0.501 and ran into the two issues below. While present it caused the service to fail on start without an error written to either the file log or the Event Log.
The configuration file must be the last parameter of the command line. If another parameter was last, such as --service-name, it would run fine when invoked the command line but would consistently fail went started as a service.
Since the service installs a Network Service by default, ensure that it has access to the directory where the log file will be written.
Once these two items were accounted for the redis as a service run smooth as silk.
Recently, I have found a way how to setup windows service for Redis and Sentinel.
During my setup, I encountered similar problem. I finally figured it out: it was caused by the configuration file path.
I have put all my configuration into my github project: https://github.com/dingyuliang/Windows-Redis-Sentinel-Config
I have a problem on mongodb setup.
I am using windows 8 64 bit, downloaded package for windows.
While I am trying to install this package on cmd, I get an error.
http://prntscr.com/1ct7pa
It's stoped this line "[websvr] admin web console waiting for connections on port 28017"
How can I repair this error?
thanks.
edit:
I realized from answers, "this problem isn't error".
I try this command, it worked flawlessly.
mongod --logpath c:\mongodb\logs\mongo.log --dbpath c:\mongodb\data\db --directoryperdb --install
From the attached screenshot, MongoDB server has started successfully. By running mongod.exe you have started MongoDB server. It is now ready to accept connections from MongoDB clients. You can connect to your MongoDB server using MongoDB shell, a MongoDB client, or your application, and perform database operations. To start the MongoDB shell, use the following from command prompt.
By default, MongoDB server listens on port 27017. In addition, the MongoDB admin console listens on MongoDB port number + 1000. Here you are using port 27017 for your MongoDB, hence admin console is on port 28017. The following url will take you to the admin console.
http://kubilay:28017/
I try this command, it worked flawlessly.
mongod --logpath c:\mongodb\logs\mongo.log --dbpath c:\mongodb\data\db --directoryperdb --install
And windows service Mongodb started successful.
I like that ;)