rabbitMQ guest login failed - authentication

I have setted up rabbitMQ and its management plubin in windows,
I found rabbitmq.config file with "EXAMPLE FILE" type in the path of
" ...AppData\Roaming\RabbitMQ " and " C:\Program Files (x86)\RabbitMQ Server\rabbitmq_server-3.3.1\etc "
I add the line {loopback_users, []} into this rabbitmq.config file, and restart the windows service, but still can't login from another computer with guest/guest
Am I editing the wrong config file?
Here is some relevant discussion:
How to access RabbitMq publicly
http://www.rabbitmq.com/access-control.html

RabbitMQ service can't read the configuration file, this is the problem. So, your configuration file is not loaded.
The path "..AppData\Roaming\RabbitMQ" is valid only if you execute rabbitmq-server.bat from the command prompt and not if you execute a service.
In order to work with Windows Service you have to configure the environment variable RABBITMQ_CONFIG_FILE in windows.
Open Control Panel > System > Advanced > Environment Variables and then add:
RABBITMQ_CONFIG_FILE
path_your_configuration_file
as:
Then you have to uninstall and re-install rabbitmq and it works.
Please read this discussion
I tried on windows7 with rabbitmq 3.3.1, it works corretly using guest/guest.
My configuration file is:
[{, [{loopback_users, []}]}].

A combination of the prior post and the comment from Jon Egerton was key to getting my Windows configuration working for the guest account remotely. Here are steps I took:
Set an environment variable: RABBITMQ_BASE (I set mine to
c:\RabbitMQData)
Create the directory and create the rabbitmq.config file as explained in the previous post.
Uninstall RabbitMQ (As mentioned already, don’t skip this step. Stopping and starting RabbitMQ won’t do the trick)
Reinstall RabbitMQ and verify the RabbitMQ Server service started.
Verify that the directory specified by RABBITMQ_BASE contains the db and log sub-directories.
Install the RabbitMQ_Management plug-in from the command line.
Verify that you can now logon as the guest account using the host’s IP address or host name.

Related

Azure Backup Failed "VM agent is unable to communicate with the Azure Backup Service"

