After applied "echo -n password | sha256sum" now I am getting issue like
"No Graylog servers available. Cannot log in".
Could you find screen shot and server.conf file and web.conf files script.
In the server.conf file:
password_secret = sDk4hzCYXJ3auybi5ZBzNB65lvO62H81tr206vJ2uOB7g3i6IDmxvowXrzYqBhKHpGdOVbQyoO1G2v3rXQxwBDnX7SdxBPVE
root_password_sha2 = 5e884898da28047151d0e56f8dc6292773603d0d6aabbdd62a11ef721d1542d8
In the web.conf file :
application.secret="sDk4hzCYXJ3auybi5ZBzNB65lvO62H81tr206vJ2uOB7g3i6IDmxvowXrzYqBhKHpGdOVbQyoO1G2v3rXQxwBDnX7SdxBPVE"
In the Graylog welcome page showing
with error like "No Graylog servers available. Cannot log in."
Could you please suggest me how to fix the issues:
1.No Graylog servers available. Cannot log in.
2.Sorry, those credentials are invalid
(here I used username:admin
password:5e884898da28047151d0e56f8dc6292773603d0d6aabbdd62a11ef721d1542d8)
but I unble to login success in Graylog.
Thanks,
Nag
Related
I use aws crontab to run my task.
it ran smoothly for some days, but today, i found crontab failed, when i open /var/log/cron
it failed to print new message, and i found
crond[296824]: No configuration file found at /root/.esmtprc or
/etc/esmtprc
in /var/log/messages, and all mail log is empty.
My Os is Centos8, can anyone offer some suggestions? Thanks a lot
Today I had the same problem. Cron send mail notifications about errors, so it take destination info from "~/.esmtprc". If you haven't configured propertly this file, you could get that error in cron log:
crond[296824]: No configuration file found at /root/.esmtprc or /etc/esmtprc
All mails whit errors that cron couldn't sent are locate in "~/.esmtp_queue/".
When attempting to debug issues with Desired State Configuration, I've found the following command invaluable;
start-dscconfiguration -wait -verbose -useexisting
This will (obviously) allow viewing of all the verbose logs.
The problem is that if the server needs to reboot as part of the configuration, or - more importantly - it's running normally (e.g. non-interactively as part of a pull configuration) it's not as easy to view these logs.
Is there any way to get the /exact/ same output logged to a specific location?
I do not have any .json files in the C:\Windows\system32\configuration\configurationstatus folder as suggested in one of the answers?
Set RebootNodeIfNeeded to false in meta configuration:
[DscLocalConfigurationManager()]
configuration Settings
{
Settings
{
ActionAfterReboot = 'StopConfiguration'
RebootNodeIfNeeded = $false
}
}
And run the existing configuration again:
Start-DscConfiguration -Wait -UseExisting -Verbose
(Adding this for posterity as other answers only contain links.)
Source: http://nanalakshmanan.com/blog/DSC-get-job-details-post-reboot/
You can follow the steps outlined in this blog to get the results post a reboot http://nanalakshmanan.com/blog/DSC-get-job-details-post-reboot/
You can also view the historical job logs as described in this blog http://nanalakshmanan.com/blog/Historical-Job-Logs/
I try to use smartmontools to monitor my device and I met 2 problems:
can't receive the test email
As the document says:http://smartmontools.sourceforge.net/man/smartd.conf.5.html, I configure the conf file with:
/dev/sda -m my#exaple.com -M test
and I start the smartd with:
/etc/init.d/smartd start
However, I don't receive the test email. I've no idea how to solve it.
BTW, As the device is something like a NAS, I guess may be there is no email service. But I don't know how to fix it.
2 log for the smartd is missing
I searched /var/log, and found nothing. Then I do the following:
add local3.* /var/log/smartd3.log to the file /etc/syslog.conf
exec: smartd -l local3
kill the smartd and start it again with: /etc/init.d/smartd start
Then,I still can't find the log file. why it is missing?
My smartmontool is 5.38 [arm-unknown-linux-gnu].
Thanks!
Ok, so I'm trying to configure and install svnserve on my Ubuntu server. So far so good, up to the point where I try to configure sasl (to prevent plain-text passwords).
So; I installed svnserve and made it run as a daemon (also installed it as a startup script with the command svnserve -d -r /var/svn).
My repository is in /var/svn and has following configuration (to be found in /var/svn/myrepo/conf/svnserve.conf) (I left comments out):
[general]
anon-access = none
auth-access = write
realm = my_repo
[sasl]
use-sasl = true
min-encryption = 128
max-encryption = 256
Over to sasl, I created a svn.conf file in /usr/lib/sasl2/:
pwcheck_method: auxprop
auxprop_plugin: sasldb
sasldb_path: /etc/my_sasldb
mech_list: DIGEST-MD5
I created it in that folder as the article at this link suggested: http://svnbook.red-bean.com/nightly/en/svn.serverconfig.svnserve.html#svn.serverconfig.svnserve.sasl (and also because it existed and was listed as a result when I executed locate sasl).
Right after that I executed this command:
saslpasswd2 -c -f /etc/my_sasldb -u my_repo USERNAME
Which also asked me for a password twice, which I supplied. All going great.
When issuing the following command:
sasldblistusers2 -f /etc/my_sasldb
I get the - correct, as far as I can see - result:
USERNAME#my_repo: userPassword
Restarted svnserve, also restarted the whole server, and tried to connect.
This was the result from my TortoiseSVN client:
Authentication error from server: SASL(-13): user not found: unable to canonify
user and get auxprops
I have no clue at all in what I'm doing wrong. I've been scouring the web for the past few hours, but haven't found anything but that I might need to move the svn.conf file to another location - for example, the install location of subversion itself. which svn results in /usr/bin/svn, thus I moved the svn.conf to /usr/bin (although that doesn't feel right to me).
Still doesn't work, even after a new reboot.
I'm running out of ideas. Anyone else?
EDIT
I tried changing this (according to what some other forums on the internet told me to do): in the file /etc/default/saslauthd, I changed
START=no
MECHANISMS="pam"
to
START=yes
MECHANISMS="sasldb"
(Actually I had already changed START=no to START=yes before, but I forgot to mention it). But still no luck (I did reboot the whole server).
It looks like svnserve uses default values for SASL...
Check /etc/sasl2/svn.conf to be readable by the svnserver process owner.
If /etc/sasl2/svn.conf is owned by user root, group root and --rw------, svnserve uses the default values.
You will not be warned by any log file entry..
see section 4 of https://svn.apache.org/repos/asf/subversion/trunk/notes/sasl.txt:
This file must be named svn.conf, and must be readable by the svnserve process.
(it took me more than 3 days to understand both svnserve-sasl-ldap and this pitfall at the same time..)
I recommend to install the package cyrus-sasl2-doc and to read the section Cyrus SASL for System Administrators carefully.
I expect this is caused by the SASL API for the call
result = sasl_server_new(SVN_RA_SVN_SASL_NAME,
hostname, b->realm,
localaddrport, remoteaddrport,
NULL, SASL_SUCCESS_DATA,
&sasl_ctx);
if (result != SASL_OK)
{
svn_error_t *err = svn_error_create(SVN_ERR_RA_NOT_AUTHORIZED, NULL,
sasl_errstring(result, NULL, NULL));
SVN_ERR(write_failure(conn, pool, &err));
return svn_ra_svn__flush(conn, pool);
}
as you may see, handling the access failure by svnserve is not foreseen, only Ok or error is expected...
I looked in /var/log/messages and found
localhost svnserve: unable to open Berkeley db /etc/sasldb2: No such file or directory
When I created the sasldb to the above file and got the permissions right, it worked. Looks like it ignores or does not use the sasl database path.
There was another suggestion that rebooting solved the problem but that option was not available to me.
I use perforce as sourcesafe, my desktop client is working fine.
I just install P4Web, perforce web client and when I try to open a file I get the following error:
P4CHARSET must be set in order to connect to a unicode server
I already add P4CHARSET registry key set to utf8 under
HKEY_CURRENT_USER\Software\perforce\environment
What more can I do?
Thanks!
You probably need to set it for the P4Web service. Check out this KB article:
http://kb.perforce.com/article/231/p4web-as-a-windows-service
There are examples of setting other parameters like the port number; you can follow those guidelines for setting P4CHARSET.
you need to run the following line on cmd:
p4 set -S "Perforce Web" P4CHARSET=utf8