I am trying to start Kafka, but my Zookeeper id is not displayed rather it only shows [myid:]
I tried changing the port numbers yet I still have the same problem. find the attached copy of the error message.
I tried changing the file name ,and port number and removing extra spaces in server properties yet I couldn't run my Kafka Cluster.enter image description here
Related
EDIT:
Not sure what I've done differently (again, these are my first steps with all of this), but now I don't get the error message I got before. Instead though, it just tries to make the connection and I get
Server selection timed out after 30000 ms
After some time.
ORIGINAL:
I am new to using MongoDB - currently taking a back end course online.
It seems that Compass has changed their interface for adding a new connection, lately, and maybe some business logic, because all guides I find use the previous one.
Specifically, when adding a new connection, in the guides I read, they leave Replica Set Name empty. When I try to do that, I get an error saying Incomplete key value pair for option.
I tried just calling it localhost and it "works", but I don't see any of my DBs.
If I connect with Robo 3t I can see them.
Is it a wrong Replica Set Name that's preventing me from deeing the DBs? Or am I doing something else wrong?
My settings for when trying to connect are:
Hostname : `localhost`
port : 27017
SRV record : I leave it off
Authentication : None
Replica Set Name : localhost
Read preferences : Primary
SSl : none
SSL tunnel : None
It appears that Compass requires a replica set name to be specified, based on the following message I get when I specify a single host which happens to be a secondary:
An error occurred while loading navigation: 'not master and slaveOk=false': It is recommended to change your read preference in the connection dialog to Primary Preferred or Secondary Preferred or provide a replica set name for a full topology connection.
"Server selection timed out" can mean different things:
There isn't a database running.
The database is running but you entered the wrong port number.
Compass attempted to perform a specific operation which required a certain server type (e.g. a primary or a secondary). The database is running and there's a server listening at the port you specified, but it is of the wrong type.
Hard to say which of these is the case just going by the error message.
I had the same problem working on a single machine for development as a replica set member(primary). I did this because I had to use #Transactional of spring-data-mongodb. What solved for me was logging to mongo shell and issuing:
rs.initiate();
I've told PostgreSQL to log to syslogd and to tag its messages with "postgresql". These messages appear in /var/log/syslog with that tag.
Now I'd like those messages not to appear in /var/log/syslog but in /var/log/example/postgresql/. I thought I could do that by creating the file /etc/rsyslog.d/25-postgresql.conf with this single line (plus some comments, in real life):
:msg,contains,"postgresql" /var/log/example/postgresql/postgresql.log
Restarting rsyslog doesn't result in postgresql messages going to that file, however: they still go to /var/log/syslog.
Any suggestions what I've done wrong?
I need to make some changes in potsgresql.conf file and pg_hba for enabling ssl. After making the changes, i stopped the postgresql server and on trying to start it , i am getting the error as :
The postgresql-x64-10 service on local computer started and then stopped.Some services stop automatically if they are not in use
Also, i notice that the postmaster.pid file gets deleted from postgresql data directory. Can anyone help in resolving this issue
Most probably you made a mistake while editing your config file, I do really recommend you to recheck the syntax, for instance for me the error was fixed after correcting the locale value (I've put first en_US), after the correction I've restarted the service and the error is gone
Why is it that when I type 'mongod -f \pluralsight\mongod.conf' (path of my conf file) in terminal, I get the following flush spam in my log file? :
Is this normal?
Here is my configuration file in case you need it.
I recently installed MongoDB and I just don't want a file that is logging that my storage is being flushed, seems like poor data management. I'm not sure what is available to me to address this, or if this is normal and permissible, or if maybe there's something I'm doing wrong when I started this project.
I figured it out, it's because in my mongod.conf file I had the verbose property set to "verbose=vvvvvv". I set it to "verbose=vvv" so it shows less info on logged.
On Centos 6.2, trying to get the kernel log redirected to the serial console, I came across an issue where agetty seems to be respawning every few keypresses.
That is, I get a login prompt in the middle of typing (after logging in).
In order to investigate the issue further, I'm looking for the location of agetty logs, but to no avail. Where and how can I see log messages for respawned agetty process?
The "diagnostics" section of the "agetty" command manpage states:
Depending on how the program was configured, all diagnostics are written to
the console device or reported via the syslog(3) facility. Error messages are
produced if the port argument does not specify a terminal device; if there is
no utmp entry for the current process (System V only); and so on.
The syslog facility by default writes the "/var/log/messages" file, but it can be configured to write another file by editing its configuration file "/etc/syslog.conf".
Finally, if the error you get is "respawning too fast", you should check your "/etc/inittab" file, as described here.