I am receiving a backup failed error since 6/20/2020 within my Azure backup policy.
I also noticed within the Properties section under Settings of the Virtual Machine instance the "Agent status" is in a "Not Ready" state.
When I click the Backup section under Operations the Backup Status shows 2 entries.
Backup Pre-Check Warning
Last backup status Failed
I can click the Warning option and the link takes me to a page that reads:
Issue Description
VM agent is unable to communicate with the Azure Backup Service.
Suggested Action(s)
Ensure that VM agent is latest and running. Allow access to IP 168.63.129.16
Per the Suggested Actions, I created the Outbound Rule to the IP Address 168.63.129.16 within the network interface of the Virtual Machine instance that is having the backup failed issue.
That did not solve the problem. I also performed the below troubleshooting steps as well with no solution:
I also Verified the Windows Azure Guest Agent service is running within services on the affected VM OS (ACMVI002).
Stopped the VM instance from the Azure Portal. I then turned the VM instance back on. Issue persisted.
Does anyone have a solution to this Backup Failed issue?
You probably still don't have access to 168.63.129.16 or your agent is too old, this is a global Microsoft IP used to facilitate a communication channel to Azure platform resources, more details you can read this article.
Azure Backup needs Azure Agent up to date, you can have an old Agent, but depends on how old it is, you can have issue, please refer to this page for more details.
You can try to update your Azure Agent manually, here it is information about it.
From C:\WindowsAzure\Logs\WaAppAgent.txt you see some options to try to identify your issue, version of your Agent appears.
[00000006] [06/25/2020 20:31:00.34] [INFO] WindowsAzureGuestAgent starting. Version 2.7.41491.971
From C:\WindowsAzure\Logs\WaSecAgent-startPoll.txt you see logs from your VM to 168.63.129.16
[2020/06/25 20:31:02:176] Info:WaSecWireServerProxy:: Will start polling for Uri 168.63.129.16 , poll time 900000 ms, running time 21600000 ms
[2020/06/25 20:31:02:176] Verbose:WaSecWireServerProxy:: - WireServerProxy::StartCACertsUpdater
[2020/06/25 20:31:02:176] Info:WaSecWireServerProxy:: Current process is the primary process for polling
[2020/06/25 20:31:02:176] Info:WaSecWireServerProxy:: CA certs polling called for 168.63.129.16, poll interval 900000
[2020/06/25 20:31:02:176] Verbose:WaSecWireServerProxy:: - WireServerProxy::StartCACertsUpdater0x0
[2020/06/25 20:31:02:176] Info:WaSecWireServerProxy:: Starting CA Cert Polling Thread
From the same file C:\WindowsAzure\Logs\WaAppAgent.txt you see logs about RecoveryServices
[00000010] [06/25/2020 20:58:15.54] [INFO] Initialize ExtensionWorkflow for 'FastTrack GS: SeqNo=3'.
[00000009] [06/25/2020 20:58:15.57] [INFO] Plugin Microsoft.Azure.RecoveryServices.VMSnapshot 1.0.65.0 not found in cache.
[00000010] [06/25/2020 20:58:15.57] [INFO] Plug-in Microsoft.EnterpriseCloud.Monitoring.MicrosoftMonitoringAgent 1.0.18038.1 found in cache.
[00000009] [06/25/2020 20:58:15.59] [INFO] Starting download of plugin version manifest Microsoft.Azure.RecoveryServices.VMSnapshot from location: https://zrdfepirv2bl4prdstr03.blob.core.windows.net/80afa74b14194a679c6347109557b7ee/Microsoft.Azure.RecoveryServices_VMSnapshot_useast_manifest.xml
[00000009] [06/25/2020 20:58:15.59] [WARN] Downloading version manifest via HostGAPlugin for plugin Microsoft.Azure.RecoveryServices.VMSnapshot from https://zrdfepirv2bl4prdstr03.blob.core.windows.net/80afa74b14194a679c6347109557b7ee/Microsoft.Azure.RecoveryServices_VMSnapshot_useast_manifest.xml.
[00000010] [06/25/2020 20:58:15.59] [INFO] Test extract the plugin zip file to the temp folder C:\windows\TEMP\b4162b75-fe14-4669-8ed5-e283671cb293
[00000009] [06/25/2020 20:58:15.62] [INFO] Download finished for plugin version manifest Microsoft.Azure.RecoveryServices.VMSnapshot.
Some logs here too
C:\WindowsAzure\Logs\Plugins\Microsoft.Azure.RecoveryServices.VMSnapshot\1.0.65.0
In case anything helped, consider open up a ticket to Microsoft, it could be a issue on Microsoft side that we don't have access to investigate it further.
You would need to re-install the Backup extension. Take a backup of whole registry then use following steps:
Login to the affected machine.
Open Registry Editor.
Remove VMSnapshot registry keys at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Azure\HandlerState
Remove or rename VMSnapshot Plugin Folders at C:\Packages\Plugins.
Now, open command prompt as admin and run below commands to force the extension installation:
REG ADD "HKLM\SOFTWARE\Microsoft\BcdrAgent" /v IsProviderInstalled /t REG_SZ /d False /f
REG ADD "HKLM\SOFTWARE\Microsoft\BcdrAgentPersistentKeys" /v IsCommonProviderInstalled /t REG_SZ /d False /f
Restart the Service "WindowsAzureGuestAgent".
Trigger a manual backup. As a part of backup, extension will be re-installed automatically.

Weblogic server won’t start, because a bad.jar was deployed in it. But I can’t start the admin console, in order to remove the .jar

