Azerothcore: Looping on Realm Selection List - azerothcore

I've set up Azerothcore for a friend. In attempting to access the server I get stuck at the Realm Selection list.
Worldserver conf extract:
LoginDatabaseInfo = "127.0.0.1;3306;acore;acore;acore_auth"
WorldDatabaseInfo = "127.0.0.1;3306;acore;acore;acore_world"
CharacterDatabaseInfo = "127.0.0.1;3306;acore;acore;acore_characters"
Authserver conf extract:
LoginDatabaseInfo = "127.0.0.1;3306;acore;acore;acore_auth"
SQLDatabase:
acore_auth/realmlist
address: 127.0.0.1
localaddress: 127.0.0.1
port: 8085
I built the same server on my own PC without any issue. I can connect to his server using his external IP and I can log in fine using the account I created in the worldserver console, but when I click on the "Azerothcore" realm listed in the Realm Selection list it briefly says "Logging in to game server" briefly before looping around to the same Realm Selection list.
Any help anyone could offer would be much appreciated. Thanks.
We've both been looking through other similar issues for other emulators but none of the fixes proposed for those apply to Azerothcore.

In the SQL acore_auth database realm list table the external address was still set to 127.0.0.1. Oddly I had absolutely changed this, but it didn't seem to stick, when my friend changed it again, the server worked and performed normally.

I ran in to this issue as well. I finally figured out that heidi initially opens the table in the tables tab, which can't edit persistently. Heidi will appear to do the edit. every time you open the table in heidi it will look edited, but if you open the table in comandline or sql work bench, the Database contains only the default values. The solution is to open the table in heidi then click the "Data" tab. Here, you can perform actual edits.

Related

database not stored on docker-image with shinyproxy

I have developed a solution and decided to use shinyproxy.
I have the following problem:
A user needs to capture data on the solution, which must be stored and updated on the database for all users accessing the solution, I used SQLite and with R for this.
Now when I log in and capture data, it saves, but when i log in with a different user I dont get to find the captured data.
The problem is that saving data doesnt seem to be saving on the docker image, why is this and how can I go about remedying it?
For problem testing purposes:
Solution link: https://xxasdfqexx.com
Data Capturer user:
username: xxxxx
password: Fxxxx
Admin user:
username: inxxx
password: prupxxxxx
Testing:
Inside the solution, if you go to the data management tab, data entry and then right click on an table and insert a new row, click save changes, it must safe new changes to the docker image but its only temporarily doing so, the other user cant see the changes made.
This is expected behavior. The SQLite DB is stored within the running container, not the image. It is therefore lost when the container is shut down. And shinyproxy starts a new container for every user. The general solution with docker is to use an external volume that is mounted into the running container and use that file/directory to store persistent data. Together with shinyproxy, you have to use docker-volumes, c.f.
https://www.shinyproxy.io/configuration/#apps.
Putting this together you can use in the shinyproxy config something like:
apps:
- name: ...
docker-cmd: ...
docker-image: ...
docker-volumes: /some/local/path/:/mnt/persistent
And in the shiny app something like:
dbConnect(RSQLite::SQLite(), "/mnt/persistent/my-db.sqlite")

Firebase Hosting from freenom (dot.tk)

I would like to host my webapp on Firebase, since I'm using their services and functionalities since a long time (before Firebase was inside Google and since its static hosting service was named Divshot... ).
But I've got a demo domain from Freenom (.tk domain) and I was wondering how to connect this with firebase:
I can set only this paramater relative to TXT record:
dns management
so where should I define the parameters needed
google-site-verification=...
?
Thank You to all!
PS: I've already seen
Firebase hosting custom domain error
and related
firebase-talk Dqmz9Iuio54
and
and the question: how-can-i-verify-my-custom-domain-using-domains-google-com/39020649#39020649
but none of them seems to respond to my problem...
PS: I've come here from firebase support page where StackOverflow is the first choice.
Thank you!
Leave the "Name" field blank and fill "Target" with the google-site-verification=... value. Once you've done so, things should go through. One way to check is to run:
dig yourdomain.tk TXT
If you've done it correctly, you should receive back the google-site-verification=... value. It may take some time to propagate before it starts showing up.
DNS registrar / records host: delete TXT records pointing to
firebase.
firebase console: delete the custom domain.
firebase console: add custom domain.
copy the two TXT records from firebase to DNS host
DNS record host should include two entries with one yourdomain.tk and www.yourdomain.tk
Once the yourdomain.tk is added it'll show as empty and other entry will be shown as www.
The copy the two given A records to Freenom DNS records.
There will be 4 A records two for yourdomain.tk and two for www.yourdomain.tk.
Wait 24-48 hours to see if the changes work.
If it doesn't work, contact firebase support from the console; be sure to take screen shots of the DNS records and the firebase console. These will help the firebase support team to troubleshoot the problem.
Mean while you can check for the dns propagation by using below tutorial
The Firebase Hosting servers run what is essentially this command for verifying the TXT records for your domain:
dig -t txt +noall +answer yourdomain.tk
If you immediately run this command right now, you might not get results. If the Firebase servers are seeing the same in their DNS query, they will not be able to continue.
That means that either you didn't save/apply your changes yet, or they haven't propagated everywhere yet. The longer it takes for the changes to show up, the more likely it becomes that you still need to take some action at your DNS provider

Contained database SQL 2012 - and ODBC connection creation failing

Hi Guys Im having trouble understanding how to get around this error
When trying to create a ODCB connection we cant get past the error Error 18470 Login failed for user ####. Reason : The account is disabled.
Of course we have tested that the login to the contained database works through SMSS.
But cant google find anything on how to do a ODBC connection string to work around the .
ODBC is needed for the application that is going to be setup to use the contained databases...
Any suggestions appreciated...
I fixed this because i remembered that often when you create the ODBC connection when setting up a sql account - you can fool the gui - put the details in of the account your trying to use - password - and then simply untick the use this account box – MoOriginal 1 min ago edit
Even though this greys out the box the details are still stored and allow you proceed to the next stages of setup so you can achieve connection by explicitly specifying the database in the next step - cut and paste - then you can go ahead and finally test the connection- this is what i did and this allowed me to create the connection. – MoOriginal just now edit

Databasename is current availability (code: 588)

I am currently working on asp.net application... I have restored a database and tried to establish a connection string on localhost, connection has been established, but when I run the app in a browser it does not give errors it only says,
Databasename is current availability (code: 588)
What does it mean and why i browser don't show me the application interface???
Although I have searched it a lot, I cannot find a solution for this.
Please give us some more information on this.
And the error 588 means the following:
"*You can only perform a full backup of the master database.
Use BACKUP DATABASE to back up the entire master database"
got it from here

ORA-24778: cannot open connections

I am getting the ORA-24778: cannot open connections, what are the possible causes?
We have a number of applications deployed in WAS7 profile and they connect to a number of schemas in Oracle 11g.
One of the schema is connecting through other schema via public DB link.
I cannot identify a solution for this cause.
After restarting the WAS7 profile, it is ok for a while and again start hitting the error.
Pls help!!
I assume you missed to tell us a few details:
You are using XA
You are using XA in combination with database links
You are using shared database links
The ora-24778 is not happening all the time
Either you haven't configured shared server option or you are not connected to a shared server. However Oracle requires you to user shared server if you want to use XA and database links.
Or the parameter OPEN_LINKS_PER_INSTANCE is not set sufficiently. Keep in mind mind that there is also a open_links init.ora parameter. The open_links parameter does not apply to XA.
This error can occur when you invoke a dblink in a existing transaction.

Resources