![]() ![]() ![]() # and put the resulting hash value into the following line # Create one by using for example: echo -n yourpassword | shasum -a 256 # This password cannot be changed using the API or via the web interface. # system and in case you lose connectivity to your authentication backend) # You MUST specify a hash password for the root user (which you only need to initially set up the # Generate one by using for example: pwgen -N 1 -s 96 ![]() # You MUST set a secret to secure/pepper the stored user passwords here. Node_id_file = /etc/graylog/server/node-id # to use an absolute file path here if you are starting Graylog server from init scripts or similar. # The auto-generated node ID will be stored in this file and read after restarts. The master will perform some periodical tasks that non-masters won't perform. # If you are running more than one instances of Graylog server you have to select one of these # (deleted initial explanatory part of file) The link you posted says that smaller code snippets should be surrounded by three backticks: This is code.įor now, here is the edited nf file for a start: # Please help figure out where to begin, since I think there are multiple issues. I have reviewed many posts on the community, but not sure where to begin. I have reinstalled sidecar and nxlog on another vm that is not sending logs, and that has had no effect on getting logs to the graylog server from that vm. Restarted sidecar service on one reporting vm, which worked to get messages flowing into the existing sidecar and inputs, but shortly after that, the graylog admin page became unavailable. What steps have you already taken to try and solve the problem? I am new at this, so need some guidance on what is needed. Please advise more specifically what is needed here, including file locations of logs. Service logs, configurations, and environment variables: If you reboot the server, it becomes available for a time, a few days, then it times out if you try to access it. Recently was able to restart sidecar on one of the vm’s sending logs, but a few days after this, the graylog web admin site began to intermittently become unavailable. All sidecar logs show x.509 certificate not valid error. All inputs show not running, but all inputs are receiving messages. Graylog server was up and running and receiving logs, but not from certain hosts. ![]()
0 Comments
Leave a Reply. |