My Weblogic server was running fine inside my Eclipse. But then I accidentally deployed an .ear into my Weblogic server (using the server's Admin Console) which conflicts with another .ear, and now my Weblogic server won't start up. I know how to remove the .ear. The way to remove it is to go to the Admin Console, choose Deployments, checkmark the offending .ear and then choose stop and delete. But I can't get to the Admin Console because the Weblogic server won't start up.
I want to undeploy it, but I can't, because I can't start up the Admin Console. I also tried undeploying it with the command line, but the command requires communicating with a running server.
The error message in the Eclipse console says: "Failed to initialize the application 'EILoggingSharedLib [LibSpecVersion=2.22,LibImplVersion=2.22]" due to error weblogic.application.library.LibraryDeploymentException: [J2EE:160145]Failed to deploy library Extension-Name: EILoggingSharedLib, Specification-Version: 2.9, Implementation-Version: 2.9, because of conflicting library Manifest values, and library information registered with the server: [Specification-Version: 2.9 vs. 2.22, Implementation-Version: 2.9 vs. 2.22]. Check the library MANIFEST.MF file and correct version information there to match server settings, or undeploy the misconfigured library."
This is the command line command I used:
C:\bea12c\wlserver\server\lib>java -cp weblogic.jar weblogic.Deployer -verbose -noexit -adminurl http://localhost:7016 -username (myusername) -password (mypassword) -name Dev12c -undeploy EILoggingSharedLib -timeout 300
weblogic.Deployer invoked with options: -verbose -noexit -adminurl http://localhost:7016 -username weblogic -name Dev12c -undeploy EILoggingSharedLib -timeout 300
Unexpected Error Initializing Deployer: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 'http://localhost:7016': Destination 0:0:0:0:0:0:0:1, 7016 unreachable; nested exception is:
java.net.ConnectException: Could not connect to /0:0:0:0:0:0:0:1; No available router to destination. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.
I also tried starting the server with startweblogic.sh with the following command, using the same ID and password that I use to log into the admin console (when it was running). But it didn't help:
startweblogic.sh username=(myusername) password=(mypassword)
Thank you!
First, try to remove your application from deployed applications with Eclipse. If it does not work, edit the ${DOMAIN_HOME}/config/config.xml file and remove the declaration of your application. Then start your server.
I found a solution. My Weblogic server that had the problem was at http://localhost:7016. Since it's a localhost server, all the libraries and apps deployed to that localhost are in a directory in my C: drive where my Weblogic server installation is. I deleted the offending .ear using File Explorer, then the Weblogic server started up fine. I was able to go into the Admin Console and delete them again from there. After that, all was good. Thank you, Emmanuel and Wesley.

How to change RabbitMQ node name without changing my hostname

How do I change the RabbitMQ node name without changing my host name?
I am using Windows, and I added these variables:
set RABBITMQ_NODE_PORT=5674
set COMPUTERNAME=192.168.10.1
set RABBITMQ_NODENAME="rabbitmq_%RABBITMQ_NODE_PORT%"
to rabbitmq-server.bat.
In the monitor page, the node name of this Rabbit instance is still rabbitmq_5674#SH-abcde, where this SH-abcde is my COMPUTERNAME. Is it possible to set RabbitMQ node name to rabbit_5672#192.168.10.1
without changing my computer name?
First of all, do not modify the batch files that ship with RabbitMQ. The correct place to set variables is in the %AppData%\RabbitMQ\rabbitmq-env-conf.bat file (where %AppData% is for the administrative user that installed RabbitMQ).
Second, it is not recommended to use an IP address in the node name. Try it if you like, but you may have issues.
So, here is what I recommend if you really wish to have _5672 as part of the node name:
Log in with the same administrative user that installed RabbitMQ
Create the %AppData%\RabbitMQ\rabbitmq-env-conf.bat file with this content:
set NODENAME=rabbitmq_5672#192.168.10.1
Open the "RabbitMQ Command Prompt (sbin dir)" start menu item
Stop RabbitMQ using .\rabbitmq-service.bat stop
Remove the %AppData%\RabbitMQ\mnesia\* directories since they will be based on the previous node name. You will lose messages if any are there.
Uninstall the Windows service: .\rabbitmq-service.bat remove
Re-install the Windows service: .\rabbitmq-service.bat install
Start the Windows service: .\rabbitmq-service.bat start

How to reset WebSphere wasadmin password

I have tried following this tutorial but the new password doesn't take effect after security is enabled again, still have to use old password to login as wasadmin:
http://weblogic-wonders.com/weblogic/2014/03/27/reset-websphere-admin-console-password/
I even tried the guide from IBM:
http://www-01.ibm.com/support/docview.wss?uid=swg21392427
But I'm lost at this step:
_Navigate via command prompt to /ConfigEngine
Because in my WebSphere it doesn't have this ConfigEngine folder in order the run the rest of the commands.
Can anyone help me?
EDIT: This is WebSphere 7 for Maximo 7.5
Have you tried the following?
To disable security, please perform the following steps via wsadmin:
/bin/> wsadmin -conntype NONE
wsadmin> securityoff
wsadmin> exit
Restart the servers.
Enable the security from administrative console.
Once the needed corrections are made, you can re-enable security in the admin console and then restart WebSphere.
NOTE: To restart the servers, you will first need to manually kill the java process since security is still enabled in the currently running process.
Or editing the xml file
Following this link you have 2 optiont:
This is for the standalone version
Make a backup of the security.xml file:
/config/cells/cellname/security.xml
Edit the security.xml file by searching for the first instance of " enabled= ". You should see enabled="true" as in:
Change to enabled="false".
Save the security.xml file.
Restart server1 and the WebSphere_Portal servers. If you get authentication exceptions while trying to stop the servers, you may have to manually kill the server processes and then restart them.
In the wpconfig.properties file, make the following changes:
PortalAdminId=wpsadmin
PortalAdminGroupId=wpsadmins
Refer to the Information Center link for specific instructions.
Save the wpconfig.propeties file.
Try to disable security again using the disable-security task:
./WPSconfig.sh disable-securit y
At this point, security should be disabled. You can verify by accessing the WebSphere Application Server admin console. You should be prompted for only a user name, not a password.
Follow these instructions for a clustered version:
Make a backup of the security.xml file on the Deployment Manager machine:
/config/cells/cellname/security.xml
Edit the security.xml file by searching for the first instance of "enabled= ". You should see enabled="true" as in:
Change to enabled="false".
Save the security.xml file.
Copy the security.xml file to the nodes:
/config/cells/cellname/security.xml
/config/cells/cellname/security.xml
Restart DMGR, NodeAgents, and WebSphere_Portal servers. If you get authentication exceptions while trying to stop the servers, you may have to manually kill the server processes and then restart them.
In wpconfig.properties, make the following changes:
PortalAdminId=wpsadmin
PortalAdminGroupId=wpsadmins
Refer to the Information Center link for specific instructions.
Save the wpconfig.propeties file.
Try to disable security again using the disable-security task. Note that the DMGR and the nodeagent should be running:
./WPSconfig.sh disable-security
At this point, security should be disabled. You can verify by accessing the DMGR AdminConsole. You should be prompted for only a user name, not a password.
Or more option is explained here
Note: I haven't tried this myself yet
Goto DMGR bin directory and follow the below process.
[root#localhost bin]# ./wsadmin.sh -connType NONE -lang jython
wsadmin>AdminTask.changeFileRegistryAccountPassword('-userId saddam -password saddamm')
wsadmin>AdminConfig.save()
Please restart dmgr.
If you have forgotten the password, then you have to directly kill the dmgr process id and start dmgr.
Login to WebSphere Console -> Users and Groups -> Manage Users -> click on <user_name> -> change the password value -> save the configuration.

Why is WLST not recognizing the user/password in the key and config file in connect() call?

I'm trying to connect to an admin server in WLST using config and key files. There are no error messages but I am prompted for a username and password. These files were created (by another developer who is long gone[1]) with the storeUserConfig() command. My call to connect looks something like this: connect(userConfigFile=configFile, userKeyFile=keyFile, url='t3://somehost:7031')).
Is there some restriction in using these files, such as it can only be used on the host where created, or it needs access to the domain's boot.properties file?
Note: I'm trying to connect to an admin server on a different host and non-standard port (e.g. not 7001). The server I am running WLST on and the remote host are the same version of Weblogic.
Some of the things I have tried:
verified that these files appear correct, the key file being binary data and the config file having a line for "weblogic.management.username={AES}..." and "weblogic.management.password={AES}...".
verified that there is a server on the specified port by entering a known login and password that is successful
specified the admin server in the connect parameter
turn on debug(true); the only output is <wlst-debug> connect : Will check if userConfig and userKeyFile should be used to connect to the server and another line giving the path to the userConfig file
turn on Python logging in jython with -Dpython.verbose=debug; nothing relevant to decryption operation
Munging the key or the config files generates no error messages and behaviour as above
[1]: These files are still used today by other existing WLST scripts. However, these scripts are so convoluted and deliberately obfuscated that they are very difficult to reverse-engineer how connect() is being called.
You do not need to access to the domain's boot.properties file. You just need to make sure the configFile and keyFile pointing to the right files. FYI, here is one of the commands we are using:connect(userConfigFile='./user.secure',userKeyFile='./key.secure',url='t3://somehost:7001')
Have you check the network connectity that might be having a firewall in between that troubling you, check the traceroute from the script machine to the Remote machine. Recently I have faced simalar issue. once the routing table updated with allow the WL admin server port everything got set.
Hope this could helps you!
I had this problem too. In a script, I exported the Linux variables userConfigFile and userKeyFile. Then I connected by running:
url='t3://localhost:7002'
userConfigFile='$userConfigFile'
userKeyFile='$userKeyFile'
connect(userConfigFile=$userConfigFile, userKeyFile=#userKeyFile, url=url)
That all worked in a script, but would not work interactively. I changed to doing the following:
url='t3://localhost:7002'
userConfigFile='/users/me/weblogic-2014/weblogic-admin-WebLogicConfig.properties'
userKeyFile='/users/me/weblogic-2014/weblogic-admin-WebLogicKey.properties'
connect(userConfigFile=userConfigFile, userKeyFile=userKeyFile, url=url)
And that worked interactively.