Based on the email service configuration document, I configure the email server for gmail. I get the following error:
| 2018-04-26 16:52:43.049 WARN 8 --- [ader-Executor-1] c.abc.myapp.service.MailService : Email could not be sent to user '<an email address>': Authentication failed; nested exception is javax.mail.AuthenticationFailedException: 534-5.7.14 <https://accounts.google.com/signin/continue?sarp=1&scc=1&plt=AKgnsbuK
myapp-app_1 | 534-5.7.14 FS7l_SlKGMmQ4NUwOUI8hV4s4DFyO9Ajb9jIQNPmd_oPTPeYKvPez2X9WTyRxci1tqFD3j
myapp-app_1 | 534-5.7.14 EIuDoA4ekrQEvFUoHHTBkBpXLPSd9WyK4OfnClEVc7LOKqRRurLkCzm7YPSVjScsoCCSfY
myapp-app_1 | 534-5.7.14 ZDkTMZpbTNSpjO7cLfFPhrk8YyKz6-Zr6PUh8diPloWF7dCGQDHb3U8Pupum7w8ZooCS6D
myapp-app_1 | 534-5.7.14 W4a_ecgcmwyU-yqYVU41sE9Ejns_E> Please log in via your web browser and
myapp-app_1 | 534-5.7.14 then try again.
myapp-app_1 | 534-5.7.14 Learn more at
myapp-app_1 | 534 5.7.14 https://support.google.com/mail/answer/78754 s65sm52666197pfj.124 - gsmtp
I follow the instruction and get a page with the following message:
Account access enabled
Please try signing in to your Google account again from your new device or application.
However, I still get the erro.
So, I try outlook email server.
myapp-app_1 | 2018-04-26 17:22:08.398 WARN 8 --- [ader-Executor-1] c.abc.myapp.service.MailService : Email could not be sent to user '<an email address>': Failed messages: com.sun.mail.smtp.SMTPSendFailedException: 554 5.2.0 STOREDRV.Submission.Exception:SendAsDeniedException.MapiExceptionSendAsDenied; Failed to process message due to a permanent exception with message Cannot submit message. 16.55847:CB210000, 17.43559:0000000094000000000000000000000000000000, 20.52176:140FCB820E00101097010000, 20.50032:140FCB827E171010AA010000, 0.35180:0A007282, 255.23226:D1010000, 255.27962:0A000000, 255.27962:0E000000, 255.31418:0A006784, 16.55847:B4000000, 17.43559:0000000068010000000000000000000000000000, 20.52176:140FCB820E0010100A00F736, 20.50032:140FCB827E1710100A00F836, 0.35180:EF010000, 255.23226:40000730, 255.27962:0A000000, 255.27962:32000000, 255.17082:DC040000, 0.27745:0A001880, 4.21921:DC040000, 255.27962:FA000000, 255.1494:07020000, 0.37692:B4000000, 0.37948:B4000000, 5.33852:00000000534D545000343345, 4.56248:DC040000, 7.40748:010000000000010B41344539, 7.57132:000000000000000000000000, 1.63016:32000000, 4.39640:DC040000, 8.45434:171C0100364C1BE8000000000000000000303833, 5.10786:0000000031352E32302E303731352E3031343A434F31505231384D42303833373A66663930326535392D346362332D346164632D383633322D36636464303663626165666600503000000000, 255.1750:02017368, 255.31418:5B030000, 0.22753:80030400, 255.21817:DC040000, 4.60547:DC040000, 0.21966:7E010000, 4.30158:DC040000 [Hostname=CO1PR18MB0837.namprd18.prod.outlook.com]
I know they are not a JHipster problem, but I am wondering how JHipster users solve them.
Related
I am building a SLURM multi-cluster setup, with a slurmdbd hosted on-premises and a slurmctld node in Oracle Cloud. The slurmctld is able to connect to the slurmdbd, but receives this error message when I try to connect to the database in any way:
sacct: error: slurm_persist_conn_open: Something happened with the receiving/processing of the persistent connection init message to <IP_ADDRESS>: Failed to unpack SLURM_PERSIST_INIT message
sacct: error: slurmdbd: Sending PersistInit msg: No error
JobID JobName Partition Account AllocCPUS State ExitCode
------------ ---------- ---------- ---------- ---------- ---------- --------
sacct: error: slurm_persist_conn_open: Something happened with the receiving/processing of the persistent connection init message to <IP_ADDRESS>: Failed to unpack SLURM_PERSIST_INIT message
sacct: error: slurmdbd: Sending PersistInit msg: No error
sacct: error: slurmdbd: DBD_GET_JOBS_COND failure: Unspecified error
Looking at the /var/log/slurm/slurmdbd.log file on my slurmdbd cluster, it records this error:
[2022-03-11T08:29:47.541] error: Munge decode failed: Invalid credential
[2022-03-11T08:29:47.541] auth/munge: _print_cred: ENCODED: Wed Dec 31 19:00:00 1969
[2022-03-11T08:29:47.541] auth/munge: _print_cred: DECODED: Wed Dec 31 19:00:00 1969
[2022-03-11T08:29:47.541] error: slurm_unpack_received_msg: auth_g_verify: REQUEST_PERSIST_INIT has authentication error: Unspecified error
[2022-03-11T08:29:47.541] error: slurm_unpack_received_msg: Protocol authentication error
[2022-03-11T08:29:47.551] error: CONN:10 Failed to unpack SLURM_PERSIST_INIT message
To ensure that my credentials are valid, I have copied the slurmdbd's MUNGE key to the slurmctld via SCP, ensured that the UID and GID of the slurm and munge users on all nodes are identical, and made sure that the clocks are all in sync. When I munge and unmunge on either server, it successfully decodes the encrypted message. However, when I try to authenticate the credential from one server to the other using the echo foo | ssh user#server munge | unmunge command, it gives me a response of unmunge: error: invalid credential. What could I be doing to still receive this response? What should I do to make sure that my credential is valid?
Using Datastax 5.1 version Cassandra, trying to integrate ldap with it. Added required parameters in dse.yaml and cassandra.yaml but when I try to authenticate ldap user then it keeps failing with below error.
[root#ip-11.11.11.11 ~]# cqlsh -u 123456
Password:
Connection error: ('Unable to connect to any servers', {'127.0.0.1': AuthenticationFailed('Failed to authenticate to 127.0.0.1: Error from server: code=0100 [Bad credentials] message="Failed to login. Please re-try."',)})
Here is the message from debug.log.
ERROR [Native-Transport-Requests-1] 2019-06-06 05:34:50,842 DefaultLdapConnectionFactory.java:68 - unable to bind connection: PROTOCOL_ERROR: The server will disconnect!
TRACE [Native-Transport-Requests-1] 2019-06-06 05:34:50,843 LdapUtils.java:577 - [ldap-fetch-user] ERROR - failed to fetch username: 123456
org.apache.directory.api.ldap.model.exception.LdapOperationException: PROTOCOL_ERROR: The server will disconnect!
at org.apache.directory.ldap.client.api.LdapNetworkConnection.startTls(LdapNetworkConnection.java:3986)
at org.apache.directory.ldap.client.api.LdapNetworkConnection.bindAsync(LdapNetworkConnection.java:1373)
at org.apache.directory.ldap.client.api.LdapNetworkConnection.bind(LdapNetworkConnection.java:1293)
at org.apache.directory.ldap.client.api.AbstractLdapConnection.bind(AbstractLdapConnection.java:130)
at org.apache.directory.ldap.client.api.AbstractLdapConnection.bind(AbstractLdapConnection.java:114)
Looks like its not able to connect to ldap, not binding with it?
I am able to connect to AD using ldapsearch and get result for the user from the cassandra node. Also imported the certificate into the keystore and mentioned it in the dse.yaml. Any pointers?
The issue was with the certificate chain, after using correct intermediate certificates binding with AD was successful.
I try to run sample application as stated here : http://hyperledger-fabric.readthedocs.io/en/release/write_first_app.html
Everything looks good until I ran this command : node registerUser
Error :
Store
path:/Users/johndoe/Desktop/myProject/fabric-samples/fabcar/hfc-key-store
Successfully loaded admin from persistence Failed to register: Error:
fabric-ca request register failed with errors
[[{"code":0,"message":"No identity type provided. Please provide
identity type"}]]
I checked logs by running docker logs ca.example.com command:
2017/11/08 09:43:07 [DEBUG] Successful authentication of 'admin'
2017/11/08 09:43:07 [DEBUG] Register request received
2017/11/08 09:43:07 [DEBUG] Received registration request from admin: &{RegistrationRequest:{Name:user1 Type: Secret:<> MaxEnrollments:1 Affiliation:org1.department1 Attributes:[] CAName:}}
2017/11/08 09:43:07 [DEBUG] Registration of 'user1' failed: No identity type provided. Please provide identity type
2017/11/08 09:43:07 [INFO] 172.18.0.1:60190 - "POST /api/v1/register" 0
Did I miss anything here? I successfully ran node enrollAdmin.js and able to get the generated eCert & key material in hfc-key-store
In my case, adding the user's role type make it works.
return fabric_ca_client.register({enrollmentID: 'user1', affiliation: 'org1.department1',role: 'client'}, admin_user);
I was having same trouble but after adding role: 'client' to the registeUser file it ran and registered successfully.
before- adding the role: 'client'
Anoops-MacBook:fabcar anoopdixit$ node registerUser.js
Store path:/Users/anoopdixit/Documents/Blockchain/projects/Hyperledger-Fabric/fabric-samples/fabcar/hfc-key-store
Successfully loaded admin from persistence
Failed to register: **Error:** fabric-ca request register failed with errors [[{"code":0,"message":"No identity type provided. Please provide identity type"}]]
Anoops-MacBook:fabcar anoopdixit$
after:adding the *role: 'client'
Anoops-MacBook:fabcar anoopdixit$ node registerUser.js
Store path:/Users/anoopdixit/Documents/Blockchain/projects/Hyperledger-Fabric/fabric-samples/fabcar/hfc-key-store
Successfully loaded admin from persistence
Successfully registered user1 - secret:aMgShhReEivm
Successfully enrolled member user "user1"
**User1 was successfully registered** and enrolled and is ready to intreact with the fabric network
Anoops-MacBook:fabcar anoopdixit$
I have modified the project balance transfer to accommodate the role attribute and modified the testAPI.sh file which contains curl call to enroll a new user.
I am trying to follow the documentation at this link:
http://docs.puppetlabs.com/pe/latest/quick_start.html
When I get to the part where one runs ...
sudo puppet agent --test
I get this error message ...
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Error 403 on SERVER: Forbidden request: red-cricket-pe-master (xxx.xxx.xxx.xx) access to /facts/red-cricket-agent [save] authenticated at line 45
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
Thanks
Red
Found my answer here: https://serverfault.com/questions/491623/puppet-enterprise-2-7-error-400-on-server-error-403-on-server-cant-puppet/493085#493085
Looks like you HAVE TO install the console.
Per this post CouchDB in CloudFoundry?, I tried the same thing, but when I run vmc create-service couchdb I get the following error reported in the couchdb_node.log:
[2012-10-01 11:31:47.335301] couchdb_node_0 - pid=22864 tid=dfcc fid=c5c1 INFO -- Creating credentials: ue26fa08a-e8d1-4043-8ba4-71f7d779ce08/pa1cdc5d8-2e92-41ef-b2f1-bdb61b8ce693 for database d73a7c8d1-9b5e-411c-ab92-09f96c7875c2
[2012-10-01 11:31:47.338018] couchdb_node_0 - pid=22864 tid=dfcc fid=c5c1 ERROR -- Failed add user ue26fa08a-e8d1-4043-8ba4-71f7d779ce08: 401 Unauthorized
[2012-10-01 11:31:47.342074] couchdb_node_0 - pid=22864 tid=dfcc fid=c5c1 INFO -- Deleting user ue26fa08a-e8d1-4043-8ba4-71f7d779ce08
[2012-10-01 11:31:47.344598] couchdb_node_0 - pid=22864 tid=dfcc fid=c5c1 ERROR -- Failure deleting user ue26fa08a-e8d1-4043-8ba4-71f7d779ce08: 401 Unauthorized
[2012-10-01 11:31:47.349463] couchdb_node_0 - pid=22864 tid=dfcc fid=c5c1 WARN -- Exception at on_provision 401 Unauthorized: {"error":"unauthorized","reason":"Name or password is incorrect."}\n
On the client side it reports an Error 503. What do I need to do that would allow me to add users? I run CF as root on Linux Ubuntu 10.04.
It was an issue where another version of CouchDB was running in the background. After killing that, I got past this error.