Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I'm attempting to install Bugzilla on a server with a MySQL database on it already. The database is on E: (for space) and Bugzilla is on C:. Currently Bugzilla does not have a database associated with it, and the perl checksetup script looks for a drive local database.
How can I attempt to get bugzilla to target the database on my other drive? Is there a line I can change in the initial scripts to do this?
You tell Bugzilla how to connect to the database server in the localconfig file.
$db_driver = mysql
# The DNS name of the host that the database server runs on.
$db_host = localhost
I believe with MySQL you can also directly connect via a local socket. Be sure to follow the Bugzilla installation instructions for setting up a database, a database user and password for the connection to use. The tables will be set up automatically by Bugzilla's setup scripts.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I need some help understanding how to connect my local machine to a separately hosted database on a different machine.
Context:
I have ssh'd into my host machine (hereafter referred to as VM) and installed MongoDB. The VM runs CentOS and I have no restrictions beyond that.
Goal
My goal is to interact with the VM remotely via my local client on my local machine (Mac), perhaps through some sort of API (direct connection works as well). I'm willing to create that API, but I need to actually establish some sort of contact before that can happen. How can I actually deliver requests from my local machine to the VM, and therefore to my database?
Edit #1:
I should add that this is not exclusive to MongoDB and its host machine. I have several other NoSQL databases (each on their own individual machine). I'm hoping that if I can find a way to make one work, the rest will follow the same pattern.
Answer:
I found out that the firewalls were preventing me from connecting to MongoDB on my remote server. So here is how I finally connected and verified:
Remote Server
Stop the firewall:
systemctl stop firewalld
Start up Mongo:
mongod
Local Client
Form connection using Mongo
mongo REMOTE_IP
or
mongo REMOTE_DOMAIN_NAME
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I have just instally successfully db2 on my linux machine, but I am not able to create a database.
When I make CREATE DATABASE ABC; I get the error that I haven't the authorization to create it...how can I get this authorization?
When you install DB2, you most probably use the root user of the Linux server.
Then in installing phase, you provide a user which will have the SYSADM and DBADM rights. That means DB2 creates a user which has all rights on the database(database admin).
So, after installation, you have to switch to that user to have rights to create a new database.
Depending on the version you installed, that username might be changed. But DB2 uses db2inst1 by default as administrator user.
Check your /home directory. You will see a new user(most probably db2inst1). Then switch to that user with:
su - db2inst1
then issue:
db2 CREATE DATABASE ABC
Let me know if you have a problem, also please provide your /home directory and the error message you get.
You can check details of create db command and related authorization required here on DB2 Info Center:
http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0001941.html?cp=SSEPGG_10.5.0%2F3-5-2-4-21&lang=en
As said above, this should work if you login as instance user. Most of times you do not need root access with DB2.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I'm trying to upgrade my version of PostgreSQL to 9.2 on a Windows Server OS and I keep getting the following error:
An error has occurred:
Error connecting to the server: FATAL: password authentication failed for user "postgres"
How do I make it not do this and actually connect like it is supposed to? I'm using the exact same password from my older installation.
Running the installer via EnterpriseDB prompts you for a password during the initial setup - This password is the postgres users password:
If you do not remember the password, or if you typed it incorrectly during the install(twice!) try these steps:
edit pg_hba.conf to allow trust authorization temporarily
Reload the config file (pg_ctl reload)
Connect and issue ALTER ROLE / PASSWORD to set the new password
edit pg_hba.conf again and restore the previous settings
Reload the config file again
The files will be located in C:\Program Files\PostgreSQL\9.2\data if you installed to the default path.
You can reload the configuration via PhAdmin III by right clicking on the server name and choosing reload configuration or use pg_ctl reload. Barring that restart the service or reboot.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I am trying to connect to my remote postgresql database using pgAdminIII. I am able to connect to the database server via command line using psql client. But when I try to connect using pgAdminIII 1.16, I get the following error :
ERROR: ACL arrays must be one dimensional.
I have checked hba_conf entries. The same entries worked for another database server.
pg_hba is not relevant. ACL arrays are used to store privileges for database objects (database, schema, table, sequence, view, function, and so on).
So the problem is that either:
You have some weird data in one of ACLs
pgAdmin has a bug
Solution would be to:
Enable logging of all queries in remote database (for example: log_statement = all, or log_min_duration_statement = 0)
start pgadmin3, and let it connect, and error out
check in Pg logs what was the last query pgadmin issued, as it is likely the problem was with data from last query
analyze the data using psql connection, and either fix data in db, or report bug in pgadmin
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I've just purchased a new computer (mac OSX) and I want to continue developing using the same database I had on the old computer. I don't want it remotely done cause I dont want to keep the other computer on. I just want to copy the db and put it on this computer for development. I have a USB stick I can use but I'm not sure how to proceed. brew, rails, ruby, rvm, pg are all installed and configured.
pg_dumpall ?
To dump all databases:
$ pg_dumpall > db.out
To reload this database use, for example:
$ psql -f db.out postgres
I had to do it with -o option for the oids